ROMS-WRF running errors
- Dominant language
- Fortran
- Stars
- 156
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
Hi, when I run a test case with ROMS and WRF, I met some problems, maybe I need some suggestions, my problems are as follow.
1. I run WRF with FNL data and ERA5-SST data, I used Vtable.ECMWF to ungrib ERA5-SST data. Actually, I'm not sure which one to choose is correct between Vtable.SST and Vtable.ECMWF
2. My grid settings are 2 for WRF and 1 for ROMS, but my WRF child grid doesn't cover all ROMS grid area. I'm wondering WRF how to receive SST(roms2wrf) from ROMS where no ROMS grid. My understanding is that when sst_update=0, it is obtained from the sst that remains unchanged in the initial field of wrf. If sst_update=1, these areas without ROMS grids are read from the provided wrflowip file for the changed sst. I don't know if this is the case.
4. Could I set different start time for wrf and roms, if ROMS needs to start before WRF to spin up a period of time?
5. My domain is China's coastal ocean, and my settings of the parameterization scheme of WRF are same as Sandy. I don't know if they're suitable.
6. When I set different coupling times, the running time of the model also varies (the same error density blow up will occur in the end). I checked the wrfout (the SST field in wrfout always has a very obvious shape of the ocean grid boundary, and the wrfout_sst.png in the attachment is a common SST distribution field) and the ocean history files separately, which are caused by overflow due to high temperature. Previously, I ran wrf at the same period of the duplicate case separately without any error messages. After coupling, it seems that the shorter the coupling time, the longer the run time can be. Therefore, I am confused whether coupling in my case makes the calculation results better or worse.
7. Should the namelist. input used in running real.exe and coawstM in wrf remain the same, as real.exe and wrf.exe in wrf are in the same directory, while in coawst they are in different locations. What modifications need to be made in namelist.input by running real.exe again to create the bry and input files? I have modified some parameters in &physics, but I am not sure if it is necessary to run real.exe again.
Below are my .h, ocean.in, namelist.input files and abnormal sst in wrfout and history.
Really thank you for any help.


[coupling.in.txt](https://github.com/DOI-USGS/COAWST/files/15094881/coupling.in.txt)
[ocean.in.txt](https://github.com/DOI-USGS/COAWST/files/15094882/ocean.in.txt)
[test.h.txt](https://github.com/DOI-USGS/COAWST/files/15094883/test.h.txt)
[namelist.input.txt](https://github.com/DOI-USGS/COAWST/files/15095030/namelist.input.txt)
Contributor guide
Research direction
Start by reviewing the attached coupling.in.txt, ocean.in.txt, test.h.txt, and namelist.input.txt files, then compare the reported wrfout SST and ocean history outputs for a reproducible coupled run. Done means narrowing the running error to a documented configuration or coupling issue and stating which settings and run sequence are supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- hpc
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100