Skip to content

Rollout update - #5

Open
grassesi wants to merge 14 commits into
SavvasMel:developfrom
grassesi:rollout_update
Open

Rollout update#5
grassesi wants to merge 14 commits into
SavvasMel:developfrom
grassesi:rollout_update

Conversation

@grassesi

@grassesi grassesi commented Sep 8, 2026

Copy link
Copy Markdown

Description

Chunked rollout during validation,, make ModelOutput more self-describing

Issue Number

Is this PR a draft? Mark it as draft.

Checklist before asking for review

  • I have performed a self-review of my code
  • My changes comply with basic sanity checks:
    • I have fixed formatting issues with ./scripts/actions.sh lint
    • I have run unit tests with ./scripts/actions.sh unit-test
    • I have documented my code and I have updated the docstrings.
    • I have added unit tests, if relevant
  • I have tried my changes with data and code:
    • I have run the integration tests with ./scripts/actions.sh integration-test
    • (bigger changes) I have run a full training and I have written in the comment the run_id(s): launch-slurm.py --time 60
    • (bigger changes and experiments) I have shared a hegdedoc in the github issue with all the configurations and runs for this experiments

grassesi and others added 14 commits August 11, 2026 10:37
Storing the steps and converting them via chunk_idx/batch_idx lets a partial
rollout be indexed without callers tracking offsets.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The predictors now take the global forecast step and let ModelOutput resolve it,
so they stay correct when the output covers only part of the rollout.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The context manager had been absorbed into the comment above it, so intermediate
rollout steps still built a graph.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sizing the zero arrays from the batch and stream config instead of indexing
preds[0] lets a step that holds no predictions for a stream still be written.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The caller knows which steps its data covers, so the writer no longer has to
reconstruct them from the target count and the offset.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Taking the steps from ModelOutput lets a partial rollout be written, at the cost
of the first chunk emitting empty entries for its leading offset steps.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Collecting the model call and the write in _process_validation_chunks gives the
rollout a single place to be split into chunks.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Each chunk continues from the previous one and is written as it completes; the
predictions themselves are still retained for the loss computation.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant