KSLCore/ksl.app.session/RunEvent/ScenarioReplicationsCompleted

ScenarioReplicationsCompleted

data class ScenarioReplicationsCompleted(val scenarioName: String, val index: Int, val totalScenarios: Int) : RunEvent(source)

Emitted by ScenarioOrchestrator the moment a scenario successfully finishes its replications — i.e. its in-memory simulation has completed cleanly but the per-scenario commit to KSLDatabase has not yet run. Sits between ScenarioReplicationEnded (per-replication) and ScenarioCompleted (post-commit) in the per-scenario event timeline.

Order: events fire in finish order under ConcurrentScenarioRunner.simulate(executionMode = CONCURRENT), matching the order in which scenarios finished their replications; under SEQUENTIAL they match scenario-list order. The event is not emitted for scenarios that failed with a RuntimeException or were cancelled — those paths surface only via the eventual ScenarioCompleted event with snapshot = null.

Multi-scenario GUIs use this signal to flip a scenario's status to COMPLETED at the moment its work actually finishes, rather than waiting for the orchestrator's sequential commit phase to reach that scenario.

Constructors

ScenarioReplicationsCompleted

constructor(scenarioName: String, index: Int, totalScenarios: Int)

Properties

index

val index: Int

1-based position of this scenario in scenario-list order

scenarioName

val scenarioName: String

the scenario name as specified in ScenarioSpec.name

totalScenarios

val totalScenarios: Int

total number of scenarios in the run