DIA speed problem
- Dominant language
- Fortran
- Stars
- 156
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
Hello everyone. Recently I have encountered with the model blow up issue. I want to couple wrf and roms using coawst (MCT) and add tidal forcing.
(060,001,15) 5.427886E-04 5.660677E-03 1.218054E-01 3.795880E+00
5620307 57204 05:56:45 9.673046E-02 1.910431E+02 1.911399E+02 3.580927E+12 02
(061,001,01) 4.058363E-01 6.268342E-04 3.180872E-02 1.047281E+02
DIAG speed trouble 104.728058795653
Blowing-up: Saving latest model state into RESTART file
DIAG speed ijk 148.106779056467 61 1 1
2
WRT_RST - wrote re-start fields (Index=1,2) in record = 0000003 01
Blowing-up: Saving latest model state into RESTART file
WRT_RST - wrote re-start fields (Index=1,2) in record = 0000003 02
Elapsed CPU time (seconds):
I have checked the points where abnormal speeds occur. Here are the specific plots for the rst file and the v variable. However, in the plot, it appears that only one point in the u variable exceeds 100. What should I do to address this?


[run_0315.txt](https://github.com/DOI-USGS/COAWST/files/14610465/run_0315.txt)
[ocean_sandy.txt](https://github.com/DOI-USGS/COAWST/files/14610468/ocean_sandy.txt)
[sandy.txt](https://github.com/DOI-USGS/COAWST/files/14610469/sandy.txt)
Contributor guide
Research direction
Start by reviewing run_0315.txt, ocean_sandy.txt, and sandy.txt alongside the reported restart output and plots. Reproduce the WRF–ROMS COAWST run with tidal forcing, then investigate the reported abnormal speed and model blow-up; done means identifying a supported configuration or concrete cause that prevents the instability.
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