PolicyEngine / PolicyEngine/microcosm

Carry educational attainment as an auxiliary variable (imputation predictor + ACS-calibratable margin)

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

Nobody has claimed this yet.

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

Description

Proposal

Carry educational attainment (ASEC A_HGA, collapsed to a small class set, e.g. the SCF's four edcl classes) on the populace-us support spine as an auxiliary variable: not a rules-engine input, but a conditioning variable for imputation and a calibratable margin.

Why

  1. Imputation quality. Attainment is among the strongest available predictors of income and wealth conditionals. Standard multiple-imputation guidance is to include strong auxiliaries in the imputation model even when no downstream analysis consumes them — the joint quality of the variables we do care about depends on conditioning richness. The imputation-paper experiments (github.com/PolicyEngine/imputation-paper) had to drop education from the SCF↔CPS shared predictor set and its absence visibly weakens the conditional signal; its "populace-scale" experiment adds it back from raw ASEC and measures the effect.
  2. Calibration surface. ACS publishes attainment margins by age and state (S1501), so the variable is not just a predictor: it is a target family for the local-area program, cheap to add to the Ledger lane.
  3. Cost is low. A_HGA ships in every ASEC vintage the spine pools; the mapping to a 4-class attainment variable is a few lines in unit construction.

Scope note

Flag it in provenance as auxiliary (carried for conditioning/calibration, not consumed by rules), so nobody reads its presence as a tax-benefit modeling claim. Related: #253 (tuition expenses) is about a rules input and is orthogonal — this issue is about attainment as a conditioning/calibration variable.

🤖 Generated with Claude Code

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 locating unit construction, provenance handling, and the Ledger lane for the populace-us support spine. Trace ASEC A_HGA into the proposed four-class attainment variable, then verify that it is carried for imputation and ACS calibration while marked auxiliary and excluded from rules-engine inputs.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data, machine-learning
Issue type
Feature
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.