Update to CBO January 2020 economic projections and extend data to 2030 #331
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates TaxData to use the latest CBO economic projections. The general steps I took were:
puf_data/StatMatch/runmatch.py
after addingasec2016_pubuse_v3.dat
to the repoMake all
A few notes:
updatecbo.py
does not successfully retrieve the CG data. I got around this by manually updating the CG data inCBO_baseline.csv
, but we might want to address this issue in a future PR.Make all
, the new weights files did not successfully overwrite the old files. To get this process to work, I had to delete*_weights.csv.gz
before runningMake all
.puf_stage2/stage2.py
line 68 so thatstage3.py
is able to read the file.benefit_growth_rates.csv
should be the same as 2027-2029. If this continues to be the case for future years, we should consider adding a note toCBO_Baseline_Updating_Instructions.md
cc @MattHJensen @andersonfrailey