Problems with time steps (model time exceeding forcing time)

[cschultz]

Hi everyone,

I am doing a run for 2 years (2003-2004), and my inputs range from dec-2002 to jan-2005. Still, it runs one year and then I get the following message for all the atmospheric forcings (bulk):

SET_2DFLD - current model time exceeds ending value for variable: Tair
TDAYS = 1461.0104
Data Tmin = 1065.0000 Data Tmax = 1858.0000
Data Tstr = 1095.0000 Data Tend = 1095.2500
TINTRP1 = 1461.0000 TINTRP2 = 1461.0000
FAC1 = -0.0104 FAC2 = 0.0104

I checked all the time parameters, in my i.n file I have

NTIMES == 70080
DT == 900.0d0
NDTFAST == 60
and
DSTART = 1095.0d0
TIDE_START = 0.0d0
TIME_REF = 20000101.0d

So that means I am telling the model to run 70080*900 seconds after [01/01/2000 +(1095 days)] (corresponding to 01/01/2003), correct?
That means it would run 730 days after day 1095 (based on TIME_REF), leading to day 1825, so I would need the inputs to range from 1095 to 1825 at least.
But the oceanic inputs (salt_time) go from day 1079-1841 and my atmospheric inputs go from day 1065-1858.

Where else should I be looking for this problem's solution? The data are there, and What really bugs me is that it ran exactly one year!

Thanks already!

[kate]

Is there a chance that you have two records with the time 1461 days in your forcing file? That could confuse ROMS.

[cschultz]

That's right, Kate, thank you very much!