Add Assertion that carriers exist within eligible sets
Open
Nobody has claimed this yet.
bug
good first issue
- Dominant language
- Python
- Stars
- 148
- Forks
- 55
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
Checklist
- I am using the current
masterbranch - I am running on an up-to-date
pypsa-usaenvironment. Update viaconda env update -f envs/environment.yaml
The Issue
If a user mistakenly places a conventional carrier in StorageUnits, instead of skipping it, we should set a warning that the carrier is not eligible.
Ideally, this happens early in each script, or in snakemake, so that the user gets the feedback immediately
Steps To Reproduce
No response
Expected Behavior
No response
Error Message
No response
Anything else?
No response
Contributor guide
No contributing guide indexed for this repository
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 file, test, or entry point is named. Trace where StorageUnits and carrier eligibility are defined, then inspect the relevant scripts or Snakemake entry point for early validation; done means an ineligible conventional carrier is reported instead of silently skipped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100