PolicyEngine / PolicyEngine/state-legislative-tracker

Migrate impact computation off split state H5 files

Open
#189 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
0
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Populace US releases are moving to a single national populace_us_2024.h5 plus region scoping, so this repo should stop downloading policyengine-us-data/states/{STATE}.h5 in scripts/compute_impacts.py.

Current references:

  • scripts/compute_impacts.py:get_state_dataset() downloads states/{STATE}.h5 from policyengine/policyengine-us-data.
  • .claude/commands/score-bill.md documents the same state-specific dataset path.

Expected migration:

  • Use the certified national Populace dataset and scope by state_fips / congressional_district_geoid through policyengine.py region scoping, or a shared helper that preserves equivalent semantics.
  • Do not synthesize one-H5-per-state or one-H5-per-district URLs.
  • Keep district calculations based on the national file's congressional_district_geoid support.

Note: the current local checkout has active uncommitted work on add-manifold-markets, so I did not patch it in place.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with get_state_dataset() in scripts/compute_impacts.py and compare its dataset selection with the path documented in .claude/commands/score-bill.md. Trace how policyengine.py applies region scoping, then migrate both references to the certified national dataset while preserving state_fips and congressional_district_geoid calculations. Done means no state- or district-specific H5 URLs remain and district calculations use the national file.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.