PolicyEngine / PolicyEngine/microcosm

US certified default undercounts households (122.5M) and overcounts married couples (81.5M): no household-type or marital-status targets in the registry

Open
#880 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
0
Forks
4
Avg merge
1d 3h
Merged PRs (30d)
94

Description

Summary

The certified US default (populace-us-2024-buildp-sparse-rmloss100-cae8640-20260728, HF blob 48b9d479…) matches person-level population targets but carries too few households and too many married couples. The target registry (5,659 targets, all household entity) has no household-count, family-structure, or marital-status targets, so calibration meets person-by-age targets with fewer, larger, married households.

Found while counting married one-earner families with a child under 13 for the HHS "parent-based child care" draft rule (Sept 2026); the Microcosm count came out 37% above the raw ASEC on the same definition.

Benchmark cells (same code over each file; marital unit = 2 adults; SPM-unit children)

Cell Raw CPS ASEC 2024 (Census weights) Old enhanced CPS 2024 Microcosm Build P sparse External benchmark
Persons 326.0M 334.8M 340.1M PEP 2024 ≈ 340.1M
Households (weight sum) 135.0M 153.8M 122.5M Census CPS ≈ 131M
Married couples (2-adult marital units) 65.6M 57.3M 81.5M married-couple households ≈ 47% of households ≈ 62M
Married couples with a child <18 in SPM unit 25.8M 20.8M 29.7M BLS 2025 Table 4 (own children <18): 22.7M
Married couples with a child <13 in SPM unit 20.1M 16.3M 22.2M
Children <18 68.8M 71.9M 76.7M ≈ 72–73M
Adults working 35+ h (annualized) 137.5M 129.9M 138.1M

Persons per household: Microcosm 2.78 vs ASEC 2.41.

Weight behaviour is otherwise much better than the old enhanced CPS (top-1% household weight share 11% vs 56%; realized max weight ratio 5.0), so this is a target-surface gap, not a weight-concentration problem.

Proposed targets (Chronicle-named, household entity)

  • Census CPS/ASEC households by type: total households; married-couple family households; other family; nonfamily (Table HH-1 / F-1 series), national and by state where published (ACS B11001).
  • BLS "Employment Characteristics of Families" Table 4: married-couple families with own children <18 (22.7M, 2025 release), by parents' employment (both employed 15.0M; one parent employed 7.1M).
  • Census/ACS children by presence of parents (living with two married parents), so child-age targets are not met by concentrating children in married households.

Repro

Scripts and outputs: ~/PolicyEngine/_drafts/vance-ccdf-parent-based-care/benchmark_cells.md and newly_eligible_count_microcosm.md (numpy over the h5 entity tables, no engine run). BLS Table 4: https://www.bls.gov/news.release/famee.t04.htm. Census household type: https://www.census.gov/topics/families/families-and-households.html.

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 by reading ~/PolicyEngine/_drafts/vance-ccdf-parent-based-care/benchmark_cells.md and newly_eligible_count_microcosm.md, then inspect how the target registry represents household entities and calibration targets. Use the cited Census and BLS sources to define the proposed household-type, marital-status, and parent-employment targets. Done means the registry includes the selected targets and the benchmark cells no longer show the reported household and married-couple distortions.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.