-
Notifications
You must be signed in to change notification settings - Fork 726
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
New module firebrand_spotting for WRF-Fire (#1540)
TYPE: new feature KEYWORDS: fire firebrand spotting Lagrangian transport passive advection burnout SOURCE: Maria Frediani, Tim W. Juliano (NCAR-RAL) DESCRIPTION OF CHANGES: The new module firebrand_spotting for WRF-Fire is a passive Lagrangian transport parameterization to advect firebrands. The Firebrand Spotting parameterization was developed for the WRF-Fire component of the WRF model versions starting at 4.0.1. The parameterization couples to WRF-Fire and uses a Lagrangian particle transport framework to advect firebrands in the innermost nest of the domain. The parameterization runs in the atmospheric model inner domain and does not modify model variables (no feedback to WRF or WRF-Fire). The code comprises two independent modules, one with the physical processes and another with the necessary MPI wrapping routines that were not yet part of the WRF source code. The motivation to separate the MPI routines in an independent module was to enable them to be used in other model parameterizations through a USE statement without importing the firebrand spotting component. The Firebrand Spotting variables are part of Registry.fire and the subroutine is called from start_em.F and solve_em.F, after all the physics parameterizations and relevant halos are completed. When fires are active, the parameterization identifies areas at risk of fire spotting by modeling transport and physical processes of individual firebrands. Firebrands are released at multiple heights from grid points along the fire front with high fire rate-of-spread and denser fuel loads. Particles are transported with the atmospheric flow and consumed by combustion. Firebrands may burnout entirely or land, once they descend below a given height threshold. Particles that land before complete burnout are accumulated in a 2-D field during regular intervals. The likelihood of new fire ignitions due to spotting is computed using the ratio of landed firebrands per grid point to the total number of landed particles within the corresponding time interval between model outputs. The ratios are then scaled by a function of fuel load and moisture content at the corresponding grid points. LIST OF MODIFIED FILES: M Registry/Registry.EM_COMMON M Registry/registry.fire M dyn_em/depend.dyn_em M dyn_em/solve_em.F M dyn_em/start_em.F M main/depend.common M phys/Makefile A phys/module_firebrand_spotting.F A phys/module_firebrand_spotting_mpi.F TESTS CONDUCTED: 1. The module was designed for high-resolution simulations and tested using large-eddy simulation (LES) in the inner nest. Simulations for various case studies in Colorado have been done. 2. All tests have passed (latest commit: afc9142, after switching pbl from MYNN to YSU). There were no differences among the serial and MPI builds with 1 and 12 processors. The tests were all done from a restart file. The time step for these runs was 5s and the outputs were compared after 20s, 40s, and 1 min. 3. Jenkins tests are all passing. RELEASE NOTE: A new module to parameterize firebrand spotting for WRF-Fire is added. This is a passive Lagrangian transport scheme to transport and burnout firebrands generated at the fire front. The scheme is activated when ifire == 2 by setting the namelist option fs_firebrand_gen_lim to an integer greater than zero (default is 0, i.e. scheme is off). It runs with dmpar and serially compiled code and in the inner nest (grid_id == max_dom). It was designed and tested using a mesoscale to LES domain configuration.
- Loading branch information
1 parent
75bfe6d
commit 609c2fc
Showing
9 changed files
with
4,869 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.