Scenario Runner
Facilitates the running of many scenarios in a sequence. A KSLDatabase is used to capture the statistics for each scenario. Each scenario is treated like a different experiment. The scenarios can be based on the same or different models. The scenarios also capture the inputs and results via a SimulationRun.
Parameters
of the scenario runner. By default, this name is used as the name of the database
a list of scenarios to execute
the KSLDatabase that will hold the results from the scenarios
Constructors
Properties
Functions
Creates a Scenario from a full ExperimentRunParameters snapshot and adds it to this runner. Use this overload when you need to configure run parameters beyond the three scalar values (e.g. antithetic option, stream-reset behaviour, stream advances).
Creates a Scenario from a ModelBuilderIfc and a full ExperimentRunParameters snapshot and adds it to this runner.
Creates a Scenario from the three most common run-parameter scalars and adds it to this runner. All other run parameters are captured from model's current state. String and JSON control overrides may be supplied via stringInputs and jsonInputs.
Gets the database observer by the scenario name or null if not there.
Sets a common number of replications for every scenario managed by this runner. Updates Scenario.scenarioRunParameters directly so that the model is not mutated and scenarios that share a model remain independent.
Returns a map of scenario name → per-replication observations for responseName across all executed scenarios.
Gets the scenario by its name or null if not there.
Interprets the integer progression as the indices of the contained scenarios that should be simulated. If the progression is not a valid index then no scenario is simulated.
Builds a ReportNode.Document containing a full scenario runner report via scenarioRunner.
Assigns non-overlapping pre-run sub-stream advances to selected scenarios.
Writes basic half-width summary reports to the provided PrintWriter