bloomctl

Command-line tool for the Bloom Database (Salk Harnessing Plants Initiative): log in and access data from Bloom, spanning cylinder experiments, plate scanners and expression data.

1. Install

Releases are still pre-releases (0.1.0aN), so install by asking for the version by name:

uv tool install "bloomctl==0.1.0a8"    # isolated CLI tool (recommended)
uvx bloomctl@0.1.0a8 --help            # one-off, no install
pip install "bloomctl==0.1.0a8"        # into the active environment

Check it worked:

bloomctl --version

Don't add --pre or --prerelease=allow. Those flags aren't specific to bloomctl — they let every dependency install an unfinished dev version too.

2. Log in

Do this once. It asks for your Bloom email and password and saves them to ~/.bloom.

bloomctl login

This logs you in to the Bloom database.

• Browsing and downloading work for any account. Commands marked (needs write access) need an account that has been given write access.

_{Note for Bloom team developers using the CLI with staging: see For developers (Bloom team) below.}

3. Cylinder experiments

In the examples below, we're downloading the experiment with experiment ID 42, named "drought 2024".

Quickstart

# Find an experiment: pick a species from a menu, note its id
bloomctl cyl experiments list --species-menu

# Download it, by id or just by name
bloomctl cyl download ./cyl_output --experiment-id 42
bloomctl cyl download ./cyl_output --experiment-name "drought 2024"

./cyl_output is the output folder: where the files are saved. Pick any name; it is created if it doesn't exist. This writes ./cyl_output/scans.csv (one row per scan) and the per-frame images.

Before a big download

Check what's in the experiment first:

bloomctl cyl accessions list --experiment-id 42          # which accessions are in it
bloomctl cyl accessions sample-counts --species-menu     # plant count per accession, all experiments
bloomctl cyl datasets list --experiment-id 42            # trait datasets already built
bloomctl cyl download ./cyl_output --experiment-id 42 --meta-only   # scans.csv only, no images

Tips

• Speed. Downloads fetch 8 frames at a time. On a fast connection, raise it with --workers 16 (up to 64). If frames start failing because the server is refusing requests, use a lower number, not a higher one.
• If a download stops part-way, run the same command again. It keeps what is already on disk and fetches only what is missing. Use one output folder per selection (an experiment plus any filters).

The download log

Every cyl download writes download_log.txt next to scans.csv: one line per frame and a summary at the bottom. It is the file to send us if something looks wrong.

OK   scan=1 frame=0 cyl-images/0.png
SKIP scan=1 frame=1 cyl-images/1.png
FAIL scan=1 frame=3 cyl-images/3.png  error=ReadTimeout: timed out
UNLISTED scan=5 (frame count unknown)  error=...
NOFRAMES scan=7 (no images recorded for this scan)

Summary: 2/3 frames present (1 downloaded this run, 1 already on disk), 1 failed, 1 scan(s) could not be listed (frames unknown), 1 scan(s) have no images

Watch for UNLISTED. A FAIL is one missing frame, but an UNLISTED scan means we don't know how many of its frames are missing, so they aren't in the "present" count at all. Check the summary's "could not be listed" number, not just "frames present". Re-running picks up both. If the run stopped early (for example, the disk filled up), the summary line ends with the reason.

Cylinder commands

4. Plate experiments

Plate (GraviScan) experiments work the same way, with plate in place of cyl.

In the examples below, we're downloading the plate experiment with experiment ID 12, named "gravitropism". PLATE-001 and wave 3 stand for one plate and one wave in that experiment.

Quickstart

# Download a whole plate experiment, by id or just by name
bloomctl plate download ./plate_output --experiment-id 12
bloomctl plate download ./plate_output --experiment-name "gravitropism" --species Arabidopsis

./plate_output is the output folder: where the files are saved. Pick any name; it is created if it doesn't exist. This writes ./plate_output/plates.csv and plate_sections.csv (metadata) and the plate images.

Download only part of an experiment

bloomctl plate download ./plate_output_plate001 --experiment-id 12 --plate-id PLATE-001   # one plate
bloomctl plate download ./plate_output_wave3    --experiment-id 12 --wave-number 3        # one wave
bloomctl plate download ./plate_output          --experiment-id 12 --meta-only            # csv only, no images

Each selection needs its own output folder. A folder remembers what it holds, so asking for a different selection into it is refused. Re-running the same command in the same folder resumes.

Tips

• Start with --meta-only. A plate session captures one image per plate per cycle, so a multi-day experiment is thousands of files. The metadata shows what you're about to pull.
• --limit N fetches at most N scans, to look at a sample. It isn't a way to export an experiment in parts, so give a sample and a full download separate output folders.
• --workers raises the download speed, as for cylinders.
• Resuming works as for cylinders, and a little better: plate images record their size, so a file cut short by a dropped connection is fetched again instead of being treated as complete.

Plate commands

5. Single-cell data

A single-cell dataset's whole AnnData file (.h5ad) is stored in Bloom, named by the SHA-256 of the uncompressed file, so the same file uploaded twice is stored once.

In the examples below, my_dataset.h5ad is a file on your computer, and "My dataset" is the name of a dataset already in Bloom.

Quickstart

bloomctl scrna hdf5 upload my_dataset.h5ad         # needs write access
bloomctl scrna hdf5 download "My dataset"          # by name, id, or --checksum
bloomctl scrna hdf5 list                           # what storage holds
bloomctl scrna hdf5 list --file my_dataset.h5ad    # is this file already stored?

• upload checks the file's structure before sending anything. If it's interrupted, run the same command again and it resumes.
• download writes the file only once its fingerprint matches.

Single-cell commands

6. Pipelines and containers

These commands are for automated pipelines (stage-in and write-back), not everyday use:

The same CLI is published as a container image. In the example below, path/to/scan.result.json is the result file the pipeline produced for one scan:

docker run --rm ghcr.io/salk-harnessing-plants-initiative/bloomctl:staging \
  cyl ingest-result path/to/scan.result.json

Tags: :staging (latest staging build) · :<version> (matches the PyPI release of the same name) · :sha-<git-sha> (one per commit, never changes). Build details are in the repo docs.

Good to know

• Help on any command: bloomctl <command> --help.
• Machine-readable output: the list commands take --output csv or --output json.
• Choosing a species: --species NAME types it (good for scripts); --species-menu picks from a menu. Use one or the other.
• Menus need a terminal. In a pipe or CI job, menus stop rather than guess. For scripts, pass the id or name directly and use --output json.

For developers (Bloom team)

Staging is for the Bloom team only. To log in to staging, use:

bloomctl login --server https://staging.bloom.salk.edu -p staging

Then add -p staging to each command. Staging has its own accounts; reach out to a Bloom admin to get one.

Documentation

Full docs, with per-command detail and access roles, are in the project repository.