policyengine-us
policyengine-us copied to clipboard
The PolicyEngine US Python package contains a rules engine of the US tax-benefit system, and microdata generation for microsimulation analysis.
We currently lump it in with the infant credit in the first year
Two examples of web app reforms breaking: https://policyengine.org/us/policy?focus=policyOutput.policyBreakdown&reform=77115®ion=enhanced_us&timePeriod=2025&baseline=2&household=47942 https://policyengine.org/us/policy?focus=policyOutput.policyBreakdown&reform=67174®ion=enhanced_us&timePeriod=2025&baseline=2&household=47942
They seem to represent the same value - I dont think both variables are necessary and I am unsure which to use
Currently we use `[person1_val, person2_val]` for yaml tests with multiple people in the household. I think it would be clearer to do: ```yaml - person1_val - person2_val ``` As it...
Minnesota introduced a Renter's Credit in 2024, see https://www.revisor.mn.gov/statutes/cite/290.0693 https://www.revenue.state.mn.us/sites/default/files/2024-12/m1-inst-24_0.pdf (pages 3, 18, 25)
Currently in PR #5575, we had to work around a parameter validation issue in policyengine-core by: 1. Changing to in the age group scale parameter 2. Hardcoding age limit values...
Since we assign take-up in the microdata construction, and reweighting then adjusts them, we can't easily give users control over specific take-up rates. But we could let them toggle full...
Fixes #5535
It's now in pypi
Fixes #5589