PolicyEngine / PolicyEngine/microcosm

Harmonize archived-model ACS predictors at pool assembly (end state for the release-side join)

Open
#800 0 comments 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

End-state decision recorded from the ACS-predictor work (weeksgate report, "Owner rulings required"; interim fix = release-side join from the sha-pinned ACS zips, PR to follow from branch acs-predictor-release-join): the archived release-stage donor models' CPS-named predictors (PEDIS*, PRDTRACE, PRDTHSP, PEIOOCC, POCCU2, SPM_TENMORTSTATUS) should ultimately be harmonized at POOL ASSEMBLY from native ACS variables (DEAR/DEYE/DREM/DPHY/DDRS/DOUT, RAC1P, HISP, OCCP, TEN), so the pool itself carries complete predictors and the release-side join can be deleted. Assembly-stage change invalidates the checkpoint chain from assembly, so this rides the next cold pool rebuild (the parsimony candidate's build is the natural vehicle) rather than forcing a ~15h rebuild of the current candidate.

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 the pool assembly entry point and the release-side join described in the issue, then inspect how the native ACS variables and archived donor-model predictors are handled. The change is complete when the pool carries the listed harmonized predictors and the release-side join can be removed; validate it through the next cold pool rebuild rather than rebuilding the current candidate.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-engineering
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.