Warm start adaptive sessions with compatible configurations and observations - #161
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adaptive sessions can queue known mixed/log configurations and import completed observations from compatible sessions or their saved result tables. Imports preserve raw summaries and evaluation identity/provenance, skip repeated evaluations across reopen/intermediate imports, and reject conflicting identities or invalid rows before importing anything.
Session journals now store a versioned factor/objective/constraint/revision schema and reject incompatible definitions. Nonempty legacy journals without that identity require a new journal/study name; they are not silently adopted. Completed observation imports require an explicit caller-managed simulator/scorer/data/fidelity revision, which is an assertion of compatibility rather than an inferred guarantee.
Refs #154. Revision/replicate/fidelity-aware evaluation caching follows separately.
Validation:
just ci; tests cover seeded proposals, queued mixed categorical/discrete/log configs, journal and table persistence, repeated/intermediate imports, schema/revision/weight/constraint mismatch, malformed summaries/provenance, conflicting results, bare tables, and legacy storage.