1 / 14

Event-Driven Models

Event-Driven Models. Continuous-time vs Discrete-event Models. GoldSim was originally built as a continuous-time simulator: “Rates of change”, predefined time steps... Gradually more and more discrete-event modeling capabilities have been added: Timed Event Generator Discrete Changes

dgreen
Télécharger la présentation

Event-Driven Models

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Event-Driven Models

  2. Continuous-time vs Discrete-event Models • GoldSim was originally built as a continuous-time simulator: “Rates of change”, predefined time steps... • Gradually more and more discrete-event modeling capabilities have been added: • Timed Event Generator • Discrete Changes • Reservoir overflows • Reliability Failures & Repairs • Etc. etc. • These changes have led to a much more complex model-updating logic.

  3. Events and Discrete Changes • An “Event” is a special type of output that is sent out at discrete times during a simulation. It carries no information other than its occurrence. • A “Discrete Change” is like an Event, but it also carries a value and an instruction: “Add” or “Replace”. • Events can only connect to a “Trigger” in another element. • It’s not their primary purpose, but Discrete Changes can also be used in Triggers.

  4. Elements that can Interrupt the Clock • The following element types can insert scheduled events that interrupt the model clock: • Timed Event Generator • Reservoir overflow, underflow • Reliability failure time, repair time • Time Series element (discrete changes) • Event Delay • Discrete Change Delay • Fund (interest charges) • Option (on maturity)

  5. The Timed Event Generator • Comes in five flavors • Has Cum_Emitted output

  6. Interrupting the Clock • The user can disable clock interruption if desired:

  7. The Trigger Dialog • Comes with five flavors of trigger input. • Optionally, after the triggering event, the trigger will wait until a specified condition is true. • Optionally, it will then “fire” only if another condition is true.

  8. Event-processing Elements • Emit only: • Timed Event Generator • Reservoir overflow, underflow • Receive only: • Conditional Container • Stochastic • Emit & Receive: • Event Delay • Triggered Event Generator • Decision • Random Choice • Milestone • Status • Discrete Change • Reliability • Splitter, Allocator • Option

  9. GoldSim’s Updating Process • When a model is being edited, GoldSim maintains a ‘causality sequence’ that is used at run time. • Links between elements are not made unless a valid causality sequence can be established. • Separate, private causality sequences exist for Submodels and for Containers with the ‘Treat as Subsystem’ option selected.

  10. Discrete-Change-processing Elements • Discrete Change Generator • Time Series element (discrete changes) • Reservoir • Discrete Change Delay • Splitter, Allocator • Fund (interest charges) • Option (on maturity) • Insurance

  11. GoldSim’s Updating Process (simplified) • Update static elements in sequence. Supported element types: • Data • Expression • Stochastic • Selector • Table • Update all initial values (inputs must be static). • For each time step: • Set the clock to the new time. • Process any ‘dynamic’ elements that can change with time. • Update all function elements in sequence.

  12. F10: the Causality Sequence

  13. Dynamic Elements • These elements have outputs that represent ‘State variables’ for the model. • Those outputs are available by any element at any time. • This allows such element to reference their own current values, directly or indirectly. • Some of those outputs can be hybrids (“Front/Back”), which can change with time and also during the function update. • Elements that reference front/back outputs TRY to sequence after the output, but they don’t have to.

  14. Phew!

More Related