Error in ROMS execution

[s.celestino]

I'm running the WC12 test case, I got this error:

Code: Select all

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


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

Is there a legend from which you can read what kind of error it is?

Thanks in advance.

[haidong]

It seem that having something wrong in your Input file. Maybe is stress file or time. You should send more information.

[kate]

If you scroll up in the output, there may or may not be more useful information. It's worth a look at least.

[arango]

Provide more information from the log file, not just the end. If you are using the latest version of ROMS, there is detailed information in the log file with source code and line number where the error occurred.

[s.celestino]

Provide more information from the log file, not just the end. If you are using the latest version of ROMS, there is detailed information in the log file with source code and line number where the error occurred.

Here the log output. The error seems to be here:

Code: Select all

SET_2DFLD  - current model time exceeds ending value for variable: zeta
              TDAYS     =      13295.0000
              Data Tmin =      12483.0000  Data Tmax =      12484.0000
              Data Tstr =      12484.0000  Data Tend =      12484.0000
              TINTRP1   =          0.0000  TINTRP2   =      12484.0000
              FAC1      =       -811.0000  FAC2      =      13295.0000

Thanks.

[arango]

There is a weird set-up of the ROMS time clock here. You need to ask the person that set-up this application. First, the input parameters:

Code: Select all

  13295.000  dstart            Time-stamp assigned to model initialization (days).
19000101.00  time_ref          Reference time for units attribute (yyyymmdd.dd)

It implies that the ROMS base time (time_ref) from is Jan 1, 1900. The model is initialized on Mar 7, 1934 (1934-03-07 00:00:00.00). That is, 12483 days after Jan 1, 1900 as specified by the time_ref parameter. ROMS internal time coordinates are meassured as days or seconds since time_ref. The dstart is set-up as 13295, which corresponds to May 27, 1936. That is, 812 days after initial conditions

Now, if you look at the input forcing filenames,

Code: Select all

    GET_2DFLD   - surface u-momentum stress,                       1934-03-06 12:30:00.00
                   (Grid=01, Rec=0001303, Index=1, File: coamps_wc12.0_stress_19990101_20050120_tave24.nc)
                   (Tmin=      11180.5208 Tmax=      13391.5208)      t =      12482.5208

according with the filename we have wind stress data form 1999-01-01 to 2005-01-20 (coamps_wc12.0_stress_19990101_20050120_tave24.nc)

No wonder why ROMS is complaining. You need to modify DSTART and TIME_REF parameters in ocean.in to make sure that the base reference time (time_ref) is the same used to process all the input data. I really doubt that the assimation was started since 1934.

The time clock reporting inside ROMS was changed recently to provide more meaningful dates than just number to avoid issues in the set-up like the shown here.

This a data assimilation application. One must examine time clocks very carefully and be consistent with all the input data.

[s.celestino]

I don't know if I understood weel but:

- TIME_REF represent the starting days of the forcing file
- DSTART is the number of days from the TIME_REF

I have changed the ocean.in file according with your suggestion, DSTART is now: 12483. But ROMS ends with this other error:

Code: Select all

NETCDF_GET_IVAR_1D - error while inquiring ID for variable:  obs_provenance
                      in input file:  obs.nc
                      call from:  obs_read.F

something wrong with the observation file? In the log file I find also:

Code: Select all

NLM: GET_STATE - Reading state initial conditions,                2024-03-06 00:00:00.00

2024? Where am I wrong?

[arango]

You cannot change those values capriciously. They have to be exactly the same values used by the person that generated the initial conditions, boundary conditions, atmospheric forcing, and observations for data assimilation. The time clock has to be the same in all those files for consistency. The time in ROMS is measured as seconds or days from the reference time (time_ref) that was chosen for this application. Otherwise, this will not work! Check the NetCDF files and look for the time variables. The information that you seek is in the variable attributes.