Lineage
Trace a figure
Follow an experiment figure back through report, analysis, catalog assets, and source files.
Use this workflow when a report or analysis result matters and you need to explain its origin.
Start from the figure
- Open the Project or Experiment that contains the figure.
- Open the figure or report section that embeds it.
- Note the figure name, version, and Experiment context.
For the trametinib demo, start with the dose-response or high-dose apoptosis figure.
Follow the source
- Open the figure context or catalog asset link.
- Inspect linked analysis or notebook information.
- Look for query-log context if the figure was published from the SDK.
- Open reachable catalog assets.
- Continue to source files or parsed tables.
What a good trace tells you
| Question | What to look for |
|---|---|
| Which experiment? | Experiment number, title, project, protocol snapshot. |
| Which data? | Data entries, raw files, parsed tables, sample/run context. |
| Which analysis? | Notebook or analysis artifact, parameters, query log. |
| Which output? | Figure/table name, version, published artifact, report embedding. |
| Which caveats? | Inferred lineage, missing metadata, partial parser status. |
When lineage stops early
If a trace stops earlier than expected, add a note to the Experiment or report. Common causes include standalone uploads without Experiment context or notebook outputs that were not published back into EpistaBase.