Simulate
FVS runs in the R worker, not here. Saving a grouping fills the queue; the worker drains it; this page reads it.
- 1Queue status
Each scoping group is tracked as queued, running, complete, or failed.
- 2Representative stands
FVS runs against the representative stand and variant recorded for each saved group.
- 3Pathway Compilation
Completed simulation trees can be compiled into the treatment sequences used by Pathways and Toggle.
- 4Objective calculation
Management-objective summaries are calculated from available simulation output rather than estimated in the interface.
This page reads the project’s current FVS queue and post-processing state. Completion and period counts are shown only where the database provides them.
Queue
Every group has been simulated.
10 scoping groups queued for FVS
Demo: replays the Kökez run made with the FEMS worker (rFVS, SN variant) — the values are the real FVS output.
What the worker has to do
One FVS run per representative stand, per variant it has to load.
- Representative stands
- 10
- FVS variants
- SN
Outstanding before FVS can run
The worker will fail on each of these. They are shown in the order it reaches them.
- Every group has treatments2, 4, 5, 6, 7
- Species named in treatments mapped to FVS species
- Regenerating treatments have a regeneration defined
- Every group has regeneration3, 4, 5, 6, 7, 8
- Regeneration species mapped to FVS species
After the run
Two passes that turn finished simulations into what the analysis modules read. Both are pure SQL and run here rather than in the worker.
Reduce the simulated trees to per-stand metrics — density, diameter, volume, cover — which the management objectives read.
Walk the tree of simulated stands and name each distinct treatment sequence. These are what Toggle allocates area between.