I came across a change in behavior between WRF version 3.8.1 and 3.9 that I haven't seen posted anywhere.
When cycling WRF, I use the previous cycle's 'input_outname' wrf output files to initialize the next cycle (replace the next cycle's wrfinput_d<domain> file). I had done this with 'use_adaptive_time_step" = true with version 3.8.1.
When I do the same type of cycling procedure in WRF 3.9 however, WRF completes almost instantaneously. Checking the rsl.error.* files shows that the model "skips" the time step calculations and displays a 'SUCCESS COMPLETE WRF' at the bottom. If I turn off adaptive_time_step, it will complete as normal. If I replace the 'input_outname' type file with the standard 'wrfout_' file from the previous cycle while use_adaptive_time_step is true, the simulation completes normally.
Is this a bug or a planned change in model behavior? My workflow is designed to use the 'input_outname' type files so knowing whether this will be changed is beneficial to know.
I've included two rsl.error files. rsl_error is a normal run with use_adaptive_time_step = false and also using the 'input_outname' type file. rsl_error_adapt is the same run but with use_adaptive_time_step = true. The debug is turned up quite a bit. It seems that there is a call to 'domain_clockisstoptime' that might returning true for the adaptive time step = true case but not for when adaptive time step = false.
Thanks for taking time to review this question!
When cycling WRF, I use the previous cycle's 'input_outname' wrf output files to initialize the next cycle (replace the next cycle's wrfinput_d<domain> file). I had done this with 'use_adaptive_time_step" = true with version 3.8.1.
When I do the same type of cycling procedure in WRF 3.9 however, WRF completes almost instantaneously. Checking the rsl.error.* files shows that the model "skips" the time step calculations and displays a 'SUCCESS COMPLETE WRF' at the bottom. If I turn off adaptive_time_step, it will complete as normal. If I replace the 'input_outname' type file with the standard 'wrfout_' file from the previous cycle while use_adaptive_time_step is true, the simulation completes normally.
Is this a bug or a planned change in model behavior? My workflow is designed to use the 'input_outname' type files so knowing whether this will be changed is beneficial to know.
I've included two rsl.error files. rsl_error is a normal run with use_adaptive_time_step = false and also using the 'input_outname' type file. rsl_error_adapt is the same run but with use_adaptive_time_step = true. The debug is turned up quite a bit. It seems that there is a call to 'domain_clockisstoptime' that might returning true for the adaptive time step = true case but not for when adaptive time step = false.
Thanks for taking time to review this question!