Compare Two Alternatives of a Model
In this task you compare the two first alternatives of a model according to the description above.
Note:
Two alternatives of the model are created and simulated, and the
simulations are compared in the task. The model alternatives are not saved in
this task, however.
Before you begin: Create an editable copy of the model example
Coupled Clutches according to
Creating an Editable Copy of a Model Example in a New Library.
-
Simulate the model.
For more information, see Simulating a Behavior.
-
From the
Variable Browser, right-click any node or
signal and select
Add to Results Manager
.
The Results Manager appears, containing the content of the Variable Browser for the currently simulated model.
-
Perform the following changes in the model:
-
In the diagram, right-click the component
J4 and select
Delete.
The component is deleted.
-
Change the parameter
J in the component
J1 from
1 to
2 the following way:
- In the diagram, right-click the component J1 and select Edit Component Parameters.
- Change the value of the parameter J from 1 to 2.
-
In the diagram, right-click the component
J4 and select
Delete.
- Simulate the model.
-
From the current
Variable Browser, right-click any node or
signal and select
Add to Results Manager
.
The following is the result:
- The content of the current
Variable Browser is added to the
Results Manager in the following way,
looking at the columns of the
Results Manager.
- The column Variable Name contains the variables that are present in any of the Variable Browsers added.
- After the column Variable Name, one column of values is added for each of the two Variable Browsers added, with the name of the Variable Browser added.
- The Unit column and the Description contain the units and the description of the variables in the Variable Name column.
- The simulations of the two alternatives of the model are
compared, and the result is displayed in the following way:
- Changed variable values give the following indications:
- A variable value that has been changed (for example, by the user) between the simulations is marked by an solid orange line in front of the value, in all models.
- For the parent nodes of this variable, the corresponding value cells are indicated by solid orange lines, to make it easy to identify deeply buried value differences from any level of the variable tree.
- Variables that are impacted by the changed variable (that is, they get different values in the simulations since they depend on the variable that has been changed) are also indicated by dashed orange lines.
- For the parent nodes of impacted variables, the
corresponding value cells are also indicated by dashed orange lines.
Note: If the parent node also contains any values that has been changed (for example, by the user), this takes precedence, and the marking is a solid orange line.
In this scenario, for example, this results in:
- The value field of J1.J (the value you changed) is marked a solid orange line in all models.
- The parent field of J1 is marked with a dashed orange line in all models.
- The variables J1.der(w) and J1.a are impacted by the change of J1.J, so the corresponding value filed are marked with a dashed orange lines in all models.
- Some variables in the components clutch1, J3, clutch3, and J4 are also impacted by the change of J1.J, the value fields of these variables, and the corresponding parents, are also marked with dashed orange lines, in all models.
- If a component exists in a simulated model but does not
exist in other simulated models, then the corresponding node and underlying
components and variables in the columns for the simulations are colored green
where the component exists, red where the component does not exist. All
corresponding cells in the
Variable Name column are colored
yellow to indicate a structure change - see last item in this list.
In this scenario, the component J4 and underlying variables are marked green for the first simulation, red for the second one. The corresponding cells in the Variable Name column are yellow.
- If a variable exists in a simulated model but does not
exist in other simulated models, then the corresponding cell in the columns for
simulations are colored green where the variable exists, red where the variable
does not exist. The cells of the node containing this variable are colored
yellow to indicate a structure change - see last item in this list. All
corresponding cells in the
Variable Name column are colored
yellow to indicate a structure change - see last item in this list.
For an example in this scenario, see next task.
- If the structure of a component is changed in any way,
the corresponding cells in the
Variable Name column are colored
yellow.
In this scenario, the cells of the node J4 are marked yellow in the Variable Name column.
- Changed variable values give the following indications:
- The content of the current
Variable Browser is added to the
Results Manager in the following way,
looking at the columns of the
Results Manager.