Skip to content

Raise the US annual static-aging default end year to 2036 - #1337

Open
buzztouniverse wants to merge 1 commit into
PolicyEngine:mainfrom
buzztouniverse:us-annual-static-aging-2036
Open

buzztouniverse wants to merge 1 commit into
PolicyEngine:mainfrom
buzztouniverse:us-annual-static-aging-2036

Conversation

@buzztouniverse

Copy link
Copy Markdown

Closes #1280.

Raises the default end year of the US annual static-aging candidate builder from 2035 to 2036 in the places listed in the issue:

  • the end_year default of build_annual_static_aging
  • the --end-year CLI default
  • docs/us-annual-static-aging.md (the "by default" note and the example command)

Also adds a changelog.d fragment.

Opened as a draft since the issue says this should go in once PolicyEngine/policyengine.py#524 activates annual US datasets. PolicyEngine/spm-calculator#51 (SPM forecast through 2036) is also still open.

Testing: ruff check and ruff format --check pass. The tests in tests/engine_workflow/us/test_us_annual_static_aging.py pass an explicit end_year, so they don't depend on the default. I didn't run the US engine suite locally and am relying on CI for that

CBO's February 2026 baseline runs its budget window through 2036 and the
SPM forecast now covers 2022-2036, so the annual candidate builder should
project through 2036 by default. Updates the function default, the
--end-year CLI default and the docs.

Closes PolicyEngine#1280

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Extend US annual static aging to 2036

1 participant