Extend US annual static aging to 2036
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown, python
- Domain
- data, documentation
Research direction
The change sits in packages/microcosm-build/src/microcosm/build/us_annual_static_aging.py, at the end_year default near line 209 and the --end-year CLI default near line 462, plus the 2035 mentions in docs/us-annual-static-aging.md. The issue says to wait for PolicyEngine/policyengine.py#524 to land and to leave the change to the maintainer, so do not start until that is merged. Done means the default and CLI end year read 2036 and the doc matches.
Written by the indexing model from the issue text.
Description
Part of the US 2036 extension, tracked in PolicyEngine/policyengine-api#3926. CBO's February 2026 baseline and its 2027–2036 budget window run through 2036, and the canonical SPM forecast now covers 2022–2036 (PolicyEngine/spm-calculator#51). This doesn't block the extension: the annual US projection candidates are used only once PolicyEngine/policyengine.py#524 activates annual US datasets.
@MaxGhenis, when that lands, raise the default end year from 2035 to 2036 in three places:
packages/microcosm-build/src/microcosm/build/us_annual_static_aging.py: theend_year: int = 2035default (line 209) and the--end-yearCLI default (line 462);docs/us-annual-static-aging.md: "2035 by default" and the example command's--end-year 2035.
🤖 Generated with Claude Code
- Dominant language
- Python
- Stars
- 0
- Forks
- 5
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 146
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from PolicyEngine/microcosm
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolicyEngine/microcosm#1220 ·
Maintainers usually reply within 1 day
-
Update two stale comments about the export-mass reviewed-exclusion registerPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PolicyEngine/microcosm#1108 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
PolicyEngine/microcosm#475 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
PolicyEngine/microcosm#1303 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
PolicyEngine/microcosm#1301 ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/microcosm
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolicyEngine/policyengine-us#10262 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
kellyjonbrazil/jc#788 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
`/search.json` ignores the documented `editions.sort` parameterPossibly taken @PranavD2905 claimed this today. OpenAffects: Server Good First Issue Module: Solr Needs: Triage Theme: Public APIs Theme: Search
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
internetarchive/openlibrary#13989 · 1 comment ·
Maintainers usually reply within 1 day
-
bug P2: misleading query
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
jeffknupp/association#478 ·