Simulation is a technique that mimics a real system - and simplifies it, to learn something useful about it. Discrete event simulation is modeling a real system with discrete events.
DE Simulation
or a library that eases the modeling: rc modeling
, industry modeling
, …Simulation is a technique that mimics a real system - and simplifies it, to learn something useful about it. Discrete event simulation is modeling a real system with discrete events. * Contains a user-specific domain, constraints, a customer-specific state and events modeling and an option to render visually the effects. * Customer simulation can use directly `DE Simulation` or a library that eases the modeling: `rc modeling`, `industry modeling`, …
(build-model model-data)
(build-model model-data registry)
Build the simulation model from model-data
with registry
.
registry
is optional and is defaulted to the registries
fn.
Build the simulation model from `model-data` with `registry`. `registry` is optional and is defaulted to the `registries` fn.
(extract-snapshot {:automaton-simulation-de.simulation-engine/keys [snapshot]
:as _response})
Extract the snapshot
of a response
.
Extract the `snapshot` of a `response`.
(registries)
Returns the built-in
registries of simulation-de.
Returns the `built-in` registries of simulation-de.
(scheduler {:automaton-simulation-de.simulation-engine/keys [initial-snapshot]
:as model})
(scheduler {:automaton-simulation-de.simulation-engine/keys [initial-snapshot]
:as model}
scheduler-middlewares
scheduler-stopping-criterias)
(scheduler model scheduler-middlewares scheduler-stopping-criterias snapshot)
Scheduler is running the simulation described in the model
.
There are three arities for this function.
model
only.stopping-criteria
and supplementary middlewares (i.e. supp-middelwares
).snapshot
to start with (supersedes the initial-snapshot
in the model
).Returns a response
containing:
snapshot
of the last event.stopping-causes
, see [[automaton-simulation-de.impl.stopping-definition.registry]] for possible values.Scheduler is running the simulation described in the `model`. There are three arities for this function. * First one specificies the `model` only. * Second one adds `stopping-criteria` and supplementary middlewares (i.e. `supp-middelwares`). * Third one specify also a different `snapshot` to start with (supersedes the `initial-snapshot` in the `model`). Returns a `response` containing: * simulation `snapshot` of the last event. * `stopping-causes`, see [[automaton-simulation-de.impl.stopping-definition.registry]] for possible values.
(validate-middleware-data middleware-data _registries)
Middleware data are validated.
Middleware data are validated.
(validate-model model)
Model - as built with build-model
- are validated.
Model - as built with `build-model` - are validated.
(validate-model-data model-data)
Validate model-data
.
Validate `model-data`.
(validate-registry registry)
(validate-response response)
(validate-stopping-criteria-data stopping-criteria-data _registries)
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close