Abnormal termination: NetCDF INPUT

General scientific issues regarding ROMS

Moderators: arango, robertson

Post Reply
Message
Author
Study_fish
Posts: 29
Joined: Thu Sep 21, 2023 2:52 pm
Location: Sun Yat-sen University

Abnormal termination: NetCDF INPUT

#1 Unread post by Study_fish »

Hi everyone,

I have no idea about the ERROR below while I was running ROMS in my rootdir /COAWST_master:

Code: Select all

Found Error: 02   Line: 55       Source: ROMS/Utility/close_io.F, close_inp.F

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

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


 ERROR: Abnormal termination: NetCDF INPUT.
 REASON: No error
Note: The following floating-point exceptions are signalling: IEEE_DIVIDE_BY_ZERO
ERROR STOP
I have seen a similar ERROR discussed in the old post,however it may be a little bit difference in my case.here is my roms.log for more details.

Thanks all
Attachments
roms.log
(71.02 KiB) Downloaded 290 times

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

Re: Abnormal termination: NetCDF INPUT

#2 Unread post by jcwarner »

keep looking in your file, it says

"INQUIRY - unable to find requested variable: EminusP
in file:
Projects/UPWELLING/ROMS_forcing.nc"

Study_fish
Posts: 29
Joined: Thu Sep 21, 2023 2:52 pm
Location: Sun Yat-sen University

Re: Abnormal termination: NetCDF INPUT

#3 Unread post by Study_fish »

The problem you have mentioned seems like a key point.Actually , I use

Code: Select all

/COAWST/Tools/mfiles/mtools/create_roms_forcings.m


to generate my roms_forcing Netcdf file, but it doesn't seem to have variable "EminusP". I wonder what variables are necessary for forcing files to be entered into the ROMS? Is there some way I can know the standard input format for these variables? Thank you for your reply!

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

Re: Abnormal termination: NetCDF INPUT

#4 Unread post by jcwarner »

here is some help.
viewtopic.php?t=2930

Study_fish
Posts: 29
Joined: Thu Sep 21, 2023 2:52 pm
Location: Sun Yat-sen University

Re: Abnormal termination: NetCDF INPUT

#5 Unread post by Study_fish »

Thanks for your provided information! Now I've known the reason of the occuried ERROR:EminusP does not exist in my forcing file.To simplify my case, I decided to first use ana_stflux instead of the actual surface freshwater flux. Now I've made some changes to my.h file and recompiled it:

Code: Select all

#define ROMS_MODEL

#define UV_ADV
#define UV_COR
#define UV_LDRAG
#define UV_VIS2
#define CURVGRID
#define SPLINES_VVISC

#define SALINITY
#define TS_DIF2
#undef  TS_DIF4
#define NONLIN_EOS
#define SPLINES_VDIFF

#define DJ_GRADPS

#define BULK_FLUXES

#define DIAGNOSTICS_TS
#define DIAGNOSTICS_UV

#define SOLVE3D
#define MASKING
#define SPHERICAL
#undef  MIX_GEO_UV
#define MIX_S_UV
#undef  MIX_GEO_TS
#define MIX_S_TS

#define AVERAGES
#undef HISTORY2
#undef  ANA_GRID
#undef  ANA_INITIAL
#define ANA_SMFLUX
#define ANA_BTFLUX
#define ANA_BSFLUX
#define ANA_STFLUX
#define ANA_SSFLUX
#undef  EminusP

#define LMD_MIXING
#define LMD_SKPP
#define LMD_BKPP
#define LMD_NONLOCAL
However,When I re-ran coawstM, something happened that confused me:

Code: Select all

 TIME-STEP YYYY-MM-DD hh:mm:ss.ss  KINETIC_ENRG   POTEN_ENRG    TOTAL_ENRG    NET_VOLUME
                     C => (i,j,k)       Cu            Cv            Cw         Max Speed

         0 2022-07-01 12:00:00.00           NaN  1.518267E+04           NaN  1.236598E+15
                    (1099,250,40)  7.504801E-01  9.817527E-01  0.000000E+00  1.380963E+00
 Found Error: 01   Line: 341      Source: ROMS/Nonlinear/main3d.F
 Found Error: 01   Line: 331      Source: ROMS/Drivers/nl_ocean.h, ROMS_run
...
 Found Error: 01   Line: 55       Source: ROMS/Utility/close_io.F, close_inp.F

 ROMS/TOMS - Output NetCDF summary for Grid 01:

 Analytical header files used:

     ROMS/Functionals/ana_btflux.h
     ROMS/Functionals/ana_stflux.h
 Found Error: 01   Line: 437      Source: ROMS/Utility/close_io.F, close_out

 ROMS/TOMS - Blows up ................ exit_flag: 1

Note: The following floating-point exceptions are signalling: IEEE_INVALID_FLAG IEEE_DIVIDE_BY_ZERO
ERROR STOP
Is there something wrong with my forcing files?
Attachments
roms.log
(91.98 KiB) Downloaded 265 times
upwelling.h
(1.23 KiB) Downloaded 307 times

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

Re: Abnormal termination: NetCDF INPUT

#6 Unread post by wilkin »

Your log shows ,,,
Maximum barotropic Courant Number = 9.00832155E+00
which seems much too large, but I can't where that comes from on the basis of initial conditions.
John Wilkin: DMCS Rutgers University
71 Dudley Rd, New Brunswick, NJ 08901-8521, USA. ph: 609-630-0559 jwilkin@rutgers.edu

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

Re: Abnormal termination: NetCDF INPUT

#7 Unread post by jcwarner »

192 ntimes Number of timesteps for 3-D equations.
900.000 dt Timestep size (s) for 3-D equations.
30 ndtfast Number of timesteps for 2-D equations between
each 3D timestep.

roms time step should be a lot smaller. i see you have ~1km spacing.
try 90 sec or something like that to start.

Study_fish
Posts: 29
Joined: Thu Sep 21, 2023 2:52 pm
Location: Sun Yat-sen University

Re: Abnormal termination: NetCDF INPUT

#8 Unread post by Study_fish »

It seemed like a problem I hadn't noticed before. I will try to adjust my model domain size and time step to start over.I really appreciate u taking time to explain everything to me!

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

Re: Abnormal termination: NetCDF INPUT

#9 Unread post by jcwarner »

i think you can start out by first adjusting the time step. and see if you can get the configuration you have to run.

Study_fish
Posts: 29
Joined: Thu Sep 21, 2023 2:52 pm
Location: Sun Yat-sen University

Re: Abnormal termination: NetCDF INPUT

#10 Unread post by Study_fish »

Hey, guys, I'm back.

I reduced the size of the model domain and time step, and enabled ANA_NUDGCOEF in my.h file with the goal of nudging just at the boundary.

When i rerun coawstM, fortunately it finally began to run, but after a couple of baroclinic time step, error happened:

Code: Select all

DIAG speed trouble    24.795668439173749
 Found Error: 01   Line: 341      Source: ROMS/Nonlinear/main3d.F
 Found Error: 01   Line: 331      Source: ROMS/Drivers/nl_ocean.h, ROMS_run

 Blowing-up: Saving latest model state into  RESTART file
     REASON: MaxSpeed =  2.5E+01

 DIAG speed ijk    20.680908753216158              589           5           1           1
      WRT_RST     - wrote re-start    fields (Index=1,1) in record = 1
I have two places did not understand. First, based on Kate's responses in previous posts, I set TNUDG and OBCFAC to 360 and 120 respectively to activate nudging of LBC. However, I did not set the
values for Znudg, M2nudg, and M3nudg, as these values are only valid if clm nudging is enabled. The question I would like to ask is: in general, what is a rational value to set for these nudging
time scales? Does the model blow up have anything to do with the fact that I set these values incorrectly?

Second, according to the error message, mode should be the problems when calculating the baroclinic equations. My friend told me that maybe the parameter in the ROMS/Drivers/nl ocean.h file is not set properly, but I am not sure. Guys, can you give me some help?

Thank you for your attention :D
Attachments
upwelling.h
(1.21 KiB) Downloaded 321 times
roms_upwelling.in
(100.41 KiB) Downloaded 262 times
roms.log
(98.31 KiB) Downloaded 282 times

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

Re: Abnormal termination: NetCDF INPUT

#11 Unread post by jcwarner »

12 2022-07-01 12:18:00.00 2.693400E-02 5.341908E+03 5.341935E+03 4.910017E+13
(588,005,03) 4.670190E-01 2.073180E-01 2.452327E+00 2.479567E+01
DIAG speed trouble 24.795668439173749
DIAG speed ijk 20.680908753216158 589 5 1 1
Blowing-up: Saving latest model state into RESTART file
REASON: MaxSpeed = 2.5E+01

WRT_RST - wrote re-start fields (Index=1,1) in record = 1

Suggest you look at the restart file. that is what the message is suggesting.
the error was near i=589 j=5 z=1 grid 1
ncview the rst file and see what is going on.

Study_fish
Posts: 29
Joined: Thu Sep 21, 2023 2:52 pm
Location: Sun Yat-sen University

Re: Abnormal termination: NetCDF INPUT

#12 Unread post by Study_fish »

Thank you jcwarner for your answer.

i used ncview to check my rst file,found that abnormal salinity existed at the southeast corner of my study area.i wonder why sal value particularly low in this place,without I/O related problem? Is it the boundary conditions that cause it?

Image

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

Re: Abnormal termination: NetCDF INPUT

#13 Unread post by jcwarner »

ok. now you know what is happening. next is to figure out why it is happening.
it blew up in 12 time steps, so save every his step, and watch what happens in that corner.
what are the sal and temp in your bc files?
I personally do not use A4 advection, i use U3. maybe try different advection or diff bc's there.

Study_fish
Posts: 29
Joined: Thu Sep 21, 2023 2:52 pm
Location: Sun Yat-sen University

Re: Abnormal termination: NetCDF INPUT

#14 Unread post by Study_fish »

Thank you very much for your valuable advice! I'll give it a try right now.

Post Reply