Repository navigation
Check robustness inputs before long scoring runs - #8
Draft
DylanCosto wants to merge 1 commit into
Draft
DylanCosto wants to merge 1 commit into
DylanCosto wants to merge 1 commit into
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
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.
A robustness experiment could previously finish earlier scores before discovering that a later pack did not match the genotype extraction. All pack/source compatibility checks now run before scoring output is created. Preparation also fingerprints inputs before opening them and verifies those fingerprints afterward.
robustness --preflightuses the shared preparation checks and writes a separate input-check report with target/model/scenario counts, structural row bounds, selected reference members, shared target IDs, model inventories and provenance. It never emits score tables or an experiment completion event. Genotype/frequency data blocks remain lazy, so the report explicitly does not claim scoring success, common-callable coverage, runtime or memory estimates. Truncated and oversized frequency headers now return errors instead of panicking.Validation: 187 Rust tests, the Rust 1.88 preflight CLI regression, formatting and Clippy pass. Tests cover a later incompatible pack, unavailable sample IDs, malformed frequency headers, output preservation, count overflow and the deliberate lazy-block limit. Preflight matches the completed 128-person study's fingerprints and 5,376-row inventories; the 1,745,179-term eight-person pilot preserves prior scores, attribution and reference results. The archive verifies 58 payload hashes and 54 documentation links, passes its extracted offline examples, and rebuilds byte-identically.
Stacked on #7. No release tag or publication is included.