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

Error in running WRF-Chem V4.4. using MOZART-GOCART chemistry

N

Nilkamal

New member
Hi,

I am running WRF-Chem v4.4 with MOZART-GOCART chemistry (chem_opt = 112), FINN for fire emission, MEGAN for Biogenic, and ANTHRO-EDGAR for anthropogenic emission. It worked perfectly for a while but my recent runs started to fail with the following log:

d01 2020-05-01_01:00:00 module_io.F: in wrf_get_next_time
d01 2020-05-01_01:00:00 3 input_wrf: wrf_get_next_time current_date: 2020-05-01_00:00:00 Status = -4
3 input_wrf: wrf_get_next_time current_date: 2020-05-01_00:00:00 Status = -4
d01 2020-05-01_01:00:00 ---- ERROR: Could not find matching time in input file wrfbiochemi_d01

It seems that the run could not find the same date time in my wrfchemi input file. I also checked the Times variable in the wrfchemi file, which also agrees. I am trying a basic test run and I cannot solve the following error. I attach my namelist.input and rsl.error file.

Please I would really appreciate any help with this.
Thank You
Nilkamal Jaisawal
 

Attachments

  • namelist.input
    8.3 KB · Views: 34
  • rsl.error.0000
    2.4 MB · Views: 3
Hi, did you solve this problem now? I met the same problem and the rsl.error.0000 shows as follows:

**WARNING** Time in input file not being checked **WARNING**
d01 2022-07-03_00:00:00 Input data processed for aux input 6 for domain 1
2 input_wrf: wrf_get_next_time current_date: 2022-07-03_00:00:00 Status = -4
d01 2022-07-03_00:00:00 ---- ERROR: Could not find matching time in input file wrfbiochemi_d01

NOTE: 1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1148
NOTE: Please check and reset these options
____________________________________________________________________________________________

When I ncdump -v Times wrfbiochemi_d01, and ncdump -v Times wrfinput_d01, both show as follows:
data:
Times =
"2022-07-03_00:00:00" ;

Looking forward to hearing from you.;)
 
Wangyike said:
Hi, did you solve this problem now?I met the same problem with wrfchemi_d02.
Click to expand...
start_domain_em: numgas = 0
Timing for Writing wrfout_d01_2022-08-01_00:00:00 for domain 1: 0.57297 elapsed seconds
d01 2022-08-01_00:00:00 Input data is acceptable to use: wrflowinp_d01
d01 2022-08-01_00:00:00 Input data processed for aux input 4 for domain 1
mediation_integrate: med_read_wrf_chem_emissions: Read emissions for time 2022-08-01_00:00:00
mediation_integrate: med_read_wrf_chem_emissions: Open file wrfchemi_d01_2022-08-01_00:00:00
d01 2022-08-01_00:00:00 Error trying to read metadata
d01 2022-08-01_00:00:00 Input data is acceptable to use: wrfchemi_d01_2022-08-01_00:00:00
d01 2022-08-01_00:00:00 Input data is acceptable to use: wrfoce_d01_2022-08-01_00:00:00
d01 2022-08-01_00:00:00 Input data processed for aux input 6 for domain 1
d01 2022-08-01_00:00:00 Error trying to read metadata
d01 2022-08-01_00:00:00 Input data is acceptable to use: wrffirechemi_d01_2022-08-01_00:00:00
d01 2022-08-01_00:00:00 Error trying to read metadata
d01 2022-08-01_00:00:00 Input data is acceptable to use: vprm_input_d01_2022-08-01_00:00:00
d01 2022-08-01_00:00:00 Input data processed for aux input 15 for domain 1
d01 2022-08-01_00:00:00 Input data is acceptable to use: wrfbdy_d01
Timing for processing lateral boundary for domain 1: 0.20004 elapsed seconds
Tile Strategy is not specified. Assuming 1D-Y
WRF TILE 1 IS 1 IE 16 JS 1 JE 16
WRF NUMBER OF TILES = 1
d01 2022-08-01_00:00:00 ----------------------------------------
d01 2022-08-01_00:00:00 W-DAMPING BEGINS AT W-COURANT NUMBER = 1.00000000
d01 2022-08-01_00:00:00 ----------------------------------------
1 100
Timing for Writing wrfout_d02_2022-08-01_00:00:00 for domain 2: 0.21045 elapsed seconds
d02 2022-08-01_00:00:00 Input data is acceptable to use: wrflowinp_d02
d02 2022-08-01_00:00:00 Input data processed for aux input 4 for domain 2
mediation_integrate: med_read_wrf_chem_emissions: Read emissions for time 2022-08-01_00:00:00
mediation_integrate: med_read_wrf_chem_emissions: Open file wrfchemi_d02_2022-08-01_00:00:00
d02 2022-08-01_00:00:00 Error trying to read metadata
d02 2022-08-01_00:00:00 Input data is acceptable to use: wrfchemi_d02_2022-08-01_00:00:00
d02 2022-08-01_00:00:00 Error trying to read metadata
d02 2022-08-01_00:00:00 Input data is acceptable to use: wrfchemi_d02_2022-08-01_00:00:00
7 input_wrf: wrf_get_next_time current_date: 2022-08-01_00:00:00 Status = -4
d02 2022-08-01_00:00:00 ---- ERROR: Could not find matching time in input file wrfchemi_d02_2022-08-01_00:00:00
NOTE: 1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1303
NOTE: Please check and reset these options
 
You must log in or register to reply here.
Top