📊 Reviewing, Mapping, & Shading Results - heinsch-fa/behave-app GitHub Wiki
- Core Objective: Preview tabular calculations, convert physical run distance to paper map scales, and apply conditional visualization filters.
- Estimated Reading Time: 4 minutes.
- Prerequisites: Complete your variable configurations in 🎛️ Managing Outputs & Inputs.
The Review Run screen acts as a vital data verification checkpoint before you commit to producing final results. This interface allows you to test if your outputs look mathematically reasonable and customize your data view without distorting the underlying science.
Look at the results carefully. Do they appear reasonable? Do they match fire observations?
- Action Required: Are all required outputs included?
- Action Required: Is the range of outputs outputs reasonable when compared to current or past fire behavior.
- Action Required: Verify that the inputs are reasonable for the time of year.
If outputs are not reasonable, think about the following questions to identify any changes that should be made.
-
How are the results different than expected?
- Were site conditions different than those in the model?
- How well did the fuel models capture fire behavior?
- Which inputs are used to calculate that output?
- Do the inputs make sense?
- If the inputs make sense, is the run revealing something you have not thought of?
- Are the inputs based on measurements taken at the time of the burn?
- Were they been obtained from a nearby weather station or based on historical values for the time of year?
- If taken from a SPOT forecast, have you provided feedback (good or bad) to the local National Weather Service Office about the accuracy of the forecast?
Translate real-world linear distances into map distances based on the scale of the map you will be using.
- Action Required: Ensure the run includes outputs that are measured in distance. This can be Spread Distance calculated for Heading, Flanking, or Backing fire, or for fire burning in a specified direction.
- Action Required: Check the box next to Convert To Map Units (turned off by default).
- Action Required: Toggle the radio button to select your desired spatial units: in (inches) or cm (centimeters).
- Action Required: Enter the target layout scale into the Map Representative Fraction (1:x) field (e.g., input 24000 to match standard USGS 7.5-Minute Topographic Quadrangles).
When you generate the final results, a separate table is produced for spread distance in map units.
Highlight specific thresholds for change or prescribed fire parameters values on the Review page.
- Action Required: Locate the variable of interest in the table, and check the box under the ENABLED? column.
- Action Required: Type your boundary thresholds directly into the MINIMUM and MAXIMUM boxes.
- Important Detail: These thresholds are used to identify which outputs meet the specified criteria (green) and which ones do not (red). If a value fails to meet the criteria, the same cell in related outputs is also assumed to fail the criteria. That way, regardless of the table you are reviewing, you can see which inputs do not meet the criteria.
- Map Representative Fraction Text Box: Translates standard real-world calculation steps into readable layout dimensions.
- Output Variable Column: Lists active targets along with their native unit measurements (e.g., Flame Length (ft)).
- Range Metric Indicator: Displays the absolute min/max mathematical values generated by your inputs to help you choose a reasonable target.
- Filtering Warning: Set realistic conditions based on a prescription that has been developed or outputs that are required. Be careful when setting conditions for multiple variables - you can quickly reject all outputs.
The tables below were shaded using the conditions shown above with Rate of Spread ≤ 40 chains per hour and Flame Length 1-9 feet.
Here are some things to think about as you review outputs with table shading.
- To prevent misinterpretation, Behave7 reviews the outputs for all spread directions (e.g., Heading, Flanking, and Backing) separately. If the criteria are not met by a heading fire, but are met by backing fire, the two tables will reveal that as the cell will be red for heading fire and green for backing fire. This can help identify the type of firing pattern you want to use. In the example below, Heading Fire Exceeds the criteria for Rate of Spread when the Midflame Wind Speed is 8 mi/h. Flanking and Backing Fire do not reach the criteria. Fire Area is calculated from Heading Rate of Spread, so its shading is the same as that for Heading Fire. _Note: If you were to change the minimum conditions that must be met (e.g., Flame Lengths 3-9 feet, the low end of the Fire Area table would not be shaded red since Heading Flame Length > 3 ft.
- Related outputs are also shaded so that you can more easily determine what outputs occur when the criteria are met. For example, if a value for Heading Rate of Spread does not meet the criteria, the same cell will be shaded red for Heading Flame Length. In this example, Flame Lengths below 9 ft are rejected when 1-hr Fuel Moisture is 7-9% and Midflame Wind Speed is 8 mi/h because the Rate of Spread exceeds the threshold.
- If you have multiple criteria, cells that do not meet the criteria for any of the outputs are shaded in all tables.
- Note: Variables not related to the selected outputs (e.g., Total live fuel load and Total dead fuel load) do not display color shading.
- 📄 Previous: 🎛️ Managing Outputs & Inputs — Generate variables via the step Range Selector.
- 📄 Next: 🧮 Standalone Calculators — Use standalone tools to compute values such as 1-Hour Fuel Moisture, Slope from Map Measurements, or Safe Separation Distance and Safety Zone Size.
