Abstract:
A device may receive a model including a group of blocks, and may receive a command to execute the model. The device may assign a parameter sample time to a subset of blocks of the group of blocks. The parameter sample time may permit a block, of the subset of blocks, to be executed based on a parameter change event detected during the execution of the model. The device may cause the model to be executed after assigning the parameter sample time to the subset of blocks. The device may detect a parameter change event, associated with the model, prior to the execution of the model being completed. The parameter change event may include an event that is external to the execution of the model. The device may cause at least one block, of the subset of blocks, to be executed based on the detecting the parameter change event.
Abstract:
Systems and methods decouple model components from a model execution style for which the model components are created, and the model components may be utilized in parent models having different execution styles. A model component may be partitioned into executable entities, and the entry points of the executable entities and their call styles may be identified. An adaptation layer that includes access points for the entry points may be constructed. The model component, including the adaptation layer, may be included in the model, and connection elements of the parent model may be connected to the access points of the adaptation layer. The execution call styles associated with the connection elements of the parent model may be bound to the execution call styles of the entry points as originally designed. The adaptation layer may manage translation of call styles and may coordinate scheduling of data communication with the model component.
Abstract:
A system for providing model level protection for resources holding data accessed by multiple tasks in a model is discussed. The protection occurs at the model level so that the protection mechanism does not interfere with model dynamics. Resources concurrently accessed by multiple tasks are identified so that a unified protection mechanism can be applied to the resource. A user interface may be provided which enables the selection of a particular type of protection mechanism for the data in the resource. User supplied protection mechanisms may also be implemented.
Abstract:
Systems and methods may aggregate and organize implicit and explicit initialization, reset, and termination operations defined throughout the hierarchy of an executable. The systems and methods may analyze the model and identify implicit and explicit initialization, reset, and termination operations defined at various hierarchical levels. The systems and methods may aggregate the implicit and explicit initialization, reset, and termination operations into an initialize callable unit, a reset callable unit, and a termination callable unit. The systems and methods may apply optimizations to the callable units, and resolve conflicts. The systems and methods may define a single entry point for each of the initialize, reset, and termination callable units.
Abstract:
A device may receive a model including a group of blocks, and may receive a command to execute the model. The device may assign a parameter sample time to a subset of blocks of the group of blocks. The parameter sample time may permit a block, of the subset of blocks, to be executed based on a parameter change event detected during the execution of the model. The device may cause the model to be executed after assigning the parameter sample time to the subset of blocks. The device may detect a parameter change event, associated with the model, prior to the execution of the model being completed. The parameter change event may include an event that is external to the execution of the model. The device may cause at least one block, of the subset of blocks, to be executed based on the detecting the parameter change event.
Abstract:
Systems and methods may generate code, for a model, with one or more service access points generated and at locations in the code based on an analysis of model constraints and deployment specifications (e.g., RTE specifications or OS specifications). The systems and methods may analyze the model and identify a functionality that needs an RTE service. The system and methods may receive deployment specifications. The systems and methods may generate code for the model, where an analysis of model constraints and the deployment specifications determine which service access points are generated and where in the code the service access points are located. In an embodiment, the code may be executed by different RTEs. In an embodiment, the systems and methods may determine, based on the analysis of the model constraints and the deployment specification, one or more admissible implementations for an RTE service that may be implemented in different ways.
Abstract:
Systems and methods may generate code, for a model, with one or more service access points generated and at locations in the code based on an analysis of model constraints and deployment specifications (e.g., RTE specifications or OS specifications). The systems and methods may analyze the model and identify a functionality that needs an RTE service. The system and methods may receive deployment specifications. The systems and methods may generate code for the model, where an analysis of model constraints and the deployment specifications determine which service access points are generated and where in the code the service access points are located. In an embodiment, the code may be executed by different RTEs. In an embodiment, the systems and methods may determine, based on the analysis of the model constraints and the deployment specification, one or more admissible implementations for an RTE service that may be implemented in different ways.
Abstract:
Systems and methods decouple model components from a model execution style for which the model components are created, and the model components may be utilized in parent models having different execution styles. A model component may be partitioned into executable entities, and the entry points of the executable entities and their call styles may be identified. An adaptation layer that includes access points for the entry points may be constructed. The model component, including the adaptation layer, may be included in the model, and connection elements of the parent model may be connected to the access points of the adaptation layer. The execution call styles associated with the connection elements of the parent model may be bound to the execution call styles of the entry points as originally designed. The adaptation layer may manage translation of call styles and may coordinate scheduling of data communication with the model component.
Abstract:
Systems and methods may aggregate and organize implicit and explicit initialization, reset, and termination operations defined throughout the hierarchy of an executable. The systems and methods may analyze the model and identify implicit and explicit initialization, reset, and termination operations defined at various hierarchical levels. The systems and methods may aggregate the implicit and explicit initialization, reset, and termination operations into an initialize callable unit, a reset callable unit, and a termination callable unit. The systems and methods may apply optimizations to the callable units, and resolve conflicts. The systems and methods may define a single entry point for each of the initialize, reset, and termination callable units.
Abstract:
Systems and methods may aggregate and organize implicit and explicit initialization, reset, and termination operations defined throughout the hierarchy of an executable. The systems and methods may analyze the model and identify implicit and explicit initialization, reset, and termination operations defined at various hierarchical levels. The systems and methods may aggregate the implicit and explicit initialization, reset, and termination operations into an initialize callable unit, a reset callable unit, and a termination callable unit. The systems and methods may apply optimizations to the callable units, and resolve conflicts. The systems and methods may define a single entry point for each of the initialize, reset, and termination callable units.