Watch a recorded Run in the real GUI.
Pick a scenario and open its replay. It is the Traceome GUI itself, reading a finished Run. Drag the replay slider along the bottom (wide screens) and you see only what was on the record at that moment: the stage, the questions the researcher was asked, and each answer with its evidence.
The demo Run
-
#457 human report, older layout The demo Run · #457 · earlier build A human genome, 29 targets, from raw reads to the reportHG001, a public human reference sample, and a request of 24 rsIDs, BRAF V600E and other targets. Merged IDs are followed, a gene-change name is placed, and the researcher amends two coordinates. 33 Work items: 18 observed, 8 not carried, 7 no VCF record.
2026-10-29 · build
d3f3c340· nvidia/Nemotron-3.5-Super-VL · HG001 ·457-human-20261029T084406Z-d3f3c340-a1A Run of an earlier build, shown as it originally ran, with its original report layout. The link opens at the report.
How to try it
No account, key or install is needed. The first load can take about 30 seconds while the server starts.
- Open the demo Run above. It opens at the Run's report: 29 targets, 27 searched in the sample's own variant file, 20 with the target allele called R21.
- Find rs4149056: HG001 carries one copy of the C version, not the A version. Find the GRCh37 APOE position and BRAF V600E: placed, no variant call, so "genotype not established", never "not carried". Find rs9999999999: unresolved, nothing invented.
- Open Findings and click a target to see the VCF records behind its answer.
- Drag the replay slider along the bottom (wide screens): the GUI shows only what was on the record at that moment, including each approval and what it does not establish.
- Open the Journey panel: every model call, tool call, approval and file, recorded once.
The replay is view-only: it cannot start Runs or spend money. Live sessions on request. Run it yourself from the code.
The latest Runs
Recorded development Runs, shown as they are, newest first. Each card names its build; only the first is on the final build.
-
Live, captured 2026-10-30 15:16 UTC during Execution, while the reference index is placed Final live Run · paper From a paper citation to a report, on the final buildThe Mullins 2020 APOE paper and an HG002 human sample: the Run finds and reads the paper, takes the reads from Object Storage, measures its health and writes the new report.
2026-10-30 · build
32b72b74e· nvidia/Nemotron-3.5-Super-VL · HG002 (about 1×) ·4-mfinal-mullins-20261030T141805Z-32b72b74-a1Still running when this page was written: Execution places the prebuilt reference index (about an hour), then the H100 job runs. No post-Run review yet. At about 1× depth, genotypes are not expected to be established.
-
Run S report, older layout Run S · smoke Run health and coverage, from staged readsA C. elegans sample read straight from Object Storage with a prebuilt reference index. The Run measures itself: 97.6% of reads mapped, depth 17.1, and each target's own depth.
2026-10-30 · build
028a063a7· nvidia/Nemotron-3.5-Super-VL · SRR7145496 (C. elegans; identity unresolved) ·4-msmoke-celegans-20261030T132733Z-028a063a-a1Older report layout. One wording defect on its page ("the paper researcher") was fixed in the final build. Biological correctness of this sample is unresolved R13
-
No GUI served for this RunRun M · paper The first full paper Run
Mullins 2020 + HG002, before the last fixes: the paper found from a bare citation, three variants read from it, and a report with a "What papers found" section.
2026-10-30 · build
a3cd32a23· nvidia/Nemotron-3.5-Super-VL · HG002 (about 1×) ·4-mlive-mullins-20261030T095056Z-a3cd32a2-a1Older report layout. Each paper target is labelled by its whole paragraph, and table passages name the wrong section.
Earlier scenarios
-
Run Q (#141), Qwen comparison baseline Run Q · #141 The whole pipelineOne question about 24 DNA variants, from raw reads to a checked report.
2026-10-18 · Qwen/Qwen3.5-397B-A17B (comparison baseline) · HG001, a public human reference sample ·
141-full-20261018T095210Z-5b06c210-a2Run Q used the Qwen comparison model, not Nemotron. Run H used NVIDIA Nemotron on the same reads; its 29 Work items equal Run Q's item for item R5
-
Screenshot comes with the replay
-
Screenshot comes with the replayFork · #437 Skip the GPU: fork a finished Run
Start again after the GPU step: planning, approval and GPU time skipped, 29/29 answers the same.
HG001 ·
437-fork-8d30b415-a1 -
Screenshot comes with the replay
-
Screenshot comes with the replayRun C · #387 A worm genome, and an open question
Four positions in a C. elegans sample: no VCF record at any of them, and the sample's identity is still in question.
2026-10-22 · nvidia/Nemotron-3.5-Super-VL · SRR7145496 (C. elegans; identity unresolved) ·
387-celegans-a2-20261022T193856Z-59c33dda-a1Biological correctness is unresolved: metadata, run alias and BAM disagree on which line this sample is R13
What you will see in Run Q
Screens from the Run Q replay, at the moments the How it works page describes.
Replay versus live
| This demo (replay) | A live Run | |
|---|---|---|
| What it shows | the Traceome GUI reading the retained Journey of a finished development Run | a new Run as it happens |
| Models and GPU | no new Run is started | Nemotron on Token Factory, Parabricks on a Nebius H100 |
| Keys | none needed | the operator's own Nebius credentials |
| Where | a hosted replay, opened from this page | the GUI or the CLI underneath it (Code) R18; live sessions on request |
Live sessions on request
A live Run needs models, a GPU and credentials, so it is not open to the public. Ask us for a session.