Scroll the runs table, pick a range, and choose what a comparison plots against

2026-08-25 16:32:34 +02:00
parent 3c15964364
commit 4350916bd8
14 changed files with 498 additions and 151 deletions
@@ -295,9 +295,16 @@ flow, by status, or down to one sweep. A sweep is worth filtering to — the
 table then draws a column per parameter that actually varied, which is what
 makes fifty runs of one flow readable.

-Tick two or more and their curves go side by side. That comparison is the
+Tick two or more and their curves go side by side — shift-click to take a
+range, or the header box to take everything on screen. That comparison is the
 address, so a link to it is a link someone else can open.

+The curves are drawn against the step by default. They can also be drawn
+against elapsed seconds, which answers "which one got there sooner" and is
+measured from each run's own first reading so that runs started hours apart
+still lie on top of each other; or against another metric of the same runs —
+an epoch, or samples seen — joined on the step the two share.
+
 One run in full is params, the per-node record with its logs and traceback,
 the artifacts it made, its metrics and its result.