Charm++ parallel programming system

[Tom Quinn <trq AT astro.washington.edu>]

Let me be explict about what I'm doing: I'm using valgrind to check for 
memory errors and I have a script that looks like this:

#!/bin/sh -f
$HOME/bin/valgrind --track-origins=yes --leak-check=yes --log-file=VG.out.$$ 
$*

which I invoke using the ++runscript argument:
./charmrun +p $proc ++runscript $HOME/bin/vgleak ./ChaNGa ...

I'd like those VG.out.NNNNNNN to be a different file for each PE, but I'm 
now getting one file per node.

On Fri, 8 Jul 2016, Phil Miller wrote:

> As an alternative, I think there was an option added not too long ago
> to have each PE redirect its output to a file, without any need for
> shell script hacking. I'll follow up later today, if someone else
> hasn't chimed in.
>
> On Thu, Jul 7, 2016 at 11:34 PM, Tom Quinn 
> <trq AT astro.washington.edu>
>  wrote:
> > I have a need to turn off scalable start: I want to redirect output to
> > separate files using the "$$" shell variable, so I need different shells for
> > each process on a node.  Is there a way to do this now?
> >
> > Tom