wrffirechemi file name delay

328 views
Skip to first unread message

Zhifeng Yang

unread,
Dec 7, 2018, 3:31:39 PM12/7/18
to wrf-chem-fire_emiss
Hi

I am using wrfchem 3.9 to read wrffirechemi fire emission data. However, it seems that the wrffirechemi file name does not match with the wrf time step. Here is the error message

d01 2015-06-01_01:00:00  ZFY20181206 ./external/io_netcdf/wrf_io.F9004            1
d01 2015-06-01_01:00:00 ZFY20181205 ./external/io_netcdf/wrf_io.F9002          2
d01 2015-06-01_01:00:00 ZFY20181205 ./external/io_netcdf/wrf_io.F9001 wrffirechemi_d01_2015-06-01_00:00:00
d01 2015-06-01_01:00:00  input_wrf: wrf_get_dom_ti_integer for ISOILWATER returns           14
d01 2015-06-01_01:00:00 module_io.F: in wrf_get_next_time
d01 2015-06-01_01:00:00            2  input_wrf: wrf_get_next_time current_date: 2015-06-01_01:00:00 Status =           -4
           2  input_wrf: wrf_get_next_time current_date: 2015-06-01_01:00:00 Status =           -4
d01 2015-06-01_01:00:00 ZFY20181203 share/input_wrf.F02 wrffirechemi_d01_2015-06-01_00:00:00
d01 2015-06-01_01:00:00  ---- ERROR: Could not find matching time in input file wrffirechemi_d01_2015-06-01_00:00:00
NOTE:       1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:    1174
NOTE:  Please check and reset these options
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

The current_date is 2015-06-01_01:00:00, while wrffirechemi data is wrffirechemi_d01_2015-06-01_00:00:00.

I tried to figure out how wrf increases the time step. However, it seems that it uses something like "get data handle". I printed out a lot of message in my log file ("ZFY" in rsl.error.0000). But I am still not sure how wrf increases time. Do you have any ideas? Thank you very much.

See the attached rsl.error.0000 and namelist.input

Best,
Zhifeng

namelist.input
rsl.error.0000
Message has been deleted

Gabriele Pfister

unread,
Jul 1, 2020, 6:03:36 PM7/1/20
to Prerita Agarwal, wrf-chem-fire_emiss
Prerita

sometimes the error message refers to one file but the error itself occurs at another file. I suggest checking also your wrfbiochemi and wrfchemi files. 

Gabriele

On Tue, Jun 30, 2020 at 10:52 AM Prerita Agarwal <prerita...@gmail.com> wrote:
Hi All,

I am facing a similar error while running .wrf.exe.  I have the right time in my wrfinput_d01 and wrffirechemi_d01 files but I am still getting the following error

d01 2016-01-01_00:00:00  NetCDF error in ext_ncd_get_dom_ti.code CHAR, line          83 Element TITLE
           4 input_wrf: wrf_get_next_time current_date: 2016-01-01_00:00:00 Status =           -4
d01 2016-01-01_00:00:00  ---- ERROR: Could not find matching time in input file wrffirechemi_d01_2016-01-01_00:00:00
  
I attach here my namelist.input and rsl.error.0000 files.


I appreciate any leads with this issue. 


--
================================
Gabriele Pfister, Acting Director
Atmospheric Chemistry Observations & Modeling
National Center for Atmospheric Research
Email: pfi...@ucar.edu
Phone: +1 303 497 2915
Web: https://staff.ucar.edu/users/pfister

Prerita Agarwal

unread,
Jul 7, 2020, 8:43:13 AM7/7/20
to wrf-chem-fire_emiss, prerita...@gmail.com
Hi Gabriele,

Thanks for you reply.
I checked the emission files for anthro, biogenic and fire for any errors in the date and it doesn't seem to be a mismatch with the wfinput_d01 file.
I wonder if there is some other error I am missing. 
I attach here my namelis.input and rsl.error file. 

Thank you for the help.


Prerita
namelist.input
rsl.error.0000

Gabriele Pfister

unread,
Jul 7, 2020, 1:01:24 PM7/7/20
to Prerita Agarwal, wrf-chem-fire_emiss
The problem is with wrfchemi_gocart_bg_d<domain>. If you are running with MOZART/GOCART you don't need background fields. Please make sure you read through the WRF-Chem User Guide and the information we have on our website on how to set up a run with different chemistry options. 

Gabriele
Reply all
Reply to author
Forward
0 new messages