Conditional Execution Control for Block Diagram Simulation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional block diagram environments lack the ability for users to select and specify execution behavior based on conditions, particularly for power cycles, and fail to manage setup and termination methods effectively during simulation.
Innovation Solution
The system allows users to define execution behavior for block diagrams based on user-specified conditions related to model variables, enabling controlled execution of setup and termination methods, including the option to exempt data from reset and maintain nonvolatile states during power cycles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional block diagram environments automatically execute setup methods during initialization, then the system ensures all blocks are properly initialized, but the system lacks the ability to execute setup methods conditionally based on user-specified conditions or events
Solution Approach 1:
The patent applies preliminary action by allowing users to pre-configure execution behavior specifications and condition definitions during model creation. The system stores these specifications and automatically evaluates them during simulation, executing setup methods only when conditions are met, thus providing conditional execution without adding complex runtime control mechanisms.
Solution Approach 2:
The patent implements dynamics by making the execution behavior configurable and changeable during simulation. Users can specify multiple execution behaviors with different conditions, and the system dynamically selects which behavior to execute based on current model variable states, enabling flexible conditional execution adaptability.
2Adaptability or versatility
If the system executes termination methods automatically when power is removed, then the system ensures proper cleanup, but the system cannot exempt specific data from reset or maintain non-volatile states
Solution Approach 1:
The patent applies segmentation by dividing the state management into hierarchical levels (model level, subsystem level, block level) and allowing independent control of termination behavior at each level. Users can specify which blocks should have their termination methods executed and which data should be preserved, enabling selective data persistence without requiring complex global state management.
Solution Approach 2:
The patent implements local quality by allowing different termination behaviors for different blocks within the same model. Each block can have its own execution behavior specification, enabling users to define local data persistence requirements independently, such as preserving state in specific memory blocks while resetting others.
3Productivity
If setup and termination methods are executed only once during initialization and shutdown, then the system maintains simplicity, but the system cannot handle multiple power cycles or repeated execution scenarios
Solution Approach 1:
The patent applies feedback by implementing a mechanism that tracks the execution status of setup and termination methods. The system monitors model variable conditions continuously and automatically triggers method execution when conditions change, providing feedback-driven repeated execution without requiring manual intervention or complex external control logic.
Solution Approach 2:
The patent implements self-service by enabling the simulation system to automatically manage the execution of setup and termination methods based on user-defined conditions. The system self-monitors model variables, self-evaluates condition satisfaction, and self-executes appropriate methods, eliminating the need for external control mechanisms while supporting multiple execution cycles.
Data Source
AI summary
A mechanism in a block diagram environment allows the modeling of an execution behavior of a block in a block diagram, where a user selects the execution behavior from a plurality of functions related to the block diagram and where the execution behavior of the block is performed when at least one model variable associated with the block satisfies a user-specified condition is disclosed. States and other internal data in the designated block are initialized upon the satisfaction of the user-specified condition. The illustrative embodiment of the present invention also allows the internal data to be reset upon the ending of the event, such as the modeled introduction or withdrawal of power. The execution behavior may be suspended and resumed multiple times during the simulation in response to multiple occurrences of the specified event. The present invention also allows for selected data to be exempt from the reset process so that the selected data is nonvolatile.