|
MPI_Scan, MPI_Iscan, MPI_Scan_init - Computes an inclusive scan (partial reduction) SYNTAXC Syntax#include <mpi.h> int MPI_Scan(const void *sendbuf, void *recvbuf, int count, Fortran SyntaxUSE MPI ! or the older form: INCLUDE 'mpif.h' MPI_SCAN(SENDBUF, RECVBUF, COUNT, DATATYPE, OP, COMM, IERROR) Fortran 2008 SyntaxUSE mpi_f08 MPI_Scan(sendbuf, recvbuf, count, datatype, op, comm, ierror) INPUT PARAMETERS
OUTPUT PARAMETERS
DESCRIPTIONMPI_Scan is used to perform an inclusive prefix reduction on data distributed across the calling processes. The operation returns, in the recvbuf of the process with rank i, the reduction (calculated according to the function op) of the values in the sendbufs of processes with ranks 0, …, i (inclusive). The type of operations supported, their semantics, and the constraints on send and receive buffers are as for MPI_Reduce. EXAMPLEThis example uses a user-defined operation to produce a segmented scan. A segmented scan takes, as input, a set of values and a set of logicals, where the logicals delineate the various segments of the scan. For example, values v1 v2 v3 v4 v5 v6 v7 v8 logicals 0 0 1 1 1 0 0 1 result v1 v1+v2 v3 v3+v4 v3+v4+v5 v6 v6+v7 v8 The result for rank j is thus the sum v(i) + … + v(j), where i is the lowest rank such that for all ranks n, i <= n <= j, logical(n) = logical(j). The operator that produces this effect is
Note that this is a noncommutative operator. C code that implements it is given below. typedef struct {
Note that the inout argument to the user-defined function corresponds to the right-hand operand of the operator. When using this operator, we must be careful to specify that it is noncommutative, as in the following: int i, base;
SeqScanPair a, answer;
MPI_Op myOp;
MPI_Datatype type[2] = {MPI_DOUBLE, MPI_INT};
MPI_Aint disp[2];
int blocklen[2] = {1, 1};
MPI_Datatype sspair;
/*
USE OF IN-PLACE OPTIONWhen the communicator is an intracommunicator, you can perform a scanning operation in place (the output buffer is used as the input buffer). Use the variable MPI_IN_PLACE as the value of the sendbuf argument. The input data is taken from the receive buffer and replaced by the output data. NOTES ON COLLECTIVE OPERATIONSThe reduction functions of type MPI_Op do not return an error value. As a result, if the functions detect an error, all they can do is either call MPI_Abort or silently skip the problem. Thus, if the error handler is changed from MPI_ERRORS_ARE_FATAL to something else (e.g., MPI_ERRORS_RETURN), then no error may be indicated. The reason for this is the performance problems in ensuring that all collective routines return the same error value. 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:
COPYRIGHT2003-2025, The Open MPI Community
|