Abstract:
A device may receive information identifying a model that, when executed, may cause an operation to be performed. The device may identify a unit associated with the operation. The device may determine that the unit is at least one of: an abstract unit, a unit associated with a dimensionless quantity, a sub-unit, a partial unit, a dynamic unit, or an enumerated unit. The device may determine information that identifies a unit property associated with the unit. The unit property may identify an attribute that is to be used to determine a unit rule associated with the unit. The device may determine a unit rule based on the unit property and information associated with the operation. The unit rule may indicate a manner in which the device is to determine a result associated with the operation. The device may provide the result, associated with the operation, based on the unit rule.
Abstract:
A device, method and tangible computer-readable medium are provided for detecting output discrepancies between representations of a block in two system models. For example, a first representation of a block may represent a default configuration and may execute in a first model. A second representation of the block may represent a user-modified configuration for the block and may execute in a second model. The user may execute the first and second models and may compare results using an exemplary embodiment. The embodiment may allow the user to define criteria and weightings for the criteria and to use the criteria for generating objective functions and constraints. The objective functions and constraints may be used to evaluate the performance of the two models. The embodiment may further perform trace back operations with respect to a model to determine a location in the model that produces an output discrepancy.
Abstract:
Methods and systems for controlling versions of models in modeling environments are disclosed. The versions of models and component interfaces are stored in a repository and checked in and out of the repository. The version designation of a model is changed when the model is checked in the repository. A selected version of the model is checked out of the repository and loaded directly in a memory so that users may load the selected version of the model without error. The loaded model is displayed with information on the version of the model. The version information may include the version number and author of the version. The version information may also include information on whether the model is locked with a version or in a read only mode.
Abstract:
A system and method automatically ensures consistency among a design model and one or more test models that test the design model. The system may include a broker adapted to construct an interface specification. The interface specification identifies the interface of the design model, e.g., its external inputs, external outputs, and initialization states. It may also identify the outputs, inputs, and initialization setting objects of the test models. Proposed changes to the design model's interface may be captured by the broker, and applied to the design model and to the test models atomically. Proposed changes to a given test model that implicate the design model's interface also may be captured, and applied to the given test model, the other test models, and the design model atomically. Default behaviors may be defined for applying the proposed changes to the other test models and the design model.