Materials-Consortia / Materials-Consortia/optimade-python-tools
Consider adjusting client to be provider-parallel rather than database-parallel
Open
Nobody has claimed this yet.
client
- Dominant language
- Python
- Stars
- 91
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
This will be equivalent in 99% of cases, but will help providers that serve multiple OPTIMADE databases from the same "physical" database.
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
The issue names no files, tests, or entry points. Start by locating the client code that controls parallelism and review how providers and OPTIMADE databases are represented; the desired provider-parallel behavior and its completion criteria need to be defined before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100