WRF-CHEM SCM Restart

[Jun Hu]

I want to know whether WRF-chem SCM can use restart. I have run restart (WRF-Chem SCM), but it shew that :
mediation_integrate: med_read_wrf_chem_emissions: Read emissions for time 2017-01-04_10:00:00
0 input_wrf: wrf_get_next_time current_date: 2017-01-04_10:00:00 Status = -102
d01 2017-01-04_10:00:00 ---- ERROR: Could not find matching time in input file
NOTE: 1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1170
NOTE: Please check and reset these options
-------------------------------------------

and this is my namelist.input using in restart:
&time_control
run_days = 0,
run_hours = 26,
run_minutes = 0,
run_seconds = 0,
start_year = 2017,
start_month = 01,
start_day = 04,
start_hour = 10,
start_minute = 00,
start_second = 00,
end_year = 2017,
end_month = 01,
end_day = 05,
end_hour = 12,
end_minute = 00,
end_second = 00,
input_from_file = .true.,
history_interval = 60,
frames_per_outfile = 10000,
restart = .true.,
restart_interval = 2040,
io_form_auxinput5 = 2
auxinput5_interval_m = 60,
io_form_history = 2
io_form_restart = 2
io_form_input = 2
io_form_boundary = 2
debug_level = 0
auxinput3_inname = "force_ideal.nc"
auxinput3_interval_h = 59
auxinput12_inname = 'wrf_chem_input',
io_form_auxinput12 = 2
write_hist_at_0h_rst = .true.
/
Sincerely
Jun Hu

 

[Jun Hu]

I found that if I delete io_form_auxinput5 = 2, it can run successfully. But what's the problem with my emission. Is it the problem of times in emission files? Here is the times in emission files:

Times =
"2017-01-04_00:00:00",
"2017-01-04_01:00:00",
"2017-01-04_02:00:00",
"2017-01-04_03:00:00",
"2017-01-04_04:00:00",
"2017-01-04_05:00:00",
"2017-01-04_06:00:00",
"2017-01-04_07:00:00",
"2017-01-04_08:00:00",
"2017-01-04_09:00:00",
"2017-01-04_10:00:00",
"2017-01-04_11:00:00" ;

 

[douglowe]

hi Jun Hu,

Can you post the rest of your namelist, so that we can see what your chem setup is (there are options there which control reading in emissions, which will be relevant to answering this question)?

Have you tried restarting at 0000 (midnight) or 1200 (midday) UTC? There is a better chance of the emissions being read if you try these times (and once you have it working for those times, you can try again to restart at 1000).