Easier than I thought...done in r21147
Let me know if that meets your needs
Ralph
On Mon, May 4, 2009 at 9:42 AM, Ralph Castain wrote:
> Should be doable
>
> Since the output was going to stderr, we just let it continue to do so and
> tagged it. I think I can redirect it when doing xml tag
Should be doable
Since the output was going to stderr, we just let it continue to do so and
tagged it. I think I can redirect it when doing xml tagging as that is
handled as a separate case - shouldn't be too hard to do.
On Mon, May 4, 2009 at 9:29 AM, Greg Watson wrote:
> Ralph,
> I did fi
Ralph,
I did find another issue in 1.3 though. It looks like with the -xml
option you're sending output tagged with to stderr, whereas
it would probably be better if everything was sent to stdout.
Otherwise it's necessary to parse the stderr stream separately.
Greg
On May 1, 2009, at 10
Arrgh! Sorry, my bad. I must have been linked against an old version
or something. When I recompiled the output went away.
Greg
On May 1, 2009, at 10:09 AM, Ralph Castain wrote:
Interesting - I'm not seeing this behavior:
graywolf54:trunk rhc$ mpirun -n 3 --xml --display-map hostname
Interesting - I'm not seeing this behavior:
graywolf54:trunk rhc$ mpirun -n 3 --xml --display-map hostname
graywolf54.lanl.gov
graywolf54.lanl.gov
graywolf54.lanl.gov
graywolf54:trunk rhc$
Can you tell me more about when you see this? Note that the display-m
Hmmm...no, that's a bug. I'll fix it.
Thanks!
On Fri, May 1, 2009 at 7:24 AM, Greg Watson wrote:
> Ralf,
>
> I've just noticed that if I use '-xml -display-map', I get the xml version
> of the map and then the non-xml version is sent to stderr (wrapped in xml
> tags). Was this by design? In my
Ralf,
I've just noticed that if I use '-xml -display-map', I get the xml
version of the map and then the non-xml version is sent to stderr
(wrapped in xml tags). Was this by design? In my view it would be
better to suppress the non-xml map altogether if the -xml option. 1.4
seems to do th
