Confirm alignment on Sectoral demand for District of Columbia
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 61/100
Research direction
Start by reviewing PR #879 and tracing how sectoral demand data is loaded and assigned to states. Check whether District of Columbia demand is dropped for other sectors, then compare that behavior with hydrogen demand. Done means confirming the existing behavior and making DC demand consistently count toward Maryland.
Written by the indexing model from the issue text.
Description
Version Checks (indicate both or one)
-
This bug exists on the master branch of PyPSA-USA.
-
This bug exists on the develop branch of PyPSA-USA.
The Issue
@WeiAi-Energy introduced hydrogen in PR #879. In this PR, he adds DC demand to Maryland. I think this is a nice way to manage the extra DC demand as we do not account for DC as a separate state. Im pretty sure for the other demands, we just drop DC right now, instead of adding the demand to Maryland.
We should:
- Confirm that DC demand is dropped when adding other sectoral demands (Im 90% sure it is, but this does need a double check)
- Add DC demand to Maryland for consistency
Steps To Reproduce
No response
Error Message
Anything else?
No response
- Dominant language
- Python
- Stars
- 150
- Forks
- 58
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 25
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from PyPSA/pypsa-usa
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
bug question
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Treat corrupt-shape state files as missing in `load_state`Possibly taken @Qrytics claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
OvertureMaps/overturemaps-py#175 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
awslabs/visual-asset-management-system#1278 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aws-samples/sample-per-model-bedrock#835 ·
Maintainers usually reply within 1 day