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
@@ -109,7 +109,7 @@ published to. Flows own the namespace; everything else is a client of it.
 | `GET` | `/runs/{id}` | one run in full: params, result, per-node record, artifacts |
 | `POST` | `/runs/{id}/cancel` | stop it |
 | `GET` | `/runs/{id}/metrics?name=&stride=` | one metric's series, in step order; every series of the run without `name` |
-| `GET` | `/runs/series/compare?ids=a,b,c&metric=` | that metric across several runs |
+| `GET` | `/runs/series/compare?ids=a,b,c&metric=&x=` | that metric across several runs. `x` is what to plot against: nothing or `step`, `time` (seconds since each run's own first reading), or another metric's name, joined on the step the two share |

 Submitting answers immediately with a `queued` run. Wrong parameters — an
 undeclared name, a value of the wrong type — come back as a 422 naming the