Read US scenario inputs at the benchmark year (TAX_YEAR)#60
Open
MaxGhenis wants to merge 1 commit into
Open
Conversation
load_enhanced_cps_person_frame read promptable inputs at the Enhanced CPS dataset's native period (sim.default_input_period, e.g. 2024) while scenarios are built and scored at TAX_YEAR (2026). PolicyEngine uprates monetary inputs across periods, so benchmark incomes sat several percent below their 2026 level and out of step with the population weights, which are computed at TAX_YEAR. The UK loader already reads at TAX_YEAR; this makes the US path consistent. The dataset's native period is still returned as dataset_year for provenance (the enhanced_cps_<year> artifact label). Reference outputs must be regenerated for this to take effect in a published run. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What
load_enhanced_cps_person_frameread promptable US inputs at the Enhanced CPS dataset's native period (sim.default_input_period, e.g. 2024), while scenarios are built and scored atTAX_YEAR(2026). PolicyEngine uprates monetary inputs across periods, so benchmark incomes sat ~9% below their 2026 level — and out of step with the population weights, which are computed atTAX_YEAR. This reads US inputs atTAX_YEAR, matching the UK loader (which already does).The dataset's native period is still returned as
dataset_yearfor provenance (theenhanced_cps_<year>artifact label); only the calculation period changes.Impact
This shifts benchmark household incomes to their 2026-representative level. Reference outputs (and the published snapshot) must be regenerated for it to take effect in a run — so this rides with the in-progress microdata refresh.
Verification
TAX_YEARwhiledataset_yearstill reports the dataset period.uv sync --locked): 280 passed.🤖 Generated with Claude Code