Change Log - heinsch-fa/behave-app GitHub Wiki
Behave version 7 is undergoing active development as we continue to add both existing elements from BehavePlus v6 (BP v6), aspects of the First Order Fire Effects Model (FOFEM) and additional new functionality. Since there are frequent updates, please check the the Latest Release page to ensure you have the latest version and to view any changes not yet listed below. Click on Future Updates to see major updates planned for future releases.
- When the Direction Mode is Heading, Flanking, Backing, the same Table Shading Filter criteria are applied to results for all three directions of spread. Before, there were different criteria for each rate of spread, making it impossible to apply a single set of criteria.
- The minimum and maximum allowable values for the filters include the combined outputs from all three direction modes.
- This makes it easier for users to specify a desired range for fire behavior (e.g., rate of spread or flame length), while Behave7 identifies conditions in all spread direction(s) that meet these criteria. In the example shown below, Flame Length must be less than or equal to 7 ft, and Fire Area must be less than or equal to 1200 acres.

- The style for the Table Shading Filter has been updated to make it easier to read.
- A green circle with a white checkmark identifies outputs that meet all relevant criteria, while a red circle with a white X identifies outputs that do not meet the specified criteria.
- Outputs that do not meet these criteria are marked with a red circle. Table shading is also applied to related outputs.
- Heading fire behavior does not meet those conditions because Flame Length values exceed the threshold if 1-hr Fuel Moisture = 5%, or if 1-hr Fuel Moisture = 10% and 20-Foot Wind Speed is greater than or equal to 10 mi/h.
- Flanking fire behavior does not meet those criteria if 1-hr Fuel Moisture is 5% and the 20-Foot Wind Speed is 10 mi/h or more.
- Backing fire behavior (not shown) met all criteria.
- Criteria for Fire Perimeter and Fire Area are the same as for Heading Fire Behavior since Heading Rate of Spread is an input to these calculations, but Flanking ROS and Backing ROS are not.

- Table Shading Filter Values Now Include Decimals
- Decimals can be used in the criteria for Table Shading Filters, even if the outputs are rounded to the nearest whole number (no decimals).
- Behave7 stores the actual value in the background regardless of what is displayed.
- Therefore, it can identify if a use criteria that contain a decimal.
- Rounding results in the Table Shading Filters also apply to the Output Tables, providing consistency among results.
- Decimals can be used in the criteria for Table Shading Filters, even if the outputs are rounded to the nearest whole number (no decimals).
- There is consistency between the Table Shading Filters and Output tables when results are rounded to the nearest number.
- This was especially noticeable when outputs appeared as "<1". Formerly, values that were < 0.5 were set to "0" by the Table Shading Filter and values > 0.5 were set to "1". This led to values of "<1" potentially having different table shading values, even if users could not see a difference.
- When Surface & Crown Results include Fire Type, Output Tables have an Optional color code, based on whether a fire is Surface, Torching, or Crowning.
- Color by: Fire Type is selected by default. To turn it off, click on the white button below Table Settings.
- Graph Settings have been moved to the Results page and there are separate Table Settings and Graph Settings.
- When three inputs have multiple values, Output Tables colors are updated to make them easier to distinguish.
- This also applies when the Direction Mode is set to Heading, Flanking, Backing.
- If a result is less than one, it appears as "<1". This only applies to outputs that have whole numbers.
- If you want to see values less than one (e.g., 0.1, 0.6), adjust the number of decimal places in Settings > General Units.
- When Map Units are enabled, a separate Output table is created so that they are easier to find.
- When all Inputs have a single value (single-ranged Inputs), Output Tables show the Outputs in rows, instead of columns.
- The "CSV Download" option has been moved above all Output Tables. It is now a button instead of a link.
- Graph axes have been updated so that the axes extend beyond the maximum calculated value.
- The Graph Legend is no longer displayed if there are only single-ranged Inputs.
- Specific Updates: Surface & Contain Workflow
- The Contained Acres diagram is automatically generated when the Contain Mode is set to Calculate Minimum Production Rate Only.
- The Minimum Fireline Production Rate Summary Table is only created when When the Contain Mode is set to Calculate Minimum Production Rate Only. Contain Mode is set to Add Resources, the Minimum Fireline Production Rate Summary Table will not appear in Results. To calculate the Minimum Fireline Production Rate Summary Table, remove all resources.
- The Standard Worksheet was updated for easier reading and to create consistency with the Guided workflow.
- When Maximum Spotting Distance from a Wind-Driven Surface Fire is an Output, the worksheet contains "Fuel Model" and not "Flame Length".
- In Contain, Elapsed Time was removed and Fire Size at Report was added. Inputs can be in either acres or hectares.
- In Surface & Crown, the default Direction Mode is now Heading and is displayed with the inputs. The Direction Mode cannot be changed because the crown fire models assume heading fire.
- Worksheet headers will always show Surface first, making them consistent with the workflows.
- Bug fixes
- In the Guided workflow, Fire Behavior Outputs will always be calculated and reported, even if the sub-module is not selected.
- If the selected Fuel Moisture option is Dead, Live Herb, and Live Woody Categories, users must enter a value for Dead Fuel Moisture since there is at least fuel load in at least one dead fuel category for all fuel models included with Behave7.
- Notes now have a drop-down menu option for Categories.
- Notes are not required, but are highly recommended,
- Categories are dependent on workflow.
- If a category is missing, select Other and enter your notes.
- Notes can be added to the Review Run and Results pages.
- You can use the Enter key to add New Lines to Notes.
- All Calculators include Validations for the range of allowable input values.
- The default Elevation Difference in the 1-HR Fuel Moisture calculator is set to Level.
- The General Units categories in Settings no longer allow inappropriate or extraneous options.
The following updates are currently planned for release in late 2026 or 2027.
All Modules: Custom Fuel Models and Moisture Scenarios
- Description: Users will have the ability to import, edit, and create their own custom fuel models and custom moisture scenarios, to use in their analysis.
- Status: Planned for release in Q4 2026
UI/UX: Significant updates are planned to improve the User Interface
-
Description: The User Interface is being updated. The following changes are currently being planned.
- Reduce whitespace to increase useable workspace.
- Modify the workspace to adjust to screen size - both larger and smaller screens.
- Update the Review Runs and Results pages to make them both more compact and easier to read.
- Modify the Settings workflow so that changes to settings are more intuitive.
- Status: Planned for release in Q4 2026 or Q1 2027
All Modules: Advanced Fuel Model Filtering Options
- Description: In addition to current options to select Fuel Model Types and the search function, users will be able to filter fuel models by class (e.g., Mediterranean fuel models) as well as categories such as Grass. Filters will also included for custom fuel models.
- Status: Planned for release in Q4 2026 or Q1 2027
Results: Improved display for three ranged outputs
- Description: Tables will be displayed side-by-side to reduce vertical scrolling. If Surface fire behavior for Heading, Flanking, Backing is selected, options will be available to group by direction mode (for example, heading) or variable (for example, Flame Length)
- Status: Planned for release in Q1 2027
FOFEM: The First Order Fire Effects Model (FOFEM) will be added to the interface
- Description: FOFEM's Consumption, Emissions, and Mortality modules will be added to the interface: This includes both creating new modules for the three elements and updating the Mortality module in Behave to include the latest calculations for Probability of Mortality.
- Status: Planned for release in 2027