PolicyEngine / PolicyEngine/policyengine-scorecard
UK counterpart compute pipeline: managed policyengine-uk sims on the certified bundle
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 32
Description
The US side computes counterparts via pipeline/compute_counterparts.py (managed_microsimulation on the certified Populace artifact). The UK side has only ad-hoc campaign runs. Build the standing UK equivalent so UK lanes can move ingested → computed repeatably.
-
pipeline/compute_uk_counterparts.py(or a country-parametrized refactor of the existing pipeline) running policyengine-uk managed sims against the current certifiedpopulace-ukbundle, under the machine-wide sim lock - Promote
countryfrom constant to key across the tidy schema andbuild_comparison.py, per the EUROMOD/UKMOD row indocs/ARCHITECTURE.md - Emit weighted counts only on the PE side; rates/deltas stay derived in one place (
build_comparison.py), matching the US contract - Full provenance per row: engine_version, data_bundle, computed_at, run_id — same fields the campaign JSONL already carries
- Reproducing section in README for the UK path
Depends on the UK harvest ingest path; unblocks DWP take-up, HBAI, HMRC, OBR, UKMOD lanes (#3).
🤖 Generated with Claude Code
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with pipeline/compute_counterparts.py, then read the EUROMOD/UKMOD row in docs/ARCHITECTURE.md and inspect build_comparison.py and the tidy schema. Check the existing campaign JSONL provenance and the certified populace-uk bundle path before running the UK harvest ingest. Done means repeatable locked UK computation, country-keyed comparison rows, complete provenance, and a README reproduction section.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100