[MITgcm-support] Error while implementing OBCS

Kevin Ha kevin.ha.pro at gmail.com
Tue Jun 25 07:44:35 EDT 2019 

Ok so now after putting a  [(nx * ny) * nTimeSteps *
deltaT/externForcingPeriod]+1, I got this message (see below). Can someone
explain ?

STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK
STOP ABNORMAL END: S/R OBCS_CHECK

Le mar. 25 juin 2019 à 10:51, Martin Losch <Martin.Losch at awi.de> a écrit :

> Hi Kevin,
>
> for 2D forcing you need to have [(nx * ny) * nTimeSteps *
> deltaT/externForcingPeriod]+1, if you use externForcingPeriod in data.
> Check out some of the examples, e.g. global_ocean.90x40x15, exp4,
> tutorial_global_oce_latlon ...
>
> If you are using pkg/exf to read the forcing, you do something similar:
> based on your ${var}period and your number of timesteps (i.e. model
> integration time span nTimeSteps * deltaT) you determine how many times you
> need to read data. In exf it is slightly more complicated, because the time
> for which the forcing is meant, can be specified explicitly. Compare
> example global_with_exf to global_ocean.90x40x15.  They do the same, one
> with exf, one without.
>
> Another common mistake is to prepare real*4 data and try to read it as
> real*8. Then you'll have only half the records that you need (plus they are
> completely garbled).
>
> M.
>
> > On 25. Jun 2019, at 09:05, Kevin Ha <kevin.ha.pro at gmail.com> wrote:
> >
> > Hello Matt,
> >
> > Thank you for your quick reply. My time parameters are the following
> (see below). I have 480 time records in my u.box file. How many should I
> have ?
> >
> > # Time stepping parameters
> >  &PARM03
> >
> >  niter0 = 0,
> >
> >  nTimeSteps  =  28800, ! 10j avec deltaT=30
> >  deltaT      =    30.,
> >  dumpFreq    =  1800.,
> >  monitorFreq = 43200.,
> >
> >  abEps       =    0.1,
> >  pChkptFreq  = 86400.,
> >  chkptFreq   =    0.0,
> >  &
> >
> > Le lun. 24 juin 2019 à 20:32, Matthew Mazloff <mmazloff at ucsd.edu> a
> écrit :
> > Hi Kevin
> >
> > You don’t have enough time records in your u.box file. The model wants
> more.
> >
> > If you think that you do have enough time records, then I would need
> more info to diagnose the issue.
> >
> > Matt
> >
> >
> > > On Jun 24, 2019, at 7:38 AM, Kevin Ha <kevin.ha.pro at gmail.com> wrote:
> > >
> > > Dear community,
> > >
> > > I am having an error message when implementing obcs package to my
> configuration. After the run I get the message written below. Can someone
> explain what is wrong ? The u.box file is my specified boundary condition
> for velocity u at the north face of the domain (the file is generated using
> matlab code and has dimension Ny*Nz*Nt).
> > >
> > > Thank you in advance
> > >
> > > Best
> > >
> > > Kevin
> > >
> > > Fortran runtime error: Non-existing record number
> > >
> > > Error termination. Backtrace:
> > > At line 1873 of file mdsio_read_section.f (unit = 9, file = 'u.box')
> > > At line 1873 of file mdsio_read_section.f (unit = 9, file = 'u.box')
> > > Fortran runtime error: Non-existing record number
> > >
> > > Error termination. Backtrace:
> > > Fortran runtime error: Non-existing record number
> > >
> > > Error termination. Backtrace:
> > > #0  0x7fb72c0b7607 in ???
> > > #1  0x7fb72c0b8115 in ???
> > > #2  0x7fb72c0b8869 in ???
> > > #3  0x7fb72c17edc9 in ???
> > > #0  0x7ff59cbfc607 in ???
> > > #1  0x7ff59cbfd115 in ???
> > > #2  0x7ff59cbfd869 in ???
> > > #3  0x7ff59ccc3dc9 in ???
> > > #4  0x43d946 in ???
> > > #5  0x4b76f4 in ???
> > > #6  0x4a1086 in ???
> > > #7  0x49a19e in ???
> > > #8  0x4a60a5 in ???
> > > #9  0x5bdbb7 in ???
> > > #10  0x5b0924 in ???
> > > #11  0x5db6fe in ???
> > > #12  0x5db8c4 in ???
> > > #13  0x511c35 in ???
> > > #14  0x402366 in ???
> > > #15  0x7ff59bee9724 in ???
> > > #16  0x402398 in ???
> > >         at ../sysdeps/x86_64/start.S:118
> > > #17  0xffffffffffffffff in ???
> > > #4  0x43d946 in ???
> > > #5  0x4b76f4 in ???
> > > #6  0x4a1086 in ???
> > > #7  0x49a19e in ???
> > > #8  0x4a60a5 in ???
> > > #9  0x5bdbb7 in ???
> > > #10  0x5b0924 in ???
> > > #11  0x5db6fe in ???
> > > -------------------------------------------------------
> > > Primary job  terminated normally, but 1 process returned
> > > a non-zero exit code.. Per user-direction, the job has been aborted.
> > > -------------------------------------------------------
> > >
> --------------------------------------------------------------------------
> > > mpirun detected that one or more processes exited with non-zero
> status, thus causing
> > > the job to be terminated. The first process to do so was:
> > >
> > >   Process name: [[9039,1],27]
> > >   Exit code:    2
> > >
> --------------------------------------------------------------------------
> > > _______________________________________________
> > > MITgcm-support mailing list
> > > MITgcm-support at mitgcm.org
> > > http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support
> >
> > _______________________________________________
> > MITgcm-support mailing list
> > MITgcm-support at mitgcm.org
> > http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support
> > _______________________________________________
> > MITgcm-support mailing list
> > MITgcm-support at mitgcm.org
> > http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20190625/654fb970/attachment-0001.html>

More information about the MITgcm-support mailing list