UK dataset sizes: informed L0 and exact-count candidates (#355) - #877
Draft
juaristi22 wants to merge 1 commit into
Draft
UK dataset sizes: informed L0 and exact-count candidates (#355)#877juaristi22 wants to merge 1 commit into
juaristi22 wants to merge 1 commit into
Conversation
10 tasks
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.
The UK rowwise driver currently exports every cloned household. This adds
--dataset-householdsto request a compact candidate after the dense solve, using contribution-informed L0, exact-count sampling, and a frozen-support refit.Stacked on #870 (
uk-rowwise-candidate-762-b) so the diff contains only the size-selection increment. Refs #355 and #665; this does not close #355's certification and default-switch requirements.Behavior
Review boundary
These are candidate artifacts. Size requests refuse
--release-candidateand remain unreleasable until matched comparisons and the promotion scorecard are adjudicated. No dataset registry, production pointer or downstream default changes. Full builds still require the dense build's peak memory and add selection/refit work; savings apply to the exported dataset and downstream use.The prior mapping and inclusion-adjusted stretch reference need measured UK evaluation before release. No licensed full-data build or reform scorecard was run. The implementation plan and operating instructions are in
docs/uk-dataset-size-plan-355.md.Validation