Error when restarting coupled WRF-ROMS
- Dominant language
- Fortran
- Stars
- 156
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I have successfully compiled COAWST and run a coupled WRF-ROMS test application. However, I get an issue when trying to restart the run. It seems ROMS cannot find the surface winds:
DEF_HIS - unable to find variable: Uwind in history NetCDF file: /global/cscratch1/sd/ddanso/ROMS_WRF/COAWST/Projects/Test/output/GOM_ocean_his.nc
Found Error: 03 Line: 159 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
I checked the ROMS history file and saw that both Uwind and Vwind have zero values over the whole domain. I previously run and restarted both ROMS and WRF individually in COAWST with no problems, so I am confused. Perhaps I missed something or made a mistake somewhere.
Please could you help me solve this issue? I have attached the full error log and input+header files.
Thank you.
P.S: To restart I changed,
ROMS:
NRREC from 0 to -1
LDEFOUT from T to F
ININAME to ocean_rst.nc
WRF:
The start dates
restart from false to true
-D
[coupling_out.log](https://github.com/jcwarner-usgs/COAWST/files/9182178/coupling_out.log)
[gom_h.txt](https://github.com/jcwarner-usgs/COAWST/files/9182181/gom_h.txt)
[ocean_gom_in.txt](https://github.com/jcwarner-usgs/COAWST/files/9182182/ocean_gom_in.txt)
[namelist_input.txt](https://github.com/jcwarner-usgs/COAWST/files/9182184/namelist_input.txt)
[coupling_gom_in.txt](https://github.com/jcwarner-usgs/COAWST/files/9182187/coupling_gom_in.txt)
Contributor guide
Research direction
Start by reviewing coupling_out.log alongside ocean_gom_in.txt, coupling_gom_in.txt, namelist_input.txt, and gom_h.txt, focusing on the restart settings and the missing Uwind/Vwind variables. A successful fix should allow the coupled WRF-ROMS test application to restart without the DEF_HIS error and retain valid surface-wind fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100