Skip to content

Retain checkpoint evaluation attempts and episode evidence - #40

Draft
PaulHax wants to merge 2 commits into
experiment-recordsfrom
evaluation-capture
Draft

PaulHax wants to merge 2 commits into
experiment-recordsfrom
evaluation-capture

Conversation

@PaulHax

@PaulHax PaulHax commented Oct 27, 2026

Copy link
Copy Markdown
Collaborator

Evaluation results lose the evidence needed to explain retries and gaps

Saved scores alone cannot show which checkpoint and settings were consumed,
whether an execution failed after completing some episodes, or which intended
trials were never launched. Retrying an evaluation must not create an extra
scientific replicate.

Capture one evaluation path and export verified records

Add declaration, execution and export commands for native CybORG checkpoint
evaluation. Retain resolved settings, checkpoint and source identities, completed
episodes, terminal status and explicit retry relationships. Export verifies the
retained evidence and maps it into the records contract from #35. The documentation
hub links the usage guide and explains how capture connects to import and collation.

Training and JAX checkpoint capture remain separate work

This slice evaluates native checkpoints serially. It does not capture training,
resume execution, evaluate JAX checkpoints or provide shared artifact retrieval.

Related: #31. Depends on #35.

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