INP_PAR, PHYPAR: Problems finding input file.

Discussion about tangent linear and adjoint models, variational data assimilation, and other related issues.

Moderators: arango, robertson

Post Reply
Message
Author
birgitrr
Posts: 4
Joined: Mon Jun 21, 2021 12:40 pm
Location: Ranold AS

INP_PAR, PHYPAR: Problems finding input file.

#1 Unread post by birgitrr »

Hi! I have spent some time trying to get to know ROMS, but unfortunately I can't seem to configure/run the model on my case (which is a freshwater lake). I am very new to modeling, and I suspect that this error could be easily fixed - by someone who is not me, apparently.

When trying to run, I get this error message:

INP_PAR:FIND_FILE - empty file name string for standard input script KeyWord: SSFNAME
Found Error: 05 Line: 434 Source: ROMS/Utility/inp_decode.F, find_file

READ_PHYPAR - Grid 01, could not find input file: Oops unassigned file name. Check standard input script...
Found Error: 04 Line: 6728 Source: ROMS/Utility/read_phypar.F
Found Error: 04 Line: 201 Source: ROMS/Utility/inp_par.F
Found Error: 04 Line: 124 Source: ROMS/Drivers/nl_roms.h, ROMS_initialize

I have tried to look through my headerfile and .in-file, without luck, and I cannot find where SSFNAME is set.

My headerfile looks like this:

** Options for Closed Basin (Lake) forced with wind.
**
** Application flag: NORSJO_TEST
** Input script: ocean_n_test.in
*/

#define UV_ADV
#define UV_COR
#define DJ_GRADPS
#define SPLINES_VDIFF
#define SPLINES_VVISC
#define TS_MPDATA
#define SALINITY
#define SOLVE3D
#define MASKING
#define AVERAGES
#define FLOATS
#define SSW_BBL
#ifdef SSW_BBL
# define SSW_CALC_UB
# define SSW_CALC_ZNOT
# undef SSW_LOGINT
#endif
#define GET_GRID
#define GET_STATE
#define ANA_SMFLUX
#define ANA_SSFLUX
#define ANA_BTFLUX
#define GLS_MIXING
#if defined GLS_MIXING
# define KANTHA_CLAYSON
# define N2S2_HORAVG
# define RI_SPLINES
#endif

The .in-file is of course long and full of possible errors, but my input-files are included like this:

! Input NetCDF file names, [1:Ngrids].

GRDNAME == /home/birgit/ROMS_scripts/Grid/norsjo.nc
ININAME == /home/birgit/ROMS_scripts/Init/norsjo_init.nc

NFFILES == 1 ! number of forcing files

FRCNAME == /home/birgit/ROMS_scripts/Forcing_data/Scripts/Output/norsjo_forcing_150.nc

! Output NetCDF file names, [1:Ngrids].

RSTNAME == /home/birgit/my_roms_projects/norsjo/norsjo_rst.nc
HISNAME == /home/birgit/my_roms_projects/norsjo/norsjo_rst.nc
AVGNAME == /home/birgit/my_roms_projects/norsjo/norsjo_avg.nc

Do any of you guys have an idea on where to start?

Sincerely, Birgit

User avatar
kate
Posts: 4088
Joined: Wed Jul 02, 2003 5:29 pm
Location: CFOS/UAF, USA

Re: INP_PAR, PHYPAR: Problems finding input file.

#2 Unread post by kate »

INP_PAR:FIND_FILE - empty file name string for standard input script KeyWord: SSFNAME
Do you have a line for SSFNAME? That is a newish requirement.

birgitrr
Posts: 4
Joined: Mon Jun 21, 2021 12:40 pm
Location: Ranold AS

Re: INP_PAR, PHYPAR: Problems finding input file.

#3 Unread post by birgitrr »

Thank you for answering, I had to add the SSFNAME. Now I am one step closer to making the model run!
My error now looks like this:

INITIAL: Configuring and initializing forward nonlinear model ...
*******
GET_GRID - Illegal output type, io_type = 0
Found Error: 03 Line: 90 Source: ROMS/Utility/get_grid.F
Found Error: 03 Line: 82 Source: ROMS/Utility/set_grid.F
GET_STATE - Illegal output type, io_type = 0
Found Error: 03 Line: 151 Source: ROMS/Utility/get_state.F
Found Error: 03 Line: 417 Source: ROMS/Nonlinear/initial.F
Found Error: 03 Line: 200 Source: ROMS/Drivers/nl_roms.h, ROMS_initialize

Elapsed wall CPU time for each process (seconds):

Thread # 0 CPU: 5.059
Total: 5.059

Nonlinear model elapsed CPU time profile, Grid: 01

Allocation and array initialization .............. 5.059 (99.9936 %)
Total: 5.059 99.9936 %

Unique kernel(s) regions profiled ................ 5.059 99.9936 %
Residual, non-profiled code ...................... 0.000 0.0064 %


All percentages are with respect to total time = 5.059


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Dynamic and Automatic memory (MB) usage for Grid 01: 150x150x30 tiling: 1x1

tile Dynamic Automatic USAGE

0 270.10 42.40 312.50

TOTAL 270.10 42.40 312.50

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Found Error: 03 Line: 85 Source: ROMS/Utility/close_io.F, close_file_nf90
Found Error: 03 Line: 85 Source: ROMS/Utility/close_io.F, close_file_nf90
Found Error: 03 Line: 85 Source: ROMS/Utility/close_io.F, close_file_nf90
Found Error: 03 Line: 85 Source: ROMS/Utility/close_io.F, close_file_nf90

ROMS/TOMS - Output NetCDF summary for Grid 01:
Found Error: 03 Line: 381 Source: ROMS/Utility/close_io.F, close_out

ROMS/TOMS - Output error ............ exit_flag: 3


ERROR: Abnormal termination: NetCDF OUTPUT.
REASON: No error
ERROR STOP

Error termination. Backtrace:
#0 0x7f338807ad21 in ???
#1 0x7f338807b869 in ???
#2 0x7f338807cf97 in ???
#3 0x55dc167099bf in myroms
at /home/birgit/my_roms_projects/norsjo/Build_romsG/master.f90:101
#4 0x55dc16709a18 in main
at /home/birgit/my_roms_projects/norsjo/Build_romsG/master.f90:50

I made my grid with pygridgen, and I thnk the grid itself should be fine. I use "#define GET_GRID" in my headerfile, and have the correct path to the grid in my .in-file. Do you have an idea of what i missed?
(Also, thanks for being so tolerant with all our questions!!)

User avatar
arango
Site Admin
Posts: 1347
Joined: Wed Feb 26, 2003 4:41 pm
Location: DMCS, Rutgers University
Contact:

Re: INP_PAR, PHYPAR: Problems finding input file.

#4 Unread post by arango »

ROMS is telling you what it is wrong:
GET_GRID - Illegal output type, io_type = 0
Make sure that your roms.in is up to date.

User avatar
kate
Posts: 4088
Joined: Wed Jul 02, 2003 5:29 pm
Location: CFOS/UAF, USA

Re: INP_PAR, PHYPAR: Problems finding input file.

#5 Unread post by kate »

Is it in the roms.in or in the grid file? My grid file has:

Code: Select all

// global attributes:
		:type = "ROMS grid file" ;

User avatar
arango
Site Admin
Posts: 1347
Joined: Wed Feb 26, 2003 4:41 pm
Location: DMCS, Rutgers University
Contact:

Re: INP_PAR, PHYPAR: Problems finding input file.

#6 Unread post by arango »

I don't think so. This is because of the PIO library support changes to ROMS. For some reason, inp_type in roms.in is zero. It is weird because it is initialized to zero internally if the user doesn't specified a value.

birgitrr
Posts: 4
Joined: Mon Jun 21, 2021 12:40 pm
Location: Ranold AS

Re: INP_PAR, PHYPAR: Problems finding input file.

#7 Unread post by birgitrr »

Hey,

I also beleive that I didn't make my roms.in-file correctly. Even if I am aware of the error message "GET_GRID - Illegal output type, io_type = 0", it is not clear to me how to "make sure my roms.in is up to date". My grid-file is included like this:

GRDNAME == /home/birgit/ROMS_scripts/Grid/norsjo.n

Do I have to state anything more for ROMS to read the file? I tried looking at multiple other example roms.in-files, but cannot find anything that seems obvious to me.

Again, thank you for your time!

User avatar
wilkin
Posts: 872
Joined: Mon Apr 28, 2003 5:44 pm
Location: Rutgers University
Contact:

Re: INP_PAR, PHYPAR: Problems finding input file.

#8 Unread post by wilkin »

it is not clear to me how to "make sure my roms.in is up to date". My grid-file is included like this:
Start from one of the example roms.in files in a recent version of the code, and work your way through adding the options you want. This is a safe way to make sure the file is complete, and that you have taken active control of all the options you set.

I notice you have in your .h #define TS_MPDATA. Advection scheme options are now set in roms.in and that #define does nothing.
John Wilkin: DMCS Rutgers University
71 Dudley Rd, New Brunswick, NJ 08901-8521, USA. ph: 609-630-0559 jwilkin@rutgers.edu

Post Reply