Documentation
Documentation
How to install, run and read pyFDS-Evac. Pick the path that fits you; each page links to the next.
New to pyFDS-Evac. Install it, run one scenario, then read real FDS output:
Requirements, install, and a one-line check.
One run on a tracked scenario, with no FDS output needed.
From tracked FDS output to FED histories and exit times, and how to spot a run that succeeds but is wrong.
150 agents, a 2 MW FDS fire, and a figure for every step.
Engineer with your own FDS case. Prepare the deck, run, and read the results:
Which slices and yields a deck must provide, and the silent failure modes.
Running simulations, every CLI flag, and the post-processing scripts.
The keys a scenario reads, with their defaults.
Every file a run writes, column by column, and how to read the results.
How to get RSET with its spread from runs over several seeds.
Error messages and warnings, with their cause and fix.
Research-software status, library-level parameters, and what is not modelled.
Coming from FDS+Evac. Map your inputs, then check where the two tools differ:
Where each FDS+Evac input goes, and what has no equivalent.
Mechanism by mechanism against FDS+Evac, where the two agree and where they differ.
Understanding the models, maintaining the code. The ideas, the code paths, and the evidence:
Speed, route choice and wayfinding: the ideas behind the models, with figures.
Configuration, API, and the ISO 20414 Table 21 runs.
Cost formulas, the exposure gate, and the decision pipeline.
How one quantity refuses a route and orders the survivors.
Sign legibility, per-agent cognitive maps, and the examples of the talk.
How slice values are read at agent positions.
Each model checked against hand calculations, published tables and FDS output.
Visibility Seminar 2026 slides: the theory behind speed, routing and wayfinding.
Last updated on