[MITgcm-support] Getting Backtrace error

[kunal madkaiker]

Hello Martin,

Thank you for your suggestion, it resolved the problem.
Could you please elaborate more on, as to when should we set
periodicExternalForcing=.TRUE.
Thanks again.

-Kunal

On Wed, Dec 9, 2020 at 7:03 PM Martin Losch <Martin.Losch at awi.de> wrote:

> Hi Kunal,
>
> this is a pretty common error, and I think it has been described quite
> often in this email list: The model tries to read forcing data that’s not
> available ("Non-existing record”, sometimes it’s “tries to read past the
> end of the file").
> Usually this means that your forcing data file (in this case: file =
> 'uwind_June_daily_2018.bin’) is too short.
> Your parameter settings (30 days of integration, daily forcing fields,
> first forcing data at 000000 = midnight) require 31 records. This is
> consistent with your error at the start of day 30, because the model
> linearly interpolates between two consecutive forcing field records. On day
> one this would be record 1 and record 2, etc, on day 30 it is record 30 and
> record 31.
>
> It would not help much to move the forcing starttime to noon (120000),
> because then you need 32 records: 30 + 1 before your first day at noon and
> one after your first day at noon.
>
> BTW, you shouldn’t have to set
>  periodicExternalForcing=.TRUE.
>  externForcingPeriod=86400.,
>  externForcingCycle =86400.,
> in data, because all of this is handled through exf, once it is turned on
> (although I recently encountered a weird interaction between these
> parameters).
>
> Hope this helps,
>
> Marton
>
>
> > On 9. Dec 2020, at 08:35, kunal madkaiker <kunal.madkaiker02 at gmail.com>
> wrote:
> >
> > Dear All,
> >
> > I am trying to run a simulation by initializing monthly climatology data
> for temp, salinity and boundary currents, and providing daily forcing of
> heat
> > and moisture fluxes through data.exf (period=86400). My external forcing
> period and cycle are 86400 (daily) in data. I am running model for June
> > 30 days (i.e. 2592000 sec) with delT of 120 sec (thus, total iterations
> of 21600)
> >
> > I get a backtrace error as follows:
> > At line 2079 of file mdsio_read_field.f (unit = 9, file =
> 'uwind_June_daily_2018.bin')
> > Fortran runtime error: Non-existing record number
> >
> > Error termination. Backtrace:
> > #0  0x7f657dca12da in ???
> > #1  0x7f657dca1ec5 in ???
> > #2  0x7f657dca268d in ???
> > #3  0x7f657de1c1ef in ???
> > #4  0x5650dd4fd4ff in ???
> > #5  0x5650dd5abc62 in ???
> > #6  0x5650dd4a06a1 in ???
> > #7  0x5650dd4a168a in ???
> > #8  0x5650dd487c3b in ???
> > #9  0x5650dd4894ac in ???
> > #10  0x5650dd69b94e in ???
> > #11  0x5650dd65e060 in ???
> > #12  0x5650dd69e0dc in ???
> > #13  0x5650dd6bce1c in ???
> > #14  0x5650dd6bcfaa in ???
> > #15  0x5650dd5ff378 in ???
> > #16  0x5650dd5ff60b in ???
> > #17  0x7f657d518b96 in ???
> > #18  0x5650dd47eb09 in ???
> > #19  0xffffffffffffffff in ???
> >
> > I am getting this error on the 20880th iteration (start of 30th day run)
> > From what I understand, my model is giving an output of 31 days (i.e.
> 1st June to 1st July). The 1st day output (1st June) I get is nothing but
> > input data that is being fed, whereas the fluxes are forced for 30 days.
> So it seems there is a mis-match of data that is happening.
> >
> > How can I fix this? Can I let model to not simulate the first day run
> which is nothing but the input data OR
> > do I have to add a dummy data at the initial timestep in my externally
> forced data, so that it becomes 31 days
> >
> > Attaching my data, data.exf file. Kindly assist.
> >
> > Regards
> > Kunal
> > <data.exf><data>_______________________________________________
> > 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/20201213/4b16a38f/attachment.html>