<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FLAM workflow on FLAM-DOCS</title><link>https://docs.flamhub.org/docs/main/flam/</link><description>Recent content in FLAM workflow on FLAM-DOCS</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://docs.flamhub.org/docs/main/flam/index.xml" rel="self" type="application/rss+xml"/><item><title>1. Daily Fuel Moisture</title><link>https://docs.flamhub.org/docs/main/flam/fuel-moisture/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flamhub.org/docs/main/flam/fuel-moisture/</guid><description>&lt;h1 id="daily-fuel-moisture"&gt;&#10; Daily Fuel Moisture&#10; &lt;a class="anchor" href="#daily-fuel-moisture"&gt;#&lt;/a&gt;&#10;&lt;/h1&gt;&#10;&lt;p&gt;&lt;strong&gt;FLAM › Daily Fuel Moisture&lt;/strong&gt; calculates the daily moisture content of fine dead fuels from weather data. It uses the moisture model behind the Canadian Fine Fuel Moisture Code (FFMC). The result feeds the ignition probability (P_m), the burned area and the spread steps.&lt;/p&gt;&#10;&lt;p&gt;Skip this step if you already have daily fuel moisture as a fraction of dry weight.&lt;/p&gt;&#10;&lt;h2 id="inputs"&gt;&#10; Inputs&#10; &lt;a class="anchor" href="#inputs"&gt;#&lt;/a&gt;&#10;&lt;/h2&gt;&#10;&lt;p&gt;&lt;img src="https://docs.flamhub.org/images/docs/fuel-moisture.png" alt="Calculate Daily Fuel Moisture window" /&gt;&lt;/p&gt;</description></item><item><title>2. Frequency Probability</title><link>https://docs.flamhub.org/docs/main/flam/fire-probability/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flamhub.org/docs/main/flam/fire-probability/</guid><description>&lt;h1 id="frequency-probability"&gt;&#10; Frequency Probability&#10; &lt;a class="anchor" href="#frequency-probability"&gt;#&lt;/a&gt;&#10;&lt;/h1&gt;&#10;&lt;p&gt;&lt;strong&gt;FLAM › Frequency Probability&lt;/strong&gt; calculates, for each pixel and day, the probability that a fire starts and isn&amp;rsquo;t put out right away (&lt;strong&gt;P&lt;/strong&gt;). It combines population, lightning, fuel load and fuel moisture.&lt;/p&gt;&#10;&lt;h2 id="steps"&gt;&#10; Steps&#10; &lt;a class="anchor" href="#steps"&gt;#&lt;/a&gt;&#10;&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;strong&gt;Parameter file.&lt;/strong&gt; Click &lt;strong&gt;New&lt;/strong&gt; to create an &lt;code&gt;.ini&lt;/code&gt; file with default values, or &lt;strong&gt;Load&lt;/strong&gt; to open an existing one. Keep the file: you need the same parameters for scenario runs.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;FLAM Parameters.&lt;/strong&gt; Adjust the values, then click &lt;strong&gt;Save&lt;/strong&gt;. This writes the &lt;code&gt;.ini&lt;/code&gt; file and opens the next window.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;FLAM Preprocess Probability.&lt;/strong&gt; Set the inputs and click &lt;strong&gt;Run&lt;/strong&gt;.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;&lt;img src="https://docs.flamhub.org/images/docs/param-file-frequency.png" alt="Parameter file dialog" /&gt;&lt;/p&gt;</description></item><item><title>3. Create Labeling Data</title><link>https://docs.flamhub.org/docs/main/flam/label-data/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flamhub.org/docs/main/flam/label-data/</guid><description>&lt;h1 id="create-labeling-data"&gt;&#10; Create Labeling Data&#10; &lt;a class="anchor" href="#create-labeling-data"&gt;#&lt;/a&gt;&#10;&lt;/h1&gt;&#10;&lt;p&gt;&lt;strong&gt;FLAM › Create Labeling Data&lt;/strong&gt; turns fire perimeter polygons into rasters of observed burned area on your model grid. &lt;a href="https://docs.flamhub.org/docs/main/flam/burned-area/"&gt;Calculate Burned Area&lt;/a&gt; uses these rasters for calibration.&lt;/p&gt;&#10;&lt;p&gt;You don&amp;rsquo;t need this step if your observations are already gridded (for example GFED). In that case, see &lt;a href="https://docs.flamhub.org/docs/main/input-data/"&gt;Input data&lt;/a&gt;.&lt;/p&gt;&#10;&lt;h2 id="inputs"&gt;&#10; Inputs&#10; &lt;a class="anchor" href="#inputs"&gt;#&lt;/a&gt;&#10;&lt;/h2&gt;&#10;&lt;p&gt;&lt;img src="https://docs.flamhub.org/images/docs/label-data.png" alt="FLAM Create Label Data window" /&gt;&lt;/p&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Field&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Description&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;&lt;strong&gt;¶&lt;/strong&gt; fills from&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Fire Delineation&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Polygon shapefile, one polygon per fire, in a projected CRS in metres&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Fire Shape&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Time Column&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Attribute with the fire date as &lt;code&gt;YYYY-MM-DD&lt;/code&gt;. The tool preselects the first column whose name contains &amp;ldquo;date&amp;rdquo; or &amp;ldquo;time&amp;rdquo;.&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;—&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Base Raster&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Defines the output grid&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Base Map&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Output Folder&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Where the subfolders are created&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Results&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;h2 id="output-types"&gt;&#10; Output types&#10; &lt;a class="anchor" href="#output-types"&gt;#&lt;/a&gt;&#10;&lt;/h2&gt;&#10;&lt;p&gt;Tick &lt;strong&gt;Daily&lt;/strong&gt; and/or &lt;strong&gt;Monthly&lt;/strong&gt; for each type:&lt;/p&gt;</description></item><item><title>4. Calculate Burned Area</title><link>https://docs.flamhub.org/docs/main/flam/burned-area/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flamhub.org/docs/main/flam/burned-area/</guid><description>&lt;h1 id="calculate-burned-area"&gt;&#10; Calculate Burned Area&#10; &lt;a class="anchor" href="#calculate-burned-area"&gt;#&lt;/a&gt;&#10;&lt;/h1&gt;&#10;&lt;p&gt;&lt;strong&gt;FLAM › Calculate Burned Area&lt;/strong&gt; converts fire probability into expected burned area. It has two modes:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Calibration&lt;/strong&gt; (&lt;em&gt;Optimize&lt;/em&gt;): fits the suppression efficiency &lt;strong&gt;q&lt;/strong&gt; to observed burned area.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Projection&lt;/strong&gt; (&lt;em&gt;Use existing data&lt;/em&gt;): applies a q you calibrated earlier.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="steps"&gt;&#10; Steps&#10; &lt;a class="anchor" href="#steps"&gt;#&lt;/a&gt;&#10;&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;strong&gt;Parameter file.&lt;/strong&gt; Click &lt;strong&gt;New&lt;/strong&gt; or &lt;strong&gt;Load&lt;/strong&gt; (a separate &lt;code&gt;.ini&lt;/code&gt; from the probability step).&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;FLAM Parameters.&lt;/strong&gt; Adjust &lt;code&gt;u_max&lt;/code&gt; and &lt;code&gt;m_e&lt;/code&gt;, then click &lt;strong&gt;Save&lt;/strong&gt;.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;FLAM Calculate Burned Area.&lt;/strong&gt; Set the inputs and click &lt;strong&gt;Run&lt;/strong&gt;.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;&lt;img src="https://docs.flamhub.org/images/docs/param-file-ba.png" alt="Parameter file dialog (burned area)" /&gt;&lt;/p&gt;</description></item><item><title>5. Spread Simulation</title><link>https://docs.flamhub.org/docs/main/flam/spread-simulation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flamhub.org/docs/main/flam/spread-simulation/</guid><description>&lt;h1 id="spread-simulation"&gt;&#10; Spread Simulation&#10; &lt;a class="anchor" href="#spread-simulation"&gt;#&lt;/a&gt;&#10;&lt;/h1&gt;&#10;&lt;p&gt;&lt;strong&gt;FLAM › Spread Simulation&lt;/strong&gt; spreads the burned area from &lt;a href="https://docs.flamhub.org/docs/main/flam/burned-area/"&gt;Calculate Burned Area&lt;/a&gt; across neighbouring pixels. The result shows where fires burn, not just how much area burns per pixel.&lt;/p&gt;&#10;&lt;h2 id="how-it-works"&gt;&#10; How it works&#10; &lt;a class="anchor" href="#how-it-works"&gt;#&lt;/a&gt;&#10;&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;strong&gt;Find fires larger than a pixel.&lt;/strong&gt; For each day, the tool computes the expected size of a fire in each pixel (&lt;code&gt;A_burn / P&lt;/code&gt;). Pixels where this exceeds the pixel area become fire origins.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Spread those fires.&lt;/strong&gt; Each fire grows across pixels, driven by that day&amp;rsquo;s fuel moisture and wind (and wind direction, if you provide it).&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Stop at fuel breaks.&lt;/strong&gt; Pixels with fuel below the connectivity threshold, or with NoData, act as barriers.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Keep small fires in place.&lt;/strong&gt; Fires smaller than a pixel keep their original &lt;code&gt;A_burn&lt;/code&gt; value.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;h2 id="inputs"&gt;&#10; Inputs&#10; &lt;a class="anchor" href="#inputs"&gt;#&lt;/a&gt;&#10;&lt;/h2&gt;&#10;&lt;p&gt;&lt;img src="https://docs.flamhub.org/images/docs/spread-simulation.png" alt="Spread Simulation window" /&gt;&lt;/p&gt;</description></item><item><title>Future scenarios</title><link>https://docs.flamhub.org/docs/main/flam/scenarios/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flamhub.org/docs/main/flam/scenarios/</guid><description>&lt;h1 id="future-scenarios"&gt;&#10; Future scenarios&#10; &lt;a class="anchor" href="#future-scenarios"&gt;#&lt;/a&gt;&#10;&lt;/h1&gt;&#10;&lt;p&gt;To project fire activity, you calibrate FLAM on historical data, then rerun it with scenario inputs while keeping the calibrated parameters and &lt;strong&gt;q&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;strong&gt;Calibrate on the historical period.&lt;/strong&gt; Run steps 1–4 of the &lt;a href="https://docs.flamhub.org/docs/main/flam/"&gt;workflow&lt;/a&gt; with &lt;strong&gt;Optimize&lt;/strong&gt; selected for q. Keep both parameter &lt;code&gt;.ini&lt;/code&gt; files and the &lt;code&gt;q&lt;/code&gt; folder.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Prepare scenario inputs.&lt;/strong&gt; You need daily weather and, if they change over time, yearly population and fuel. Use the same grid and the same &lt;a href="https://docs.flamhub.org/docs/main/input-data/#time-series"&gt;file naming&lt;/a&gt;.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Create a new Output Folder&lt;/strong&gt; for the scenario. Tools always write to the same subfolder names, so a shared folder would overwrite your historical results or reuse the wrong &lt;code&gt;a/&lt;/code&gt;.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Daily Fuel Moisture&lt;/strong&gt;: run it with the scenario weather.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Frequency Probability&lt;/strong&gt;: &lt;strong&gt;Load&lt;/strong&gt; the historical parameter file. Point the inputs to the scenario data and set the scenario period.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Calculate Burned Area&lt;/strong&gt;: &lt;strong&gt;Load&lt;/strong&gt; the historical parameter file and select &lt;strong&gt;Use existing data&lt;/strong&gt;. As &lt;strong&gt;Existing q&lt;/strong&gt;, select the historical q files, copied to a separate folder as described in &lt;a href="https://docs.flamhub.org/docs/main/flam/burned-area/#output"&gt;Calculate Burned Area&lt;/a&gt;.&lt;/li&gt;&#10;&lt;li&gt;Optionally, run &lt;strong&gt;Spread Simulation&lt;/strong&gt;.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;blockquote class="book-hint info"&gt;&#10;&lt;p&gt;The &lt;strong&gt;¶&lt;/strong&gt; button loads the &lt;em&gt;historical&lt;/em&gt; paths from the configuration. After clicking it, replace every time-dependent input (weather, moisture, P, and population and fuel if they change) with its scenario equivalent.&lt;/p&gt;</description></item></channel></rss>