-
Notifications
You must be signed in to change notification settings - Fork 30
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
Why would n24 exceed nu18? #157
Comments
@MaxGhenis, I don't have a specific answer for you right now, but I do know we can do a better job calculating n24 in general. I'm wrapping up a few other things right now, but when I finish I'll work on a fix for how we count n24. |
Now that #131 is resolved,
#164 (including 17-year-olds) explains some of this. |
Updating the notebook for taxcalc 0.19.0, where
|
@MaxGhenis said in taxdata issue #157:
@andersonfrailey, Why would the CPS values for n24 and nu18 be inconsistent? |
I can think of a couple of reasons why First, in our scripts, any dependent filers who are under 18 would be counted for Second, I can change the SAS scripts so that |
@andersonfrailey to clarify, this is about Sorry to see this request move logic from Python to SAS. Is a long-term goal to move everything out of SAS? FWIW I'm not too personally concerned with this issue given the totals look OK, in case waiting to move logic to Python is an option. |
Yes, I'm working on moving everything from SAS to Python ASAP. That is the next big milestone for this repo. |
My understanding of the Child Tax Credit's definition of child is that it should be a subset of children under age 18. One criterion is being under age 17, and others limit further within that.
2014 CPS data shows that
n24
andnu18
have almost identical totals: 78.7M and 78.8M, respectively. Yetn24
exceedsnu18
for 9M tax units, 19% of all tax units wheren24>0
(notebook). These 9M tax units have 15M totaln24
and 1.3M totalnu18
Is there a reason I'm missing here, like different residency requirements? If not, should
n24
be capped atnu18
?NB: this will become a slightly starker issue after #131 is resolved.
The text was updated successfully, but these errors were encountered: