Perfect foresight incompatible with transmission losses
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 615
- Forks
- 459
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 6
Description
Atm the perfect foresight code is not compatible with the reversed column in n.links. The easiest solution would actually be to support the reversed column in pypsa itself. Otherwise, the default is nan which infers with consistent dtype assignment expected by the IO.
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
Start by tracing the perfect foresight handling and how the n.links reversed column is passed into PyPSA. Check the dtype and IO behavior around that column. Done means perfect foresight supports transmission losses with reversed links and consistent dtype assignment.
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
- Mostly clear
- Newbie friendliness
- 35/100