PolicyEngine / PolicyEngine/imputation-paper

Carve-out: harness formalization moves to the popdgp methods paper; this paper becomes the fill dossier + first application

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

Nobody has claimed this yet.

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

Description

Decision

The portfolio review (2026-07-03) promotes the population-view harness from a section of this paper to its own methods paper + package: popdgp (Survey Methodology / JOS target). This paper stays the fill operator's dossier and the harness's first application.

Changes here

  1. Trim the harness formalization (methodology §"The population-view harness") to a working summary + citation of the popdgp paper (in prep); keep everything needed to read the results tables.
  2. Keep all experiments and results as-is — both harness profiles, the tail block, floors. The application is this paper's evidence; only the framework's general formalization moves.
  3. Code extraction (coordinate with popdgp's extraction issue): experiments/views.py and the joint/tail metrics migrate to the popdgp package; this repo then depends on popdgp (pinned) and keeps only task-specific wiring. Behavior-preserving — regenerated tables must be bit-identical.
  4. Background §"Evaluating imputed files": the formal-ancestry paragraph (Lohr–Raghunathan, Rässler, proper scoring, PRDC) largely moves to the popdgp paper; keep two sentences + citation.
  5. Update the contributions list: contribution 2 becomes "first application of the population-view harness (popdgp)" rather than the framework itself.

Sequencing: this paper submits first (IJM); the popdgp paper cites it as the first application — the standard application/methods split, no cannibalization.

🤖 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 reading the methodology section “The population-view harness,” the “Evaluating imputed files” background, and experiments/views.py. Coordinate with popdgp’s extraction issue, then trim the formalization, update the contributions list, preserve task-specific wiring, and verify regenerated tables are bit-identical.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data, documentation
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.