Use national Populace scoping for place repro code#1078
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This reverts commit a764e04.
|
Cycle review found a blocker: default US place regions cannot be safely moved to national Populace scoping yet because the current Populace H5 has state_fips and congressional_district_geoid, but no place_fips, and policyengine.py place regions currently have no scoping_strategy. I pushed a revert of this PR's place change. App-v2 main already handles default state and congressional-district regions through Populace region scoping from #1077; this PR should not be merged unless/until Populace emits place_fips and policyengine.py adds place scoping. |
|
Closing after cycle review: the only remaining change attempted to move default place regions to national Populace scoping, but the current Populace H5 does not include place_fips and policyengine.py place regions have no scoping strategy yet. State and congressional-district default repro paths are already handled on main by #1077. |
Summary
place/regionspolicyengine-us-data/states/NJ.h5This complements PolicyEngine/populace#237, which removes state and congressional-district H5 artifacts from US releases so consumers rely on the single national Populace file plus region scoping.
Verification
bun run vitest src/tests/unit/utils/reproducibilityCode.test.tsbunx prettier --check app/src/utils/reproducibilityCode.ts app/src/tests/unit/utils/reproducibilityCode.test.tsbun run eslint src/utils/reproducibilityCode.ts src/tests/unit/utils/reproducibilityCode.test.ts