Browse and analyze runs
Use the web app to find runs, inspect processed results, claim attribution, download files, comment, and manage run lifecycle.
After instruments are uploading, the web app is where you find runs and act on them: inspect results, claim work, download files, and leave lab notes. The sections below follow the order you’ll use them in.
Orient yourself in the app
The sidebar and the home page are the two starting points for daily work.
Home lists recent runs across instruments, most recent first, with counts for today and this week at the top. Filter by date range, who ran it, and instrument-specific metadata when it’s available, then page through results.
Instruments in the sidebar opens each instrument’s page. That page’s runs table adds column filters that match the instrument type (for example wavelengths on a plate reader).
My runs lists runs you’ve claimed, so you can return to your own work without re-filtering the full dashboard.
Narrow a long run list
Home and the instrument pages share the same four controls:
- Search runs: filters the list by run name as you type
- Date range: presets from Today through Last 4 weeks, plus a custom range
- Add filter: filter by run status, or turn on Show deleted runs
- Column headers: sort by size, by who ran it, or by any instrument-specific column
What each run status means
A run’s status tells you how far its files have got from the instrument to the dashboard:
| Status | Meaning |
|---|---|
| Pending upload | The watcher found the files but hasn’t sent them yet. |
| Uploaded | The files are in storage. Processing hasn’t started, or this instrument type has no processor. |
| Processing | The server is reading the files, extracting metadata, and building reports. |
| Completed | Processing finished. |
| Failed | Processing stopped on an error. |
| Empty | The run has no files. |
Search the workspace
Press ⌘ K (macOS) or Ctrl K (Windows/Linux) to open global search from any page. Results are grouped into runs, files, instruments, users, and comments. That means you can also look up a colleague’s work or the text of a lab note. A file hit opens the parent run with the files table already filtered to that file.
Open a run and inspect results
Each run has a details page at /instruments/your_instrument_id/runs/your_run_id. The arrows beside the run name step you to the next or previous run without going back to the list.
What you see depends on the instrument type and whether a processor ran:
- Metadata badges for extracted fields
- Processed reports such as tables, images, or PDFs, including interactive plate maps for plate readers
- A files table of everything in the run, labeled Raw or Processed, with each file’s size and status
Reports with many images, PDFs, or spectra show one item at a time. Search by filename to jump anywhere in the run, or use the arrows to step through it. The counter beside the arrows shows your position out of the total.
Per-type inputs and outputs are in Instrument data preprocessing.
Claim who ran it
Use Claim on the run details page to attribute yourself. You can claim or unclaim your own user only, so nobody else can attribute a run to you. Claims show on the run and appear in “ran by” filters on Home and elsewhere.
Download files
From the files table you can:
- Download a single file, which opens a temporary download link
- Choose Download all to build a zip of active files in the run, with any active file filters applied
Large zips build in the background. When one isn’t ready yet, Data Hub tells you how long to wait before trying again.
Act on several runs at once
Select the checkbox on any run row to open an action bar at the bottom of the list:
- I ran these: claim every selected run in one step
- Remove my attribution: unclaim them
- Download: download the files from the selected runs
- Reprocess: run server-side processing again for all of them
- Delete: mark the selected runs deleted
The checkbox in the header row selects every run on the page, and Clear drops the selection.
Comment on a run
The comments thread on run details is for lab notes and follow-ups. Comment activity can notify people who claimed the run or already commented. Set preferences under Settings → Notifications; see Configure notifications.
Reprocess or delete a run
After a failed process, or after an engineer fixes the code that reads a file type, use Reprocess on a file or the whole run (where available) to run server-side processing again. The row menu in a run list reprocesses a whole run without opening it.
Delete marks the run deleted without removing stored files. Admins and operators can restore it from the same page when that control is shown. To find a deleted run again, turn on Show deleted runs under Add filter.
For instruments in manual upload mode, detected files may also show upload or dismiss actions while the watcher waits for approval. See Manage the watcher fleet.
Use the same data outside the UI
You can also list and fetch the same runs and files over the REST API or the Model Context Protocol (MCP) endpoint. REST needs a personal access token; scopes and creation are covered in Issue and revoke tokens. MCP clients sign in through the browser instead.