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 opening wrffirechemi_d01

arovithakis

New member
Hi everyone,

I've been trying to run WRF-chem with EDGAR anthropogenic emissions with PREP-CHEM-SRC-1.8.3 (see text attached), biogenic emissions with megan (see text attached), and hourly biomass burning emissions with FINNv2.5 (see text attached). I have linked in the WRF em_real directory the wrfbiochemi_d01, wrfchemi_d01 and the hourly wrffirechemi_d01_2021-07-15_00:00:00 ... wrffirechemi_d01_2021-08-13_23:00:00 files

However I'm getting the following error

READING EMISSIONS DATA OPT 3
mediation_integrate: med_read_wrf_chem_fireemissions: Open file wrffirechemi_d01
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 2931
med_read_wrf_chem_fireemissions: error opening wrffirechemi_d01

It seems as if WRF is expecting to look for the file format wrffirechemi_d01 instead of wrffirechemi_d01_2021-07-15_00:00:00 even though I have defined it as such in the namelist. Also I can't seem to find the stdin file's directory to look for the potential error in line 2931 as the rsl.error.0000 file states.

I would really appreciate your help.

Regards,
Tasos
 

Attachments

  • namelist.input
    10.3 KB · Views: 34
  • rsl.error.0000
    2.6 KB · Views: 10
  • fire_emis.txt
    677 bytes · Views: 9
  • megan_bio_emiss.txt
    207 bytes · Views: 5
  • prep_chem_sources.txt
    6.2 KB · Views: 8
Hi Tasos,

Try this:

Create a link to the first emission file:

ln -s wrffirechemi_d01_2021-07-15_00:00:00 wrffirechemi_d01

Then run real.exe as normal, that should at least get you passed that step. Then try running WRF with the namelist specifying hourly emission files (what you have), and check the logs to make sure that it is indeed reading in the correct files at runtime.

Jordan
 
Thank you for the response Jordan.
I found the problem.
It gave me this error because it was expecting to read the file with the name wrffirechemi_d01_2021-07-15 instead of wrffirechemi_d01_2021-07-15_00:00:00
 
Thank you for the response Jordan.
I found the problem.
It gave me this error because it was expecting to read the file with the name wrffirechemi_d01_2021-07-15 instead of wrffirechemi_d01_2021-07-15_00:00:00
Hi Tasos

I'm wondering how did you solve the problem. I'm trying setting auxinput7_inname = 'wrffirechemi_d<domain>_<date>_<hr>' to read the specific date but is not working when I run real.exe. Could you guide me to solve this problem?

Thanks,

Juan
 
Hi Tasos

I'm wondering how did you solve the problem. I'm trying setting auxinput7_inname = 'wrffirechemi_d<domain>_<date>_<hr>' to read the specific date but is not working when I run real.exe. Could you guide me to solve this problem?

Thanks,

Juan
Hi juan

Someone will correct me if I'm wrong but you need to turn of the chemistry part of the namelist when you run real.exe and then turn it back on for wrf.exe

Tasos
 
Hi Juan,

Your issues seems to be the inclusion of <hr> in the name. <date> includes the full time stamp:

e.g.,


auxinput7_inname = 'wrffirechemi_d<domain>_<date>',

wrffirechemi_d01_2020-09-01_00_00_00
wrffirechemi_d01_2020-09-01_01_00_00
...


Jordan
 
Top