WesleyMoob
New member
Hello,
I have encountered a fatal runtime error during my WRF-Chem simulation covering the period from 28 June to 14 July 2022.
The model runs smoothly when initialized at 00 UTC on 28 June 2022. Nevertheless, the simulation terminates abruptly with a timestamp-mismatch error linked to the wrffirechemi biomass burning emissions once the integration progresses to 12:00 UTC on 30 June. The relevant error log snippet is shown below:
mediation_integrate: med_read_wrf_chem_emissions: Read emissions for time 2022-06-30_12:00:00
d01 2022-06-30_12:00:00 Error trying to read metadata
d01 2022-06-30_12:00:00 Input data is acceptable to use: wrfchemi_12z_d01
**WARNING** Time in input file not being checked **WARNING**
d01 2022-06-30_12:00:00 Input data is acceptable to use: wrffirechemi_d01_2022-06-28_00:00:00
3 input_wrf: wrf_get_next_time current_date: 2022-06-28_12:00:00 Status = -4
d01 2022-06-30_12:00:00 ---- ERROR: Could not find matching time in input file wrffirechemi_d01_2022-06-28_00:00:00
NOTE: 1 namelist vs input data inconsistencies found.
Notably, I have confirmed that all required timestamps for the full simulation window are included inside the wrffirechemi input files.
Has anyone come across this identical issue or figured out its potential triggers? I would highly appreciate any troubleshooting advice or solutions.
Best regards,
WesleyMoob
I have encountered a fatal runtime error during my WRF-Chem simulation covering the period from 28 June to 14 July 2022.
The model runs smoothly when initialized at 00 UTC on 28 June 2022. Nevertheless, the simulation terminates abruptly with a timestamp-mismatch error linked to the wrffirechemi biomass burning emissions once the integration progresses to 12:00 UTC on 30 June. The relevant error log snippet is shown below:
mediation_integrate: med_read_wrf_chem_emissions: Read emissions for time 2022-06-30_12:00:00
d01 2022-06-30_12:00:00 Error trying to read metadata
d01 2022-06-30_12:00:00 Input data is acceptable to use: wrfchemi_12z_d01
**WARNING** Time in input file not being checked **WARNING**
d01 2022-06-30_12:00:00 Input data is acceptable to use: wrffirechemi_d01_2022-06-28_00:00:00
3 input_wrf: wrf_get_next_time current_date: 2022-06-28_12:00:00 Status = -4
d01 2022-06-30_12:00:00 ---- ERROR: Could not find matching time in input file wrffirechemi_d01_2022-06-28_00:00:00
NOTE: 1 namelist vs input data inconsistencies found.
Notably, I have confirmed that all required timestamps for the full simulation window are included inside the wrffirechemi input files.
Has anyone come across this identical issue or figured out its potential triggers? I would highly appreciate any troubleshooting advice or solutions.
Best regards,
WesleyMoob