PolicyEngine / PolicyEngine/policyengine-app-v2
Remove place fallback to split state H5s once Populace supports place scoping
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1
- Forks
- 3
- Avg merge
- 1d 50m
- Merged PRs (30d)
- 39
Description
State and congressional-district repro code can use national Populace scoping, but places still fall back to hf://policyengine/policyengine-us-data/states/{STATE}.h5 in app/src/utils/reproducibilityCode.ts.\n\nA direct switch to national Populace is not safe yet because the current Populace export does not include place_fips, and policyengine.py does not expose a place scoping strategy. Migration target:\n\n1. Add place geography support to the Populace H5, or decide places are metadata-only.\n2. Add policyengine.py place scoping if places should run on national Populace.\n3. Update app-v2 repro code and tests so no examples point at states/*.h5.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with app/src/utils/reproducibilityCode.ts and the current Populace H5 export, then inspect policyengine.py for existing geography scoping. Review the app-v2 repro tests; done means place geography and scoping are supported or explicitly treated as metadata, and no examples point at states/*.h5.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- backend, data, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100