RCarpenter
Member
I have set step_to_output_time and adjust_output_times so that WRF will output at the desired hourly interval (filename rounded to nearest hour). However the wrfoutReady files are not obeying this. In the example below, you can see that the ready file is 11 sec later than the history file. Thank you.
wrfout_d02_2018-07-03_13:00:00
wrfoutReady_d02_2018-07-03_13:00:11
Timing for main (dt= 7.97): time 2018-07-03_12:59:32 on domain 3: 0.10429 elapsed seconds
Timing for main (dt= 7.97): time 2018-07-03_12:59:40 on domain 3: 0.09938 elapsed seconds
Timing for main (dt= 7.97): time 2018-07-03_12:59:48 on domain 3: 0.09993 elapsed seconds
Timing for main (dt= 23.91): time 2018-07-03_12:59:48 on domain 2: 0.44077 elapsed seconds
Timing for main (dt= 7.97): time 2018-07-03_12:59:56 on domain 3: 0.10513 elapsed seconds
Timing for main (dt= 7.97): time 2018-07-03_13:00:04 on domain 3: 0.09929 elapsed seconds
Timing for Writing wrfout_d03_2018-07-03_13:00:00 for domain 3: 0.31473 elapsed seconds
Timing for main (dt= 7.97): time 2018-07-03_13:00:11 on domain 3: 6.49053 elapsed seconds
Timing for main (dt= 23.91): time 2018-07-03_13:00:11 on domain 2: 6.83432 elapsed seconds
Timing for main (dt= 95.65): time 2018-07-03_13:00:00 on domain 1: 8.45433 elapsed seconds
Timing for Writing wrfout_d01_2018-07-03_13:00:00 for domain 1: 6.60405 elapsed seconds
d01 2018-07-03_13:00:00 Input data is acceptable to use: wrfbdy_d01
Timing for processing lateral boundary for domain 1: 9.57743 elapsed seconds
Timing for Writing wrfout_d02_2018-07-03_13:00:00 for domain 2: 2.53546 elapsed seconds
Timing for main (dt= 7.79): time 2018-07-03_13:00:19 on domain 3: 0.10429 elapsed seconds
Timing for main (dt= 7.79): time 2018-07-03_13:00:27 on domain 3: 0.09974 elapsed seconds
Timing for main (dt= 7.79): time 2018-07-03_13:00:35 on domain 3: 0.10099 elapsed seconds
Timing for main (dt= 23.37): time 2018-07-03_13:00:35 on domain 2: 12.38588 elapsed seconds
Timing for main (dt= 7.79): time 2018-07-03_13:00:43 on domain 3: 0.10413 elapsed seconds
Timing for main (dt= 7.79): time 2018-07-03_13:00:50 on domain 3: 0.51537 elapsed seconds
wrfout_d02_2018-07-03_13:00:00
wrfoutReady_d02_2018-07-03_13:00:11
Timing for main (dt= 7.97): time 2018-07-03_12:59:32 on domain 3: 0.10429 elapsed seconds
Timing for main (dt= 7.97): time 2018-07-03_12:59:40 on domain 3: 0.09938 elapsed seconds
Timing for main (dt= 7.97): time 2018-07-03_12:59:48 on domain 3: 0.09993 elapsed seconds
Timing for main (dt= 23.91): time 2018-07-03_12:59:48 on domain 2: 0.44077 elapsed seconds
Timing for main (dt= 7.97): time 2018-07-03_12:59:56 on domain 3: 0.10513 elapsed seconds
Timing for main (dt= 7.97): time 2018-07-03_13:00:04 on domain 3: 0.09929 elapsed seconds
Timing for Writing wrfout_d03_2018-07-03_13:00:00 for domain 3: 0.31473 elapsed seconds
Timing for main (dt= 7.97): time 2018-07-03_13:00:11 on domain 3: 6.49053 elapsed seconds
Timing for main (dt= 23.91): time 2018-07-03_13:00:11 on domain 2: 6.83432 elapsed seconds
Timing for main (dt= 95.65): time 2018-07-03_13:00:00 on domain 1: 8.45433 elapsed seconds
Timing for Writing wrfout_d01_2018-07-03_13:00:00 for domain 1: 6.60405 elapsed seconds
d01 2018-07-03_13:00:00 Input data is acceptable to use: wrfbdy_d01
Timing for processing lateral boundary for domain 1: 9.57743 elapsed seconds
Timing for Writing wrfout_d02_2018-07-03_13:00:00 for domain 2: 2.53546 elapsed seconds
Timing for main (dt= 7.79): time 2018-07-03_13:00:19 on domain 3: 0.10429 elapsed seconds
Timing for main (dt= 7.79): time 2018-07-03_13:00:27 on domain 3: 0.09974 elapsed seconds
Timing for main (dt= 7.79): time 2018-07-03_13:00:35 on domain 3: 0.10099 elapsed seconds
Timing for main (dt= 23.37): time 2018-07-03_13:00:35 on domain 2: 12.38588 elapsed seconds
Timing for main (dt= 7.79): time 2018-07-03_13:00:43 on domain 3: 0.10413 elapsed seconds
Timing for main (dt= 7.79): time 2018-07-03_13:00:50 on domain 3: 0.51537 elapsed seconds