weird problem with forcing file

[jsouza]

Hi all;

I am having a weird problem when trying to read wind stress into the model. Have done it several times, but this is the first I have this "error".
ROMS seams to be reading my input files, but gives me zero values of wind stress over the domain.
For example, in the log file it writes:

GET_2DFLD - surface u-momentum stress, t = 4020 00:00:00
(Rec=0004, Index=1, File: NCEP_wind_2011_2015.nc)
(Tmin= 4019.2500 Tmax= 5489.0000)
(Min = 1.00000000E+35 Max = -1.00000000E+35)

Note the max and min values make no sense, although my input files look OK.
I masked out the land in the input file using the attribute missing_value (may be the problem?). Wind stress grid (lat/lon) looks OK and is slightly larger than the model domain.
Does anyone knows what am I missing?

Cheers

[kate]

ROMS is looking for the "_FillValue" attribute, not "missing_value".

[jsouza]

Thank you Kate.

I changed it in the files, but am still getting the same error though.

[jsouza]

I am still having problems with the forcing files.
Taking the Uwind as an example, even though all the values in my files are between -20<Uwind<20 ROMS says the min and max values to be:
Min= 1e+35 Max= -1e+35.
There are no Nan's in my files.

I tried to externally interpolate the forcing files to the model grid, but still get the same error.
Please, any tips would be highly appreciate!

[kate]

ROMS isn't wont to lie about things like this. How have you checked your files to be sure all is in range? My tools of choice are ncview, ncdump -h, a Python script for finding min/max values and the i,j,k point at which they occur (which you can then double-check with ncview).

Beyond that, it's debugger time.

[jsouza]

I just loaded in MatLab and checked for Nan, max and min values.
Well, I am going to run the debug now...

[kate]

If you have some sort of special value that Matlab respects but ROMS does not, then Matlab won't help you find the problem.

[jsouza]

ncview doesn't show any problems either...

[colberg]

Have you checked that the coordinates in your forcing file are sorted from low to high values (i.e. increasing) ?

[jivica]

This is because of your meteo data are flipped up-down, and lower left coordinate is not correct. You have to make sure that lower left coordinate is (1,1), because of search/interpolate algorithm within ROMS.
Easy to check this is to make your lat coords (or lon, depending where you model and switched) flipud (or lr), as well, as your meteo data within matlab/python and save.

Ivica

[jsouza]

It works!
Thank you Ivica!