i have a question
i have a question
hello
When i run roms model, i have some errors.
the log file show that like this.
'current model time exceeds ending value for variable : zeta west'
Even if, i check time of zeta west, i could't understand why this error represented.
When i run roms model, i have some errors.
the log file show that like this.
'current model time exceeds ending value for variable : zeta west'
Even if, i check time of zeta west, i could't understand why this error represented.
Re: i have a question
Can you print out the times for zeta_west? Are they in order of increasing time?
Re: i have a question
the dimension of this variable, zeta west,is (zeta_time, erho).
And i run the model for 1 year(366 days)
This picture shows that zeta time.
and i use nudging scheme for 3D velocity. This time interval is 1 day.
And i run the model for 1 year(366 days)
This picture shows that zeta time.
and i use nudging scheme for 3D velocity. This time interval is 1 day.
- Attachments
-
- zeta.png (30.59 KiB) Viewed 8266 times
Re: i have a question
Your times for zeta-_est are between 0.5 and 365.5, but the model time is 0. So model time is not bracketed by the forcing time, hence ROMS won't start.
Either:
(1) Change your initial conditions time to greater than 0.5 days << BEST
(2) Just change the first time in the boundary file to 0 days (instead of 0.5) - this makes the first half day of boundary data not quite right
(3) Add a new time record to the front of the forcing file (e.g. for t = -0.5 days) if you have those data. (If you just copied the data for day 0.5 that would be hold the values constant from t=0 to t=0.5 and then the correct linear interpolation would begin).
Either:
(1) Change your initial conditions time to greater than 0.5 days << BEST
(2) Just change the first time in the boundary file to 0 days (instead of 0.5) - this makes the first half day of boundary data not quite right
(3) Add a new time record to the front of the forcing file (e.g. for t = -0.5 days) if you have those data. (If you just copied the data for day 0.5 that would be hold the values constant from t=0 to t=0.5 and then the correct linear interpolation would begin).
John Wilkin: DMCS Rutgers University
71 Dudley Rd, New Brunswick, NJ 08901-8521, USA. ph: 609-630-0559 jwilkin@rutgers.edu
71 Dudley Rd, New Brunswick, NJ 08901-8521, USA. ph: 609-630-0559 jwilkin@rutgers.edu
- m.hadfield
- Posts: 521
- Joined: Tue Jul 01, 2003 4:12 am
- Location: NIWA
Re: i have a question
Or if the data are supposed to repeat year on year, you could add a cycle_length attribute to the zeta_west variable.
Re: i have a question
When i change initial time like t = 0, will i change the other kind of times?? For example, ocean time, temp time and salt time and so on.
Re: i have a question
The time in the initial conditions file does not have to match the first time in all the boundary conditions, forcing, and other input files.
ROMS is clever enough to take the initial conditions time and figure out which records to read and interpolate from all the others. If it were any other way we would be having to change the forcing files every time we restart run.
So my suggestion ...
ROMS is clever enough to take the initial conditions time and figure out which records to read and interpolate from all the others. If it were any other way we would be having to change the forcing files every time we restart run.
So my suggestion ...
is by far the easiest solution for you to get started.(1) Change your initial conditions time to greater than 0.5 days << BEST
John Wilkin: DMCS Rutgers University
71 Dudley Rd, New Brunswick, NJ 08901-8521, USA. ph: 609-630-0559 jwilkin@rutgers.edu
71 Dudley Rd, New Brunswick, NJ 08901-8521, USA. ph: 609-630-0559 jwilkin@rutgers.edu
Re: i have a question
I have a similar question.wilkin wrote:The time in the initial conditions file does not have to match the first time in all the boundary conditions, forcing, and other input files.
ROMS is clever enough to take the initial conditions time and figure out which records to read and interpolate from all the others. If it were any other way we would be having to change the forcing files every time we restart run.
So my suggestion ...is by far the easiest solution for you to get started.(1) Change your initial conditions time to greater than 0.5 days << BEST
Code: Select all
NLM: GET_STATE - Read state initial conditions, t = 0 00:00:00
(Grid 01, File: ssc12_ini.nc, Rec=0001, Index=1)
- free-surface
(Min = -1.48966948E-01 Max = 3.61947780E-01)
- vertically integrated u-momentum component
(Min = -6.00885394E-01 Max = 4.97978379E-01)
- vertically integrated v-momentum component
(Min = -9.50324788E-01 Max = 3.26700159E-01)
- u-momentum component
(Min = -1.05035297E+00 Max = 8.54699225E-01)
- v-momentum component
(Min = -1.33850665E+00 Max = 1.10605943E+00)
- potential temperature
(Min = 1.14820875E+00 Max = 2.94470631E+01)
- salinity
(Min = 3.24921652E+01 Max = 3.49794372E+01)
GET_NGFLD - tidal period
(Min = 4.30819210E+04 Max = 9.67262421E+04)
GET_2DFLD - tidal elevation amplitude
(Min = 1.05619027E-04 Max = 2.04697708E+01)
GET_2DFLD - tidal elevation phase angle
(Min = 8.09572363E-06 Max = 6.28317033E+00)
GET_2DFLD - tidal current inclination angle
(Min = 2.46404577E-06 Max = 6.28318082E+00)
GET_2DFLD - tidal current phase angle
(Min = 1.82233990E-06 Max = 6.28318114E+00)
GET_2DFLD - maximum tidal current, ellipse major axis
(Min = 3.85134858E-06 Max = 1.81928232E+01)
GET_2DFLD - minimum tidal current, ellipse minor axis
(Min = -1.04224347E+00 Max = 1.16227576E+00)
forrtl: severe (408): fort: (3): Subscript #1 of the array TVAL has value 0 which is less than the lower bound of 1
Image PC Routine Line Source
oceanG 0000000001D7107D Unknown Unknown Unknown
oceanG 0000000001D6FB85 Unknown Unknown Unknown
oceanG 0000000001D16409 Unknown Unknown Unknown
oceanG 0000000001CD4A8F Unknown Unknown Unknown
oceanG 0000000001CD4E92 Unknown Unknown Unknown
oceanG 00000000018CBDBF get_cycle_ 224 get_cycle.f90
oceanG 000000000163732F inquire_ 277 inquire.f90
oceanG 00000000015CA9C0 get_2dfld_ 102 get_2dfld.f90
oceanG 00000000012C728B get_data_ 100 get_data.f90
oceanG 00000000006930BF initial_ 282 initial.f90
oceanG 00000000004131ED ocean_control_mod 130 ocean_control.f90
oceanG 000000000041235F MAIN__ 95 master.f90
oceanG 00000000004121FC Unknown Unknown Unknown
libc.so.6 00002AE0D133CCDD Unknown Unknown Unknown
oceanG 00000000004120F9 Unknown Unknown Unknown
Code: Select all
wind_time = -2, -1.75, -1.5, -1.25, -1, -0.75, -0.5, -0.25, 0, 0.25, 0.5,
0.75, 1, 1.25, 1.5, 1.75, 2, 2.25, 2.5, 2.75, 3, 3.25, 3.5, 3.75, 4,
4.25, 4.5, 4.75, 5, 5.25, 5.5, 5.75, 6, 6.25, 6.5, 6.75, 7, 7.25, 7.5,
7.75, 8, 8.25, 8.5, 8.75, 9, 9.25, 9.5, 9.75, 10, 10.25, 10.5, 10.75, 11,
11.25, 11.5, 11.75, 12, 12.25, 12.5, 12.75, 13, 13.25, 13.5, 13.75, 14,
14.25, 14.5, 14.75, 15, 15.25, 15.5, 15.75, 16, 16.25, 16.5, 16.75, 17,
17.25, 17.5, 17.75, 18, 18.25, 18.5, 18.75, 19, 19.25, 19.5, 19.75, 20,
20.25, 20.5, 20.75, 21, 21.25, 21.5, 21.75, 22, 22.25, 22.5, 22.75, 23,
23.25, 23.5, 23.75, 24, 24.25, 24.5, 24.75, 25, 25.25, 25.5, 25.75, 26,
26.25, 26.5, 26.75, 27, 27.25, 27.5, 27.75, 28, 28.25, 28.5, 28.75, 29,
29.25, 29.5, 29.75, 30, 30.25, 30.5, 30.75, 31, 31.25, 31.5, 31.75, 32,
32.25, 32.5, 32.75 ;
}
Code: Select all
bry_time = -16, 14, 44 ;
Code: Select all
ocean_time = 0 ;
Re: i have a question
Can you shift your time origin (DSTART) forward say 30 days so that you have no negative times?
Re: i have a question
You say you removed the cycle_length attribute:
So you need to sort out what's wrong with your netcdf file. Perhaps browse the logic in get_data and figure out which variable ROMS was reading when it threw the error.
But the traceback indicates that inquire found the attribute and therefore called get_cycle.I use the BULK_FLUX. and the line 100 of get_data.f90 want to get wind component.I also remove the cycle attribute.But canot run.
Code: Select all
oceanG 0000000001CD4A8F Unknown Unknown Unknown
oceanG 0000000001CD4E92 Unknown Unknown Unknown
oceanG 00000000018CBDBF get_cycle_ 224 get_cycle.f90
oceanG 000000000163732F inquire_ 277 inquire.f90
oceanG 00000000015CA9C0 get_2dfld_ 102 get_2dfld.f90
John Wilkin: DMCS Rutgers University
71 Dudley Rd, New Brunswick, NJ 08901-8521, USA. ph: 609-630-0559 jwilkin@rutgers.edu
71 Dudley Rd, New Brunswick, NJ 08901-8521, USA. ph: 609-630-0559 jwilkin@rutgers.edu
Re: i have a question
I have a similar issue with time steps so decided to ask my question in this topic.
I am trying to read in atm. forcing files for my 2014 run. I have the forcing fields for the whole year and I am only interested in 3 months starting May 23rd (12PM). Hence I changed times in the forcing files as days relative to May 23rd (in the form of ...-0.25,0,0.25...). My issue is before my simulation starts, ROMS reads my forcing files twice (you can see it below) which causes a time shift in the forcing files (3 and 6 hours to be specific). I tried using both TIME_REF=0 and TIME_REF=20140523.5d and same thing happened.
I could cheat and subtract 1 more time step but it is an annoying issue which has to have a simpler solution.
I tried different ROMS versions and I encountered this problem with OBC as well. What am I missing?
I am trying to read in atm. forcing files for my 2014 run. I have the forcing fields for the whole year and I am only interested in 3 months starting May 23rd (12PM). Hence I changed times in the forcing files as days relative to May 23rd (in the form of ...-0.25,0,0.25...). My issue is before my simulation starts, ROMS reads my forcing files twice (you can see it below) which causes a time shift in the forcing files (3 and 6 hours to be specific). I tried using both TIME_REF=0 and TIME_REF=20140523.5d and same thing happened.
I could cheat and subtract 1 more time step but it is an annoying issue which has to have a simpler solution.
I tried different ROMS versions and I encountered this problem with OBC as well. What am I missing?
Code: Select all
NLM: GET_STATE - Read state initial conditions, t = 0 00:00:00
(Grid 01, File: ini_rsrt.nc, Rec=0001, Index=1)
- free-surface
(Min = 0.00000000E+00 Max = 4.74517411E-01)
- vertically integrated u-momentum component
(Min = -4.75181724E-01 Max = 1.28795831E-01)
- vertically integrated v-momentum component
(Min = -3.13548350E-01 Max = 3.95202656E-01)
- u-momentum component
(Min = -8.25463918E-01 Max = 3.82607522E-01)
- v-momentum component
(Min = -7.25966545E-01 Max = 6.09747377E-01)
- potential temperature
(Min = 0.00000000E+00 Max = 1.85641359E+01)
- salinity
(Min = 0.00000000E+00 Max = 3.44186987E+01)
GET_NGFLD - tidal period
(Min = 2.19720214E+04 Max = 2.38071336E+06)
GET_2DFLD - tidal elevation amplitude
(Min = 0.00000000E+00 Max = 9.73092002E-01)
GET_2DFLD - tidal elevation phase angle
(Min = 0.00000000E+00 Max = 5.38337522E+00)
GET_2DFLD - tidal current inclination angle
(Min = 0.00000000E+00 Max = 3.14159257E+00)
GET_2DFLD - tidal current phase angle
(Min = 0.00000000E+00 Max = 6.28316856E+00)
GET_2DFLD - maximum tidal current, ellipse major axis
(Min = 0.00000000E+00 Max = 1.27036483E-01)
GET_2DFLD - minimum tidal current, ellipse minor axis
(Min = -2.26668086E-02 Max = 7.04508832E-02)
GET_2DFLD - surface u-wind component, t = 0 00:00:00
(Rec=0000571, Index=1, File: wind.nc)
(Tmin= -142.5000 Tmax= 222.2500)
(Min = 6.16196944E-01 Max = 3.08001225E+00)
GET_2DFLD - surface v-wind component, t = 0 00:00:00
(Rec=0000571, Index=1, File: wind.nc)
(Tmin= -142.5000 Tmax= 222.2500)
(Min = -3.33173673E-01 Max = 2.05091213E+00)
GET_2DFLD - surface air pressure, t = 0 00:00:00
(Rec=0001140, Index=1, File: pair.nc)
(Tmin= -142.3750 Tmax= 222.5000)
(Min = 1.01738097E+03 Max = 1.01870001E+03)
GET_2DFLD - surface air temperature, t = 0 00:00:00
(Rec=0001140, Index=1, File: tair.nc)
(Tmin= -142.3750 Tmax= 222.5000)
(Min = 1.28998051E+01 Max = 1.42748051E+01)
GET_2DFLD - surface air relative humidity, t = 0 00:00:00
(Rec=0001140, Index=1, File: qair.nc)
(Tmin= -142.3750 Tmax= 222.5000)
(Min = 8.90000000E-01 Max = 9.80000000E-01)
GET_2DFLD - solar shortwave radiation flux, t = 0 00:00:00
(Rec=0001140, Index=1, File: swrad.nc)
(Tmin= -142.3750 Tmax= 222.5000)
(Min = 0.00000000E+00 Max = 0.00000000E+00)
Basin information for Grid 01:
Maximum grid stiffness ratios: rx0 = 2.000022E-01 (Beckmann and Haidvogel)
rx1 = 1.294633E+01 (Haney)
Initial basin volumes: TotVolume = 8.9261530669E+11 m3
MinVolume = 1.7694182887E+04 m3
MaxVolume = 1.5259540454E+07 m3
Max/Min = 8.6240435921E+02
NL ROMS/TOMS: started time-stepping: (Grid: 01 TimeSteps: 00000001 - 00002700)
GET_2DFLD - surface u-wind component, t = 0 06:00:00
(Rec=0000572, Index=2, File: wind.nc)
(Tmin= -142.5000 Tmax= 222.2500)
(Min = -1.75372802E-01 Max = 3.15555706E+00)
GET_2DFLD - surface v-wind component, t = 0 06:00:00
(Rec=0000572, Index=2, File: wind.nc)
(Tmin= -142.5000 Tmax= 222.2500)
(Min = 1.56416958E+00 Max = 5.38237476E+00)
GET_2DFLD - surface air pressure, t = 0 03:00:00
(Rec=0001141, Index=2, File: pair.nc)
(Tmin= -142.3750 Tmax= 222.5000)
(Min = 1.01703815E+03 Max = 1.01945001E+03)
GET_2DFLD - surface air temperature, t = 0 03:00:00
(Rec=0001141, Index=2, File: tair.nc)
(Tmin= -142.3750 Tmax= 222.5000)
(Min = 1.30743656E+01 Max = 1.40743656E+01)
GET_2DFLD - surface air relative humidity, t = 0 03:00:00
(Rec=0001141, Index=2, File: qair.nc)
(Tmin= -142.3750 Tmax= 222.5000)
(Min = 9.60000000E-01 Max = 9.80000000E-01)
GET_2DFLD - solar shortwave radiation flux, t = 0 03:00:00
(Rec=0001141, Index=2, File: swrad.nc)
(Tmin= -142.3750 Tmax= 222.5000)
(Min = 3.56742872E-06 Max = 3.06048023E-05)
STEP Day HH:MM:SS KINETIC_ENRG POTEN_ENRG TOTAL_ENRG NET_VOLUME
C => (i,j,k) Cu Cv Cw Max Speed
0 0 00:00:00 5.572512E-03 1.345057E+03 1.345062E+03 9.089321E+11
(113,119,39) 3.857196E-02 2.753595E-02 0.000000E+00 9.874988E-01
DEF_HIS - creating history file, Grid 01: out/roms/ocean_his_00001.nc
WRT_HIS - wrote history fields (Index=1,1) into time record = 0000001
5 0 00:02:00 5.408521E-03 1.363454E+03 1.363459E+03 8.964269E+11
(103,121,40) 5.674017E-03 8.682401E-03 7.697877E-01 1.003817E+00
10 0 00:04:00 5.287900E-03 1.363436E+03 1.363441E+03 8.963257E+11
(103,122,40) 0.000000E+00 1.914535E-03 8.916389E-01 1.074895E+00
15 0 00:06:00 5.254022E-03 1.363472E+03 1.363477E+03 8.962258E+11
(113,008,40) 9.494561E-03 4.083571E-03 1.226500E+00 1.081200E+00
20 0 00:08:00 5.285353E-03 1.363488E+03 1.363494E+03 8.961248E+11
(188,112,40) 3.399103E-03 3.832126E-03 6.726246E-01 1.055692E+00
25 0 00:10:00 5.355226E-03 1.363492E+03 1.363497E+03 8.960253E+11
(101,122,40) 6.725133E-04 1.318796E-02 8.352360E-01 1.025486E+00
Re: i have a question
I don't see what the problem is. Yes, it is reading the forcing files for time 0 and for time 6 hours, then it linearly time-interpolates between them to the current model time. It always has two time records in memory for this interpolation. Once six hours pass, it will read hour 12, and so on.