In MotionView, an analysis is a container entity that can contain collection of the loads, motions, and entities that describe the event to be simulated for a model. A model can contain any number of analyses but only one analysis can be active at a given instance. When a model is run in MotionView, a particular analysis is selected and MotionView includes the loads and motions described in the analysis when it submits the model to the solver.
An analysis is represented by the 
icon and has following characteristics:
| • | An analysis can be added only to the root system Model. |
| • | It can contain any other modeling entities like points, bodies, joints, forces etc. |
| • | An analysis can have a system as its child entity. |
| • | Only one analysis can be active at a given instance. The MDL statement that sets an analysis active is *SetActiveAnalysis. The Run panel and Export Solver Deck pre-selects the active analysis. |
| • | The analysis take attachments in similar way as system and assembly. |
| Note | When an inactive analysis is set active, the current active analysis is deactivated automatically. The inactive analysis instance would be listed in the model browser tree, but its child entities would not be shown and are not accessible until the analysis is made active. |
Similar to an assembly, which is an extended version of systems, the analysis container entity is also extended to have an distributed file approach. However, the extension is contained within the same entity called “Analysis”. Starting in version 11.0.120, the Analysis container comes in two variations:
Inline Analysis
This refers to the existing style of using the Analysis feature, where the analysis definition and properties are saved inline within the Model mdl file.
| • | In MDL, an inline analysis is created by instantiating a definition using the *Analysis() statement that refers to a *DefineAnalysis block. |
Distributed Analysis
This refers to the distributed files based analysis, similar to assembly entity. This type of analysis works on a similar concept as assemblies with some rules and exceptions:
| • | Distributed analysis refers to a data file and data file subsequently refers to a definition file, which is similar to assembly entity. |
| • | An assembly can be added to a distributed analysis, but not to an inlined analysis. |
| • | Unlike assemblies, a placeholder for distributed analysis is not available. |
| • | Distributed analysis has ALLOWED_MODEL_TYPE attribute that can be used to restrict the application of analysis for a particular type of Model. |
Refer to Analysis Panel to learn more about adding an analysis.
Example
The following simple example model demonstrates the concept of Analysis. This model is available at ~hw_install/demos/mv_hv_hg/modeling/container_entities/system_analysis/door.mdl. The model has been arranged into a system called Hatchback System, which in turn has two child systems: the Door System and the Damper System. The images below shows a simplified model of a hatchback door of a car with the model mdl file shown alongside.
One analysis is a Kinematic Analysis to be performed on the above model which is accomplished by adding a motion to the hinge joint in the Door System.
Another analysis is a Dynamic Analysis that is accomplished by applying a force at the end of the door. These two events are exclusive, for example the motion at the hinge joint is not applied when the force is applied and vice-versa.
To explain both types of analysis, one of them is modeled as inlined analysis and other one is modeled as distributed analysis.
Referring to the MDL file:
| • | The entire model information is contained within a *BeginMDL - *EndMDL block in the door.mdl (model file). |
| • | Apart from the two system instances and their definition block, the model contains *Analysis statement that instantiates the Kinematic Analysis (ana_kin). This analysis instance refers to the analysis definition (def_ana_kin) within the *DefineAnalysis block in the model file. |
| - | The door hinge joint from the Door System is passed as an attachment to the analysis. A motion entity is defined that uses this attachment. |
| - | The data related to the motion is within *BeginContext (ana_kin) block. |
| • | The model file also contains *BeginAnalysis block that instantiates the Dynamic Analysis. |
| - | This block refers to the data file (dyn_data.mdl) which in turn refers to the definition file (dyn_def.mdl). |
| - | The door body and the center end point at the door are passed as attachment to this analysis. A force entity is defined that uses these attachments. |
| - | The force data is contained in the data file. |
| - | The MDL structure is similar to that of the assembly. The data is contained within *BeginAnalysisDataFile. The analysis definition block *DefineAnalysis in the definition file is contained within *BeginAnalysisDefinitionFile. |
| • | The *SetActiveAnalysis statement controls which analysis is active. |
See Also:
*BeginAnalysis ()
*Analysis()
