[MITgcm-support] Difficult with cpl_aim+oce
Chris Horvat
horvat at fas.harvard.edu
Thu Sep 19 14:18:56 EDT 2013
Hi all,
I know there have been a few threads covering this from other directions,
but I'm looking for a little help running the coupled ocean/aim experiment.
Currently the run_cpl_test 3 command returns the following:
--------------------------------------
execute 'mpirun -p4pg pr_group -v ./build_cpl/mitgcmuv' :
-umask <umask> # umask for remote process
-path <dirname> # place to look for executables
-host <hostname> # host to start on
-soft <spec> # modifier of -n value
-arch <arch> # arch type to start on (not implemented)
-envall # pass all env vars in current
environment
-envnone # pass no env vars
-envlist <list of env var names> # pass current values of these vars
-env <name> <value> # pass this value of this env var
mpiexec [global args] [local args] executable args : [local args]
executable...
mpiexec -gdba jobid # gdb-attach to existing jobid
mpiexec -configfile filename # filename contains cmd line segs as
lines
(See User Guide for more details)
Examples:
mpiexec -l -n 10 cpi 100
mpiexec -genv QPL_LICENSE 4705 -n 3 a.out
mpiexec -n 1 -host foo master : -n 4 -host mysmp slave
----------------------------------------------------
which I take to mean it isn't liking one of the optional (most likely
mpirun -pgp4). Is anyone familiar with this error?
If I run the simple command
mpd
mpirun ./build_cpl/mitgcmuv > xx
in a batch script, the job will send and appear to be running, but won't
produce any STD* output or error output.
Thanks for your help!!!!
Chris
---
Christopher Horvat -- www.chrv.at <http://www.chrv.at/blog.html>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20130919/942d9ecc/attachment.htm>
More information about the MITgcm-support
mailing list