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

wrf fire namelist

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

cjones

Member
Hello,

i am trying to run wrf activating the fire module but there is something incorrectly setup in my namelist (attached) - i setup the &fire section as follows:
&fire
ifire = 0, 0, 0, 2,
fire_fuel_read = 0, 0, 0, -1,
fire_num_ignitions = 0, 0, 0, 1,
fire_ignition_start_long1= 0, 0, 0,-119.719355,
fire_ignition_start_lat1 = 0, 0, 0, 34.473697,
fire_ignition_end_long1 = 0, 0, 0,-119.719355,
fire_ignition_end_lat1 = 0, 0, 0, 34.473897,
fire_ignition_radius1 = 0, 0, 0, 100,
fire_ignition_time1 = 0, 0, 0, 60,
fire_print_msg = 1,
fire_print_file = 1,
/
my interpretation looking at the registry.fire is that these variables are domain dependent. the problem is that when i run wrf, it stops right at the beginning with:
taskid: 0 hostname: voyager.eri.ucsb.edu
module_io_quilt_old.F 2931 F
Quilting with 1 groups of 0 I/O tasks.
------ ERROR while reading namelist fire ------
Maybe here?: fire_num_ignitions = 0, 0, 0, 1,
Maybe here?: fire_ignition_start_long1= 0, 0, 0,-119.719355,
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 10851
ERRORS while reading one or more namelists from namelist.input.
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

it is not clear to me which subroutine is giving the error in line 10851.

Any ideas/suggestions are greatly appreciated.

thanks

Charles.
 

Attachments

  • namelist.input
    8 KB · Views: 86
The nameless options should be fire_ignition_start_lon1 and fire_ignition_end_lon1 (Not fire_ignition_start_long1 and fire_ignition_end_long1).
Please change the above options and try again.
Ming Chen
 
hi Ming Chen,

thank you so much for the suggestion. It works!

for the record, there is a namelist.input.fire that comes with the wrf tar file. I was following the examples in that namelist but the syntax for some variables is different than the ones in the registry.fire. The users guide 4.0 also has some incorrect descriptions.
Apparently, the update in the fire module in version 4.0 left some outdated material.
so far the correct ones are:
fire_ignition_start_lon1 = 0, 0, 0,-119.719355,
fire_ignition_start_lat1 = 0, 0, 0, 34.473697,
fire_ignition_end_lon1 = 0, 0, 0,-119.719355,
fire_ignition_end_lat1 = 0, 0, 0, 34.473897,
fire_ignition_start_time1= 0, 0, 0, 60,

Cheers,

Charles
 
Charles,
Thank your for letting me know the issues in the released code of WRF and WRF User's Guide. We will fix these issues soon.
Ming Chen
 
Top