Publish complete ACS-local WIC participation and remove the temporary .py assumption
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with the generator and validation changes described in the prepared drafts, then review the existing WIC generator and unit, small H5, and country-engine workflow tests. The checklist also requires a separate dataset owner to rebuild, validate, publish, and certify a replacement release before compatibility removal; code changes alone are not completion. Done means the release is certified and the ACS True-fill exception is removed.
Written by the indexing model from the issue text.
Description
Problem
The certified local-area release populace-us-2024-buildo-acs-local-767312d60-20260923T074941Z stores donor WIC participation under would_claim_wic, but its ACS person records have no generated participation decisions. The current US model consumes takes_up_wic_if_eligible. The wrapper's strict old-name mapping therefore refuses the incomplete ACS column.
PolicyEngine/policyengine.py#560 temporarily sets only missing, explicitly identified ACS decisions to True: every eligible affected ACS person claims WIC. Existing decisions and model eligibility remain unchanged. This is a disclosed temporary modelling assumption, not generated or observed participation.
Related: #1026 (renamed WIC input); #1031 (release rejection of obsolete stored input names).
Prepared code changes
- Temporary
.pycompatibility draft: https://github.com/PolicyEngine/policyengine.py/pull/566 - Separate
.pyremoval draft: https://github.com/PolicyEngine/policyengine.py/pull/563 — blocked until the replacement is actually published and certified. - Microcosm code-repair draft: #1156 (fixes the narrowly scoped code issue #1155, not this parent issue).
Generation/validation changes and focused unit/H5/country-engine tests are implemented in those drafts. No full dataset rebuild, publication, or replacement certification has been performed.
Completion checklist
- Merge the Microcosm repair: run the existing source-backed WIC generator after ACS demographic inputs are populated and before combining populations; preserve donor decisions.
- Require complete valid current-name participation before calculation/export and reject default filling missing WIC decisions.
- Add unit and small H5/country-engine workflow tests.
- Separate dataset owner: choose a qualified donor with complete current-name participation; rebuild ACS-local inputs and affected calculation/calibration outputs, without reusing pre-fix calculations.
- Separate dataset owner: pass all existing release checks, record generation provenance, and publish a new immutable local-area release, including its revision and hashes. Do not overwrite the old release or change the national default/latest pointer.
- Certify that actual replacement release in the separately opened policyengine.py removal PR; preserve the national dataset and verify preparation against the replacement.
- Merge removal of the ACS
True-fill exception. Keep ordinary old-name mapping while other certified datasets require it.
Boundaries
The code implementation does not rebuild, calibrate or publish the full dataset, launch paid compute, or deploy API services. Rebuilding/publication is performed by another owner. Passing code PR checks does not certify a dataset. Do not close this issue on code-PR merge; it remains open until publication, certification and compatibility removal are complete.
- Dominant language
- Python
- Stars
- 0
- Forks
- 5
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 144
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/microcosm
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolicyEngine/microcosm#1220 ·
Maintainers usually reply within 1 day
-
Update two stale comments about the export-mass reviewed-exclusion registerPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PolicyEngine/microcosm#1108 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
PolicyEngine/microcosm#475 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
PolicyEngine/microcosm#1303 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
PolicyEngine/microcosm#1301 ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/microcosm
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
collective/icalendar#1968 · 1 comment ·
Maintainers usually reply within 1 day
-
Deferred from #1869: Complete the companion pytest guardrail update noted in the PR description...Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#140958 ·
Maintainers usually reply within 1 day
-
Bug triage/confirmed
Difficulty 2/5 Half a day Newbie friendliness 85/100
agentscope-ai/agentscope#3355 ·
Maintainers usually reply within 2 days