Bug outputs frequencies wrfout and restart with adaptive time step.

[Manuarii]

Hi,

I'm using WRF 4.4, with adaptive time step, using the following specification, in namelist.input attached. I'm using 3 nested domains, that goes from 3000m to 1000m and then 111.111m.

Here I have an issues, when relauching simulation from first run, and another time from the second run.

The initial run (without restart) from 26-07 at 00:00 to 17:00, as show below, produces output without any issues. However, upon restarting for the first time, I noticed that the output now has timestamps ending in 01 instead of 00 for the seconds. Now, if I attempt to restart again (for the second time), for instance, at 23:00 on 26-07, the output files are generated every 3 seconds instead of every hour. I'm puzzled as to why this occurs. It seems to happen when I have the adaptive time step option enabled. It important to note that it happens only for the inner domain, here the third domain of my simulation.

- May 14 10:50 wrfout_d02_2078-07-26_22:00:00
- May 15 14:06 wrfout_d02_2078-07-26_23:00:00
- May 14 12:20 wrfout_d02_2078-07-27_00:00:00
- May 12 20:57 wrfout_d03_2078-07-26_00:00:00
- May 12 22:00 wrfout_d03_2078-07-26_01:00:00
- May 12 23:08 wrfout_d03_2078-07-26_02:00:00
- May 13 00:15 wrfout_d03_2078-07-26_03:00:00
- May 13 01:24 wrfout_d03_2078-07-26_04:00:00
- May 13 02:34 wrfout_d03_2078-07-26_05:00:00
- May 13 03:43 wrfout_d03_2078-07-26_06:00:00
- May 13 04:51 wrfout_d03_2078-07-26_07:00:00
- May 13 06:00 wrfout_d03_2078-07-26_08:00:00
- May 13 07:06 wrfout_d03_2078-07-26_09:00:00
- May 13 08:13 wrfout_d03_2078-07-26_10:00:00
- May 13 09:15 wrfout_d03_2078-07-26_11:00:00
- May 13 10:17 wrfout_d03_2078-07-26_12:00:00
- May 13 11:29 wrfout_d03_2078-07-26_13:00:00
- May 13 12:37 wrfout_d03_2078-07-26_14:00:00
- May 13 13:44 wrfout_d03_2078-07-26_15:00:00
- May 13 14:48 wrfout_d03_2078-07-26_16:00:00
- May 14 07:17 wrfout_d03_2078-07-26_17:00:00
- May 14 08:07 wrfout_d03_2078-07-26_18:00:01
- May 14 08:55 wrfout_d03_2078-07-26_19:00:01
- May 14 09:44 wrfout_d03_2078-07-26_20:00:01
- May 14 10:35 wrfout_d03_2078-07-26_21:00:01
- May 14 11:20 wrfout_d03_2078-07-26_22:00:01
- May 15 14:06 wrfout_d03_2078-07-26_23:00:00
- May 14 12:05 wrfout_d03_2078-07-26_23:00:01
- May 15 14:06 wrfout_d03_2078-07-26_23:00:04
- May 15 14:07 wrfout_d03_2078-07-26_23:00:07
- May 15 14:07 wrfout_d03_2078-07-26_23:00:10
- May 15 14:07 wrfout_d03_2078-07-26_23:00:13
- May 15 14:08 wrfout_d03_2078-07-26_23:00:16
- May 15 14:08 wrfout_d03_2078-07-26_23:00:20
- May 15 14:08 wrfout_d03_2078-07-26_23:00:25
- May 15 14:09 wrfout_d03_2078-07-26_23:00:29
- May 15 14:09 wrfout_d03_2078-07-26_23:00:34
- May 15 14:09 wrfout_d03_2078-07-26_23:00:40
- May 15 14:09 wrfout_d03_2078-07-26_23:00:46
- May 15 14:10 wrfout_d03_2078-07-26_23:00:49
- May 15 14:10 wrfout_d03_2078-07-26_23:00:53
- May 15 14:10 wrfout_d03_2078-07-26_23:00:57
- May 15 14:11 wrfout_d03_2078-07-26_23:01:01
- May 15 14:11 wrfout_d03_2078-07-26_23:01:06
- May 15 14:11 wrfout_d03_2078-07-26_23:01:12
- May 15 14:11 wrfout_d03_2078-07-26_23:01:17
- May 15 14:12 wrfout_d03_2078-07-26_23:01:22
- May 15 14:12 wrfout_d03_2078-07-26_23:01:27


It's worth noting that I need to restart the simulations because the job's time limit is set to 20 hours. Does anyone have a solution to address this problem?
If anyone has encountered similar issues or has insights into resolving them, I would greatly appreciate the assistance.


Manuarii Vazquez Ballesta

 

[kwerner]

Hi Manuarii,
Try adding "override_restart_timers = .true." to the &time_control namelist record and try again. Let me know if that makes a difference.

 

[Manuarii]

Hi kwerner,

Thank you very much, this seems to solve my problem ! I will be able to continue using the adaptive time step to improve my computational costs.

Manuarii