I've just update ROMS to SVN Revision : 396M and got
SET_NGFLD - current model time exceeds ending value for variable: river_transport
TDAYS = 223.1389
Data Tmin = 2448638.0000 Data Tmax = 2448968.0000
Data Tstr = 2448968.0000 Data Tend = 2448968.0000
TINTRP1 = 0.0000 TINTRP2 = -100393198.0000
FAC1 = -100393421.1389 FAC2 = 223.1389
for all River variables (under UV_PSOURCE
and TS_PSOURCE) that did not appear before.
Would please somebody get me out?
Many thanks,
SET_NGFLD - current model time exceeds ending value for var
Re: SET_NGFLD - current model time exceeds ending value for var
So this used to run before a ROMS update? Or not?
What do you think are the times in your initial file and in your sources file? What are the time units? Look at an ncdump of your file and look at all the attributes.
What do you think are the times in your initial file and in your sources file? What are the time units? Look at an ncdump of your file and look at all the attributes.
Re: SET_NGFLD - current model time exceeds ending value for var
Thank you, Kate
I've used the same configuration (header file) for both.
But as fas as I remember, I've got this error before but I did not post it here and I've modified the source code instead (just to pass this error).
Now, it comes back after upgrade.
I didn't see any special thing in my input files e.g.:
River forcing file:
...................
river = 1, 2, 3 ;
river_Xposition = 1, 1, 21 ;
river_Eposition = 299, 251, 500 ;
river_direction = 0, 0, 1 ;
river_flag = 3, 3, 3 ;
river_Vshape =
0.2, 0.2, 0.2,
0.2, 0.2, 0.2,
0.2, 0.2, 0.2,
0.2, 0.2, 0.2,
0.2, 0.2, 0.2 ;
river_time = 18, 48, 78, 108, 143, 173, 203, 233, 263, 293, 323, 353 ;
river_transport =
4590, 4590, -4590,
3060, 3060, -3060,
...............................
My initial condition is at day 304.
output by ROMS as:
.........................
NLM: GET_STATE - Read state initial conditions, t = 304 00:00:00
(File: ini.nc, Rec=0001, Index=1)
- free-surface
(Min = 0.00000000E+00 Max = 0.00000000E+00)
- vertically integrated u-momentum component
(Min = 0.00000000E+00 Max = 0.00000000E+00)
.......................
GET_NGFLD - temperature northern boundary condition, t = 90 00:00:00
(Rec=0001, Index=1, File: bry.nc)
(Tmin= 90.0000 Tmax= 270.0000)
(Min = 2.00000000E+01 Max = 2.00000000E+01)
SET_NGFLD - current model time exceeds ending value for variable: river_transport
TDAYS = 304.0000
Data Tmin = 2448641.0000 Data Tmax = 2448976.0000
Data Tstr = 2448976.0000 Data Tend = 2448641.0000
TINTRP1 = 353.0000 TINTRP2 = 378.0000
FAC1 = 74.0000 FAC2 = -49.0000
...............
Strange thing here is the river_time varied from 18 to 353 as in my input file but it was somehow translated into:
Data Tmin = 2448641.0000 Data Tmax = 2448976.0000
Data Tstr = 2448976.0000 Data Tend = 2448641.0000
Thank again for any suggestion,
I've used the same configuration (header file) for both.
But as fas as I remember, I've got this error before but I did not post it here and I've modified the source code instead (just to pass this error).
Now, it comes back after upgrade.
I didn't see any special thing in my input files e.g.:
River forcing file:
...................
river = 1, 2, 3 ;
river_Xposition = 1, 1, 21 ;
river_Eposition = 299, 251, 500 ;
river_direction = 0, 0, 1 ;
river_flag = 3, 3, 3 ;
river_Vshape =
0.2, 0.2, 0.2,
0.2, 0.2, 0.2,
0.2, 0.2, 0.2,
0.2, 0.2, 0.2,
0.2, 0.2, 0.2 ;
river_time = 18, 48, 78, 108, 143, 173, 203, 233, 263, 293, 323, 353 ;
river_transport =
4590, 4590, -4590,
3060, 3060, -3060,
...............................
My initial condition is at day 304.
output by ROMS as:
.........................
NLM: GET_STATE - Read state initial conditions, t = 304 00:00:00
(File: ini.nc, Rec=0001, Index=1)
- free-surface
(Min = 0.00000000E+00 Max = 0.00000000E+00)
- vertically integrated u-momentum component
(Min = 0.00000000E+00 Max = 0.00000000E+00)
.......................
GET_NGFLD - temperature northern boundary condition, t = 90 00:00:00
(Rec=0001, Index=1, File: bry.nc)
(Tmin= 90.0000 Tmax= 270.0000)
(Min = 2.00000000E+01 Max = 2.00000000E+01)
SET_NGFLD - current model time exceeds ending value for variable: river_transport
TDAYS = 304.0000
Data Tmin = 2448641.0000 Data Tmax = 2448976.0000
Data Tstr = 2448976.0000 Data Tend = 2448641.0000
TINTRP1 = 353.0000 TINTRP2 = 378.0000
FAC1 = 74.0000 FAC2 = -49.0000
...............
Strange thing here is the river_time varied from 18 to 353 as in my input file but it was somehow translated into:
Data Tmin = 2448641.0000 Data Tmax = 2448976.0000
Data Tstr = 2448976.0000 Data Tend = 2448641.0000
Thank again for any suggestion,
Re: SET_NGFLD - current model time exceeds ending value for var
Show us the attributes on river_time.
Re: SET_NGFLD - current model time exceeds ending value for var
Thank you, Kate, for your hint. It's solved.
I've made a mistake when generate netCDF file without taking care of the difference of the offsets of River.time between ROMS and Matlab Codes.
By the way, I'm having some problem in reproduce inundation maps due to the combination of storm surge and tides. It is possible to use WET_DRY in 3D mode.
Thanks,
I've made a mistake when generate netCDF file without taking care of the difference of the offsets of River.time between ROMS and Matlab Codes.
By the way, I'm having some problem in reproduce inundation maps due to the combination of storm surge and tides. It is possible to use WET_DRY in 3D mode.
Thanks,
Re: SET_NGFLD - current model time exceeds ending value for var
Hi,
Can you tell me how to fix this problem? what do you mean by "difference of the offsets of River.time between ROMS and Matlab Codes."
Thank you very much!
Can you tell me how to fix this problem? what do you mean by "difference of the offsets of River.time between ROMS and Matlab Codes."
Thank you very much!