problems after updating to latest revision(321)

[rongzr]

Hi All, I got the following IO error after i updating to the latest revision(321), the output is like this:

Horizontal mixing scaled by grid size, GRDMAX = 1.78056264E+01 km

NLM: GET_STATE - Read state initial conditions, t = 0 00:00:00
(File: ECSYS_Test_Ini_Jul.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)
- vertically integrated v-momentum component
(Min = 0.00000000E+00 Max = 0.00000000E+00)
- u-momentum component
(Min = 0.00000000E+00 Max = 0.00000000E+00)
- v-momentum component
(Min = 0.00000000E+00 Max = 0.00000000E+00)
- potential temperature
(Min = 4.86735870E+00 Max = 2.88753368E+01)
- salinity
(Min = 0.00000000E+00 Max = 3.48849592E+01)

GET_CYCLE - starting time for variable: river
is greater than current model time.
TMIN = 1.0000 TDAYS = 0.0000

Elapsed CPU time (seconds):

Node # 1 CPU: 2.660
Node # 0 CPU: 6.832
Node # 3 CPU: 1.550
Node # 5 CPU: 2.766
Node # 7 CPU: 4.752
Node # 2 CPU: 4.496
Node # 4 CPU: 5.291
Node # 6 CPU: 2.622
Node # 9 CPU: 5.387
Node # 8 CPU: 1.836
Total: 38.191

Nonlinear model elapsed time profile:

2D/3D coupling, vertical metrics ................. 0.134 ( 0.3508 %)
Omega vertical velocity .......................... 0.129 ( 0.3377 %)
Equation of state for seawater ................... 0.325 ( 0.8509 %)
Total: 0.588 1.5394

Nonlinear model message Passage profile:

Message Passage: 2D halo exchanges ............... 3.036 ( 7.9483 %)
Message Passage: 3D halo exchanges ............... 0.580 ( 1.5184 %)
Message Passage: data broadcast .................. 4.618 (12.0926 %)
Message Passage: data reduction .................. 0.126 ( 0.3299 %)
Message Passage: data scattering.................. 26.602 (69.6547 %)
Total: 34.962 91.5438

All percentages are with respect to total time = 38.191

ROMS/TOMS - Output NetCDF summary for Grid 01:

Analytical header files used:

ROMS/Functionals/ana_hmixcoef.h
ROMS/Functionals/ana_nudgcoef.h

ROMS/TOMS - Input error ............. exit_flag: 2


ERROR: Abnormal termination: NetCDF INPUT.
REASON: No error

All the input files work fine for my last version(177). I check my forcing file, the river variables are like this, also look fine.

nc{'river'} = ncdouble('river'); %% 2 elements.

nc{'s_rho'} = ncdouble('s_rho'); %% 20 elements.

nc{'river_time'} = ncdouble('river_time'); %% 360 elements.
nc{'river_time'}.long_name = ncchar('river runoff time since model initialization');
nc{'river_time'}.units = ncchar('days');
nc{'river_time'}.cycle_length = ncdouble(360);

nc{'river_Xposition'} = ncdouble('river'); %% 2 elements.
nc{'river_Xposition'}.long_name = ncchar('river runoff XI position at RHO-points');
nc{'river_Xposition'}.units = ncchar('nondimensional');

nc{'river_Eposition'} = ncdouble('river'); %% 2 elements.
nc{'river_Eposition'}.long_name = ncchar('river runoff ETA position at RHO-points');
nc{'river_Eposition'}.units = ncchar('nondimensional');

nc{'river_direction'} = ncdouble('river'); %% 2 elements.
nc{'river_direction'}.long_name = ncchar('river runoff direction');
nc{'river_direction'}.units = ncchar('nondimensional');

nc{'river_transport'} = ncdouble('river_time', 'river'); %% 720 elements.
nc{'river_transport'}.long_name = ncchar('river runoff mass transport');
nc{'river_transport'}.units = ncchar('meter3 second-1');

nc{'river_Vshape'} = ncdouble('s_rho', 'river'); %% 40 elements.
nc{'river_Vshape'}.long_name = ncchar('river runoff mass transport vertical profile');
nc{'river_Vshape'}.units = ncchar('nondimensional');

nc{'river_flag'} = ncdouble('river'); %% 2 elements.
nc{'river_flag'}.long_name = ncchar('river runoff flag');
nc{'river_flag'}.units = ncchar('nondimensional');

nc{'river_temp'} = ncdouble('river_time', 's_rho', 'river'); %% 14400 elements.
nc{'river_temp'}.long_name = ncchar('river runoff potential temperature');
nc{'river_temp'}.units = ncchar('Celsius degree');

nc{'river_salt'} = ncdouble('river_time', 's_rho', 'river'); %% 14400 elements.
nc{'river_salt'}.long_name = ncchar('river runoff salinity');
nc{'river_salt'}.units = ncchar('PSU');



Any ideas about this???

[rongzr]

I set the river time from 1day:1day:360day.This is fine for last version.For the new version, should i set it from 0 to 359 or how to solve the problem?

[rongzr]

the same error even I set the river_time from 0 to 359! Seems i have to change some other configurations when using the latest version. Any ideas??

[rongzr]

I output the variable in the get_cycle.F

Tvarname=river
Tval= 1.00000000000000 2.00000000000000
Tmin= 1.00000000000000 Tmax= 2.00000000000000

Seems it are reading the wrong variable. The Tmin and Tmax should be 1 and 360 respectively.

[das7105]

Hi rongzr,

I am getting the same problem after updating to revision 338. I run the same code as before (that ran under roms 3.0) and get an error :

"GET_CYCLE - starting time for variable: river
is greater than current model time.
TMIN = *************** TDAYS = 120.0000"

Did oyu ever resolve this problem, or find the issue? Thanks for any help,

Dave

[rongzr]

Sorry. I have no time to solve this problem right now. I think it shoulb be something related to ROMS input bug.

[das7105]

It's resolved now. In my previous runs, my river forcing file had the variable 'river' (river identification number in varinfo.dat) but never specified values for it. Apparently, this didn't cause a problem in the old code, but did when I got the latest (revision 338).

An easy fix- just specify river ID in the forcing files and all is good again...

[feroda]

It's resolved now. In my previous runs, my river forcing file had the variable 'river' (river identification number in varinfo.dat) but never specified values for it. Apparently, this didn't cause a problem in the old code, but did when I got the latest (revision 338).

An easy fix- just specify river ID in the forcing files and all is good again...

I don't quite understand what does "just specify river ID in the forcing files" mean.

*****************************************************************************************
I put two rivers into my forcing file, which is
%% Dimensions:
nc('river') = 2;

%% Variables and attributes:
nc{'river'} = ncdouble('river'); %% 2 elements.
nc{'river'}.long_name = ncchar('river runoff identification number');
nc{'river'}.units = ncchar('nondimensional');
nc{'river'}.field = ncchar('river, scalar');

By Matlab,
>> nc{'river'}(:)

ans =

1
2
*****************************************************************************************

That's what I do for the river forcing file, is it what you mean here?

But, SAME errors as posted here when I run ROMS.

Thanks

[hbzong]

By Matlab,
>> nc{'river'}(:)

ans =

1
2

[/quote]
Set the river ID starting from 0.

nc{'river'}(:) = [0,1];

[feroda]

Yes, you are right! I tested your tragedy and the model goes well in reading river forcing from the input NC file.
But, what's the reason for that the first river must be marked with "0"?

Thanks