PolicyEngine / PolicyEngine/policyengine-api
Compute top-level net income impacts (for decile chart) independently of deciles
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 33
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 22
Description
Currently these are averaged across deciles, which results in some reforms having different directional impacts between relative and absolute, e.g. this.
Let's instead compute these as total aggregates, i.e.
- Absolute = total change to net income in £/$ divided by number of households
- Relative = absolute / total baseline net income
Then we should change the client to read:
- [Reform] would {increase, decrease} total net income by $x per household
- [Reform] would {increase, decrease} total net income by y%
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 by tracing the decileAverageImpact calculation in the API and the corresponding client text, using the linked policy example as a reference. Done means absolute and relative impacts use total aggregates rather than decile averages, and the client displays the requested per-household dollar and percentage wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100