<model>
Defines the model attached to the analysis.
Input
- id
- Unique model ID
Parent
<analysis>
Example
<model id="model">
<create>
<add resource="fem" />
</create>
<commit>
<call name="Globalize" nodes="fem::nodes"
systems="fem::systems"
coords="fem::subcase[0]::coordinates" />
</commit>
</model>
Comments
- model is optional, and is only necessary to resolve duplicate content, or to trigger a command when the model is created.
- Since resources are typeless (they can contain model content, result content, or both, and are not classified as a model or result), and multiple resources can be attached to an analysis. The model command enables specific resources to define the model to avoid passing duplicate entities. For example, a fem/op2 pair typically contains duplicate model content. Adding only the fem resource to the model avoids entity duplication.
- Only one model command can occur in the XML command file.
- The model must contain create and/or commit events.
- The create event occurs once before the model is processed, and defines what resources will be attached to the model.
- The commit event occurs once after all entities have been added to the model, and is typically used to transform coordinates and systems.