Thanks Daniel, Yes you rightly suggested, it worked with '--multi-prog' and specifying core in a separate text file as
0-223 prog1.x 224-239 prog2.x prog2.parm Appreciate your response. Best regards Akhilesh > On Jun 14, 2016, at 3:51 AM, Daniel Letai <d...@letai.org.il> wrote: > > Possibly with `--multi-prog` as per > http://slurm.schedmd.com/srun.html#SECTION_MULTIPLE-PROGRAM-CONFIGURATION > > >> On 06/13/2016 06:26 PM, Akhilesh Mishra wrote: >> Dear Developers and SLURM users, >> I have been running two separate executables on TACC's SLURM scheduler using >> ibrun via a script as following; >> >> echo $args >> cat>my_config<<EOF >> -n 224 :prog1.x >> -n 16 :prog2.x prog2.parm >> EOF >> touch f00 >> chmod 755 f00 >> ibrun f00 1>$here_dir/$outs.ft$hx 2>&1 >> cc=$? >> >> This was part of my mpisub script and in main job script, I had to add >> MY_MPIRUN_OPTIONS="-config ./my_config" >> right in the beginning after all #SBATCH declarations. >> >> Recently I started testing this code on another HPC facility where they >> don't have "ibrun" and my request to install "ibrun" has been declined. I >> have been told that "srun" is powerful enough to handle this. I have been >> trying various options, so far no luck. >> Any suggestion/help would be greatly appreciated. >> Many Thanks >> -Akhilesh >
