MPI_COMM_REMOTE_GROUP(3)

🎀 MPI_COMM_REMOTE_GROUP(3) 🎀

okay so this is the Open MPI manual page for MPI_Comm_remote_group, bestie — yes, the MPI_COMM_REMOTE_GROUP(3) girlies are here. 💖

✨ NAME ✨

MPI_Comm_remote_group — accesses the remote group associated with an intercommunicator. no cap, that is literally her whole job. 🦋

✨ SYNTAX ✨

💅 C Syntax 💅

#include <mpi.h>

int MPI_Comm_remote_group(MPI_Comm comm, MPI_Group *group)

🌸 Fortran Syntax 🌸

USE MPI
! or the older form: INCLUDE 'mpif.h'
MPI_COMM_REMOTE_GROUP(COMM, GROUP, IERROR)
     INTEGER COMM, GROUP, IERROR

🦋 Fortran 2008 Syntax 🦋

USE mpi_f08
MPI_Comm_remote_group(comm, group, ierror)
     TYPE(MPI_Comm), INTENT(IN) :: comm
     TYPE(MPI_Group), INTENT(OUT) :: group
     INTEGER, OPTIONAL, INTENT(OUT) :: ierror

💖 INPUT PARAMETER 💖

• comm — Communicator. 💬

🎀 OUTPUT PARAMETERS 🎀

• group — Remote group of communicator. 🫶
• ierror — Fortran only: Error status (integer). 🔢

🦋 DESCRIPTION 🦋

okay so MPI_Comm_remote_group accesses the remote group associated with an intercommunicator. that's the vibe. ✨

the intercommunicator accessors (MPI_Comm_test_inter, MPI_Comm_remote_size, MPI_Comm_remote_group) are all local operations. periodt. 💅

💅 ERRORS 💅

almost all MPI routines return an error value; C routines as the return result of the function and Fortran routines in the last argument. 📬

before the error value is returned, the current MPI error handler associated with the communication object (e.g., communicator, window, file) is called. if no communication object is associated with the MPI call, then the call is considered attached to MPI_COMM_SELF and will call the associated MPI error handler. when MPI_COMM_SELF is not initialized (i.e., before MPI_Init/MPI_Init_thread, after MPI_Finalize, or when using the Sessions Model exclusively) the error raises the initial error handler. the initial error handler can be changed by calling MPI_Comm_set_errhandler on MPI_COMM_SELF when using the World model, or the mpi_initial_errhandler CLI argument to mpiexec or info key to MPI_Comm_spawn/MPI_Comm_spawn_multiple. if no other appropriate error handler has been set, then the MPI_ERRORS_RETURN error handler is called for MPI I/O functions and the MPI_ERRORS_ABORT error handler is called for all other MPI functions. 🫠

Open MPI includes three predefined error handlers that can be used:

• MPI_ERRORS_ARE_FATAL — Causes the program to abort all connected MPI processes. 💀
• MPI_ERRORS_ABORT — An error handler that can be invoked on a communicator, window, file, or session. When called on a communicator, it acts as if MPI_Abort was called on that communicator. If called on a window or file, acts as if MPI_Abort was called on a communicator containing the group of processes in the corresponding window or file. If called on a session, aborts only the local process. 🛑
• MPI_ERRORS_RETURN — Returns an error code to the application. 📨

MPI applications can also implement their own error handlers by calling:

• MPI_Comm_create_errhandler then MPI_Comm_set_errhandler
• MPI_File_create_errhandler then MPI_File_set_errhandler
• MPI_Session_create_errhandler then MPI_Session_set_errhandler or at MPI_Session_init
• MPI_Win_create_errhandler then MPI_Win_set_errhandler

note that MPI does not guarantee that an MPI program can continue past an error. ⚠️

see the MPI man page for a full list of MPI error codes.

see the Error Handling section of the MPI-3.1 standard for more information.

🌈 SEE ALSO 🌈

• MPI_Comm_test_inter
• MPI_Comm_remote_size
• MPI_Intercomm_create
• MPI_Intercomm_merge

👑 COPYRIGHT 👑

2003-2026, The Open MPI Community. 💖

---

💖 cute little sign-off: this is Open MPI, page date Sep 11, 2026, manual page MPI_COMM_REMOTE_GROUP(3). bye bestie! 💖✨