Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CBO June 2024 update #2831

Draft
wants to merge 15 commits into
base: master
Choose a base branch
from
Draft

CBO June 2024 update #2831

wants to merge 15 commits into from

Conversation

bodiyang
Copy link
Contributor

@bodiyang bodiyang commented Nov 4, 2024

This PR is to update Tax-Calculator for the June 2024 CBO baseline update.

This is the next step to the Tax-Data CBO update, which updates Tax-Calculator with the new files of PUF weights, ratios.

Copy link

codecov bot commented Nov 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.42%. Comparing base (95d55d4) to head (ddb5eda).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2831   +/-   ##
=======================================
  Coverage   99.42%   99.42%           
=======================================
  Files          13       13           
  Lines        2616     2616           
=======================================
  Hits         2601     2601           
  Misses         15       15           
Flag Coverage Δ
unittests 99.42% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@martinholmer martinholmer marked this pull request as draft November 4, 2024 20:53
@martinholmer
Copy link
Collaborator

@bodiyang, I have two questions to start with:

(1) If you are updating using the new CBO 2024+ projections, why are the historical results as far back as 2021 changing? Why are you revising HISTORY?

(2) If you are updating using the new CBO 2024+ projections, why are the 2024+ contents
of the growfactors.csv file not changing?

@bodiyang
Copy link
Contributor Author

bodiyang commented Nov 5, 2024

@martinholmer

For (1): It is because CBO themselves revised the baseline value for the previous years in June 2024 publication.

Same can be seen in Tax-data's CBO_baseline.csv. This file shows the baseline difference between June 2024 publication and Feb 2024 publication.

@bodiyang
Copy link
Contributor Author

bodiyang commented Nov 5, 2024

@martinholmer

I'm also having recheck on growth factors now. Will send updates later

@martinholmer
Copy link
Collaborator

martinholmer commented Nov 5, 2024

@bodiyang said in PR #2831:

For (1): It is because CBO themselves revised the baseline value for the previous years in June 2024 publication.

OK. What is the answer to my question (2)?

@bodiyang
Copy link
Contributor Author

bodiyang commented Nov 5, 2024

@martinholmer @jdebacker

There has been a new update from BLS for CPI in September, which will affect the growth factor, baseline, ... files. I will make another update in Tax-Data and incorporate the change in this Tax-Calculator PR.

@martinholmer
Copy link
Collaborator

@bodiyang said:

There has been a new update from BLS for CPI in September, which will affect the growth factor

I don't understand. Are you saying CBO did not change its economic projections in the June report? Why are you planning to change only the CPI projection?

Also, if you change the CPI projection in growfactors.csv, be sure to do this as described in taxdata issue #444.

@bodiyang
Copy link
Contributor Author

bodiyang commented Nov 5, 2024

I don't understand. Are you saying CBO did not change its economic projections in the June report? Why are you planning to change only the CPI projection?

CBO changed its economic projections in the June report and it has already been reflected in this June report.

The "CBO update process" in Tax-Data actually also includes the updates from BLS. details can be found at updatecbo.py

I completed the CBO update process in Tax-Data in August, but I just noticed that BLS has made an update in CPI (which will affect the CPIM in CBO_baseline.csv) in September. So I decide to make an update for this.

And thanks for bringing up the taxdata issue #444 , I will do the update from there.

@martinholmer
Copy link
Collaborator

@bodiyang said:

CBO changed its economic projections in the June report and it has already been reflected in this June report.

This sentence makes no sense to me. When I look at taxdata growfactors.csv it has not changed in eight months even though CBO has new June economic projections. Why are you not using the new June CBO economic projections?

@bodiyang
Copy link
Contributor Author

bodiyang commented Nov 5, 2024

@bodiyang said:

CBO changed its economic projections in the June report and it has already been reflected in this June report.

This sentence makes no sense to me. When I look at taxdata growfactors.csv it has not changed in eight months even though CBO has new June economic projections. Why are you not using the new June CBO economic projections?

  1. Yes, I am using the new CBO June 2024 update
  2. I am currently working on another update in Tax-Data, which will reflect CBO June 2024 update as well as recent BLS update ~ This update will show change in growth factor. I haven't put it up on github yet, but already get it locally.
  3. Last Tax-Data PR: This PR reflect the CBO June 2024, resulting in change of weight files, ratio files ... But it does not result in the change in growth factors. ~~ I didn't conduct a thorough check the reason why growth factor changed there (Maybe the change of baseline is not large enough / or Maybe there is a mistake). However, the update process follow the standard procedure of CBO update, and the produced files passed all tests in Tax-Data & Tax-Calculator. And the projection result looks good, as in this new report.

In a conclusion, I will make another update in Tax-Data with the new changes, including growth factors, soon. Would make sense to wait a lit bit as I'm finalizing it.

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.

2 participants