[MITgcm-support] eedata

[Martin.Losch at awi.de]

Nico,

Instead of changing all namelist termination characters from "&" to "/" you can also add a flag to your build_options file like this (taken from sp4+mpi_jump):
DEFINES=$DEFINES' -DNML_TERMINATOR'
which will do the replacement on the fly.

Martin


Martin Losch
Alfred Wegener Institute 
Postfach 120161, 27515 Bremerhaven, Germany; 
Tel./Fax: ++49(0471)4831-1872/1797


-------------- next part --------------


Comrades,

During my modest and chaotic cohabitation with MITgcm,
i have never had the need to modify the eedata file.
Even when using our local small cluster (~20 procs).

I have started using a somehow more serious cluster
yesterday (~500+ procs) and now get the following
error message at the execution:

::::::::::::::
STDERR.0000
::::::::::::::
(PID.TID 0000.0001) *** ERROR *** S/R EESET_PARMS
(PID.TID 0000.0001) *** ERROR *** Error reading execution environment
(PID.TID 0000.0001) *** ERROR *** parameter file "eedata"

Of course, I have tried to feed the beast with some common
but tasty instructions but with no effect so far:

# Example "eedata" file
# Lines beginning "#" are comments
# nTx - No. threads per process in X
# nTy - No. threads per process in Y
  &EEPARMS
  nTx=1,
  nTy=1,
  usingMPI=.TRUE.,
  &
# Note: Some systems use & as the
# namelist terminator. Other systems
# use a / character (as shown here).


Would you have any idea on how i could improve the situation?
I am using mpich or openmpi, which the moab queuing system.
I apologize for my known incompetence, thanks a lot.





Nico Wienders                          (850) 644-1987 (office)
Florida State University                      294-3542    (cell)
Oceanography - OSB415                    644-2581    (fax)
P.O. Box 3064320                 117 N. Woodward Avenue
Tallahassee, FL 32306-4320    wienders at ocean.fsu.edu



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20080430/0d80ac1b/attachment.htm>
-------------- next part --------------
_______________________________________________
MITgcm-support mailing list
MITgcm-support at mitgcm.org
http://mitgcm.org/mailman/listinfo/mitgcm-support