Update agent docs away from split state/district H5 datasets
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- documentation
Research direction
Read the three named SKILL.md files and the standard region/scoping machinery in policyengine.py, then search the repository for split state and district H5 URIs. Update the documented paths to use the certified Populace default dataset, add or update regression coverage for state and congressional-district runs, and verify that no active docs or app paths depend on split regional H5 files.
Written by the indexing model from the issue text.
Description
PolicyEngine/populace#237 removed release generation for one-file-per-state and one-file-per-district artifacts. The replacement path is the single certified Populace national H5 plus the standard region/scoping machinery in policyengine.py, not direct hf://policyengine/policyengine-us-data/states/... or districts/... files.
GitHub code search still finds split-H5 references in this repo:
skills/tools-and-apis/policyengine-microsimulation-skill/SKILL.mdskills/analysis/policyengine-district-analysis-skill/SKILL.mdskills/domain-knowledge/policyengine-healthcare-skill/SKILL.md
Migration checklist:
- Stop constructing or documenting
policyengine-us-data/states/*.h5andpolicyengine-us-data/districts/*.h5dataset URIs. - Use the certified Populace default dataset through policyengine.py, with region filters/scoping for state and congressional-district analyses.
- Add or update a regression test so future state/CD runs do not depend on split regional H5 files.
- Keep historical/generated output unchanged unless it is actively used by the app or docs.
- Dominant language
- Python
- Stars
- 32
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from PolicyEngine/policyengine-claude
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
18 skills/commands still reference old Microsimulation API instead of policyengine.py SimulationOpen
Difficulty 3/5 1-2 days Newbie friendliness 55/100
All issues in PolicyEngine/policyengine-claude
Similar issues
-
[Bug]: Streamed /v1/chat/completions sends unredacted agent error text (keys) in the final chunkPossibly taken @rodricksz4h5 claimed this today. Openarea/streaming comp/gateway P2 type/security
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#138245 ·
Maintainers usually reply within 1 day
-
[oblt-aw][autodoc] Update user onboarding guide for mandatory trigger CODEOWNERS stepPossibly taken @github-actions claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
correction metadata
Difficulty 2/5 Under an hour Newbie friendliness 68/100
acl-org/acl-anthology#10378 · 1 comment ·
Maintainers usually reply within 1 day
-
cloudtrail_multi_region_enabled_logging_management_events fails when the advanced event selector has a custom namePossibly taken @12YYCCYY16 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
prowler-cloud/prowler#13033 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
graygarbage/HermesKey#23 ·