Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FBP Go: Flank & Fire Spread Distance; inverted outputs #4251

Open
NicolasLivanos opened this issue Feb 5, 2025 · 0 comments
Open

FBP Go: Flank & Fire Spread Distance; inverted outputs #4251

NicolasLivanos opened this issue Feb 5, 2025 · 0 comments
Assignees
Labels
4Refinement this ticket is ready for refinement with the team Bug Something isn't working

Comments

@NicolasLivanos
Copy link
Collaborator

NicolasLivanos commented Feb 5, 2025

Actual Behaviour

BB 1: " Our fire spread distance for flank and fire spread distance for backing are wrong.
In the screen shot I sent the Backing should be 47m where the flanking should be 161.7m.
There numbers are just backwards "

Steps To Reproduce + Inputs

Open FBP Go + enter the following parameters:
Fuel Type = C-2 boreal spruce
Time elapsed = 60 minutes
Lat = 37.00
Long = -122.00
Elevation = 100 m
Wind = 20 km/h
Direction = SE 135
Slope = 0%
Aspect = North 0.0
BUI = 35
FFMC = 90

Screenshot of Advanced Fire Behaviour Outputs

Image

Expected Behaviour

In the Advanced Fire Behaviour Outputs:
Backing should be 47m and flanking should be 161.7m

@NicolasLivanos NicolasLivanos added the Bug Something isn't working label Feb 5, 2025
@NicolasLivanos NicolasLivanos changed the title FBP GO: Flank Fire Spread Distance FBP Go: Flank Fire Spread Distance Feb 5, 2025
@NicolasLivanos NicolasLivanos changed the title FBP Go: Flank Fire Spread Distance FBP Go: Flank & Fire Spread Distance; inverted numbers Feb 5, 2025
@NicolasLivanos NicolasLivanos changed the title FBP Go: Flank & Fire Spread Distance; inverted numbers FBP Go: Flank & Fire Spread Distance; inverted outputs Feb 5, 2025
@NicolasLivanos NicolasLivanos added the 4Refinement this ticket is ready for refinement with the team label Feb 5, 2025
@brettedw brettedw self-assigned this Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4Refinement this ticket is ready for refinement with the team Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants