You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Timing for main (dt=600.00): time 0001-01-01_02:50:00 on domain 1: 0.16676 elapsed seconds
Timing for main (dt=600.00): time 0001-01-01_03:00:00 on domain 1: 0.16646 elapsed seconds
Timing for main (dt= 0.00): time 0001-01-01_03:00:00 on domain 1: 0.16646 elapsed seconds
d01 0001-01-01_03:00:00 wrf: SUCCESS COMPLETE WRF
Also for other test cases, the simulation terminates after 3 hours, e.g. em_quarter_ss if you put more than 3 hours as simulation time.
Expected behavior
WRF should run until end_hour is reached (5 days for test/em_b_wave).
Screenshots
If applicable, add screenshots to help explain your problem.
Attachments
If applicable, attach supporting files: namelist.input, rsl.* files, etc.
Additional context
Add any other context about the problem here, such as:
This should be fixed by a bug fix in WRF4.3 as documented in the updates, right?
Hi @lkugler,
We have tracked down the bug, but haven't coded a fix yet. Please see your post on our User's Forum for information regarding a work-around for now. Thank you so much for bringing this issue to our attention!
Describe the bug
The use of adaptive time steps leads to WRF stopping before namelist's end of simulation with
SUCCESS COMPLETE WRF
anddt=0
.To Reproduce
Steps to reproduce the behavior:
icc version 19.1.0.166 (gcc version 4.8.5 compatibility)
Also for other test cases, the simulation terminates after 3 hours, e.g. em_quarter_ss if you put more than 3 hours as simulation time.
Expected behavior
WRF should run until end_hour is reached (5 days for test/em_b_wave).
Screenshots
If applicable, add screenshots to help explain your problem.
Attachments
If applicable, attach supporting files: namelist.input, rsl.* files, etc.
Additional context
Add any other context about the problem here, such as:
configure.wrf.txt
namelist.input.txt
The text was updated successfully, but these errors were encountered: