|
MPI_Intercomm_create_from_groups — Creates a new inter-communicator from a local and remote group and stringtag SYNTAXC Syntax#include <mpi.h> int MPI_Intercomm_create_from_groups(MPI_Group local_group, int local_leader, MPI_Group remote_group, int remote_leader, const char *stringtag, MPI_Info info, MPI_Errhandler errhandler, MPI_Comm *newintercomm) Fortran SyntaxUSE MPI ! or the older form: INCLUDE 'mpif.h' MPI_INTERCOMM_CREATE_FROM_GROUPS(LOCAL_GROUP, LOCAL_LEADER, REMOTE_GROUP, REMOTE_LEADER, STRINGTAG, INFO, ERRHANDLER, NEWINTERCOMM, IERROR) Fortran 2008 SyntaxUSE mpi_f08 MPI_Intercomm_create_from_groups(local_group, local_leader, remote_group, remote_leader, stringtag, info, errhandler, newintercomm, ierror) INPUT PARAMETERS
OUTPUT PARAMETERS
DESCRIPTIONMPI_Intercomm_create_from_groups creates an inter-communicator. Unlike MPI_Intercomm_create, this function uses as input previously defined, disjoint local and remote groups. The calling MPI process must be a member of the local group. The call is collective over the union of the local and remote groups. All involved MPI processes shall provide an identical value for the stringtag argument. Within each group, all MPI processes shall provide identical local_group, local_leader arguments. Wildcards are not permitted for the remote_leader or local_leader arguments. The stringtag argument serves the same purpose as the stringtag used in the MPI_Comm_create_from_group function; it differentiates concurrent calls in a multithreaded environment. The stringtag shall not exceed MPI_MAX_STRINGTAG_LEN characters in length. For C, this includes space for a null terminating character. In the event that MPI_GROUP_EMPTY is supplied as the local_group or remote_group1 or both, then the call is a local operation and MPI_COMM_NULL is returned as the newintercomm. NOTESThe errhandler argument specifies an error handler to be attached to the new inter-communicator. The info argument provides hints and assertions, possibly MPI implementation dependent, which indicate desired characteristics and guide communicator creation. MPI_MAX_STRINGTAG_LEN shall have a value of at least 63. ERRORSAlmost 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 applications can also implement their own error handlers by calling:
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_create_from_group
COPYRIGHT2003-2025, The Open MPI Community
|