You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Plots are generated ad hoc. The result is inconsistent sizing, colour that means different things in different figures, and small text in exactly the figures carrying the most detail — the system architecture and the generated-versus-ground-truth comparisons. Several plots also overlap heavily in what they show, adding length without adding information.
Proposal
One theme module setting figure size, DPI, and font sizes suitable for print.
A colourblind-safe categorical palette with colours pinned per strategy, so colour carries the same meaning in every figure.
Vector export for any figure containing small text.
Audit the figure set: merge or drop near-duplicates, keeping a plot only where it answers a question no other plot answers.
Regenerate the architecture diagram at a legible size, or split it into two levels of detail.
Done when:
All figures produced through the styling module
Strategy colours consistent set-wide and legible in greyscale
Figure inventory documents the question each plot answers
Is the architecture diagram better maintained as code-generated output or as a hand-drawn asset checked into the repo? The first stays in sync; the second usually reads better.
Motivation
Plots are generated ad hoc. The result is inconsistent sizing, colour that means different things in different figures, and small text in exactly the figures carrying the most detail — the system architecture and the generated-versus-ground-truth comparisons. Several plots also overlap heavily in what they show, adding length without adding information.
Proposal
Done when:
Scope
Open questions
Related