Add multi-rollout support to giant analyze (gitea #77) #80
Assignees
lars (Lars Bogner)
Clear assignees
lars (Lars Bogner)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: lars/giant#80
Reference in New Issue
Block a user
Delete Branch "fix/issue-77"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
giant analyze compares N rollout YAMLs against one shared reference file
(all must name the same dataset, checked up front) instead of exactly one
rollout vs one reference, rendering each rollout as its own colored series
against a single reference line/panel. Series names come from a repeated
--label flag, else the YAML stem, else "rollout" for a single YAML — a
single-rollout run keeps rendering identically to before this change.
Bundle now holds a name-keyed dict of rollout sides instead of one fixed
pair, every catalog compute_partial/finalize builds a Reduced.payload
keyed the same way ("series": {name: ...}, "reference": ... as the one
distinguished non-rollout entry), and every renderer draws N series (or
N panels, for the two heatmap-shaped specs and the router/type-embedding
diagnostics, which are inherently one-matrix/one-checkpoint per rollout)
against the reference's fixed dashed-ink style.
giant analyze compares N rollout YAMLs against one shared reference file (all must name the same dataset, checked up front) instead of exactly one rollout vs one reference, rendering each rollout as its own colored series against a single reference line/panel. Series names come from a repeated --label flag, else the YAML stem, else "rollout" for a single YAML — a single-rollout run keeps rendering identically to before this change. Bundle now holds a name-keyed dict of rollout sides instead of one fixed pair, every catalog compute_partial/finalize builds a Reduced.payload keyed the same way ("series": {name: ...}, "reference": ... as the one distinguished non-rollout entry), and every renderer draws N series (or N panels, for the two heatmap-shaped specs and the router/type-embedding diagnostics, which are inherently one-matrix/one-checkpoint per rollout) against the reference's fixed dashed-ink style.