[MITgcm-support] eedata

Sergey Vinogradov svinogra at aer.com
Wed Apr 30 11:38:45 EDT 2008


What happens if you put a slash (/) instead of & on the line after  
usingMPI=.TRUE. ?

On Apr 30, 2008, at 11:33 AM, Nico Wienders wrote:

>
>
> 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
>
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20080430/2f0c8a1f/attachment.htm>


More information about the MITgcm-support mailing list