Leave a dotted key out of the runs export header

_leaves named a column for a key like `-1.0` that _dig can never read back, so the export showed an always-empty column. Skip such a key.
2026-09-16 16:43:52 +02:00
parent d4f0345e97
commit 02907bbe27
3 changed files with 13 additions and 1 deletions
@@ -134,7 +134,8 @@ the inputs that *vary* across the selection in `param.` columns (the sweep
 axis) unless `?params=` names them, and the run's numbers in `metric.`
 columns. Both are dotted paths into whatever a node returned, so
 `?metrics=final_metrics.train_loss` selects a field of a record and the
-defaults reach every number inside one. The run id is on every row of both, which is what makes an exported
+defaults reach every number inside one. A key with a dot in its own name, such
+as `-1.0`, cannot be addressed that way and gets no column. The run id is on every row of both, which is what makes an exported
 file a join back to the run rather than a loose table.

 `compare` answers in the same shape a chart widget draws, so three training