Define Sections and Levels

Levels and sections are defined when setting up a standard slice framework in MSO.

Sections control the horizontal slicing of the orebody to define individual tubes across strike or dip direction. Each section becomes a 2D plane from which tubes are extended vertically using levels.
Levels define the vertical segmentation of the tubes. Each level represents a horizontal position within a tube where stopes may be accessed or seeded.

Activity steps

Create or select an MSO scenario.
If not already defined, specify a block model.
Set up the run economics.
Define your framework orientation.
Display the Framework screen.
Expand Framework Type to select Standard Framework, if not already selected.
Choose a Section Type.
- Fixed – Equally spaced sections based on an Increment value. Number is a read-only field that displays how many sections (U) will be generated based on the current Increment and model extent.
- Variable – Section locations are defined by entering one or more horizontal Coordinate and Size value pairs into the table below.
Choose a Level Type:
- Fixed – Levels are placed at equal vertical Increment intervals. This defines the vertical spacing between levels (say, every 20m). As with the section field above, Number shows the number of levels the current model extents can accommodate, and is updated as the Increment value changes.
- Variable – Level elevations are read from a string file.
- Gradient Strings – Levels are generated along a string using gradually changing spacing. Choose a String File.
- Gradient Strike and Dip Strings – Similar to Gradient Strings, but each level inherits local dip and strike from the control string geometry.
Optionally, Configure Ore Development Strings.
If your Level Type is Gradient Strings, or you are using Ore Development Strings (with fixed or variable levels), you can optionally assign a "Level ID" to each generated level using an attribute from a loaded data object. This can help identify, group, or trace levels using meaningful identifiers from the source data.
1. Check Use Level ID to enable Level ID assignment for Gradient Strings. When enabled, additional controls allow you to specify a data field in the block model that will be used to populate Level ID values. If this option is not selected, Level IDs are not assigned using data object attributes.
2. Select the Field from the block model that will supply the Level ID values. The chosen field should contain meaningful identifiers, such as level names, codes, or numeric identifiers that can be associated with generated levels.
3. Default Specifies a value that will be used when the selected Field does not contain a value. The type of value you can enter depends on the type of the selected Field.
  
  Tip: Choose a default that clearly indicates that no value was available in the source data, such as Unassigned or 0.
Save your settings