Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix to the Collective Chapter for the rank/process/group/file/win/communicator nomenclature #448

Closed
tonyskjellum opened this issue Feb 23, 2021 · 2 comments
Closed

Fix to the Collective Chapter for the rank/process/group/file/win/communicator nomenclature #448

tonyskjellum opened this issue Feb 23, 2021 · 2 comments
Assignees
@tonyskjellum
Labels
chap-collective Collective Communication Chapter Committee mpi-5 For inclusion in the MPI 5.0 standard
Projects
MPI 4.1

Comments

@tonyskjellum
Copy link

Problem

Terminology requires that "rank" and "process rank" and "task" be eliminated in favor of new, canonical nomenclature that always scopes the process to have a rank w.r.t. a group of a communicator, group, or underlying group of a file, window, or communicator.

Proposal

The Forum agrees the nomenclature must be updated as proposed

Changes to the Text

Naming of processes is always with regard to ranks related to the underlying object, not as an absolute.

Impact on Implementations

None.

Impact on Users

The user community gets better nomenclature and the standard improves considerably.

References and Pull Requests

TBD.
@tonyskjellum tonyskjellum changed the title Fix to the Collective Chapter for the rank/process/group/file/communicator nomenclature Fix to the Collective Chapter for the rank/process/group/file/win/communicator nomenclature Feb 23, 2021
@tonyskjellum
Copy link
Author

Latest PDF:

mpi40-report-PR541-f1c78b3-23feb21.pdf

@tonyskjellum tonyskjellum self-assigned this Feb 23, 2021
@tonyskjellum tonyskjellum added the chap-collective Collective Communication Chapter Committee label Feb 23, 2021
@wesbland wesbland added this to Triage in MPI 4.0 Ratification via automation Feb 24, 2021
@wesbland wesbland moved this from Triage to In Progress in MPI 4.0 Ratification Feb 24, 2021
@tonyskjellum tonyskjellum mentioned this issue Feb 24, 2021
Closed
@schulzm schulzm added mpi-4.1 For inclusion in the MPI 4.1 standard and removed mpi-4.0 labels Mar 22, 2021
@wesbland wesbland removed this from In Progress in MPI 4.0 Ratification Mar 23, 2021
@wesbland wesbland added this to To Do in MPI 4.1 Jun 9, 2021
@wesbland
Copy link
Member

wesbland commented Dec 8, 2022

This wasn't read at the December 2022 meeting. The last opportunity for MPI 4.1 is to have it ready at the March 2022 meeting (and it needs to "pass" the reading).

@tonyskjellum Are you (or is someone else) planning to push this forward or should we move it out of the plan for MPI 4.1?

@wesbland wesbland added mpi-5 For inclusion in the MPI 5.0 standard and removed mpi-4.1 For inclusion in the MPI 4.1 standard labels May 3, 2023
@wgropp wgropp closed this as completed Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tonyskjellum tonyskjellum

Labels
chap-collective Collective Communication Chapter Committee mpi-5 For inclusion in the MPI 5.0 standard
Projects
MPI 5.0
Status: Merged
MPI 4.1
To Do
Milestone
No milestone
Development

No branches or pull requests
3 participants
@schulzm @tonyskjellum @wesbland