BTW -- that was a good hutch but now I guess I would need to look into
what causes cmdline options incompatibilities (that is on s390 box):
testLastUsedCode (test_environ.TestWorldAttrs) ... ok
testUniverseSize (test_environ.TestWorldAttrs) ... [mpiexec@zelenka] match_arg
(./utils/args/args.c:122): unrecognized argument pmi_args
[mpiexec@zelenka] HYDU_parse_array (./utils/args/args.c:140): argument matching
returned error
[mpiexec@zelenka] parse_args (./ui/mpich/utils.c:1387): error parsing input
array
[mpiexec@zelenka] HYD_uii_mpx_get_parameters (./ui/mpich/utils.c:1438): unable
to parse user arguments
Usage: ./mpiexec [global opts] [exec1 local opts] : [exec2 local opts] : ...
Global options (passed to all executables):
Global environment options:
-genv {name} {value} environment variable name and value
-genvlist {env1,env2,...} environment variable list to pass
-genvnone do not pass any environment variables
-genvall pass all environment variables not managed
by the launcher (default)
Other global options:
-f {name} file containing the host names
-hosts {host list} comma separated host list
-wdir {dirname} working directory to use
-configfile {name} config file containing MPMD launch options
Local options (passed to individual executables):
Local environment options:
-env {name} {value} environment variable name and value
-envlist {env1,env2,...} environment variable list to pass
-envnone do not pass any environment variables
-envall pass all environment variables (default)
Other local options:
-n/-np {value} number of processes
{exec_name} {args} executable name and arguments
Hydra specific options (treated as global):
Launch options:
-launcher launcher to use ( ssh rsh fork slurm ll
lsf sge manual persist)
-launcher-exec executable to use to launch processes
-enable-x/-disable-x enable or disable X forwarding
Resource management kernel options:
-rmk resource management kernel to use ( user
slurm ll lsf sge pbs)
Hybrid programming options:
-ranks-per-proc assign so many ranks to each process
Processor topology options:
-binding process-to-core binding mode
-topolib processor topology library ( hwloc plpa)
Checkpoint/Restart options:
-ckpoint-interval checkpoint interval
-ckpoint-prefix checkpoint file prefix
-ckpoint-num checkpoint number to restart
-ckpointlib checkpointing library (none)
Demux engine options:
-demux demux engine ( poll select)
Other Hydra options:
-verbose verbose mode
-info build information
-print-all-exitcodes print exit codes of all processes
-iface network interface to use
-ppn processes per node
-profile turn on internal profiling
-prepend-rank prepend rank to output
-prepend-pattern prepend pattern to output
-outfile-pattern direct stdout to file
-errfile-pattern direct stderr to file
-nameserver name server information (host:port format)
-disable-auto-cleanup don't cleanup processes on error
-disable-hostname-propagation let MPICH2 auto-detect the hostname
-order-nodes order nodes as ascending/descending cores
Please see the intructions provided at
http://wiki.mcs.anl.gov/mpich2/index.php/Using_the_Hydra_Process_Manager
for further details
On Mon, 04 Jun 2012, Yaroslav Halchenko wrote:
> good call -- just for the sake of testing I guess I should better first
> test it on e.g. s390 -- will request access to it
--
Yaroslav O. Halchenko
Postdoctoral Fellow, Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
