Closed donboyd5 closed 1 month ago
@donboyd5, Has issue #20 (from early March) been resolved? If so, you should close #20. If not, please add to issue #20 that explaining what else needs to be done.
On July 16, @martinholmer asked this about issue #20:
@donboyd5, Has issue https://github.com/PSLmodels/tax-microdata-benchmarking/issues/20 (from early March) been resolved? If so, you should close https://github.com/PSLmodels/tax-microdata-benchmarking/issues/20. If not, please add to issue https://github.com/PSLmodels/tax-microdata-benchmarking/issues/20 that explaining what else needs to be done.
There has been no additions to issue #20 since July 16, so it is being closed.
@martinholmer Thanks for closing. Once we have a contract in place I'll open a new issue with planned steps for states and CDs.
@donboyd5 said in closed issue #20:
Once we have a contract in place I'll open a new issue with planned steps for states and CDs.
Please make the issues action-oriented so that merging a pull request will close the issue. Any commentary that is not immediately action-oriented should be put in a GitHub Discussion.
Sounds good.
Sent from my phone; please excuse brevity and speech-to-text errors.
On Sat, Sep 21, 2024, 2:22 PM Martin Holmer @.***> wrote:
@donboyd5 https://github.com/donboyd5 said in closed issue #20 https://github.com/PSLmodels/tax-microdata-benchmarking/issues/20:
Once we have a contract in place I'll open a new issue with planned steps for states and CDs.
Please make the issues action-oriented so that merging a pull request will close the issue. Any commentary that is not immediately action-oriented should be put in a GitHub Discussion.
— Reply to this email directly, view it on GitHub https://github.com/PSLmodels/tax-microdata-benchmarking/issues/20#issuecomment-2365277511, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABR4JGG6LDU67XEXBXI54J3ZXW2OFAVCNFSM6AAAAABEDCAAQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRVGI3TONJRGE . You are receiving this because you were mentioned.Message ID: @.***>
@nikhilwoodruff @martinholmer
I wrote code in R to:
The code is written to minimize the risk of error inherent in extracting bits and pieces from different sections of multiple spreadsheets, and to make it easy and low-risk-of-error to add more targets from individual spreadsheets or to add additional IRS spreadsheets.
The data can be used to create summary and distributional targets for PUF variables for tax filers. The data are a superset of variables we'll want for targeting. Hence I call them "potential" targets. In early stages, we'll only target a small number of values. Later, we may target many more, but still not target everything that is in the csv file.
I expect that eventually we'll translate the potential-targets-getting code to python, although that may occur after Phase 3 of the project. The csv file (after review) may be all we need in Phases 2 and 3. Alternatively, we could move the R project into the PSL project.