Thanks to Ralph, Gus and Georg for your input!
I was diverted to other things for a week, but now back on track...
You deserve to have the question marks straightened out first: The two
application are (1) a commercial solver and (2) an in-house code handling
some special physics. The two codes
Hi,
Here is what I do to execute 20 mpirun calls using LSF and one job but
it is similar for your case I assume.
I use $LSB_HOSTS to extract the hosts from the job. I know how many
cores I want per job so I create machine files. For our application,
each execution has its own nodes but the l
I'm afraid the two solvers would be in the same comm_world if launched that way
Sent from my iPhone
> On Nov 27, 2013, at 11:58 AM, Gus Correa wrote:
>
> Hi Ola, Ralph
>
> I may be wrong, but I'd guess launching the two solvers
> in MPMD/MIMD mode would work smoothly with the torque PBS_NODEFI
Hi Ola, Ralph
I may be wrong, but I'd guess launching the two solvers
in MPMD/MIMD mode would work smoothly with the torque PBS_NODEFILE,
in a *single* Torque job.
If I understood Ola right, that is what he wants.
Say, something like this (for one 32-core node):
#PBS -l nodes=1:ppn=32
...
mpiex
Are you wanting to run the solvers on different nodes within the
allocation? Or on different cores across all nodes?
For different nodes, you can just use -host to specify which nodes you want
that specific mpirun to use, or a hostfile should also be fine. The FAQ's
comment was aimed at people who
Hi,
We have an in-house application where we run two solvers in a loosely
coupled manner: The first solver runs a timestep, then the second solver
does work on the same timestep, etc. As the two solvers never execute at
the same time, we would like to run the two solvers in the same allocation
