input forcing files

General scientific issues regarding ROMS

Moderators: arango, robertson

Post Reply
Message
Author
Scarlett
Posts: 48
Joined: Tue Aug 04, 2015 4:42 pm
Location: Universidad del Mar (UMAR), Mexico
Contact:

input forcing files

#1 Unread post by Scarlett »

Hi everybody
I have had some problems with my inputs forcing files.
I have 3 forcing files, one for general forcing "GT_gnfrc.nc", one for tidal forcing "GT_tidfrc.nc" and the lastone for winds "GT_wind2003.nc". But ROMS only read one.

Here is my setting up in my **.in file
******************************************************************************
NFFILES == 3 ! number of unique forcing files

FRCNAME == /media/Ahumada2016/HyCom_Tehua_Scar/GT_tidfrc.nc\
FRCNAME == /media/Ahumada2016/HyCom_Tehua_Scar/GT_genfrc.nc\
FRCNAME == /media/Ahumada2016/HyCom_Tehua_Scar/GT_wind2003.nc

the output is as follow
***************************************************************************

Output/Input Files:

Output Restart File: /home/ahumada/Roms_tools/Run/SCRATCH/ocean_rst.nc
Output History File: /home/ahumada/Roms_tools/Run/SCRATCH/ocean_his.nc
Output Averages File: /home/ahumada/Roms_tools/Run/SCRATCH/ocean_avg.nc
Input Grid File: /media/Ahumada2016/HyCom_Tehua_Scar/GT_roms_grd.nc
Input Nonlinear Initial File: /media/Ahumada2016/HyCom_Tehua_Scar/GT_inic.nc
Input Forcing File 01: /media/Ahumada2016/HyCom_Tehua_Scar/GT_wind2003.nc

READ_PHYPAR - could not find input file: T

Elapsed CPU time (seconds):


ROMS/TOMS - Output NetCDF summary for Grid 01:

ROMS/TOMS - I/O error ............... exit_flag: 4


ERROR: I/O related problem.


Could someone help me?
I have already tried changing the order of the files and removing the symbol (\).
Any kind of help I will be very grateful. Thanks in advance.

Mar.Mo.

jcwarner
Posts: 1172
Joined: Wed Dec 31, 2003 6:16 pm
Location: USGS, USA

Re: input forcing files

#2 Unread post by jcwarner »

try this
NFFILES == 3 ! number of unique forcing files

FRCNAME == /media/Ahumada2016/HyCom_Tehua_Scar/GT_tidfrc.nc \
/media/Ahumada2016/HyCom_Tehua_Scar/GT_genfrc.nc \
/media/Ahumada2016/HyCom_Tehua_Scar/GT_wind2003.nc

depending on the version of roms, the newer version wants the tidal forc to be listed separately.

Scarlett
Posts: 48
Joined: Tue Aug 04, 2015 4:42 pm
Location: Universidad del Mar (UMAR), Mexico
Contact:

Re: input forcing files

#3 Unread post by Scarlett »

Hi jcwarner!
So many thanks for your quick response, it worked, almost.
Now I have other error.
***********************************************************************************************
...
Minimum barotropic Courant Number = 2.71230438E-01
Maximum barotropic Courant Number = 7.65529758E-01
Maximum Coriolis Courant Number = 2.70719381E-02


NETCDF_CHECK_VAR - inconsistent value of variable: Tcline 1.500000E+02 1.000000E+01
in file: /media/Ahumada2016/HyCom_Tehua_Scar/GT_inic.nc

Elapsed CPU time (seconds):

Thread # 11 CPU: 0.218
Thread # 14 CPU: 0.218
Thread # 23 CPU: 0.218
Thread # 4 CPU: 0.218
Thread # 6 CPU: 0.218
Thread # 16 CPU: 0.218
Thread # 17 CPU: 0.218
Thread # 2 CPU: 0.218
Thread # 19 CPU: 0.218
Thread # 21 CPU: 0.218
Thread # 8 CPU: 0.218
Thread # 10 CPU: 0.218
Thread # 13 CPU: 0.218
Thread # 22 CPU: 0.218
Thread # 3 CPU: 0.218
Thread # 1 CPU: 0.218
Thread # 12 CPU: 0.218
Thread # 9 CPU: 0.218
Thread # 15 CPU: 0.218
Thread # 7 CPU: 0.218
Thread # 20 CPU: 0.218
Thread # 18 CPU: 0.218
Thread # 0 CPU: 0.218
Thread # 5 CPU: 0.218
Total: 5.238

Nonlinear model elapsed time profile, Grid: 01

Allocation and array initialization .............. 99.968 (******* %)
Total: 99.968 ********

All percentages are with respect to total time = 5.238


ROMS/TOMS - Output NetCDF summary for Grid 01:

ROMS/TOMS - Configuration error ..... exit_flag: 5


ERROR: Illegal model configuration.

***********************************************************************************
Have you have some idea about this? Could you help me? I'm working with roms-3.7.
So many thanks in advance.

Mar.Mo.

jcwarner
Posts: 1172
Joined: Wed Dec 31, 2003 6:16 pm
Location: USGS, USA

Re: input forcing files

#4 Unread post by jcwarner »

check the values of Tcline in your ocean.in and the media/Ahumada2016/HyCom_Tehua_Scar/GT_inic.nc file.
these all need to be the same.

Scarlett
Posts: 48
Joined: Tue Aug 04, 2015 4:42 pm
Location: Universidad del Mar (UMAR), Mexico
Contact:

Re: input forcing files

#5 Unread post by Scarlett »

Jcwarner, you have all the reason. It works. Sorry, I had not read well:

NETCDF_CHECK_VAR - inconsistent value of variable: Tcline 1.500000E+02 1.000000E+01

Thanks a lot.

Mar.Mo.

Post Reply