Appearance
Runs & Lineage
Runs tells you what happened. Lineage helps you remember how you got there: the parent run, the checkpoint you started from, the change you tried, and the outcome you kept.
Inspect runs
Open Experiments in the sidebar for the model’s runs. Select a run to inspect its configuration, status, metric history, and recorded artifacts or evaluations.
Check up to three runs to overlay their metric curves on shared step axes. For a detailed pairwise comparison, select exactly two and choose Compare selected runs.
klars shows only metrics and relationships reported to the service. An empty plot means no matching points have been logged; it is not a measurement of zero.
Follow Lineage
Choose Lineage in the model toolbar or Checkpoint lineage in the sidebar. The view connects runs, captures, checkpoints, and recorded revisions where relationships exist.
Select a node to inspect its evidence record. Move between Graph, Diff, and Lineage to inspect the same model from different angles. Your Lineage selection is restored when you return if that object still exists.
A run’s record explains:
| Part | What it means |
|---|---|
| from | The reported parent run or source checkpoint. |
| tried | Configuration changes from the parent. A root run lists its configuration. |
| why | Your recorded experiment reason, result, and decision. |
| after | Descendants and runs forked from this one. |
Record what you learned
In the selected run’s review form, enter the reason for the experiment and an outcome note. Choose a logged metric and whether lower or higher is better.
klars takes that metric’s last value by step when you save. You cannot type an outcome value, and the saved outcome does not silently follow later points.
Choose Undecided, kept, discarded, or chosen, and add tags if useful. Save records the review. Undo returns the form to its saved values. If saving fails, your edits remain so you can retry.
Open projects on Lineage
Enable Open models on Lineage in Settings or the Lineage options menu if experiment history is your preferred starting point. The default is to open the graph.
Learn how to report parent and capture links, or compare runs and captures.