PolicyEngine / PolicyEngine/policyengine-sim-api
Identify data version numbers for all v1 and v2 runs
Open
Nobody has claimed this yet.
v1-v2-testing
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 10h 29m
- Merged PRs (30d)
- 7
Description
- UK-data and US-data should, when uploading to HF or GCS, overwrite a json file with the repo's commit hash.
- V1 should return in the economy output this commit hash
- V2 should also
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the UK-data and US-data upload paths for Hugging Face and GCS, then trace how V1 and V2 produce economy output. Done means uploads overwrite a JSON file with the repository commit hash and both versioned outputs return that hash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100