Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ACS local release: real-data verification checklist for the first build of the #1019–#1023 stack

Open
#1,093 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
python

Research direction

Start by rebuilding staging, then run the materialize → calibrate → finalize → package pipeline on real data. Work through the checklist across the ACS local-lane stack, including memory, SNAP/TANF, immigration, work, disability, income, SSI, units, vehicles, and reviewed fills; done means every listed verification has results before a local release is published.

Written by the indexing model from the issue text.

Description

What

The ACS local-lane stack (#1051 → #1052 → #1054 → #1055 → #1056 → #1058 → #1060 → #1061 → #1062 → #1064 → #1071) is tested only on synthetic frames. The reviews asked for several checks on real data before any local release is published. This issue collects them in one place so none gets lost.

Prerequisites:

  • Rebuild staging. Every stage's method id changed, so the release tool refuses older staging.
  • Then run materialize → calibrate → finalize → package.

Checklist

Memory and run

  • Peak RSS and runtime of materialize, including the SSI/Medicaid engine pre-pass over donor and ACS households. The earlier peak was 74.8 GB under a 77.3 GB limit (#1060).

SNAP and TANF take-up (#1051, #1062)

  • Modeled SNAP take-up among eligible units, by state and by household type, compared with the FNS participation rates. Do this before describing take-up as calibrated.
  • The overlap between the transferred receives_tanf and the TANF take-up draw.
  • The weighted share of housing units with FS == 1, against 12.2% from the 2023 ACS.
  • How often FS == 1 housing units have several SPM units.
  • How often the reference-unit fallback is used, and its benefit sensitivity.
  • The SNAP × TANF cross-tab on ACS units against the donor spine.

Immigration (#1052)

  • Pooled delivered counts of the worker and student statuses against the national controls.
  • The composition of the residual status, and the downstream eligibility split.
  • Sensitivity of years_since_us_entry to the lag between arrival and qualified status.

Work and disability (#1054, #1055)

  • The ACS weeks-worked distribution and the staging gate.
  • The changed disability distribution.
  • Blank and invalid HINS3 counts, and the Medicare share at 65+.
  • The distribution of the discretionary-exemption draw. It is a cap-based proxy, not an observed exemption.

Income and SSI (#1056, #1058, #1060)

  • The distributions of the nine locally transferred income leaves.
  • Reproduce the OIP and aligned-RETP holdout gains on real data.
  • Predictor distributions and the transferred financial inputs for the SSI criteria model.
  • ACS shares meeting the SSI disability criteria, by age.
  • Final pooled SSI recipients by age band and Medicaid enrollment by state, against the SSA and CMS counts.
  • HINS4 excess and thinning by state.

Units and vehicles (#1061, #1064)

  • The prevalence of each RELSHIPP 36 case, and the sensitivity block on real data.
  • Benefit sensitivity of the SPM partition rule.
  • The share of roommates moved into their own unit who have no shelter cost, and the SNAP effect.
  • County-aid overstatement from the zero owned vehicle count and value.
  • Head Start take-up among eligible children aged 3–5, compared with the donor.

Reviewed fills (#1071)

  • The affected population weight for each known_bias fill.

🤖 Generated with Claude Code

Dominant language
Python
Stars
0
Forks
5
Avg merge
1d 10h
Merged PRs (30d)
129

Getting set up

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.

More from PolicyEngine/microcosm

All issues in PolicyEngine/microcosm

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.