Run lineage and groups
Follow how one run leads to another.
Use run lineage to follow a result back to the steps that produced it. For example, connect an evaluation run to the quantization run that produced its input model, so a teammate can find the conversion settings and model file.
Each link identifies a parent run that supplied the input for a later run. Record this relationship in the web app or SDK.
Inspect lineage in the web app#
Open a run’s Lineage tab, or choose Show lineage from its actions in the Runs table. Follow a connected run to inspect an earlier step or later evaluation.
In this example, a training run produces the model used by a quantization run. The evaluation and profile runs both use the quantized model:
Follow either result back to Quantize to find the conversion settings and model file.
Connect existing runs#
Link a run to the parent that supplied its input.
Choose Link runs from the run’s actions, select its parent, and save.
Browse run groups#
A group keeps a selection of runs together. See Model Registry for when to use a group or a model.
Open Runs > Groups and choose a group to inspect its runs, dashboard, and lineage.
Check the source#
A run has one parent and can have multiple children, all in the same project. Check the model identifier, dataset version, settings, and artifacts when following a relationship.
For relationships recorded by your pipeline, see Link runs with the SDK or Decorator tracking.
Next steps#
- Create a model to group related runs.
- Submit evidence to review those results against a requirement.