You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Control lines that hold only where the fire is weak? #254
@filippi, would you want ForeFire to have control lines that hold only where the fire is weak? Roads and DFCI tracks often stop a flank or a night front, but not a head run.
I tried roads as non-burnable cells on a real case (Gonfaron, Var, 2021; ensemble as in #172), and a static break is wrong either way:
DFCI tracks as breaks stop the first run in the plain: the median head error goes from 4.9 km to 11.6 km. The real fire crossed every track at 3–7 km/h, with spot fires 1–2 km ahead.
Without them, the flanks keep going. The real head stopped on the D98 and the A92 track around midnight, with crews and tactical fire, and the flanks were held overnight. The ensemble puts p > 0.5 on 54 km² that never burnt, almost all of it on one flank.
Two ways I can see:
A control-line layer: a node on a marked cell stops if its rate of spread (or Byram intensity) is below a threshold, and goes through otherwise.
A fuel layer that changes at a given time, so a road becomes a break from some hour on. It's simpler, but it needs the suppression timing as an input.
Is this something you already handle another way, or would you take a PR for 1?
Hi Hugo,
One way oh handeling that is momentum, this is why a node never go from
fast to 0, thete is a momentum parameter in firenode.cpp
Basically the width of the obstacle is tge controlling parameter there
The physical parameter would be the fire depth. Other than that, spotting
is important, as well as crowning, not really here yet.
*Jean-Baptiste Filippi*
Directeur de recherche CNRS | Research Director
Sciences Pour l'Environnement (UMR CNRS 6134)
Università di Corsica Pasquale Paoli
20250 Corte, France - firecaster.org
Le mar. 3 nov. 2026, 12:32, Hugo ***@***.***> a écrit :
*HugoFara* created an issue (forefireAPI/forefire#254)
<#254>
@filippi <https://github.com/filippi>, would you want ForeFire to have
control lines that hold only where the fire is weak? Roads and DFCI tracks
often stop a flank or a night front, but not a head run.
I tried roads as non-burnable cells on a real case (Gonfaron, Var, 2021;
ensemble as in #172 <#172>),
and a static break is wrong either way:
- DFCI tracks as breaks stop the first run in the plain: the median
head error goes from 4.9 km to 11.6 km. The real fire crossed every track
at 3–7 km/h, with spot fires 1–2 km ahead.
- Without them, the flanks keep going. The real head stopped on the
D98 and the A92 track around midnight, with crews and tactical fire, and
the flanks were held overnight. The ensemble puts p > 0.5 on 54 km² that
never burnt, almost all of it on one flank.
Two ways I can see:
1. A control-line layer: a node on a marked cell stops if its rate of
spread (or Byram intensity) is below a threshold, and goes through
otherwise.
2. A fuel layer that changes at a given time, so a road becomes a
break from some hour on. It's simpler, but it needs the suppression timing
as an input.
Is this something you already handle another way, or would you take a PR
for 1?
*Drafted with Claude Opus 5.5.*
—
Reply to this email directly, view it on GitHub
<#254?email_source=notifications&email_token=AAUZ7CVBWZ2GMPV2V62E2Q35XHF6XA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NRRHAZDMMZTGQ3TLJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FMMZXW65DFOJPWG3DJMNVQ>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAUZ7CRKZDGRIFXXYOV23R35XHF6XAVCNFSNUABEKJSXA33TNF2G64TZHMYTOMRUHE3TKMJ3JFZXG5LFHM3DCOBSGYZTGNBXGWQXMAQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
Thanks. I tested momentum with a straight non-burnable strip on flat SH5 (Farsite, 5.3 m/s, 2 h), one strip across the wind for the head and one along it for the flank, in separate runs:
relax
minSpeed
head crosses up to
flank crosses up to
free flank extent
0.5
0
nothing, even 30 m
nothing
0.8 km
0.2
0
60 m
60 m
1.75 km
0.2
0.05
30 m
30 m
1.7 km
0.1
0
90 m
90 m
1.97 km
0.1
0.05
60 m
60 m
1.8 km
So the obstacle's width is the control, as you say, but head and flank cross at the same width. Lowering relax also makes the fire 2.5× wider (#253), so I can't tune it for this.
Fire depth might separate them, but Farsite doesn't read it: only Balbi2015, BalbiUnsteady and FrontDepthDriven do. Would you make a break depend on depth inside one of those, or is there a way to use it with Farsite?
Spotting would matter for this fire too (spot fires of 1–2 km). If you have a plan for it, I'd be glad to use Gonfaron as a test case.
Drafted with Claude Opus 5.5, reviewed by a me before posting.
Activity
filippi commentedon Nov 3, 2026
HugoFara commentedon Nov 3, 2026
Thanks. I tested momentum with a straight non-burnable strip on flat SH5 (Farsite, 5.3 m/s, 2 h), one strip across the wind for the head and one along it for the flank, in separate runs:
So the obstacle's width is the control, as you say, but head and flank cross at the same width. Lowering
relaxalso makes the fire 2.5× wider (#253), so I can't tune it for this.Fire depth might separate them, but
Farsitedoesn't read it: onlyBalbi2015,BalbiUnsteadyandFrontDepthDrivendo. Would you make a break depend on depth inside one of those, or is there a way to use it withFarsite?Spotting would matter for this fire too (spot fires of 1–2 km). If you have a plan for it, I'd be glad to use Gonfaron as a test case.
Drafted with Claude Opus 5.5, reviewed by a me before posting.