search

WISE-Developers / Project_issues

This handles incoming tickets like bugs and feature requests
GNU Affero General Public License v3.0
2 stars 0 forks source link

[WISE FR]: Auto-stop of simulations - termination module. #117

Open RobBryce opened 2 years ago

RobBryce commented 2 years ago

Contact Details

rbryce@heartlandsoftware.ca

What is needed?

We currently have a few options to stop a simulation - e.g. when a fire reached the edge of the fuel data. We also have a few settings for self-extinguishment, but without user defined thresholds.

I ask that we consider adding a few other modes where the simulation can stop based on a threshold, such as a percentage of FI through-out the perimeter (for a duration of time). E.g. if a fire perimeter is completely below, say, 2500kW/m, then it can in theory be managed and thus a 3 week duration modelling can stop earlier.

How will this improve the project or tool?

Experimental burn simulations, related to some of Jen Beverly's and Cordy Tymstra's studies.

TODO

BadgerOnABike commented 2 years ago

Its an interesting concept, I'd be curious to pull it back from intensity to some weather values as well and just have lots of ways to stop fire. That would largely be up to some user discretion though.

Personally, I would be modelling the whole thing out and showing where long term low intensity exists as a method to say 'we would most likely be able to manage the fire here, but if we couldn't this is the extent it would achieve". Much the same way I treat fire breaks.

spydmobile commented 2 years ago

This idea makes a huge amount of sense to me. I see it as a new point of modularity and extensibility. Starting with termination conditions of the simulation based on a formula of metrics logically ANDed or ORed. These could give way in the future to spatial patches that could end propagation in parts of the active perimeter, but that is a future discussion.

I see the value of this in both the static analysis context, but also the operational modelling context and would like to explore this further.

@RobBryce You mentioned Cordy & Jen, is this something you are cooking up on your own, or is there maybe a possible champion for this feature by way of an HSS Client? No need for names as these issues are in the public domain.

RobBryce commented 2 years ago

It's more Cordy than Jen. And yes, there's a project that can champion the motivation and costs of this.

I'm not sure how it'd fit into an operational role, but that sounds like a discussion worth having!

We haven't created complex OR and AND operations for burning conditions, so maybe that's worth considering too. Right now, I wanted to simply take an OR approach like we do burning conditions.

RobBryce commented 1 year ago

I'd like to merge this work back in (first cut), contribution by Alberta Parks.