Merging models with the same elements
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.2k
- Forks
- 699
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 13
Description
Describe the feature you'd like to see
https://docs.pypsa.org/v0.35.1/api/_source/pypsa.Network.merge.html
The current merge function requires component lists to be disjunct, however I believe a significant number of cases to require merging of networks where the component list might overlap. It would be helpful to have an argument that implements merge logic that ignores identical elements (e.g. typical with carriers)
This logic may have strict standards for combining elements (only when all parameters are equal) or we could allow one network to have "priority" where the parameters of elements with the same name are made equal to the parameters in n1 (the "priority" network)
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
Start with the Network.merge API documentation at docs.pypsa.org/v0.35.1/api/_source/pypsa.Network.merge.html and inspect the current merge behavior. Before implementation, clarify whether identical overlapping elements only should be accepted or whether a priority network is intended; done means the chosen behavior is documented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100