Structural models
The Structural models branch contains saved depth- and time-domain models, grouped by user and domain.
A model's Data Manager properties show its source under Conceptual model: the source model's current name, None (project horizons) when project horizons were chosen, or Not recorded for an older model without a recorded source. A deleted source is marked (deleted). To choose a different source, open the model in the Structural Modeling wizard.
Right-click the branch, a user folder, or a Depth/Time folder and choose Create new to open the Structural Modeling wizard. Starting from a domain folder presets that domain.
Use Slicer in the 3D view header to show the shared slicing plane. First activation fits it to all available supported objects without opening a wizard; later activations retain your adjustments. Its dropdown offers Edit slicer parameters... and Fit slicer to objects. See the shared toolbar procedure in Geological modeling.
The example below shows Demo Structure built from Demo Framework, with three surfaces under TIN Maps and two volumes under Zones. Select the model to see its Conceptual model property, and select its result check boxes to display the geometry in the matching depth 3D view.

A built model organizes its results into these subfolders:
- TIN Maps — modeled horizon surfaces
- Faults — fault surfaces used by the model
- Intrusions — modeled intrusion surfaces
- Zones — volumes generated between horizon pairs when Generate zones from horizon pairs is enabled
- Fault Blocks — separate blocks generated from a selected fault model
TIN Maps, Intrusions and Zones are always present under a built model and stay visible even when they contain nothing, so an empty Zones folder means that layer generation produced no volumes, not that the model itself is incomplete. Faults and Fault Blocks appear only when the model actually produced fault surfaces or fault blocks, so a model built without a fault model shows neither folder.
To give every object in a folder a different automatically generated color at once, right-click the model's TIN Maps, Faults, Intrusions or Zones folder and choose Colorize. The new colors are applied immediately, without a dialog, and repaint the Data Manager and views that use solid object colors. A TIN map with Color by palette enabled in the 3D view keeps its Z-based colors. On the Faults folder the command usually appears to change nothing, because each fault keeps the color it takes from the fault model rather than the one stored with the structural model. An individual fault under a model offers Extract fault data, Export fault throw... and Color by throw, but no Set color. To change its solid color, use the fault model or the interpreted fault of the same name; see Fault model. Colorize is not offered on the Fault Blocks folder; fault blocks are given distinct colors automatically when the model is built, and Set color on an individual fault block changes one of them.
A result zone linked to the Conceptual Model uses that conceptual zone's name, including merged-zone names; an unlinked interval uses its top/bottom horizon pair. Fault-divided pieces add [Block 1], [Block 2] and so on. If two pairs would share a zone name, the horizon pair disambiguates it. The zone tooltip identifies the conceptual zone, when linked, and its top and base horizons. Under TIN Maps, horizon entries show (Reference), (Dependent) or (Markers only) according to how they were built.
Right-click an individual zone and choose Save isochore to save the effective built thickness as a thickness map: base minus top, with negative thickness set to zero. Choosing a fault-block piece saves the whole zone's thickness. Both bounding horizons need modeled grids; a horizon kept directly as a Hard Multi-Z mesh has no grid for this command. Older results without stored horizon links must be run again before saving an isochore.
The blocks are numbered as they are built, so the folder lists Fault block 1, Fault block 2 and so on.
Right-click a single fault block for its own commands:
- Set color — replaces the color the block was given automatically when the model was built.
- Rename — opens the Rename fault block dialog. The name it offers starts with the model name, which the Data Manager does not repeat in the tree, and a name already used by another block of the same model is refused with a message.
- Delete — removes that block.
- Isolate — shows the block on its own by clearing the check boxes of the other blocks in the folder.
On the Fault Blocks folder itself, Delete removes every block of the model at once.
For an individual block, Delete asks you to confirm deletion of the named fault block; decline to keep it. Delete on the Fault Blocks folder removes every block without confirmation. Neither command changes the model definition, so running the model again with Generate fault blocks enabled rebuilds the full set.
To turn modeled fault surfaces into points, right-click the model's Faults folder and choose Extract fault data to include every fault in it, or right-click a single fault under that folder to include only that fault. The command opens the Extract fault data dialog with an Output name already filled in from the model name for the folder and from the fault name for a single fault; Points is the only Output data type, so the extraction always produces a point set under Points in the Data Manager. See Fault model for the dialog options and for the same command on a fault model.
Fault-throw QC
After building a model, select a fault under its Faults folder and inspect Object Properties. Fault throw lists Min / Max / Mean for each modeled horizon with throw samples. These values are measured along the horizon–fault cut-off from the final modeled geometry, including any Manual throw adjustments, rather than copied from the input settings. They use the project depth unit (m or ft) in Depth and the project time unit (ms or s) in Time.
Throw is the hanging-wall Z minus the footwall Z: positive means hanging wall down (normal), and negative means hanging wall up (reverse). A vertical fault has no hanging wall, so its values are unsigned vertical offsets between the two sides and its fault type is not checked. A horizon kept continuous across the fault is reported with zero throw and identified as not offset. An inconsistency warning marks throw sense that disagrees with the assigned fault type; this QC changes neither the fault type nor the model geometry.
Right-click an individual fault and choose Export fault throw... to export that fault, or use the same command on the model's Faults folder to export all faults with available samples. Choose an output file in Export fault throw. The comma-separated output contains fault, geological type and horizon names, sample coordinates on both sides, throw values, and a per-horizon summary with sample counts, minimum, maximum, mean and type consistency. Headers state the domain and coordinate/throw units. For vertical faults, the down-thrown side occupies the hanging-wall columns; consistency is not applicable for vertical faults or continuous horizons.
When a fault has no throw samples, its properties report that it does not cut any modeled horizon. If none of the selected faults has samples, export reports "No fault throw to export: the selected faults do not cut any modeled horizon." No throw is available without modeled fault and horizon geometry; generated Top and Bottom boundary planes are excluded.
Fault throw on the Location map
In the Location map, make a horizon used by the structural model current and ensure its Depth or Time domain matches the model. Select the model and fault check boxes in the Data Manager. Open Visual Settings, choose Object(s), and switch on Structural model fault throw on current horizon. Spaced labels along the faults show the same QC throw values and project units as Object Properties. They require available throw samples for that matching model horizon; uncertainty realizations do not add duplicate labels.
The label item is independent of Structural model faults on current horizon: switching labels off leaves fault traces unchanged. Clearing a fault's Data Manager check box hides both its trace and its throw labels. Labels display the QC result without changing geometry or fault type.
Fault coloring by throw in 3D
Right-click a fault under the model's Faults folder and toggle Color by throw to color its surface by calculated throw in the matching-domain 3D view. This helps inspect variation over the fault surface; it is separate from Location map labels and horizon Z-based palette coloring. Toggle it off to return to solid fault coloring. The solid-color instructions above still apply.
Save zones as geobodies
To reuse layer volumes as ordinary geobodies, right-click the model's Zones folder and choose Save as geobodies to copy every layer in that folder into the Geo-bodies branch, or right-click a single layer and choose Save as geobody to copy just that one. Each copy takes the layer's geometry, color, age and class, and the structural model keeps its own layers, so the copy is an independent object — clearing the layer's check box does not hide the geobody, and clearing the geobody's check box does not hide the layer. From then on the copy behaves like any other geobody: it has its own check box in the Data Manager, an entry in the 3D view and in the Visual Settings panel, and the standard geobody actions.

A copy is named after the layer as the Data Manager shows it. In that name a slash, a backslash, an opening square bracket, a space or a tab becomes an underscore and a closing square bracket is dropped, repeated underscores are collapsed, and a leading or trailing underscore is removed, so a layer shown as Object_1/Object_2 [Block 1] gives a geobody named Object_1_Object_2_Block_1. When a geobody of that name already exists, the Geobody name collision dialog offers Overwrite existing objects, Create unique names and Cancel (Overwrite existing object, Create unique name and Cancel for a single layer). A unique name is made by appending a space and a number, as in Object_1_Object_2_Block_1 1 and then Object_1_Object_2_Block_1 2. For the folder command the question is asked once, before anything is written, and the answer applies to every colliding name, so Cancel leaves the project unchanged.
A layer whose geometry is incomplete is skipped instead of converted: Save as geobody reports that the layer failed because its geometry is invalid and creates nothing, while Save as geobodies lists such layers under Failed in the summary it shows when it finishes. That summary also reports how many geobodies were saved, how many were overwritten and which ones were renamed to keep names unique. On an empty Zones folder, Save as geobodies reports that no layer objects are available to save as geobodies.
Each object under TIN Maps, Faults, Intrusions, Zones and Fault Blocks is listed in the Data Manager with its assigned color filling the object icon, so horizons, faults, intrusions, layers and fault blocks can be told apart by color directly in the tree. An object's assigned color is used in section views and for solid coloring in the 3D view; horizon TIN maps can instead use Z-based palette coloring as described below. A fault takes its color from the fault model. An object with no assigned color keeps the plain icon, and some interface themes show plain icons throughout.
Every object in these subfolders has its own check box. Select or clear a check box to show or hide just that object in the 3D view and on section views; the check box on the Structural models branch hides the whole set. The same objects are listed under Structural model 3D on the Object(s) tab of the Visual Settings panel, and that list stays in sync with the Data Manager check boxes.
The Structural model 3D item also has a Display mode property that limits what the model shows in the 3D view: Full structure (default) shows every object of the model, Surfaces only shows only the modeled horizon surfaces from TIN Maps and hides intrusions, layers and fault blocks, and Faults only shows only the fault surfaces. The mode is set on the parent Structural model 3D item and applies to all of its objects, so a cleared check box always wins: the mode only limits what the selected objects may show. The chosen mode is stored with the view. Display mode is a 3D view property and is not available for section views.
In the time or depth 3D view that matches a structural model, open Visual Settings, choose the Object(s) tab, expand Structural model 3D, and select the modeled horizon surface you want to color. The surface is listed under TIN Maps in the Data Manager. Color by palette colors the surface by vertex Z, with an automatic range from that TIN map's minimum to maximum Z. For a horizon TIN map with no assigned object color, it is enabled by default, with Color bar set to Jet and Inverted palette cleared. A horizon with an assigned object color, including one inherited from its geological object in the Conceptual Model, starts in that solid color instead; enable Color by palette to use Z-based coloring. Choose another palette with Color bar, or select Inverted palette to reverse it. Clear Color by palette to use the solid Color. These defaults apply to new items and views, and to older projects without saved palette settings. Your choice is kept when the project is reopened, including an explicitly saved unchecked setting. Faults, intrusions, layers and fault blocks keep solid coloring by default.
The same models are also displayed on inline, crossline and arbitrary line sections in both domains, where they are listed under All structural model on the Object(s) tab of the Visual Settings panel. Modeled horizon, intrusion and fault surfaces are drawn as their intersection lines with the section, while Zones and Fault Blocks are drawn as translucent filled bands that are split where the volume pinches out. Select a layer or fault block under All structural model to restyle its band: Object item properties then offers Fill type (No fill, Solid, a hatch pattern or a gradient), Fill color, Fill color 2 for the second color of the gradient fill types, and Transparency level, which sets how translucent the band is; the band is redrawn immediately. By default a band is solid-filled in the object's own color and translucent. Each choice is kept per object and re-applied whenever the section is rebuilt, so a fill or transparency change is no longer lost when the view refreshes or you step to another line.
A model is displayed only in the views that match its own domain: a model stored in a Depth folder in the 3D view depth and on depth sections, and a model stored in a Time folder in the 3D view time and on time sections. No time-to-depth conversion is applied, so a time-domain model never appears in a depth view.
Double-click a model, or right-click it and choose Open, to restore its settings in the wizard. Only one model can be open in the wizard at a time, so close the wizard before opening another one. Use Run to rebuild or update its results and Save to store changed settings without running.
Other model actions include Rename, Delete and Verify 3D model.
Several models can be removed in one step. Select them in a Depth or Time folder, right-click the selection and choose Remove, the only command offered for a multiple selection. A single confirmation, "Remove N selected structural models?", names the number of selected models; answer No to leave everything unchanged. Each model is then removed exactly as Delete removes a single one, so any Multi-Z surfaces published from it and any uncertainty realizations built from it disappear with it, and the Data Manager, the 3D view, the inline, crossline and arbitrary line sections in both domains, the Location map and the Visual Settings object lists of those views are refreshed at once, so the deleted geometry and its object items disappear immediately and no view or project has to be reopened. The command applies to the model entries only, not to their TIN Maps, Faults, Intrusions, Zones or Fault Blocks folders or to the objects inside them, and no dependency warning is shown here; that extra confirmation belongs to removing fault models (see Fault model).
See Also