Repository navigation
Compare paired robustness policies within participant groups - #7
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.
Researchers can inspect individual group scenarios, but previously had to combine repeated seeds themselves.
robustness-summarize --groups participants.tsvnow compares policies within each participant group, rate and seed, retaining the same full-target percentile thresholds and common-callable terms.The opt-in group-study schema records memberships, group/source sample counts, per-seed differences, unavailable metrics and explicitly labeled source-cohort reference overlap. The existing whole-cohort schema, numerical summaries, tables and HTML remain unchanged when grouping is omitted. Inputs are rechecked before the completion marker is published.
Validation: 185 Rust tests, the Rust 1.88 CLI regression, formatting and Clippy pass. An independent Python checker passes 168 score-metric and 432 cutoff/reference distribution checks on the completed 128-person public study. The artificial 64-person partitions validate the workflow, not ancestry or demographic effects. The extracted offline example covers a singleton group and rejects an altered seed pair. The candidate archive verifies 57 payloads and 53 local documentation links, passes the extracted examples, and rebuilds byte-identically.
Stacked on #6. No release is tagged or published.