So we do that for residuals/loads since we only print one residual output or
group loads total. The warning messages are send from the process that had the
issue and that is what is interrupting the output of loads data.
From: users On Behalf Of Ralph Castain via
users
Sent: Sunday, December
Hi Mark,
"[...] MPI makes neither requirements nor recommendations for the output
[...]" (MPI4.0, ยง2.9.1)
From my experience, an application can avoid such scrambling (still no
guarantee), if the output of lines is written atomically. C++ streams
are worst for concurrent output, as every str
All strings are writing as one output so that is not the issue. Adding in some
flushing is a good idea and we can try that. We do not open stdout just write
to unit 6, but we could open it if there is some un-buffered option that could
help. I will look into that also. Thanks!
-Original Me
I would assume, that the buffering mode is compiler/runtime specific. At
least for Intel compiler, the default seems to be/have been unbuffered
for stdout, but there is a flag for buffered output:
https://community.intel.com/t5/Intel-Fortran-Compiler/Enabling-buffered-I-O-to-stdout-with-Intel-i
This usually happens if we get a number of warning message from multiple
processes. Seems like unbuffered is what we want but not sure how this
interacts with MPI since stdout/stderr is pulled back from different hosts. Not
sure how you are doing that.
-Original Message-
From: Joachim
