Abstract: A system and method graphically display ports in a discrete event system (DES) environment. A graphical representation of a model having at least one DES component is provided in the DES environment. A first port of the DES component and a second port of the DES component are indicated by symbols. The first port is indicated by a first symbol representing a port type of the DES environment and the second port is indicated by a second symbol representing a port type of a non-DES environment.

Abstract: A Discrete Event System model created or provided in a time domain modeling and simulation environment and/or an event domain modeling and simulation environment may be divided into multiple independent regions, e.g. “subgraphs”, to achieve interleaved execution of the components from different domains. The subgraphs are automatically identified by the modeling and simulation environment during the compilation. Each subgraph consists of one or more interconnected event-driven components. Each subgraph is associated with an event calendar that controls the execution of the associated subgraph. Such multiple event calendar design enables multi-domain simulation, where event-driven components modeled by an event domain modeling environment and time-driven components modeled by a time domain modeling environment are simulated in an integrated fashion.

Abstract: A time-driven block provided in a block diagram model may be executed in an event domain without user modification. The time-driven block is connected to one or more event-driven blocks using event domain signals. The time-driven block automatically adapts to the execution rules of the event domain modeling and simulation environment. The blocks that are configured to execute in more than one modeling and simulation environments are called polymorphic blocks. The polymorphic blocks are identified during the compilation stage of the block diagram model taking into consideration the port and line styles of the blocks. The execution rules of the polymorphic blocks are also determined during the compilation stage of the block diagram model.

Abstract: A time-driven block provided in a block diagram model may be executed in an event domain without user modification. The time-driven block is connected to one or more event-driven blocks using event domain signals. The time-driven block automatically adapts to the execution rules of the event domain modeling and simulation environment. The blocks that are configured to execute in more than one modeling and simulation environments are called polymorphic blocks. The polymorphic blocks are indentified during the compilation stage of the block diagram model taking into consideration the port and line styles of the blocks. The execution rules of the polymorphic blocks are also determined during the compilation stage of the block diagram model.

Abstract: A system and method graphically display ports in a discrete event system (DES) environment. A graphical representation of a model having at least one DES component is provided in the DES environment. A first port of the DES component and a second port of the DES component are indicated by symbols. The first port is indicated by a first symbol representing a port type of the DES environment and the second port is indicated by a second symbol representing a port type of a non-DES environment.

Abstract: A Discrete Event System model created or provided in a time domain modeling and simulation environment and/or an event domain modeling and simulation environment may be divided into multiple independent regions, e.g. “subgraphs”, to achieve interleaved execution of the components from different domains. The subgraphs are automatically identified by the modeling and simulation environment during the compilation. Each subgraph consists of one or more interconnected event-driven components. Each subgraph is associated with an event calendar that controls the execution of the associated subgraph. Such multiple event calendar design enables multi-domain simulation, where event-driven components modeled by an event domain modeling environment and time-driven components modeled by a time domain modeling environment are simulated in an integrated fashion.

Abstract: A mechanism to dynamically vary the amount of delay for an event-generated function call is discussed. The event causing the generation of the function call may be a signal-based event, function call event or some other type of event. A function call generating delay component is inserted into a DES model and dynamically adjusts the amount of delay to apply prior to generating and transmitting the function call to an intended target component. The function call generating component reads a value from an input port in determining the amount of delay. The identified value at the input port may be a signal value or an attribute associated with an event entity received at the port.

Abstract: A mechanism to dynamically vary the amount of delay for an event-generated function call is discussed. The event causing the generation of the function call may be a signal-based event, function call event or some other type of event. A function call generating delay component is inserted into a DES model and dynamically adjusts the amount of delay to apply prior to generating and transmitting the function call to an intended target component. The function call generating component reads a value from an input port in determining the amount of delay. The identified value at the input port may be a signal value or an attribute associated with an event entity received at the port.

Abstract: In one embodiment, a model of a system includes one or more event-driven blocks and one or more time-driven blocks. The model is executed in part by receiving an entity from a event-driven block, and in response to receiving the entity, generating a time-varying data signal descriptive of the entity. The data signal is passed to one or more time-driven blocks, which generate one or more results at least in part from the data signal, and display at least some of the one or more results.

Abstract: A mechanism to dynamically vary the amount of delay for an event-generated function call is discussed. The event causing the generation of the function call may be a signal-based event, function call event or some other type of event. A function call generating delay component is inserted into a DES model and dynamically adjusts the amount of delay to apply prior to generating and transmitting the function call to an intended target component. The function call generating component reads a value from an input port in determining the amount of delay. The identified value at the input port may be a signal value or an attribute associated with an event entity received at the port.

Abstract: A mechanism for processing events in a modeling environment is discussed. Embodiments of the invention identify multiple entities in a model, at least one of which includes an associated event. A combination entity is created from the identified entities with the combination entity including at least one event derived from the associated events. The combination entity is processed based upon the occurrence of at least one derived event.

Abstract: The present invention provides systems and methods for transfer of information between various modeling environments in a model of a system. In one embodiment, a system and method for transferring data between a discrete event model environment and an external model environment other than a discrete event environment is provided.

Abstract: A discrete event system (DES) modeling environment models the occurrence of events independent of continuous model time. In a DES modeling environment, state transitions depend not on time, but rather asynchronous discrete incidents known as events. A user may customize selected parameters of a block or other component able to support at least one entity passing therethrough holding a value of arbitrary data type in a DES modeling environment. For example, a user can enable and disable ports a discrete event execution block in a discrete event execution model using a graphical user interface, such as a dialog box. Based on user-selected dialog inputs, a discrete event execution program can automatically update a specification for a block, for example, by adding ports to the graphical representation of the block.

Abstract: A discrete event system (DES) modeling environment models the occurrence of events independent of continuous model time. In a DES modeling environment, state transitions depend not on time, but rather asynchronous discrete incidents known as events. A discrete event modeling environment can be used to model a control system using one or more discrete event-driven components. The event-driven components can be used to model certain portions of a control system that cannot be accurately modeled using a time-based model.

Abstract: A discrete event system (DES) modeling environment models the occurrence of events independent of continuous model time. In a DES modeling environment, state transitions depend not directly on time, but rather aperiodic discrete incidents known as events. A discrete event modeling environment can be used to model a control system using one or more discrete event-driven components. The event-driven components can be used to model certain portions of a control system that cannot be accurately modeled using a time-based model.

Abstract: A system and method models regional timeout functionality in a discrete event execution environment. A timeout function is initiated associated with an entity upon occurrence of a start condition and terminated or reset upon reaching an end condition. The timeout function is configured to expire after a selected amount of time. Upon expiration of the timeout function, the entity is redirected to a predetermined location for timeout processing.