On Fri, 2008-07-11 at 07:59 -0600, Ralph H Castain wrote:
> Not until next week's meeting, but I would guess we would simply prepend the
> rank. The issue will be how often to tag the output since we write it in
> fragments to avoid blocking - so do we tag the fragment, look for newlines
> and tag
Not until next week's meeting, but I would guess we would simply prepend the
rank. The issue will be how often to tag the output since we write it in
fragments to avoid blocking - so do we tag the fragment, look for newlines
and tag each line, etc.
We'll figure something out... ;-)
On 7/11/08 7:
That sounds great Ralph! Do you have any more details about how the
process rank would be added?
And thanks for the other suggestions from Ashley and Galen. Both
methods look like they would work great, and are probably a little
nicer than my current setup.
-Mark
On Jul 11, 2008, at 9
Adding the ability to tag stdout/err with the process rank is fairly simple.
We are going to talk about this next week at a design meeting - we have
several different tagging schemes that people have requested, so we want to
define a way to meet them all that doesn't create too much ugliness in the
If you are using the openmpi mpirun then you can put the following in a
wrapper script which will prefix stdout in a manner similar to what you
appear to want. Simply add the wrapper script before the name of your
application.
Is this the kind of thing you were aiming for? I'm quite surprised
m
OMPI users] Outputting rank and size for all outputs.
Lately I have been doing a great deal of MPI debugging. I have, on an
occasion or two, fallen into the trap of "Well, that error MUST be
coming from rank X. There is no way it could be coming from any other
rank..." Then procee
Lately I have been doing a great deal of MPI debugging. I have, on an
occasion or two, fallen into the trap of "Well, that error MUST be
coming from rank X. There is no way it could be coming from any other
rank..." Then proceeding to debug what's happening at rank X, only to
find out a
