Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

Adaptive time-step has wrfout half-hour times varying from expected

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

A

allenea

New member
Does anyone have a clue why my wrfout times might differ by the second on the half hour and how might I fix it? Before I used the adaptive timestep I didn't have this issue.

I have data being output every 30 minutes on the 2nd and 3rd domain, and then every 60 minutes for domain 1.

input_from_file = .true., .true., .true.,
history_interval = 60, 30, 30,

use_adaptive_time_step = .true.,
adaptation_domain = 1,
step_to_output_time = .true.,
target_cfl = 1.2, 1.2, 1.2,
target_hcfl = 0.84, 0.84, 0.84,
max_step_increase_pct = 5, 51, 51,
starting_time_step = -1, -1, -1,
max_time_step = -1, -1, -1,
min_time_step = -1, -1, -1,

data:

Times =
"2014-06-03_12:00:00",
"2014-06-03_12:30:00",
"2014-06-03_13:00:00",
"2014-06-03_13:30:00",
"2014-06-03_14:00:00",
"2014-06-03_14:30:00",
"2014-06-03_15:00:00",
"2014-06-03_15:30:00",
"2014-06-03_16:00:00",
"2014-06-03_16:30:00",
"2014-06-03_17:00:00",
"2014-06-03_17:30:01",
"2014-06-03_18:00:00",
"2014-06-03_18:30:02",
"2014-06-03_19:00:00",
"2014-06-03_19:30:00",
"2014-06-03_20:00:00",
"2014-06-03_20:30:04",
"2014-06-03_21:00:00",
"2014-06-03_21:30:01",
"2014-06-03_22:00:00",
"2014-06-03_22:30:03",
"2014-06-03_23:00:00",
"2014-06-03_23:30:07",
"2014-06-04_00:00:00",
"2014-06-04_00:30:04",
"2014-06-04_01:00:00",
"2014-06-04_01:30:05",
"2014-06-04_02:00:00",
"2014-06-04_02:30:03",
"2014-06-04_03:00:00",
"2014-06-04_03:30:00",
"2014-06-04_04:00:00",
"2014-06-04_04:30:00",
"2014-06-04_05:00:00",
"2014-06-04_05:30:00",
"2014-06-04_06:00:00",
"2014-06-04_06:30:02",
"2014-06-04_07:00:00",
"2014-06-04_07:30:00",
"2014-06-04_08:00:00",
"2014-06-04_08:30:03",
"2014-06-04_09:00:00",
"2014-06-04_09:30:00",
"2014-06-04_10:00:00",
"2014-06-04_10:30:00",
"2014-06-04_11:00:00",
"2014-06-04_11:30:01",
"2014-06-04_12:00:00",
"2014-06-04_12:30:01",
"2014-06-04_13:00:00",
"2014-06-04_13:30:05",
"2014-06-04_14:00:00",
"2014-06-04_14:30:06",
"2014-06-04_15:00:00",
"2014-06-04_15:30:00",
"2014-06-04_16:00:00",
"2014-06-04_16:30:00",
"2014-06-04_17:00:00",
"2014-06-04_17:30:07",
"2014-06-04_18:00:00",
"2014-06-04_18:30:01",
"2014-06-04_19:00:00",
"2014-06-04_19:30:01",
"2014-06-04_20:00:00",
"2014-06-04_20:30:02",
"2014-06-04_21:00:00",
"2014-06-04_21:30:04",
"2014-06-04_22:00:00",
"2014-06-04_22:30:03",
"2014-06-04_23:00:00",
"2014-06-04_23:30:02",
"2014-06-05_00:00:00",
"2014-06-05_00:30:04",
"2014-06-05_01:00:00",
"2014-06-05_01:30:05",
"2014-06-05_02:00:00",
"2014-06-05_02:30:05",
"2014-06-05_03:00:00",
"2014-06-05_03:30:04",
"2014-06-05_04:00:00",
"2014-06-05_04:30:03",
"2014-06-05_05:00:00",
"2014-06-05_05:30:01",
"2014-06-05_06:00:00" ;
}
 
Hi allenea,

I already had the same problem and I made some workarounds:

1 - edited the netcdf directly.
2 - the routines that loop through times ignore the seconds

I know that it is not a solution, but it works for me. Apparently step_to_output_time = .true only works hourly.
 
You must log in or register to reply here.
Top