Hi Gabriele,Thanks for your help last time!!It read in wrffirechemi* datafiles (from FINN) successfully based on your comments--I recompiled WRF-Chem with KPP, compiled MOZART, and modified namelist.input,Now a quick question for using the antro_emiss utility:Besides global inventories (such as EDGAR-HTAP) on lat/lon projection, can I use it to create WRF-Chem ready emission files from NEI 2011 inventory on Lambert projection, please?I could put the question in the anthro_emiss discussion group if need. Thanks for your time!Bo
On Tuesday, January 16, 2018 at 3:53:54 PM UTC-6, Bo Wang wrote:Hi Gabriele,Appreciate your prompt reply so much! That's clear enough and very helpful.Indeed, I felt somewhat conflicting when I setting up the namelist.input to use FINN.Now I realized that I need to compile WRF-Chem with KPP library to use MOZART chemistry options. I'll do that and let you know if any other questions.Thanks again!Bo
On Tuesday, January 16, 2018 at 3:00:41 PM UTC-6, Gabriele Pfister wrote:Hello Bo,it seems you are mixing up a few things in your namelist.First, FINN emissions processed through fire_emiss should really only be used for MOZART chemistry options. This is, because when using the online plumerise model, WRF-Chem expects as input the smoldering component only whereas FINN provides the total emission strength. For the MOZART chemistry options this is accounted for within the code, but has not been done for other chemistry options. Please see the README to fire_emiss for information.Second, I see you are running with chem_opt=2. Unfortunately we cannot provide support for chemistry options other than the MOZART schemes and I will have to refer you to wrfchemhelp. I am not familiar with the other chemistry options, but it seems from your namelist that you are running with a non-KPP chemistry option (2, RADM2), yet set emiss_opt=5 (GOCART RACM_KPP emissions). I suggest looking through the WRF-Chem Tutorials and Tutorial presentations (https://ruc.noaa.gov/wrf/wrf-chem/Tutorial.html) to see examples of how the namelist needs to be configured for different chemistry options.GabrieleOn Tue, Jan 16, 2018 at 1:40 PM, Bo Wang <bw0...@uah.edu> wrote:Hi everyone,I got similar error (error opening wrrfirechemi*) with time_step = 180. Could you help me to fix the problem, please? Any help would be greatly appreciated!I'm running WRF-Chem v3.9.1. I have prepared meteorological datafiles by WPS and hourly fire emission files named: wrffirechemi_d0N_2016-11-12_HH:00:00 from FINN inventory (by fire_emis processor) for a test case.With the following namelist.input:&time_controlframes_per_auxinput7 = 1, 1,auxinput7_inname = 'wrffirechemi_d<domain>_<date>',auxinput7_interval_m = 60, 60,io_form_auxinput7 = 2&domainstime_step = 180,max_dom = 2,dx = 30000, 10000,dy = 30000, 10000,&chemkemit = 2,chem_opt = 2, 2,biomass_burn_opt = 3, 3,plumerisefire_frq = 30, 30,When I run real.exe, I got the following information in rsl.error.0000 :STARTING WITH BACKGROUND CHEMISTRY14 Subroutine input_chem_profile:13 d01 2016-11-12_12:00:00 input_chem_profile: exit subroutine12 READING EMISSIONS DATA OPT 311 d01 2016-11-12_12:00:00 DEBUG wrf_timetoa(): returning with str = [2016-11-12_12:00:00]10 mediation_integrate: med_read_wrf_chem_fireemissions: Open file wrffirechemi_d019 d01 2016-11-12_12:00:00 NetCDF error: No such file or directory8 d01 2016-11-12_12:00:00 NetCDF error in wrf_io.F90, line 10777 -------------- FATAL CALLED ---------------6 FATAL CALLED FROM FILE: <stdin> LINE: 29075 med_read_wrf_chem_fireemissions: error opening wrffirechemi_d014 -------------------------------------------3 application called MPI_Abort(MPI_COMM_WORLD, 1) - process 02 [unset]: write_line error; fd=-1 buf=:cmd=abort exitcode=11 :2166 system msg for write_line failure : Bad file descriptorCould you help me with that problem, please?Another question is:I'm also confused that, in one of my test run, without setting up any auxinput7 information in namelist.input, I could still get simulation result seems with fire emission input. Does model has default configuration for reading wrffirechemi* fires, please?Thanks!!Bo
On Thursday, December 28, 2017 at 9:30:18 AM UTC-6, Stacy Walters wrote:StacyOf course this will increase your execution time by ~ 12%.time_step = 120I recommend you try setting the namelist variable time_step as follows:19:00:45 which does not exist on the dataset.135 seconds. This results in WRF trying to read wrffirechemi_d01 at a time ofXin,The error you encountered is due to the fact that your time step for domain 1 isOn Thu, Dec 28, 2017 at 6:42 AM, Xin Zhang <xinzha...@gmail.com> wrote:Hi everyone,
When I used fire_emissions in WRF-Chem, I encountered a problem.
I set these options in namelist.input (2015_08_06_18:00:00-2015_08_07_18:00:00):&time_control
io_form_auxinput7 = 2,
frames_per_auxinput7 = 1, 1, 1,
auxinput7_inname = 'wrffirechemi_d<domain>_<date>',
auxinput7_interval_m = 60, 60, 60,
&domains
time_step = 135,
max_dom = 3,
dx = 27000, 9000, 3000,
dy = 27000, 9000, 3000,
&chem
biomass_burn_opt = 2, 2,2,
plumerisefire_frq = 30, 30,30,
So, WRF-Chem should read fire_emission data one houy by one hour. But, I got this error:d01 2015-08-06_19:00:45 open_aux_u : opening wrffirechemi_d01_2015-08-06_19:00:45 for reading. DATASET DATASET=AUXINPUT7
d01 2015-08-06_19:00:45 calling wrf_open_for_read_begin in open_u_dataset
d01 2015-08-06_19:00:45 module_io.F: in wrf_open_for_read_begin
d01 2015-08-06_19:00:45 NetCDF error: No such file or directory
d01 2015-08-06_19:00:45 NetCDF error in wrf_io.F90, line 1077
...........
d01 2015-08-06_19:00:45 ---- ERROR: Could not find matching time in input file wrffirechemi_d03_2015-08-06_19:00:00
NOTE: 1 namelist vs input data inconsistencies found.
Could you help me with this problem?
Thank you,
Xin--Web: https://staff.ucar.edu/users/pfisterPhone: +1 303 497 2915Email: pfi...@ucar.eduNational Center for Atmospheric Research================================Atmospheric Chemistry Observations & Modeling
Gabriele Pfister