Scenario Simulation¶

How scenario definitions become parallel simulation runs: from processed features and scenario mappings, through building upgrades and copied simulation instances, to persistence and GIS export.

Tap the diagram to open it full screen.

Scenario mappings¶

Preprocessing feeds Scenario Mappings, which applies measure packages according to selection criteria, once per scenario. It is drawn as a stacked card for that reason.

Building upgrade scenarios¶

Building Upgrade Scenarios are copies of the Building produced by Feature2Building, with scenario selections and measures applied. Feature2Building supplies the copy; Scenario Mappings supplies the applied selections and scenario measures.

Like Scenario Mappings, this is a stacked card: one set of upgraded buildings exists per scenario. The upgraded buildings write their definitions to the Definition Tables, so a scenario's building and zone definitions are persisted alongside the baseline's.

Parallel simulation instances¶

Each set of upgraded buildings produces a copy of the simulation instance. The Baseline runs the reference case without scenario upgrades, taking zone geometry and location directly from Feature2Building.

Baseline and scenario instances are ranked side by side in the diagram to make the parallel explicit. Drill into Simulation to see the stages each instance runs: precompute boundary conditions, Zone5R1C, and results aggregation. These are the same stages described in Simulation Stages and Data Flow.

Persistence and export¶

All instances write into the same Result Tables, and site energy results reach GIS Tables as a selective projection. Results GeoJSON is exported from GIS properties and GIS results, exactly as in the baseline flow.

Because every scenario's results are persisted rather than held in memory, they remain available for the Post-hoc Scenario Mixer after the run finishes.