On Mar 15, 2014, at 6:21 PM, christophe petit
wrote:
> Ok, so from what you say, on a "execution system" point view, the ring
> communication is well achieved (i.e respecting the good order with, in last
> position, rank0 which receives from rank 6) but the stdout doesn't reflect
> what real
Ok, so from what you say, on a "execution system" point view, the ring
communication is well achieved (i.e respecting the good order with, in last
position, rank0 which receives from rank 6) but the stdout doesn't reflect
what really happened, does it ?
Is there a way to make stdout respect the ex
The explanation is simple: there is no rule about ordering of stdout. So even
though your rank0 may receive its MPI message last, its stdout may well be
printed before one generated on a remote node. Reason is that rank 0 may well
be local to mpirun, and thus the stdout can be handled immediatel
