-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add 2023 examination data from CBO, TSY, and JCT #10
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Martin- but do we need to have these as .text and .awk files? It'd be more manageable if everything was a CSV (or even JSON/YAML).
@nikhilwoodruff asked in PR #10:
Why would it "be more manageable? The .txt files are not rectangular, so CSV-format is not a good choice. |
Not sure I follow really. The data seems rectangular to me, or at least we could make it so. And there's a script already doing the interpolation in shell language- why is Python much more complicated? |
@nikhilwoodruff said:
So, you have not answered my question:
And @nikhilwoodruff also said:
What shell language and which script? |
Yes, well my thinking is that CSV files are easiest to manipulate/show in documentation/pull into programs across all languages in this project, and especially Python. Second to that, consistency probably helps us, so if everything is CSV/Python that'd be the easiest combination and avoid having to build logic to parse text files, or copy the values. |
Sorry- was referring to the AWK script. |
@nikhilwoodruff, I changed the spaced-delimited text files to CSV files so that they "are easie[r] to manipulate/show in documentation/pull into programs across all languages in this project." |
Add FY data from CBO, TSY, and JCT, that can be converted to CY 2023 amounts, against which microdata estimates will be compared in the examination phase of the project.