MatterMiners / MatterMiners/lapis
Consistent definition of simulation modi
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Once we actually merge the `feature/caching` and `master` branch we need to come up with a consistent way of defining and documenting for which kind of user input caching effects are simulated (propably when storage objects are defined), how jobs with input file information should be treated when no storage objects are defined (use file transfer mechanism like with caching but only with remote connection?) and whether we want a command line flag that allows to disable caching on the fly.
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 comparing the feature/caching and master branches, then review how storage objects and jobs with input-file information are currently represented. Resolve when caching effects are simulated, how jobs behave without storage objects, and whether a command-line switch is needed; done means these behaviors and their documentation are consistently defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100