MAGNET Modeler uses rules which define how certain objects and entities within the current MAGNET Office file are going to be transformed into a virtual model.
MAGNET Modeler provides a comprehensive list of different rule types for different types of requirements. Each rule has its specialties.
See the list for a quick comparison:
|Surface Models||Surfaces with textures|
|Material Areas||Textured, closed areas|
|Buildings||Textured building models|
|Road Lines||Roads and road markings|
|Fences||Fences and wall-like objects|
|Ditches||V-shaped ditches in surface|
|Pipes||Textured pipe models|
|Single Elements||Trees, lamps, humans, etc.|
|Element Chains||Trees, lamps, solar panels, etc.|
|Element Areas||Areas with Single Elements|
|Materials||Materials used in rules|
Rules should always be specified in a correct manner.
1. Layer selection:
MAGNET Modeler is layer based. Every rule has to have at least one layer assigned. You can choose multiple layers as well. Depending on the rule type, MAGNET Modeler will read every compatible object on the layer(s) and use it within the rule. You cannot exclude objects on a certain layer from being used in the rule.
2. Material definition:
MAGNET Modeler comes with an extensive default material library from which you can choose one or even multiple materials. In case you selected more than one material, the materials will be distributed randomly. You can also create custom materials on the fly.
3. Group definition:
MAGNET Modeler uses a group hierarchy in the background. Every single rule can be assigned to a certain group or subgroup. This does not play a huge role within MAGNET Office itself, but it gets even more important in MAGNET Explorer. A clear group structure is the only way for you to differentiate between objects, turn them on or off, or further use them downstream for simulation purposes.
Depending on the rule type, certain attributes/advanced attributes are provided to control how the compatible entity is going to be translated into a virtual model. As of now, these attributes are assigned to every entity on the layer used in that rule. In other words, this means you cannot exclude or adjust attributes for a certain subset of entities on that layer. In case you want different attributes for similar objects, you must create a second layer, move the subset over, and create a second rule.
Example of a Surface rule setting: