Difference between revisions of "How to run the standalone fire model in WRF-SFIRE"

From openwfm
Jump to navigation Jump to search
(Split off SFIRE)
Line 16: Line 16:
 
** Run '''./ideal.exe''' to create the file '''wrfinput_d01'''
 
** Run '''./ideal.exe''' to create the file '''wrfinput_d01'''
 
** Run '''./fire.exe'''
 
** Run '''./fire.exe'''
−
 
−
==Interface between WRF and SFIRE==
 
−
 
−
* The defined interface to SFIRE is between '''WRFV3/phys/module_fr_sfire_driver_wrf.F''' and subroutine '''sfire_driver_em''' in '''WRFV3/phys/module_fr_sfire_driver.F'''
 
−
* WRF calls '''sfire_driver_em''' once at initialization, and then (with slightly different arguments) in every time step.
 
−
* The arguments of '''sfire_driver_em''' consist of two structures (called derived types in Fortran), '''grid''', which contains all state, input, and output variables, and '''config_flags''', with all variables read from from file '''namelist.input''', and some array dimensions.
 
−
** The standalone code defines its own '''grid''' derived type with only the subset of the fields needed. All fields in '''grid''' are set in the standalone driver main file, '''standalone/model_test_main.F''', and nothing is hidden elsewhere.
 
−
** The standalone code replicates '''config_flags''' from WRF using '''*.inc''' files in the directory, which are copies of the files generated by the WRF build process in '''WRFV3/inc'''. They are not soft links so that one can build the standalone code without building WRF. The '''inc''' files may need to be updated when the description of the configuration flags in the WRF registry changes.
 
−
* SFIRE is compliant with [http://www.mmm.ucar.edu/wrf/WG2/WRF_conventions.html WRF coding conventions].
 
−
** WRF divides the horizontal domain into ''patches'' and divides the patches into ''tiles''. Each patch executes in one MPI process. Each tile is updated by one OpenMP thread.
 
−
** The SFIRE standalone code is capable of parallel execution in shared memory. Division into tiles is controlled by fields in '''grid'''. There is only one OpenMP parallel loop over the tiles, in '''WRFV3/phys/module_fr_sfire_driver.F'''. The rest of the SFIRE code executes on a single tile, starting from '''WRFV3/phys/module_fr_sfire_model.F''' Because the tiles need to access values from neighboring tiles at several points in the computation, within a single invocation of SFIRE, the parallel loop is executed several times to synchronize the data in memory at the exit from the loop. Each execution of the parallel loop performs a different stage of the computation.
 
−
** When SFIRE runs in distributed memory, the communication between the patches is done in includes in '''WRFV3/phys/module_fr_sfire_driver.F''' (search for HALO). This has no effect in the standalone code; in WRF, the includes are provided by the WRF parallel infrastructure, RSL-Lite. If you want to run SFIRE in MPI, you need to provide equivalent HALO includes yourself.
 
−
** SFIRE does not keep any state except scalar flags and fixed-size tables, set at initialization. All adjustable-sized arrays preserved beween calls are in '''grid'''.
 
−
* The build process in '''standalone''' uses the fire code files '''WRFV3/phys/module_fr_sfire_*.F''' except '''WRFV3/phys/module_fr_sfire_driver_wrf.F'''. There is no code duplication. Instead of WRF, the fire code is linked with the  '''*.F''' files in the '''standalone''' directory, which provide I/O and substitute the required subset of WRF functionality.
 
  
 
==Testing==
 
==Testing==
Line 43: Line 29:
 
* tested with gfortran 4.4 (gcc44 on Centos 5.5) and 4.3 (on OS X, from [http://www.macports.org/ MacPorts]), but will not compile under gfortran 4.1.2 (which is the default compiler distributed with RHEL5 and [http://www.centos.org Centos 5.5]) because of its lack of support of the Fortran 2003 standard
 
* tested with gfortran 4.4 (gcc44 on Centos 5.5) and 4.3 (on OS X, from [http://www.macports.org/ MacPorts]), but will not compile under gfortran 4.1.2 (which is the default compiler distributed with RHEL5 and [http://www.centos.org Centos 5.5]) because of its lack of support of the Fortran 2003 standard
 
* [http://www.pgroup.com/support/new_rel.htm PGI Fortran] 10.5 and hopefully later
 
* [http://www.pgroup.com/support/new_rel.htm PGI Fortran] 10.5 and hopefully later
 +
 +
==See also==
 +
 +
* [[SFIRE#Fire model interface|Fire model interface in WRF-Fire]]
  
 
[[Category:WRF-Fire]]
 
[[Category:WRF-Fire]]
 
[[Category:Howtos|Standalone fire model in WRF-Fire]]
 
[[Category:Howtos|Standalone fire model in WRF-Fire]]

Revision as of 08:15, 2 August 2010

The fire code in WRF-Fire, called SFIRE (for Spread FIRE model), can be used independently without WRF for testing. To make comparison easier, it can run from the same inputs as WRF-Fire.

Step by step instructions

  • cd wrf-fire/standalone
  • Find a suitable make.inc.* file and soft-link it to make.inc, for example ln -s make.inc.gfortran make.inc
  • Type make to create fire.exe.
  • To run from the same inputs as WRF-Fire
    • Build WRF-Fire
    • Change to one of the test directories, for example cd ../WRFV3/test/em_fire/hill
    • Run ./ideal.exe to create the file wrfinput_d01
    • Run ./fire.exe

Testing

If you change anything in the files WRFV3/phys/module_fr_sfire_*.F, you must test that the changes do not break WRF-Fire, otherwise your changes will not be maintainable.

  • Build WRF-Fire with SM+DM parallelism with debugging, and test all 4 versions (serial, SM, DM, SM+DM) with the examples provided in WRFV3/test/em_fire and various numbers of processors. The results (the wrfrst files) must be bit-identical to each other and identical to what they were before your changes.
  • Build WRF-Fire with optimization and test on several platforms (at least gfortran and PGI).

Works with

  1. REDIRECT Template:WRF-Fire-branch Aug 2 2010
  • tested with gfortran 4.4 (gcc44 on Centos 5.5) and 4.3 (on OS X, from MacPorts), but will not compile under gfortran 4.1.2 (which is the default compiler distributed with RHEL5 and Centos 5.5) because of its lack of support of the Fortran 2003 standard
  • PGI Fortran 10.5 and hopefully later

See also

Retrieved from "http://wiki.openwfm.org/mediawiki/index.php?title=How_to_run_the_standalone_fire_model_in_WRF-SFIRE&oldid=1316"