feature: resources can be defined by algorithm or problem
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 184
- Forks
- 53
- Avg merge
- 7d 2h
- Merged PRs (30d)
- 1
Description
It would be nice if there was a handy option to define the resources needed by a specific algorithm or problem within the definition of them.
Now you just generate everything and then have to select afterwards what to start with which resources.
Further remark: Sending jobs with different resource demands in different batches might lead to underutilized queues so it would be beneficial to be able to start jobs kind of stratified.
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 issue #44 and trace the existing resource-definition, job-generation, and batch-selection entry points. Clarify with maintainers whether the goal includes stratified starts as well as per-algorithm or per-problem resource definitions. Done means the agreed resource demands can be declared with the relevant definitions and jobs can be selected or started without underutilized queues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- hpc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100