Charm++ parallel programming system

[Jim Phillips <jim AT ks.uiuc.edu>]

If you're using an MPI build you can just use srun on the binary and 
ignore charmrun.  If you're using a non-MPI (e.g., ibverbs) build, then 
use "charmrun ++mpiexec ++remote-shell /path/to/mysrun ..." where mysrun 
is the following script:

#!/bin/csh -f
shift
exec /path/to/srun -n $*

(The "shift" command drops the "-np" argument.)

-Jim


On Wed, 25 Mar 2015, Robert Steinke wrote:

> Our machine recently got switched to the Slurm job scheduler.  Now, in order 
> to run jobs we need to use "srun -n <number of processes>" instead of "mpirun 
> -np <number of processes>". The charmrun script doesn't work as-is.  I hand 
> edited this part of charmrun to replace "mpirun -np" with "srun -n" and it 
> worked:
>
>    if [ -n "$setarch_cmd" -a -x "$setarch_cmd" ]
>    then
>      # Disables randomization of the virtual address  space (turns  on
>      #          ADDR_NO_RANDOMIZE).
>      cur_arch=`uname -m`
>      echo "charmrun>  $setarch_cmd $cur_arch -R  mpirun -np $pes $args"
>      $setarch_cmd $cur_arch -R  mpirun -np $pes $args
>    else
>      echo "charmrun> mpirun -np $pes $args"
>      mpirun -np $pes $args
>    fi
>
> Is there an official solution for using charmrun with Slurm?
>
> Thanks
> Bob Steinke
> _______________________________________________
> charm mailing list
> charm AT cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/charm
> _______________________________________________
> ppl mailing list
> ppl AT cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/ppl