I am trying to couple WRF and ROMS in recent days,the issue is that the compute stopped after several hours,i checked all the coawst_clm.nc files and i don't know how to solve it.
the log.txt reported below.
ROMStoWRF Min/Max SST (K): -Infinity 1.207246E+03
## ROMS grid 2 sent data to WRF grid 2
## WRF grid 2 recvd data from ROMS grid 2
ROMStoWRF Min/Max SST (K): -Infinity 1.510327E+03
Timing for main: time 2018-09-01_12:00:00 on domain 1: 34.78535 elapsed seconds
Timing for main: time 2018-09-01_12:00:00 on domain 1: 34.78535 elapsed seconds
Found Error: ** Line: 1007 Source: ROMS/Utility/wrt_his.F
WRT_HIS - error while writing variable: temp
into history NetCDF file for time record: 25
Found Error: 03 Line: 181 Source: ROMS/Nonlinear/output.F
Found Error: 03 Line: 567 Source: ROMS/Nonlinear/main3d.F
Found Error: 03 Line: 331 Source: ROMS/Drivers/nl_ocean.h, ROMS_run
and i attached the whole reported error file,If any of you have some ideas to share I would be grateful.
cheers,
stan
issue with coupling WRF+ROMS , REASON: NetCDF: Numeric conversion not representable
-
- Posts: 2
- Joined: Fri Jul 07, 2023 9:24 pm
- Location: Changsha University Of Science and Technolo
issue with coupling WRF+ROMS , REASON: NetCDF: Numeric conversion not representable
- Attachments
-
- 1713510315850.png (65.96 KiB) Viewed 3451 times
-
- Posts: 2
- Joined: Fri Jul 07, 2023 9:24 pm
- Location: Changsha University Of Science and Technolo
Re: issue with coupling WRF+ROMS , REASON: NetCDF: Numeric conversion not representable
here is log.txt
- Attachments
-
- log.txt
- (3.04 MiB) Downloaded 202 times
Re: issue with coupling WRF+ROMS , REASON: NetCDF: Numeric conversion not representable
this looks like COAWST and it is probably best to post an issue over there.
but it looks to me that the model ran for a few hours, then ROMS computed Inf for SST.
So i suggest you look in the rst file, save the roms his every 20 minutes, look at the his file and see where an issue is developing.
You need to dig into the output and try to identify what is happening, where it is happening. etc.
but it looks to me that the model ran for a few hours, then ROMS computed Inf for SST.
So i suggest you look in the rst file, save the roms his every 20 minutes, look at the his file and see where an issue is developing.
You need to dig into the output and try to identify what is happening, where it is happening. etc.