ModelPart and SubModelPart

In the previous part of the tutorial, we already saw how the ModelPart is the object containing Element, Conditions, Nodes and Properties.

A fundamental feature is that it can also hierarchically contain "SubModelParts" intended as other ModelParts which belong to the same parent. This relation can be repeated recursively, so that each "root" ModelPart can actually own a tree of SubModelParts.

Data Ownership

The parent-son relation is such that anything that belongs to a given SubModelPart also belongs to the parent ModelPart. This implies that the ultimate "owner" of any Node, Element, etc, will be the "root" ModelPart. The consistency of the tree is ensured by the ModelPart API, which provides the tools needed for creating or removing anything any of the contained objects.