Package-level declarations
Types
A central composite design represent a two-level factorial design that has been augmented with a center point and axial point to enable the modeling of quadratic response surface models.
Executes a list of Scenario instances concurrently and writes all results to a shared KSLDatabase.
Coroutine-aware runner for one simulation model and one SimulationRun.
Facilitates the simulation of a model via an experimental design.
Lightweight reporting and analysis surface shared by designed experiments.
A design point is a specification of the settings for the factors of an experiment.
Defines how design points in a ParallelDesignedExperiment are positioned in the model's random-number streams.
An experimental design represents a set of factors with design points. This permits the execution of a model using the factors and their levels
Model-intrinsic defaults for the run-parameter surface of an experiment.
Holds data about the run parameters of a simulation experiment.
This class represents an individual factor within a factorial design. The name of the factor must be provided and will be required to be unique when placed within a design. The supplied values of the levels must be strictly increasing. That is, they must be unique and increasing in value.
A factorial design represents a list of design points where every design point represents a possible row in the cartesian product of the levels for the factors. That is, all possible combinations of the levels for the factors are possible design points. A design point is individually generated when needed via the associated iterator for the design.
This class provides the ability to specify a linear model (for use in regression and design of experiments). This is only a string specification of the model. The terms are specified by the names of the factors.
A scenario is a specification of a model to run with a fixed set of inputs and run parameters. Each call to simulate produces a new SimulationRun.
Describes how a Scenario obtains the ksl.simulation.Model used for execution.
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.
Can be used to supply logic to configure a model prior to simulating a scenario.
A SimulationRun represents the execution of a simulation with inputs (controls and parameters), and output (results). A run consists of a number of replications that were executed with the same inputs and parameters, which cause the creation of results for each response within each replication. The main purpose of SimulationRun is to transfer data about the execution of a simulation. It acts as a data transfer class.
The purpose of this class is to facilitate the running of a simulation model based on some inputs and experimental run parameters. The simulate() functions take in the inputs and the experimental run parameters, and after execution return an instance of SimulationRun.
Creates a two level factor with provided low and high values.
Functions
Assigns non-overlapping pre-run sub-stream advances to the selected scenarios.
Turns the list of design points into a data frame. The columns of the data frame are the factor names and the rows are the design points values.