PyPSA / PyPSA/powerplantmatching
Swap duke with other record linkage solution
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 227
- Forks
- 74
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 4
Description
Describe the feature you'd like to see
The java dependency that duke pulls in seems to make powerplantmatching for especially Windows users difficult to develop and there were discussions whether to try to replace it.
I do not think there is any pressing need, given that the default ppl list is pre-built and can be downloaded w/o java being installed.
BUT: if that was attempted, i'd really like the implementors to consider mismo as an alternative (maybe also after taking a wait and see approach for it to stablize first).
In any case, nick, collected a detailed list of pros and cons for the other more established current recordlinkage solutions: https://nickcrews.github.io/mismo/concepts/goals_and_alternatives/
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
Review how the current Duke dependency is used in powerplantmatching and assess the Windows development impact described in the issue. Read Mismo's linked goals and alternatives, along with the established record-linkage options, before proposing a replacement. Done would require an agreed alternative and a working migration that preserves the project's record-linkage behavior without requiring Java.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, python
- Domain
- data, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100