-
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
Various age fields include end points when names and documentation indicate otherwise #164
Comments
A process tweak that could help avoid this is to use exclusively either |
@andersonfrailey, |
I'll put together a PR to address these issues today. In the PUF |
@MaxGhenis, where in the documentation did you see |
From https://github.com/open-source-economics/taxdata/blob/master/cps_data/cps_file_doc.md |
@MaxGhenis, Thanks for pointing out these bugs in the generation of the CPS age variables. |
Documentation and variable name structure for various age fields indicate they should not include the end point. I see four contradictions in the code on this front:
nu05
includes 5-year-olds based on the finalprep.py code.nu13
includes 13-year-olds based on the finalprep.py codeelderly_dependent
is described as "over 65 years old" in the documentation, but includes 65-year-olds based on the finalprep.py code. As an aside, it would be helpful if the user documentation specified the age threshold for this variable.n24
has a related issue: only children under age 17 are eligible for the CTC, but finalprep.py includes 17-year-olds inn24
.n24
aside, I'm not sure if these are used elsewhere, and how that affects whether the variable names or the logic should be changed.Relevant links:
The text was updated successfully, but these errors were encountered: