evaluate comm_world
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 108
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
We need to re-evaluate SCR's use of MPI_COMM_WORLD. If we were to move away from this, we must be explicit about our assumptions from applications.
For example, do we expect .scr metadata on each node? Does SCR assume it has an MPI task on each node?
Tagging @white238 for tracking
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 by auditing SCR's use of MPI_COMM_WORLD and documenting the application assumptions it relies on. Resolve whether .scr metadata is expected on each node and whether SCR assumes an MPI task per node; done means these assumptions are explicit and any resulting work is scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100