Skip to content

feat(eval): mark cells carried forward from a previous run - #44

Merged
jasonodoom merged 1 commit into
mainfrom
feat/mark-carried-forward
Aug 26, 2026
Merged

feat(eval): mark cells carried forward from a previous run#44
jasonodoom merged 1 commit into
mainfrom
feat/mark-carried-forward

Conversation

@jasonodoom

Copy link
Copy Markdown
Contributor

eval-live merges its manifest with whatever is already in the output directory, so a run can be assembled one model at a time. That is deliberate and stays. Doing it invisibly does not: the 17 and 24 August reports listed ten cells when five ran, and nothing in the artifact said so.

Cells present in the output directory but not measured by the invocation are now:

  • named in a warning at generation time
  • recorded in the manifest as carriedForward
  • marked in the report roster as not run in this invocation, with a note that their figures come from samples already on disk

This covers directories with no manifest entry as well, which loadCells aggregates using the directory name. Those previously reached the results table with no roster entry at all.

Regression test drives runLiveEval against a planted stray directory rather than the formatter alone.

Merging an existing manifest supports running one model at a time, and
that stays. Doing it silently does not: the 17 and 24 August reports
listed ten cells when five ran and the artifact said nothing. Carried
cells are now named in the manifest, marked in the report and warned
about at generation time.
@jasonodoom
jasonodoom enabled auto-merge (squash) August 26, 2026 03:08
@jasonodoom
jasonodoom merged commit c8095dc into main Aug 26, 2026
3 checks passed
@jasonodoom
jasonodoom deleted the feat/mark-carried-forward branch August 26, 2026 03:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant