Organization
 
Log In
Fire Behavior

Files

Tables

Tiles

Files
103

What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.

Arvada1lcp.zip

v0
2 weeks ago

Arvada90th.tif

v0
2 years ago

Arvada90thnew.tif

v0
2 years ago

Arvada97th.tif

v0
2 years ago

Arvada97thBP.tif

v0
2 years ago

Arvada97thBP.zip

v0
8 months ago

Arvada97thnew.tif

v0
2 years ago

Mitigation Simulations: Run 1 (2026-10-22 16:48)

Built 2 weeks ago
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
2 weeks ago

Mitigation Simulations: Run 1 (copy) (2026-10-22 17:29)

Built 2 weeks ago
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
2 weeks ago

Mitigation Simulations: Run 1 (copy) — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 1 (copy) (2026-10-22 17:29)".
v0
2 weeks ago

Mitigation Simulations: Run 1 (copy) — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 1 (copy) (2026-10-22 17:29)".
v0
2 weeks ago

Mitigation Simulations: Run 1 (copy) — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 1 (copy) (2026-10-22 17:29)".
v0
2 weeks ago

Mitigation Simulations: Run 1 (copy) — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 1 (copy) (2026-10-22 17:29)".
v0
2 weeks ago

Mitigation Simulations: Run 1 (copy) — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 1 (copy) (2026-10-22 17:29)".
v0
2 weeks ago

Mitigation Simulations: Run 1 (copy) — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 1 (copy) (2026-10-22 17:29)".
v0
2 weeks ago

Mitigation Simulations: Run 1 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 1 (2026-10-22 16:48)".
v0
2 weeks ago

Mitigation Simulations: Run 1 — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 1 (2026-10-22 16:48)".
v0
2 weeks ago

Mitigation Simulations: Run 1 — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 1 (2026-10-22 16:48)".
v0
2 weeks ago

Mitigation Simulations: Run 1 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 1 (2026-10-22 16:48)".
v0
2 weeks ago

Mitigation Simulations: Run 1 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 1 (2026-10-22 16:48)".
v0
2 weeks ago

Mitigation Simulations: Run 1 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 1 (2026-10-22 16:48)".
v0
2 weeks ago

Mitigation Simulations: Run 10 - Beartooth and Pine Ridge (2026-10-26 12:51)

Built 7 days ago
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
7 days ago

Mitigation Simulations: Run 10 - Beartooth and Pine Ridge — Assets reached

Built 7 days ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 10 - Beartooth and Pine Ridge (2026-10-26 12:51)".
v0
7 days ago

Mitigation Simulations: Run 10 - Beartooth and Pine Ridge — Burning edge by time

Built 7 days ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 10 - Beartooth and Pine Ridge (2026-10-26 12:51)".
v0
7 days ago

Mitigation Simulations: Run 10 - Beartooth and Pine Ridge — Fire pathways

Built 7 days ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 10 - Beartooth and Pine Ridge (2026-10-26 12:51)".
v0
7 days ago

Mitigation Simulations: Run 10 - Beartooth and Pine Ridge — Perimeters by time

Built 7 days ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 10 - Beartooth and Pine Ridge (2026-10-26 12:51)".
v0
7 days ago

Mitigation Simulations: Run 10 - Beartooth and Pine Ridge — Roads cut off

Built 7 days ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 10 - Beartooth and Pine Ridge (2026-10-26 12:51)".
v0
7 days ago

Mitigation Simulations: Run 10 - Beartooth and Pine Ridge — Roads reached

Built 7 days ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 10 - Beartooth and Pine Ridge (2026-10-26 12:51)".
v0
7 days ago

Mitigation Simulations: Run 11 - Spring Mesa (2026-10-26 13:29)

Built 7 days ago
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
7 days ago

Mitigation Simulations: Run 11 - Spring Mesa — Assets reached

Built 7 days ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 11 - Spring Mesa (2026-10-26 13:29)".
v0
7 days ago

Mitigation Simulations: Run 11 - Spring Mesa — Burning edge by time

Built 7 days ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 11 - Spring Mesa (2026-10-26 13:29)".
v0
7 days ago

Mitigation Simulations: Run 11 - Spring Mesa — Fire pathways

Built 7 days ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 11 - Spring Mesa (2026-10-26 13:29)".
v0
7 days ago

Mitigation Simulations: Run 11 - Spring Mesa — Perimeters by time

Built 7 days ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 11 - Spring Mesa (2026-10-26 13:29)".
v0
7 days ago

Mitigation Simulations: Run 11 - Spring Mesa — Roads cut off

Built 7 days ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 11 - Spring Mesa (2026-10-26 13:29)".
v0
7 days ago

Mitigation Simulations: Run 11 - Spring Mesa — Roads reached

Built 7 days ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 11 - Spring Mesa (2026-10-26 13:29)".
v0
7 days ago

Mitigation Simulations: Run 12 - Spring Mesa (2026-10-26 13:52)

Built 7 days ago
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
7 days ago

Mitigation Simulations: Run 12 - Spring Mesa — Assets reached

Built 7 days ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 12 - Spring Mesa (2026-10-26 13:52)".
v0
7 days ago

Mitigation Simulations: Run 12 - Spring Mesa — Burning edge by time

Built 7 days ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 12 - Spring Mesa (2026-10-26 13:52)".
v0
7 days ago

Mitigation Simulations: Run 12 - Spring Mesa — Fire pathways

Built 7 days ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 12 - Spring Mesa (2026-10-26 13:52)".
v0
7 days ago

Mitigation Simulations: Run 12 - Spring Mesa — Perimeters by time

Built 7 days ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 12 - Spring Mesa (2026-10-26 13:52)".
v0
7 days ago

Mitigation Simulations: Run 12 - Spring Mesa — Roads cut off

Built 7 days ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 12 - Spring Mesa (2026-10-26 13:52)".
v0
7 days ago

Mitigation Simulations: Run 12 - Spring Mesa — Roads reached

Built 7 days ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 12 - Spring Mesa (2026-10-26 13:52)".
v0
7 days ago

Mitigation Simulations: Run 3 (2026-10-22 17:58)

Needs upload
Fire run for the simulation "Mitigation Simulations", from Simulations.
2 weeks ago

Mitigation Simulations: Run 4 (2026-10-22 18:55)

Built 2 weeks ago
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
2 weeks ago

Mitigation Simulations: Run 4 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 4 (2026-10-22 18:55)".
v0
2 weeks ago

Mitigation Simulations: Run 4 — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 4 (2026-10-22 18:55)".
v0
2 weeks ago

Mitigation Simulations: Run 4 — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 4 (2026-10-22 18:55)".
v0
2 weeks ago

Mitigation Simulations: Run 4 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 4 (2026-10-22 18:55)".
v0
2 weeks ago

Mitigation Simulations: Run 4 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 4 (2026-10-22 18:55)".
v0
2 weeks ago

Mitigation Simulations: Run 4 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 4 (2026-10-22 18:55)".
v0
2 weeks ago

Mitigation Simulations: Run 4 — Spot landings

Built 2 weeks ago
Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 4 (2026-10-22 18:55)".
v0
2 weeks ago

Mitigation Simulations: Run 4 — Spotting

Built 2 weeks ago
Embers, one line per spotting source: from a burning cell with a maximum spot distance to where its farthest ember lands (FlamMap's maximum spot distance and direction under the run's wind, not the engine's random draws). `minutes` when the source burned, `distanceMeters`, `fireType` 1 surface / 2 passive crown / 3 active crown at the source, `landingMinutes` when the fire reached the landing, `spotFire` true when the landing was outside the fire at the time (worked out in DuckDB against the arrival table). The longest in each part of the fire when there are more than a map can draw. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 4 (2026-10-22 18:55)".
v0
2 weeks ago

Mitigation Simulations: Run 5 (2026-10-22 19:22)

Built 2 weeks ago
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
2 weeks ago

Mitigation Simulations: Run 5 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 5 (2026-10-22 19:22)".
v0
2 weeks ago

Mitigation Simulations: Run 5 — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 5 (2026-10-22 19:22)".
v0
2 weeks ago

Mitigation Simulations: Run 5 — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 5 (2026-10-22 19:22)".
v0
2 weeks ago

Mitigation Simulations: Run 5 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 5 (2026-10-22 19:22)".
v0
2 weeks ago

Mitigation Simulations: Run 5 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 5 (2026-10-22 19:22)".
v0
2 weeks ago

Mitigation Simulations: Run 5 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 5 (2026-10-22 19:22)".
v0
2 weeks ago

Mitigation Simulations: Run 6 (2026-10-22 21:36)

Built 2 weeks ago
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
2 weeks ago

Mitigation Simulations: Run 6 - Beartooth and Pine Ridge (2026-10-25 20:02)

Built last week
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
last week

Mitigation Simulations: Run 6 - Beartooth and Pine Ridge — Assets reached

Built last week
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 6 - Beartooth and Pine Ridge (2026-10-25 20:02)".
v0
last week

Mitigation Simulations: Run 6 - Beartooth and Pine Ridge — Burning edge by time

Built last week
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 6 - Beartooth and Pine Ridge (2026-10-25 20:02)".
v0
last week

Mitigation Simulations: Run 6 - Beartooth and Pine Ridge — Fire pathways

Built last week
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 6 - Beartooth and Pine Ridge (2026-10-25 20:02)".
v0
last week

Mitigation Simulations: Run 6 - Beartooth and Pine Ridge — Perimeters by time

Built last week
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 6 - Beartooth and Pine Ridge (2026-10-25 20:02)".
v0
last week

Mitigation Simulations: Run 6 - Beartooth and Pine Ridge — Roads cut off

Built last week
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 6 - Beartooth and Pine Ridge (2026-10-25 20:02)".
v0
last week

Mitigation Simulations: Run 6 - Beartooth and Pine Ridge — Roads reached

Built last week
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 6 - Beartooth and Pine Ridge (2026-10-25 20:02)".
v0
last week

Mitigation Simulations: Run 6 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 6 (2026-10-22 21:36)".
v0
2 weeks ago

Mitigation Simulations: Run 6 — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 6 (2026-10-22 21:36)".
v0
2 weeks ago

Mitigation Simulations: Run 6 — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 6 (2026-10-22 21:36)".
v0
2 weeks ago

Mitigation Simulations: Run 6 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 6 (2026-10-22 21:36)".
v0
2 weeks ago

Mitigation Simulations: Run 6 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 6 (2026-10-22 21:36)".
v0
2 weeks ago

Mitigation Simulations: Run 6 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 6 (2026-10-22 21:36)".
v0
2 weeks ago

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:05)

Built last week
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:06)

Built last week
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:30)

Built last week
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:56)

Built last week
Fire run for the simulation "Mitigation Simulations", from Simulations.
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Assets reached

Built last week
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:06)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Assets reached

Built last week
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:56)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Assets reached

Built last week
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:30)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Assets reached

Built last week
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:05)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Burning edge by time

Built last week
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:06)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Burning edge by time

Built last week
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:56)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Burning edge by time

Built last week
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:30)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Burning edge by time

Built last week
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:05)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Burning edge by time, without the timed ignitions

Built last week
The part of the edge still burning at each time step of the fire without the run's timed ignitions (worked out in DuckDB from its perimeters). Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:05)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Fire pathways

Built last week
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:30)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Fire pathways

Built last week
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:05)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Fire pathways

Built last week
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:56)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Fire pathways

Built last week
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:06)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Perimeters by time

Built last week
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:30)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Perimeters by time

Built last week
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:56)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Perimeters by time

Built last week
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:05)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Perimeters by time

Built last week
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:06)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Perimeters by time, without the timed ignitions

Built last week
The fire as it would have gone without the run's timed ignitions: spread from the first one's time on the same ground with the run's own barriers, one polygon per time step, cumulative, at the run's own steps. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:05)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Roads cut off

Built last week
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:56)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Roads cut off

Built last week
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:30)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Roads cut off

Built last week
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:06)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Roads cut off

Built last week
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:05)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Roads reached

Built last week
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:56)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Roads reached

Built last week
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:06)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Roads reached

Built last week
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:30)".
v0
last week

Mitigation Simulations: Run 7 - Beartooth and Pine Ridge — Roads reached

Built last week
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Mitigation Simulations: Run 7 - Beartooth and Pine Ridge (2026-10-25 21:05)".
v0
last week
Bintel