Error in emission files for WRF Chem ( wrf_season_wes_usgs_d01, exo_coldens_d01, wrfchemi_d01, wrfbiochemi_d01 and wrffirechemi_d01)

35 views
Skip to first unread message

Swathi V S

unread,
Apr 2, 2025, 2:14:21 AMApr 2
to wrf-...@ucar.edu
Dear All,

I am running wrf-chem with anthropogenic emissions. 
I downloaded emission datasets from EDGAR-HTAP (0.1 degree, monthly data). According to manual we have to untar this data and follow according to this:

>tar –xvf wes_coldens.tar
Compile the MOZART source code by issuing the commands:
>make_util wesely
>make_util exo_coldens
This will create the executable files – wesely and exo_coldens.

The wesely program reads WRF wrfinput_d01 files and a MOZART-data file
containing dry emission parameters - season_wes_usgs.nc.
Adjust the text file wesely.inp for:
1. domains – the number of domains used in your WRF model
2. pft_flnm – season_wes_usgs.nc
3. wrf_dir – the directory where the associated wrfinput_d01 resides, and
4. pft_dir – the directory in which the MOZART data file exists

To create the wesely data files for MOZART, issue the command:
>wesely < wesely.inp > wesely.out
This creates a file for each domain wrf_season_wes_usgs_d01 which should be
copied to the WRF run directory for use in WRF-Chem MOZART/MOZCART model
runs.

The exo_colden program reads WRF wrfinput_d<nn> files and a MOZART data file
exo_coldens.nc (found in the tar file above). Adjust the text file exo_coldens.inp for:
A. domains – the number of domains used in your WRF model
B. exo_flnm – exo_coldens.nc
C. wrf_dir – the directory where the associated wrfinput_d<nn> resides, and
D. exo_dir – the directory in which the MOZART data file exists

To create the exo_coldens data files for MOZART, issue the command:
>exo_coldens < exo_coldens.inp > exo_coldens.out
This creates a file for each domain exo_coldens_d01 which should be copied to the
WRF run directory for use in WRF-Chem MOZART/MOZCART model runs.


But I am facing problems while doing >wesely < wesely.inp > wesely.out and not getting wrf_season_wes_usgs_d01 and exo_coldens_d01 files. 

Also not getting the wrfchemi_d01 file.

If someone knows about these types of problems then please suggest some solution for this problem.

Regards,
Swathi V S



--
Swathi V S
Project Associate I
Department of Earth and Environmental Sciences 
Indian Institute of Science Education and Research Bhopal
swat...@iiserb.ac.in,(+91)97783804266

Gabriele Pfister

unread,
Apr 2, 2025, 2:17:35 PMApr 2
to swath...@gmail.com, wrf-...@ucar.edu
Hello Swathi

what error message do you get in your wesely.out  file? 

I also do not understand your comment about not getting the wrfchemi_d01 file. This file is not generated with the wesely or exo_coldens tools. 

Gabi
--
================================
Gabriele Pfister
Atmospheric Chemistry Observations & Modeling (ACOM) Lab
NSF National Center for Atmospheric Research (NCAR)
Email: pfi...@ucar.edu
Work Phone: +1 303 497 2915
Web: https://staff.ucar.edu/users/pfister

Swathi V S

unread,
Apr 3, 2025, 2:40:24 AMApr 3
to Gabriele Pfister, wrf-...@ucar.edu

Hello Gabriele Pfister,

I am currently running a WRF-Chem simulation with two nested domains: d01 (9 km) and d02 (3 km). When running the model without chemistry, I was able to successfully generate the required files (wrfinput_d01 and wrfbdy_d01). However, when enabling chemistry, I encountered a segmentation fault error while executing ./real.exe.

Steps Taken Before the Error:
Successfully completed geogrid.exe and ungrib.exe.

Ran metgrid.exe without any apparent issues.

Encountered an error immediately after running real.exe.

System and Model Details:
WRF-Chem Version: WPS 4.4, WRFV 4.4

Simulation Period: Start: 2010-01-01_00:00:00; End: 2010-01-07_18:00:00

Error Message:

STARTING WITH BACKGROUND CHEMISTRY
Subroutine input_chem_profile:

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0  0x14cb72b63d11 in ???
#1  0x14cb72b62ee5 in ???
#2  0x14cb727fc08f in ???
at /build/glibc-FcRMwW/glibc-2.31/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
#3  0x559893ccba5a in ???
#4  0x559893cd273a in ???
#5  0x55989192a8be in ???
#6  0x55989192b445 in ???
#7  0x55989191be32 in ???
#8  0x14cb727dd082 in __libc_start_main
at ../csu/libc-start.c:308
#9  0x55989191be6d in ???
#10  0xffffffffffffffff in ???
Segmentation fault (core dumped)

I have tried different chemistry schemes, but the issue persists. I would appreciate any insights from anyone who has faced a similar problem and found a solution.

I have attached my namelist.input file for reference.

Thank you for your time and expertise.

Best regards,

Swathi

namelist.input

Gabriele Pfister

unread,
Apr 3, 2025, 12:50:54 PMApr 3
to Swathi V S, wrf-...@ucar.edu
Hello Swathi, 

I am still not sure why you want to run real.exe again if you already created the wrfbdy and wrfinput files. Is this because you want to set idealized chemical initial and boundary conditions rather than setting them from a global model using e.g. mozbc?

Also please note that we had already years ago recommend to no longer use chem_opt = 111 and have stopped supporting that scheme (https://www.acom.ucar.edu/wrf-chem/T1-MOZCART-UsersGuide-27April2018.pdf). 

Gabi
Reply all
Reply to author
Forward
0 new messages