Can we separate `referencedata` to a different package?
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 10
- Forks
- 4
- Avg merge
- 12h 31m
- Merged PRs (30d)
- 13
Description
I would love to use the elastic properties in elaston, but I don’t really need the rest of atomistics there. Can we maybe think about separating it into a different module in pyiron?
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 how referencedata is currently organized within atomistics and how its elastic properties are consumed by elaston. Clarify the intended package boundary and the required consumer changes; the work is done when the separation plan is agreed and both packages can use the needed functionality without the unwanted dependency.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100