Documente Academic
Documente Profesional
Documente Cultură
VERSION 3.0.1
REFERENCE MANUAL
PURPOSE
This manual documents the methods for generating stope-shapes using Version-3 of the
Stope Shape Optimiser developed by Alford Mining Systems.
The Stope Shape Optimiser engine (also referred to as "SSO" in this manual) is
available in commercial products that are marketed and supported by the mining
software suppliers - Datamine, Maptek and Deswik have an established client base and
several new suppliers will be added with the release of Version 3. The look and feel of
the Stope Shape Optimiser product on each vendor platform will conform to the interface
standards and functionality available in each environment. Additional capabilities may
have been added by the vendor to fully integrate the Stope Shape Optimiser with the
proprietary platform.
This manual does not describe the user interface, data conventions, proprietary input
and output file formats, or mechanisms for maintaining scenarios and processing
capabilities for single or multiple scenario execution. For further information on these
supplier package specific topics, please consult the User and/or Training manuals
supplied by your preferred vendor.
This reference manual aims to explain the optimisation techniques and clarify the input
parameters for the optimisation methods, and provide guidelines for effective and
efficient processing of data sets.
In some cases, the XML parameter file formats will be referenced to highlight the options
available. For a complete description of the XML format and parameters used, consult
the separate document “Version 3 Parameter Summary”. The parameter summary will
be of more interest to interface builders and expert users who manipulate XML
parameter files in a text editor.
ACKNOWLEDGEMENTS
Peter Mokos (AMC Consultants), one of the researchers on the AMIRA P1037 project
"Optimization of Stope Designs and Stope Layouts", prepared the initial drafts of this
manual. Ian Glover (AMS) prepared the graphics and Shane Clauson (AMS) edited
earlier Version 2 drafts.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 i
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
CONTENTS
PURPOSE
2.7.4.2
(HIW, HIS, HIWS) Horizontal Irregular Framework
(Rectangular Stope-Shape Tubes) .............................. 38
2.7.4.3 (HIFSC, HIVSC) Horizontal Irregular Framework
(Trapezoidal Stope-Shape Tubes)............................... 39
2.7.4.4 (HUR, HUT) Horizontal Irregular Framework (User
Defined Rectangular or Trapezoidal Stope-Shape
Tubes)......................................................................... 40
2.7.5 Transverse Section Orientation Stope-Shape Tubes ..................... 41
2.7.5.1 (TIL, TISL) Transverse Section Irregular Framework
(Rectangular Stope-Shape Tubes) .............................. 41
2.7.5.2 (TIFS, TIVS) Transverse Section Irregular Framework
(Trapezoidal Stope-Shape Tubes)............................... 42
2.7.6 Shape Types ................................................................................. 43
2.7.6.1 Sub-Stopes ................................................................. 43
2.7.6.2 Sub-Stopes with Varying Strike Length ....................... 45
2.7.6.3 Automatic Sub-Stope Edge Sequences ...................... 47
2.7.6.4 Overlapping Sub-Stopes ............................................. 48
2.7.6.5 Sub-Stope Polygons ................................................... 48
2.7.6.6 Sub-Stope Optimisation .............................................. 49
2.7.6.7 Pillar Locations ............................................................ 50
2.8 Seed-Slice Interval Selection ...................................................................... 51
2.8.1 Use of Control Surface for Lenses with Different Orientations ....... 54
2.9 Shape Parameterisations ............................................................................ 55
2.9.1 Minimum Stope Width ................................................................... 57
2.9.2 Maximum Stope Width .................................................................. 58
2.9.3 Narrow Ore.................................................................................... 58
2.9.4 Dilution ELOS/Skin ........................................................................ 59
2.9.5 Minimum Pillar Width ..................................................................... 60
2.9.6 Strike Angle ................................................................................... 61
2.9.6.1 Strike Angle Range ..................................................... 61
2.9.6.2 Strike Angle Maximum Change ................................... 61
2.9.7 Side Length Ratio .......................................................................... 62
2.9.7.1 Side Length - vertical_side_length_ratio,
top_bottom_maximum ................................................. 62
2.9.7.2 Side Length - vertical_side_length_ratio,
front_back_maximum .................................................. 63
2.9.8 Waste Inclusion Control................................................................. 63
2.9.9 Exclusion Control .......................................................................... 64
2.10 Stope-Shape Framework Angles ................................................................ 65
2.10.1 Apparent Specification Method for Angle Conventions .................. 65
2.10.2 True Specification Method for Angle Conventions ......................... 72
2.10.3 Stope Wall Angles (Equal or Different) .......................................... 73
2.10.4 Geological and Geometric Stope Wall Definitions.......................... 73
2.10.4.1 Geometric (previously called Local)............................. 73
2.10.4.2 Geological (previously called Global) .......................... 73
2.11 Additional Control Surfaces ......................................................................... 75
2.13.3
Merge ............................................................................................ 86
2.13.3.1 Merge on Grid ............................................................. 86
2.13.3.2 Merge on Interval ........................................................ 86
2.14 Advanced Optimisation Controls ................................................................. 88
2.14.1 Do Not Force Full-stope Sub-Stope Pillars .................................... 88
2.14.2 Do Not Force Stope Split Sub-Stope Pillars................................... 88
2.14.3 Stope Sequence Subset Optimisation ........................................... 88
2.14.4 Disable Structure Test on Seed ..................................................... 88
2.14.5 Force Different Dip Case Corner Width Tests................................ 89
2.15 Good Practice - Tips and Procedures ......................................................... 90
2.15.1 Discretisation................................................................................. 94
2.15.2 Stope Control Surface ................................................................... 95
2.15.3 Stope String Types ........................................................................ 96
2.15.4 Wireframe Types ........................................................................... 96
2.15.4.1 Stopes......................................................................... 96
2.15.4.2 Verification .................................................................. 98
2.15.5 Gradient Control Strings ................................................................ 98
3 PRISM METHOD ................................................................................................. 99
3.1 General Stope-Shape Framework ............................................................... 99
3.2 Prism Method Framework ......................................................................... 101
3.3 Stope-shapes............................................................................................ 104
3.4 Trough Undercut ....................................................................................... 105
3.5 Shape Refinement - Crown Shape Annealing ........................................... 105
3.6 Waste Pillar Separation............................................................................. 106
3.7 Advanced Parameters .............................................................................. 106
3.7.1 MIP Solvers ................................................................................. 106
3.7.2 Rectangular and Shaped Stopes ................................................. 107
3.7.3 Stope Sublevel Constraints ......................................................... 107
3.7.3.1 Stope Sublevel – “common_base_sublevel”.............. 108
3.7.3.2 Stope Sublevel – “common_mine_sublevel” .............. 108
3.7.3.3 Stope Sublevel – “common_local_sublevel” .............. 108
3.7.3.4 Stope Sublevel – “variable_stope_height” ................. 108
3.7.4 Validation Test Cell ..................................................................... 110
3.7.5 Prism Optimisation Exceptions .................................................... 110
3.8 Good Practice - Tips and Procedures ....................................................... 110
4 OPTIMISATION OPTIONS (SLICE & PRISM) ................................................... 112
4.1 Model Discretisation.................................................................................. 112
4.2 Cut-off and Head-grade ............................................................................ 114
4.2.1 Cut-off Grade using Curve Table ................................................. 117
4.3 Evaluation Methods .................................................................................. 118
TABLES
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 v
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Table 2.2 Stope-Shape Framework Orientation and Extents Summary (with NX, NY,
NZ supplied for the regular framework case) .......................................... 29
Table 2.3 Vertical Orientation Stope-Shape Tubes Summary................................. 31
Table 2.4 Horizontal Orientation Stope-Shape Tubes Summary ............................ 36
Table 2.5 Transverse Section Orientation Stope-Shape Tubes Summary .............. 41
Table 2.6 Apparent Strike and Dip Angle Conventions ........................................... 65
Table 4.1 Detail Report Codes ............................................................................. 126
Table 4.2 Summary Report Codes ....................................................................... 127
Table 4.3 File Field Names .................................................................................. 129
FIGURES
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 vi
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 vii
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
APPENDICES
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 viii
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The SSO application mimics what an engineer would do, generating strings on sections,
linking these to create a wireframe shape and then evaluating the wireframes against a
block model. The SSO provides a stope-shape that maximises recovered resource
value above a cut-off while also catering for practical mining parameters such as;
minimum and maximum mining width, anticipated wall dilutions, minimum and maximum
wall angles, minimum separation distances between parallel and sub-parallel stopes,
minimum and maximum stope heights and widths, etc.
Figure 1-1 summarises the general process flow for the SSO.
This document discusses the Stope Shape Optimiser methods, the typical optimisation
applications and clarifies the input parameters for the optimisation methods.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 1
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The block model must spatially represent the location of the mineralisation. Regularised
models that use a percentage populated field are not applicable for SSO. These models
however can be converted by over-printing cells filled within the mineralisation
wireframe(s) over the regularised model to create a sub-celled model. The cell size and
the level of sub-celling used in the block model will determine the precision of the
orebody representation.
For mining software vendor packages that use a cell filling plane for populating a block
model (i.e. the following is not applicable to say Maptek models), the cell filling plane
should ideally be aligned with the strike plane of the orebody such that sub-celling
occurs perpendicular to the proposed mining width. For example, if the orebody is
tabular and the strike plane is generally YZ then the filling plane should ideally also be
YZ so that sub-cells terminate exactly at the orebody X-axis extents. The cell filling
orientation has implications regarding the SSO accuracy for optimising and evaluating
the stope-shapes.
Models should ideally have an enclosing envelope of waste cells modelled around the
mineralisation. The surrounding waste is required for cases where a sub-stope may be
mined adjacent to a full stope using waste pillar criteria (a SSO function requirement). If
sub-stopes are not required, then unmineralised waste cells can be filtered from the
block model to reduce run times.
Models should ideally avoid absent data (for example ’-‘in Datamine Studio models),
especially for the density field, the cut-off evaluation field or any other reported field(s).
For the situation where cells have “absent” values or where cells are missing from within
the stope-shape, the default value supplied for each field is applied. Careful
consideration is required regarding the default values selected, especially regarding the
optimisation field. For example if the optimisation field is a metal grade field then zero
may be appropriate, but if the optimisation field is a value field (e.g. net smelter return
dollar value) then a negative number representing the cost to mine (and process) waste
may be more appropriate than a zero value.
The block model cell size should ideally correlate with the definition of the mineralised
zone such that several cells define the stope width (XZ/YZ strike orientation) or stope
height (XY/YX plan orientation). One or two cells representing the stope width/height
would generally be too coarse to represent the ore-body grade distribution.
The model must have definitions for the size and number of cells, origin and optional
rotation (if applicable) and be able to be expressed with the Datamine Studio model
definition conventions. The model definitions used internally by the SSO are the set of
fields [IJK, XC, YC, ZC, XINC, YINC, ZINC, NX, NY, NZ, XMORIG, YMORIG, and
ZMORIG]. For rotated models, the optional rotation fields [X0, Y0, Z0, ANGLE1,
ANGLE2, ANGLE3, ROTAXIS1, ROTAXIS2, and ROTAXIS3] are also used internally
by the SSO. The rotation point [X0, Y0, Z0] used is at the origin of the model. If a
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 2
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Maptek Vulcan model is supplied, the SSO rotation point is recalculated from the
Maptek Vulcan rotation point and offset distance.
These methods are briefly explained here, and described in more detail in Section 2 and
3 respectively of this manual.
The Slice Method generates and evaluates thin slices across the mineralised zones that
are aggregated into seed-shapes (looking at all possible permutations) that satisfy stope
and pillar width constraints. The seed-shapes are then annealed to the final optimised
stope-shape satisfying the stope and pillar width, stope geometry constraints (e.g. wall
dips angles, strike twist, etc.), and other miscellaneous constraints (e.g. zone mixing,
exclusion zones, etc.). The result is a set of stope-shapes constrained to the basic
limitations of the envisaged mining method.
At a high-level there are four stages in the SSO process that are described as follows:
1) Seed-slice : Analogous to sample intervals across the mineralisation in the
transverse direction.
2) Seed-shape : An aggregation of the seed-slices into seed-shapes that satisfy
stope and pillar width constraints and cut-off, and other miscellaneous
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 3
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The SSO process generates thin slices (seed-slices) across the mineralised zones that
are aggregated into seed-shapes that satisfy stope and pillar width constraints and cut-
off. The SSO looks at ALL possible combinations of seed-slices and selects the
aggregated seed-slices that yield the highest value above cut-off. SSO operates quite
differently to how many users anticipate a typical algorithm might work. A typical
heuristic could be to identify grade intervals, retain them if they meet the minimum
interval length, and then merge to carry short intervals with other acceptable length
intervals. These interval heuristics and similar strategies are not used by SSO as they
fail on a number of grounds: - they are not guaranteed to yield the optimal solution, and
cannot deal with more complex situations with multiple lenses and variable grade
distributions; or specific end-cases where it might be optimal to have waste added to
ore, or pillars containing ore; to meet the stope and pillar width parameters.
The seed-slices or aggregates of seed-slices are only added to the seed-shape(s) if the
cumulative value of the slice aggregate falls above the cut-off. The only exception
would be where the stope geometry or other miscellaneous constraints also had to be
satisfied. The grade or value for the aggregated slice-volumes above and below cut-off
must be equal-to or greater-than the nominated cut-off to allow inclusion to the stope-
shape. The cut-off concept is described in more detail under Cut-off and Head-grade .
The seed-shapes are annealed to form the optimised stope-shape (prior to the addition
of wall skin dilution(s)), that is inclusive of internal dilution to form a practical stope-
shape based on the geometry parameters applied. The final stope-shape wireframe
includes the dilution skin(s) - if applicable.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 4
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The seed-slice orientations can be defined by using one of (in increasing order of utility):
a) Default “dip and strike angle” settings (least preferred option).
b) Using “Dynamic Anisotropy” fields contained within the input block model.
"Dynamic Anisotropy" is a specialised interpolation technique that generates a
local strike and dip at each cell centre from the orientation of bounding
geological wireframes. It is typically used to deal with anisotropy in folded
orebodies and has some minor advantages over the "Stope Control Surface",
but has the possible disadvantage of being dependant on the model cell size.
c) A “Stope Control Surface” which is a simple wireframe to define the general
orientation expected for the stope-shapes in the mineralised zones of the
orebody. This is the most preferred option as it is customised to the specific
requirements of SSO, is quite efficient, and is independent of model cell size.
If the Stope Control Surface or Dynamic Anisotropy field data does not extend to all
areas, then the default dip and strike angle settings will be applied in the undefined
areas.
The seed-slice orientation and seed-slice interval are key parameters for the
successful generation of the seed-shape. A seed-shape cannot be formed without seed-
slice(s) above cut-off. A stope-shape cannot be generated without a seed-shape.
While a geology wireframe is often a good proxy for the stope orientation, the geology
wireframe is often far too detailed for the purposes of stope generation. Blindly using the
geology wireframe can sometimes lead to unexpected results or missing stopes that
arise from kinks and inflections in the geology wireframe surface.
The seed-slice interval should ideally be a sub-multiple of the minimum stope width, the
dilution widths on both sides of the stope-shape (near/far or hangingwall/footwall) and
half of the minimum pillar width. This requirement at the seed-slice generation stage
becomes more important if there are many lenses that will form narrow stope-shapes
with a minimum pillar width between lodes. As a general rule, a seed-slice interval that
generates a minimum of 3-5 seed-slices for the minimum stope width is recommended.
Typically generating more will increase the run time for little benefit, and conversely,
generating less will reduce the result quality.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 5
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The Prism Method allows the user to define a library of possible stope-volumes by using
permutations of stope length, width and height (as rectangular prisms). The library of
stope-volumes can be defined as rectangular-prisms or defined as prisms with a
centralised undercut-trough (i.e. a shape like an inverted “milk-carton”). The stope-
library can be developed quickly by using minimum, maximum and step increments for
each axis or the library can be explicitly defined giving specific axis dimensions for each
stope-volume.
The Prism Method optimally combines the stope-volumes within each framework
"region" with no overlapping of either regular or various irregular stope-volumes (i.e. it
selects the optimum non-overlapping combination of rectangular stope-volumes). The
goal of the optimisation is to select the set of non-overlapping stope-shapes that
maximises value for the material to be extracted by the selected stope-shapes. All
possible combinations of shapes and positions are considered in the optimisation.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 6
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Flat or Horizontal
0
10
Vertical Dip
30
60
90 80
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 7
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Table 1.1 Stope Shape Optimiser Method Applicable to Various Orebody Geometries and Mining Methods
MINING METHODS OREBODY GEOMETRIES OPTIMISATION METHOD (Version2 Stope Optimiser Engine)
Caving Methods Typical Dip Typical Geometry SLICE VERTICAL SLICE HORIZONTAL SLICE SECTION PRISM
Block Caving Vertical to Sub-Vertical Massive to Pipe √ factorised #
Sub-level Caving Vertical to Sub-Vertical Massive to Lenticular √ splits W-axis & factorised #
Core and Shell Vertical to Sub-Vertical Massive to Lenticular √ sub-stope & factorised √ factorised #
Open Stoping Methods
Sub-level Open Stoping ** Vertical to Sub-Vertical Massive to Lenticular √ √ √
Longhole Open Stoping ** Sub-Vertical to Moderate Lenticular to Tabular √
Benching **/ Avoca / Modified Avoca Sub-Vertical to Moderate Tabular to Narrow Vein √ √ plunging orebody ##
Shrinkage / Vertical Retreat Sub-Vertical to Moderate Tabular to Narrow Vein √
Drifting Methods
Room and Pillar Flat to Sub-Horizontal Lenticular to Tabular √ sub-stopes √ factorised #
Post Pillar Cut and Fill * Sub-Horizontal to Moderate Lenticular to Tabular √ sub-stopes
Mechanised Cut and Fill * Flat to Vertical Lenticular to Narrow Vein √ narrow orebody ^
Drift and Fill * Flat to Vertical Lenticular to Narrow Vein √ splits W-axis
Notes:
* Indicates backfill is incorporated into the mining method.
** Indicates backfill can be used to increase ore recovery.
#
Indicates conceptual planning accuracy.
##
Indicates special case suited to plunging moderate orebody (dip and geometry).
^
Indicates suited to narrow orebody, requires factors for moderate geometry.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 8
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
2 SLICE METHOD
2.1 Stope-Shape Frameworks General
The Slice Method frameworks are sub-categorised as:
Vertical; XZ or YZ orebody orientations.
Horizontal; XY or YX orebody orientations.
Transverse; special case of XZ or YZ orebody orientations, that optimise
shapes in both the transverse and vertical directions.
The first letter of the framework orientation is the U direction and the second is the V
direction. So for example with the XZ orientation, X is the U-axis and Z is the V-axis.
Slice frameworks for Vertical and Horizontal orientations are further sub-categorised as:
Regular frameworks, where both axes use fixed intervals (the U-axis intervals
and V-axis intervals are fixed) – like having fixed section spacing and fixed level
spacing for vertical orientations or fixed strike sections and fixed wall spacing for
horizontal orientations.
Irregular frameworks; where either or both of the U and V-axis intervals is
variable. For example like having 4x25m levels and 1x15m sill pillar level for a
mine block covering 115m vertical extent which is repeated, or like having 15m
primary and 20m secondary stopes along strike (for vertical orientations).
User Defined frameworks; where coordinates are provided to define long
section (U, V) dimensions of the stope-shape geometry. The coordinates can
represent either rectangular shapes (orthogonal), or trapezoidal or quadrilateral
shapes (non-orthogonal).
Irregular Slice Method frameworks can also use control strings for defining variable level
elevations (gradients for vertical orientations) or variable side-wall spacing – likened to
topographic contours (for horizontal orientations).
The framework and stope geometry are described in the following terms:
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 9
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
and stope-shape are defined within the extents of the tube. The Slice Method
optimisation is applied within the individual tubes, independently, and each tube
is assigned a unique quadrilateral or QUAD number.
Tube Definition
Regular Framework - XZ Stope Orientation Plane
Tube
Z(V)
Stope
Shapes
X(U)
Y(W)
Stope face
(rectangle for regular framework)
Tube Definition
Irregular Framework with Gradient Control Strings - XZ Stope Orientation Plane
Z(V)
Tube
Stope
Shapes
X(U)
Y(W)
Stope face
(trapezoid for gradient control strings)
The following figure summarises the stope framework hierarchical structure for the Slice
methods. The controls for stope-shape geometry for each case will be explored in more
detail in subsequent sections.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 10
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
V
U (VR-O) Optimise Level, V (HR-O) Optimise Wall, V
W V
U
W
Irregular (Rectangles) Control Strings Irregular (Rectangles) Control Strings Irregular (Rectangles)
(VIL) Fixed U, Variable V (VIL-D) OreDev (HIW) Fixed U, Variable V (HIW-D) Horizon W
(TIL) Fixed U, Optimised V
W
V
V U Optimised W
U
V V V
U U
U
W W W
(VIS) Variable U, Fixed V (VIS-D) OreDev (HIS) Variable U, Fixed V (HIS-D) Horizon W
(TISL) Variable U, Optimised V
W
V
V U Optimised W
U
V V V
U U
W U
W W
(VILS) Variable U, Variable V (VILS-D) OreDev (HIWS) Variable U, Variable V (HIWS-D) Horizon W
W
V U
V U
V V
U U
W W
Irregular (Trapezoids) Irregular (Trapezoids) Irregular (Trapezoids) Control Strings (for V-axis)
Fixed U Control Strings (for V-axis) Control Strings (for V-axis) Fixed U Control Strings (for V-axis) Control Strings (for V-axis) Fixed U (TIFS) Section (Regular W)
(VIFSG) Gradient (VIFSG-D) OreDev-Gradient (HIFSC) Contour W (HIFSC-D) Horizon-Contour
V W
U
V U V
W U
V V
U U
W W
Variable U Variable U Variable U (TIVS) Section (Regular W)
V
Control Strings (for V-axis) Control Strings (for V-axis) Control Strings (for V-axis) Control Strings (for V-axis)
W U
User Defined V
U
V
U
User Defined
W W
(VUR) Rectangles (HUR) Rectangles
V W
U
V U
W
V
U W
W V U
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 11
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The stope sections (U-axis) may be regularly spaced or irregularly spaced. At the same
time, the stope levels (V-axis) may be regularly spaced, irregularly spaced or irregularly
spaced with variable gradient.
The faces of the stope-shapes produced are sectional outlines defined by four points.
For orebodies with vertical orientation this will be two on the floor and two on the back.
For orebodies with horizontal orientation this will be two on each of the stope end faces.
The points lay in the stope-shape UV-axis plane and the projection of the face is either a
rectangle or a trapezoid where the opposite sides are parallel. Rectangular and
trapezoidal shapes are special cases of 4 sided polygons. These are commonly referred
to as quadrilaterals in SSO. The quadrilaterals form a tube-shape when extruded in the
transverse direction representing the stope-shape W-axis.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 12
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Examples of the Slice Method vertical orientation frameworks are depicted in Figure 2-
3 and Figure 2-4 Slice Method Framework - Vertical YZ
Orebody
Stope
Shapes Z(V)
Level Spacing
X(U)
Section
Y(W) Spacing
Transverse Direction
Pillar Width
Orebody
Level
Spacing
Z(V)
Pillar Width
Y(U)
Section
Spacing Stope
Shapes
X(W)
Transverse Direction
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 13
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The Slice Method horizontal orientation frameworks are depicted in Figure 2-5 and
Figure 2-6. The selection of YX over XY will be dictated by the ability to have greater
control over roof and floor angles along the V-axis.
Z(W)
Stope
Shapes
X(U)
Orebody
Y(V)
Pillar Width
Strike Section
Spacing
Transverse
Section Spacing
Z(W)
Y(U)
Stope
Shapes
Orebody
X(V)
Pillar Width
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 14
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The Slice Method transverse section orientation frameworks are depicted in Figure 2-7
and Figure 2-8. The sublevel height and location are optimised independently between
sections. This method is suited to gentle/shallow dipping, thicker orebodies.
Level
Spacing
Z(V)
Stope
Shapes
Section Spacing
Y(W)
Orebody
X(U)
Transverse Direction
Pillar Width
Level Spacing
Z(V)
Orebody
Section
Spacing
Stope
Shapes
X(W)
Pillar Width
Y(U)
Transverse Direction
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 15
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The stope-shape framework can be floated in the stope orientation plane (using defined
step increments) to optimise the start location for both the level and section without
changing the dimensions of the level interval (V-axis dimension) or section spacing (U-
axis dimension). The stope-shape framework can then be further refined by also
changing the level and/or section spacing dimensions.
For framework optimisation the stope-shape minimum and maximum size and increment
are supplied for the axes specified by the stope orientation plane, and the step size for
the origin shift along the same axes.
The initial framework specification defines the extent of the volume to be considered. To
minimise the number of combinations to be considered, the stope-shape size
increment should be a sub-multiple of the stope dimension. The origin shift should be
a sub-multiple of the stope sizes. For example, the stope sizes might be 20-35 in
increments of 5 and the origin step size is set to 5. As the run-time for a large set of
increment combinations might be prohibitive, a single test scenario should be run to
estimate the likely runtime for all combinations. E.g. nominate a single stope size and no
origin step to ascertain the run-time for a single iteration.
The “output_best_case” option will only output the stopes for the single framework that
generates the best set of stopes. The “output_all_cases” option outputs all
combinations of the stope size and framework increment to the output files (if supported
by the vendor data store). The “output_all_cases” and “output_best_case” options are
mutually exclusive (i.e. one or the other may be selected, but not both at the same time).
For the Transverse Section method there is a more restricted optimisation procedure
whereby the user provides a set of alternative stope heights, and the best combination
of sublevel intervals and stope heights is chosen.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 16
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
If a zone iteration field is defined in the block model and each zone is spatially
separate, then the framework position and extent will be optimised for each zone. The
set of possible zones is nominated by a list. These zones can be different lodes, pods or
even independent mine areas.
Zone Iteration allows the flexing of the level start location, level interval, and level offset
and/or section start location, section interval, and section offset between multiple zones.
The “iterate” function evaluates all combinations of level spacing and offsets of the level
start location, and reports the results as a sorted list to guide the design choice. The
user has the option of outputting the best case.
Where the orebody is made up of discrete ore zones, each is evaluated independently,
and the sorted list is reported by ore zone. This feature can be useful when there are a
significant number of zones to be evaluated, for example where the orebody has many
pods.
The runtime for a large number of combinations can be prohibitive. A single scenario
with all required zones should be run to estimate the likely runtime for all combinations.
(I.e. a run without zone iteration)
Figure 2-9 shows the result of optimising (in the sectional orientation) the level location
for two different lodes with a fixed sublevel interval. This technique could be extended
to allow a range of sublevel intervals.
Z(V)
Origin
Y(W) Optimised origin for parallel lode
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 17
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Figure 2-10 shows the result of using zone iteration to optimise the section start location
for multiple lodes. The iteration is in the horizontal orientation and there is a fixed section
interval.
Optimised origin
for parallel lode
Z(W)
Origin
Y(V)
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 18
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
(i.) Where the string projection in the UV plane is used to define the face shape, or
(ii.) Where the string position in the W dimension controls the position of the
stope.
An example of (i.) would be to allow gradients on levels, and an example of (ii.) would be
to control the position of stopes and pillars.
The best location for these control-strings will only be known after a preliminary run
without control-strings has been completed.
A multiple optimisation run approach should be used to guide the optimal placement of
the control-strings. In the first pass, a regular optimisation can be completed without the
control-strings. The first pass result is then used to guide the location of the control-
strings, and a second optimisation run is conducted to define the stope-shapes that
honour the control-strings. Alternatively in cases where level development data already
exists, control-strings may be created from that information.
Control-strings can be supplied for each of the framework orientation cases as detailed
below.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 19
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Control-string functions for XZ|YZ orientation frameworks that extend along the U-axis.
2.4.1.1 GRADIENT
The gradient control-string is used to define the gradients of levels along the orebody
strike axis (variable V-axis). The strings would typically be used for orebodies with an
extensive strike length, such that the difference in elevation from the level access point
to the level strike extremity is significant. The gradient control-string will change the
framework geometry, as shown in Figure 2-11.
A stope face is created where a pair of gradient strings intersects adjacent sections.
Ideally the control-strings should have the same orientation as the stope-framework U-
axis.
Care is required to ensure that adjacent strings extend to intersect all sections. This will
avoid unintended trapezoidal shapes, or unintended gaps, as shown in Figure 2-12
OreDev Control-String Example.
2.4.1.2 OREDEV
The OreDev control-string is used to define level layouts on fixed elevations (horizontal
gradient) using development centrelines. A stope cannot be created unless its’ floor is
located on a control-string, and a stope floor cannot be located on more than one
control-string.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 20
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
OreDev strings do not change the framework, and should be added as an option
to a second-pass run. The strings are typically used to control the location of stopes
and pillars from section to section. They define practical level layouts by constraining the
transverse lateral extents of stope-shapes for parallel lodes (i.e. W-axis direction). The
strings can also be used to constrain the strike extents (U-axis) to say remove strike
outliers.
The seed / annealed stope-section-ends lying at floor level must straddle the string in
order to be accepted. The strings ideally run along the floor of the stopes (but if above,
they will be projected to the floor position) and assume horizontal levels. The intent of
this control-string is to remove transverse pillars and transverse outliers. They may be
used for dropping out irregular pillars. This function may combine transverse stopes,
creating more practical but less optimal stope-shapes. An example is provided in Figure
2-12
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 21
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
2.4.1.3 OREDEV-GRADIENT
2.4.1.4 SECTION
The section control-string is used to define gradients of levels for the Transverse Section
XZ|YZ cases (special case of sectional frameworks). It should be used as a second pass
process to apply gradients to levels and would be used after the initial transverse
section optimisation identifies the approximate sublevel position and height for that
section.
Control-string functions for XY|YX orientation frameworks, like the vertical orientation
frameworks, extend along the U-axis.
2.4.2.1 CONTOUR
2.4.2.2 HORIZON
This control-string is equivalent to OREDEV for XY|YX – the floor and roof must straddle
the string (in the vertical sense i.e. W-axis) to be included.
2.4.2.3 HORIZON-CONTOUR
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 22
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Frameworks, like the geological block models, can be defined as Un-rotated or Rotated.
For most cases, users deal with un-rotated frameworks which are easier to understand
and faster to process due to simpler geometric calculations.
The block model rotations may be the same or different to the stope-shape framework
rotations. The rotated block model is defined in local coordinates and world coordinates
via rotation parameters. The following describes the various cases.
It is always advised that the location and extents of a rotated framework be checked
visually against the mineralised portion of a block model to ensure that stopes can be
generated where they are expected.
The stope-shape framework and block model combinations (as illustrated in Figure 2.13)
are reported in the run-time logfile (with verbose output) as:
Neither the block model nor the stope-shape framework are rotated
(MODROT=1)
The block model and stope-shape framework are both rotated, and have the
same rotation definitions (MODROT=2).
The block model and stope-shape framework are both rotated, and the axes are
parallel but offset (MODROT=3). Note that this case also requires the rotations of
model and framework to be identical
One or both of the block model and stope-shape framework are rotated, but do
not have equal rotation angles (MODROT=4).
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 23
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Block model
Stope-shape framework
Origin
One or both of the block model and stope-shape framework are rotated,
but do not have equal rotation angles
Block model
Block model
Stope-shape
framework
Stope-shape
framework
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 24
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
For un-rotated cases, the stope-shape frameworks implicitly use world coordinates [X,
Y, Z] i.e. both the level coordinates and section coordinates are defined in the world
coordinates.
For un-rotated cases, the world coordinates define the framework extents (minimum and
maximum) and the step sizes are entered directly to the user interface. This defines the
x, y and z extents and the number of steps based on the step size.
Rotated frameworks use local coordinates [X’,Y’,Z’] and world coordinates [X,Y,Z] to
specify the framework origin point (both local and world). The coordinates for the local
framework origin are typically set as [0, 0, 0] or even [0, 0, “mine_level_elevation”], and
use of the world coordinates for the local framework origin should be avoided for
simplicity. A specific requirement is that the rotation point and the origin of the
framework must be coincident.
There is no standard among mining software suppliers for conventions for specifying
block models. Specification of origins, rotations, angle conventions, cell and sub-cell
size and indexing, and even absent data values and modelling of undefined cells differ.
Each mining software supplier provides a software API (Application Programming
Interface) to AMS to directly and efficiently read the proprietary model formats.
The specification of the framework is equivalent to specifying a model origin, extent, cell
size and rotation for a block model.
The AMS Stope Shape Optimiser internally adopts the conventions of the Datamine
Studio software, and each vendor convention is mapped to the Datamine Studio
convention to run the engine. The goal of the vendor interface is to accept framework
parameters in conventions that are familiar to the user of that mining software and
convert these to the conventions used by the Stope Shape Optimiser. Inspection of the
XML parameter files supplied to the Stope Shape Optimiser will show that a conversion
has taken place to make the appropriate transformations between the mining software
conventions and those of the Stope Shape Optimiser.
The stope-shape framework reference point in the XML is defined in world coordinates
at the bottom left-hand-side corner of the stope-shape framework [x0, y0, z0]. The origin
and dimensions are then redefined in local coordinates [xr0, yr0, zr0]. The order of the
axes selected for rotation and the rotation angles are defined in Table 2.1.
The stope-shape framework orientation [U,V,W] axes correspond to the world [X,Y,Z] for
the un-rotated case. However, for the rotated case, the stope orientation [U,V,W] axes
correspond to the local framework grid coordinates [X’,Y’,Z’], not the world framework
coordinates [X,Y,Z]. The stope-shape framework is specified in the [U,V,W] grid.
With an irregular framework, parameters like section location and sublevel elevation
should be provided in local coordinates. If no stopes are output it is likely that the
coordinates were supplied in world rather than local coordinates.
If strings or wireframes are supplied to the Stope Shape Optimiser, then these will need
to be in world coordinates. All output from SSO is in world coordinates, but internally the
Stope Shape Optimiser works in local coordinates.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 25
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The key elements to consider for rotated models are illustrated in Figure 2-14. The
world coordinates are identified as [X,Y,Z] and the local coordinates as [X',Y',Z']
Shape Framework
Section Spacing
Stope Orebody
Shapes
Z’ (V)
Y’ (W) X’ (U)
-15o
Framework Origin
(XR0 YR0 ZR0)
Block Model
Extent
X0 Y0 Z0
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 26
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The parameters entered for rotated frameworks are summarised in Table 2.1.
The axis around which the first rotation angle will occur. 0
ROTAXIS1
for no rotation, 1 for X axis, 2 for Y axis, 3 for Z axis.
The axis around which the third rotation angle will occur. 0
ROTAXIS3
for no rotation, 1 for X axis, 2 for Y axis, 3 for Z axis.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 27
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Below is an example of the XML syntax for a rotated framework, located in the XML
<Control> Section. This specifies an XZ stope-framework that is rotated -30o and has
the effect of orientating the stope-framework’s primary strike axis azimuth to 60o :
<layout_framework>
<volume_specification xmorig="0" ymorig="0" zmorig="0"
xextent="2525" yextent="1410" zextent="800"/>
<rotation_specification rotaxis1="3" rotaxis2="0" rotaxis3="0"
angle1="-30" angle2="0" angle3="0"
x0="26829" y0="10733" z0="280" />
<model_evaluation_orientation plane="xz" />
</layout_framework>
Note in particular that the cell_specification number of cells [nx, ny, nz] can only be set
using whole integer values, decimal or fractional vales are not permitted.
It is good practice to visually confirm that the stope-framework has been oriented as
intended relative to the deposit block model using your specific vendor mining package.
For Datamine Studio, this can be done by creating an empty test block model using the
framework specification parameters, and viewing this test model in conjunction with the
deposit block model.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 28
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
For irregular stope-shape frameworks, where the stope dimension vary in the U and/or V
direction, the extent of the stope-framework volume is determined by the values
supplied for (xextent, yextent,zextent), and the notional intervals [xinc,yinc,zinc] for a
regular framework will be superseded by an irregular definition (either by supplying
control strings and/or user defined levels/section intervals and locations) when defining
the tube shapes (as illustrated in Figure 2-1).
N is the number of intervals in the primary “strike” direction (U, the stope-shape U-axis),
M in the number of intervals in the secondary “vertical” direction (V, the stope-shape V-
axis), and P is the number of intervals in the transverse “width” direction (W, the stope-
shape W-axis).
Table 2.2 Stope-Shape Framework Orientation and Extents Summary (with NX,
NY, NZ supplied for the regular framework case)
Framework Orientation U-axis V-axis W-axis NX NY NZ
“strike” “height” “width”
Prism YZ Y Z X P N M
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 29
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Angles for dip and strike, and widths for stopes and pillars can be specified as either
Apparent or True. The True specification is added in Version 3 to allow stope width and
dip angles to be specified in a plane perpendicular to the stope strike, and independent
of the Framework rotation. If True specification is used then the equivalent Apparent
specification is calculated for internal processing based on the orientation of the seed
stope, so a good estimate of the seed stope strike and dip is required and this is best
controlled by the use of a Stope Control Surface.
Note that the easiest and most intuitive method of specifying the strike and dip angles is
to provide a Stope Control Surface wireframe over the full extent of the orebody where
stope shapes are to be generated. The Stope Control Surface is generated and
displayed in world coordinates, irrespective of the orientation of the model and the stope
shape framework. If required, the vendor software can be used to display true dip and
strike off this wireframe surface. The Stope Control Surface has priority over the default
dip and strike (Vertical XZ|YZ, Section XZ|YZ) and default strike dip and transverse dip
(Horizontal XY|YX ) angles.
Specification of strike and dip angles is not needed in the Prism method.
The angle conventions are the same for the Vertical XZ|YZ methods and the Section
XZ|YZ methods. Strike is measured clockwise from the primary stope shape framework
axis (the long section view), looking along the axis in the positive coordinate direction.
Dip is measured from the horizontal left axis looking along the primary axis.
For the Horizontal XY|YX method, dip angles are measured downwards from the
horizontal on both the primary (the first axis in XY|YX) and secondary (the second axis
in XY|YX) axes, and are termed the ‘strike dip’ angle, and the ‘transverse dip’ angle
respectively.
For rotated stope shape frameworks the strike and dip are measured in the local
coordinate system. All angle values are specified in Degrees.
Angles for dip and strike are specified as true dip (TRDIP), and true dip direction
(TRDIPDIR) respectively. TRDIPDIR ranges [0..360] and TRDIP normally ranges [0..90]
but when specifying the stope dip angles the range is [0..180]. TRDIPDIR is found by
adding 90 degrees to the bearing of the TRDIP direction.
These angles have the angle conventions that the Datamine Dynamic Anisotropy
modelling functions provide in the TRDIP and TRDIPDIR fields, with dip measured
positive downwards, and the dip direction measured as a clockwise bearing, with north
being zero degrees.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 30
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
For the Slice Methods, the stope-shapes are constrained to the tube geometry (as
illustrated in Figure 2-1), when extruded in the transverse direction (W-axis). The face or
projected wall shape will be defined by the four corners in the wall plane (i.e.
hangingwall/footwall or near/far wall for vertical orientation, roof/floor wall for horizontal
orientation). The shape of the tubes can be rectangular or trapezoidal (and later
releases will be able to defined with full quadrilaterals).
The stope-shape tube volumes are defined by the framework options and optional
control-string combinations. These are generally described in the following sub-sections.
The vertical orientation is best suited to narrow vein, tabular and lenticular geometry with
narrow to moderate thickness and moderate to sub-vertical dip. For an overview
diagram of deposit morphology, see Figure 1-2 . Option codes are used to identify the
various stope-shape types, a summary of vertical codes appears in Table 2.3 below.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 31
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The regular stope-shape tubes are rectangles having a fixed section spacing (U-axis)
and a fixed level interval (V-axis). The option code for regular stope-shape tubes is VR.
Special case optimisation options (with option code VR-O) are available that can:
Optimise the stope framework origin (Optimise Origin – U|V origin) whereby the
U|V origin is floated on axes step increments.
Optimise the section spacing (Optimise Section – U dimension). The U
dimension (a single optimised dimension) can also be optimised independently
by ZONE (e.g. a different U dimension for each independent lode, pod or mine
area).
Optimise the level interval (Optimise Level – V dimension). The V dimension (a
single optimised dimension) can also be optimised independently by ZONE (e.g.
a different V dimension for each independent lode, pod or mine area).
Combinations of all of the above.
The control-string case (with option code VR-D) can be used to constrain the stopes in
the W and U axes. It is typically applied as a secondary run refinement to remove
impractical stopes such as strike outliers and/or impractical stopes in the transverse
extents i.e. W-axis direction (e.g. where the mineralisation is erratic for parallel lodes
which results in stopes jumping across from one lode to the other or randomly bridging
the parallel lodes). This control-string option does not change the U|V dimensions, and
cannot be used with the optimisation options.
The regular framework rectangle stope-shape tube options (with option codes) are
depicted in Figure 2-15 below:
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 32
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Framework with regular section spacing (U-axis) and irregular level intervals (V-
axis – option code VIL).
Framework with regular level interval (V-axis) and irregular section spacing (U-
axis – option code VIS).
Framework with irregular level interval (V-axis) and irregular section spacing (U-
axis – option code VILS).
The control-string cases (with option codes VIL-D, VIS-D and VILS-D) are used to
constrain the stopes in the W and U axes. It is typically applied as a secondary run
refinement to remove impractical stopes such as strike outliers and/or impractical
transverse extents in the W-axis direction (e.g. where the mineralisation is erratic for
parallel lodes which results in stopes jumping across from one lode to the other or
randomly bridging the parallel lodes). This control-string option does not change the U|V
dimensions.
The irregular framework rectangular stope-shape tube options (with option codes) are
depicted in Figure 2-16 below:
Figure 2-16 (VIL, VIS, VILS) Vertical Irregular - Rectangular Stope-Shape Tubes
V V
U U
W W
V V
U U
W W
V V
U U
W W
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 33
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Control-strings with variable gradient (and lateral extents in the U-axis direction) are
used to form the irregular level intervals (in the V-axis). The irregular trapezoid
framework can either have:
Framework with regular section spacing (U-axis) and irregular level intervals
defined by variable gradient control-strings (V-axis – option code VIFSG), or
Framework with irregular section spacing (U-axis) and irregular level intervals
defined by variable gradient control-strings (V-axis – option code VIVSG).
In addition to irregular level intervals (using the variable gradient control-strings) the
control-strings can optionally be used to remove impractical stopes such as strike
outliers and/or impractical transverse extents in the W-axis direction (e.g. where the
mineralisation is erratic for parallel lodes resulting in stopes jumping from one lode to the
other or randomly bridging the parallel lodes). Note that the OreDev-Gradient control-
string for Version 3 only allows defining one long section trace per level in the stope
orientation plane projection. As such, for multiple parallel orebodies it can only produce
one stope in the W-axis direction (unlike the OreDev control strings for option codes VR-
D, VIL_D, VIS_D or VILS_D which can allow multiple parallel lodes but for a horizontal
plane only (i.e. multiple stopes in the W-axis for each horizontal level).
The irregular framework trapezoidal stope-shape tube options (with option codes) are
depicted in Figure 2-17 below:
V V
U U
W W
Variable U
V V
U U
W W
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 34
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Both methods define the stope-shape in long section, and the projection of this shape in
the W-axis direction (i.e. transverse direction) forms the face of the stope-shape "tube".
User Defined
(VUR) Rectangles
V
U
W
(VUT) Trapezoid
V
U
W
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 35
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The horizontal orientation is best suited to narrow vein, tabular and lenticular geometry
with narrow to moderate thickness and moderate to sub-horizontal dip. For an overview
diagram of deposit morphology, see Figure 1-2. Option codes are used to identify the
various stope-shape types, a summary of horizontal codes appears in Table 2.4 below
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 36
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The regular stope-shape tubes are rectangles having a fixed section spacing (U-axis)
and a fixed width interval (V-axis). The option code for regular stope-shape tubes is HR.
Special case optimisation options (with option code HR-O) are available that can:
Optimise the stope framework origin (Optimise Origin – U|V origin) whereby the
U|V origin is floated on axes step increments.
Optimise the section spacing (Optimise Section – U dimension). The U
dimension (a single optimised dimension) can also be optimised independently
by ZONE (e.g. a different U dimension for each independent lode, pod or mine
area).
Optimise the wall interval (Optimise Wall – V dimension). The V dimension (a
single optimised dimension) can also be optimised independently by ZONE (e.g.
a different V dimension for each independent lode, pod or mine area).
Combinations of all of the above.
The control-string case (with option code HR-D) can be used to constrain the stopes in
the W and U axes. It is typically applied as a secondary run refinement to remove
impractical stopes such as strike outliers and/or impractical steps in the W-axis direction
(e.g. where the mineralisation is erratic for parallel lodes and resulting in stopes jumping
up and down from one lode to the other or randomly bridging the parallel lodes). This
control-string option does not change the U|V dimensions, and cannot be used with the
optimisation options.
The regular framework rectangle stope-shape tube options (with option codes) are
depicted in Figure 2-19 below:
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 37
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Framework with regular section spacing (U-axis) and irregular wall intervals (V-
axis – option code HIW.
Framework with regular wall interval (V-axis) and irregular section spacing (U-
axis – option code HIS).
Framework with irregular wall interval (V-axis) and irregular section spacing (U-
axis – option code HIWS).
The control-string cases (with option codes HIW-D, HIS-D and HIWS-D) are used to
constrain the stopes in the W and U axes. It is typically applied as a secondary run
refinement to remove impractical stopes such as strike outliers and/or impractical steps
in the W-axis direction (e.g. where the mineralisation is erratic for parallel lodes and
results in stopes jumping up and down from one lode to the other or randomly bridging
the parallel lodes). This control-string option does not change the U|V dimensions.
The irregular framework rectangle stope-shape tube options (with option codes) are
depicted in Figure 2-20 below:
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 38
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Control-strings with variable strike direction (and lateral extents in the U-axis direction)
are used to form irregular wall intervals (in the V-axis). The irregular trapezoid
framework can either have:
The irregular framework trapezoidal stope-shape tube options (with option codes) are
depicted in Figure 2-21 below:
Variable U
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 39
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Vmax V2max
V1max
V1min
Vmin V2min
Umin Umax Umin Umax
Both methods define the stope-shape in plan and the projection of this shape in the W-
axis direction (i.e. transverse direction) forms the face of the stope-shape "tube".
W
V
U
(HUT) Trapezoid
W
V U
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 40
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The transverse section orientation is best suited to moderate plunging orebodies with
lenticular, pipe or massive geometry and moderate to wide thickness that are amenable
to benching type mine methods where the stopes walls for adjacent sections abut. It is
typically a “special case” vertical orientation option. For an overview diagram of deposit
morphology, see Figure 1-2. Option codes are used to identify the various stope-shape
types, a summary of transverse codes appears in Table 2.5
Irregular (Rectangles)
(TIL) Fixed U, Optimised V
W U
W U
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 41
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
W U
W U
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 42
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
In the stope optimisation run, full-shapes are processed first in a tube, and then sub-
shapes (from the remaining ore not mined with a full-shape), and lastly development-
shapes (from the ore that cannot be taken in either full-shapes or sub-shapes).
Any combination of these shapes can be selected in an optimisation run, and some
overlap in definition is possible. A sub-shape having the same dimension as the full-
shape could be specified, but there would not be any value in this if the full-shape had
also been selected, as the full-stope would have already formed stopes of that
dimension.
2.7.6.1 Sub-Stopes
Full-shapes (full-stopes) can be sub-divided in either and/or both of the shape’s U-axis
and V-axis, to create sub-shapes (sub-stopes). Defining sub-stopes helps maximise
resource recovery into stopes, especially at the orebody strike extents or where the
mineralisation may be patchy or irregular.
A maximum of 25 sub-shapes can be specified in any one run (i.e. 25 different sub-
shape U|V dimensions).
Note that sub-stoping requires a model with cells defined in waste/pillar areas in order to
honour stope geometry rules for the minimum pillar width between stopes and sub-
stopes, and between sub-stopes (in the W-axis). The “minimum pillar width” function
requires model cells to be present in order to flag what has already been mined in earlier
passes of stopes and sub-stopes. This is necessary so that the minimum pillar width can
be maintained between "mined" material and the new sub-stope.
a) Divisor - specifying the number of sub-shapes along the U and/or V axes. The
sub-shapes are strictly non-overlapping.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 43
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
b) User Defined – The user can specify a list of sub-shapes using proportions as
fractions. Later entries in the list can be overlapping and/or non-overlapping.
c) Automatic Function - this will automatically generate a list of over-lapping sub-
shapes relative to a face position based on a selected divisor. There are three
options being; [edge, forward edge, and backward edge].
The following two examples show the parameters for two equal half stopes along strike
for a sectional orientation where U is along the primary horizontal strike-axis and V is
along the vertical axis. The first example uses the (a) integer divisor approach and the
second uses the (b) user defined fractional proportion approach.
Example 1
Divisors would be
unumber = 2 vnumber = 1
Example 2
More complex sub-stopes could be half of the section and half of the level spacing –
potentially forming 4 sub-stopes. Figure 2-26 depicts examples of situations with 2 sub-
stopes in both the strike (U-axis) and elevation (V-axis) directions for (1) a regular U|V
framework and also for (2) a regular U and irregular V framework.
Figure 2-26 Sub-Stopes for Regular and Irregular Vertical Frameworks Example
Regular U/2 & Regular V/2 Regular U/2 & Irregular V/2
V V
U U
0.5 0.5 0.5 0.5
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 44
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The sub-divisions to form sub-stopes may be regular divisors (e.g. 2 for halves, 3 for
thirds, 4 for quarters, 5 for fifths, etc.) or they can be variable divisors based on
fractional proportion (e.g. {0.3 and 0.7}, {0.2 and 0.4 and 0.4}, etc.)
The following set of values would create 3 sub-stopes with a full-stope height of 20m but
with varying strike lengths of 10m, 15m, and 25m based on a full-stope dimension of
50m strike by 20m height. This is achieved by using fractional proportions of 0.2, 0.3
and 0.5 for the U-axis, as illustrated in Figure 2-27.
Level
Height
The simplest sub-stope could be half-of either the section or level spacing (vertical
orientation framework) – potentially forming 2 sub-stopes (either in the strike direction or
in the vertical direction). Both sub-stopes could be produced, especially if the orebody
geometry is erratic but still carries acceptable grade within the full-stope interval.
Alternatively, either sub-stope could be produced, especially if the orebody extents or
mineralisation extents do not cover the full-stope extents (e.g. mineralisation that “falls-
short” of a level interval or strike interval).
Variable divisors (using fractional proportion) can be used to replicate repeating regular
patterns, such as for the Room-and-Pillar mining method layout (using a Horizontal
framework).
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 45
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The SSO can be visualised as working in sequence from top to bottom in Figure 2-28
until a successful stope-shape was found.
0
1
1 0
0 1
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 46
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The 2.7.6.1 Sub-Stopes (c) “automatic function” option enables irregular shapes to be
defined (e.g. the stope and drive shapes, or the primary and secondary stope-shapes)
and would be used without full shapes being specified. A number of automatic
configurations of sub-shapes can be supplied where the interval dimension is given on
the U or the V-axis (but not both at the same time), and where sub-shapes abut the
framework cell boundary. The largest sub-shape is chosen first. These automatic
methods have the goal of identifying how stope sub-shapes might be used to find a sub-
shape contiguous with an adjacent full shape (or sub-shape).
The following automatic function examples (depicted in Figure 2-29) assume the U
divisor number is 4 and the sub-shape dimensions are umin, umax, vmin, vmax.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 47
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
0 1 0 1 0 1
1 0 1 0 1 0
0 1 0 0
1 0
0 1
By default, sub-shapes are processed in the order supplied (either from a user supplied
list or an automatically generated list), and ore will be mined in the first economic sub-
shape encountered in the list. In the case where there are multiple orebody
lodes/lenses and potentially multiple stopes transversely across strike, if one lode/lens is
successful with a full stope, but not the others, the others will still be considered for sub-
stopes.
With overlapping sub-shapes it is logical to supply the largest first, otherwise a smaller
sub-shape may remove the opportunity to mine a larger shape in the same position.
The sequential order of evaluation does not guarantee the best combination of sub-
shapes is found.
Note that the Stope Shape Optimiser does not check the combination of full-stopes and
sub-stopes simultaneously for the set that optimises the objective (grade / value /
calculated value). E.g. It could be the case that two solutions exist, one with a full-shape
and another with sub-shape(s). Even though the sub-shape solution may have a higher
grade/value/calculated value, the full-shape solution will always be generated as the
evaluation sequence terminates with the earliest solution found.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 48
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
0.6
Level
Height
(V)
0 0
Strike (U)
0 1
Sub-stope Optimisation evaluates all the sub-stopes, and finds the best combination of
non-overlapping sub-stopes. The processing time overhead should not be any higher
than evaluating a list of sub-stopes.
If a full stope-shape is included in the sub-shape list then optimisation can assess
whether a sub-stope captures more value than a full-stope (that is otherwise forced to
mine more included waste).
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 49
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Irregular U or V axes “pillars” can be defined by specifying the position co-ordinate and
size. Typical pillar examples are:
Coordinate Size
55500 10
55510 20
55530 10
55540 20
10 20 10 20
U
55500 55510 55530 55540 55560
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 50
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The seed-slice interval should typically be set to get a minimum of 3 to 5 intervals in the
minimum stope width.
If the slice interval is not an integer divisor then inaccuracies may occur at the seed
stage because the seed-shape and pillar shape can only be multiples of the seed-slice
intervals. If ore lenses are widely spaced, the choice of slice interval will be less critical.
However if the ore lenses are closely spaced and the optimal pillar width is close to the
minimum pillar width, then the choice of slice interval will be more critical. If there is a
single lens then the choice is less critical.
The number of seed-slice intervals across the orebody can be up to a maximum of 4096
in Version 3. The seed-slice generation process gets proportionately slower as the
number of slice intervals increases. Hence careful selection of seed-slice interval,
minimum stope width, minimum pillar width between stopes and dilution skin intervals is
required to not exceed this limit and/or to keep the processing time reasonable. The
maximum number of seed-slice intervals allowed is not constrained by the W dimension
of the framework, but it is constrained by the maximum distance along the tube (W-axis)
that would contain the slices.
In Error! Reference source not found., the results of using different seed-slice
intervals are illustrated where the orebody has 2 lenses and the lenses are either both
high grade, or a combination of high and marginal grade. In case (A) a1.0m interval is
modelled which is optimal for the stope and pillar geometry. In case (B) a 1.5m slice is
used and while a larger seed-shape must be modelled so that multiples of the interval
satisfy the stope and pillar geometry, two stopes are still generated. In case (C) the
lower grade lens does not meet cut-off for the larger seed-shape and only one seed-
shape is (incorrectly) found.. A slice interval of 1.5 is not an integer divisor, and hence
the seed-shapes chosen differ. If both seed-shapes remain economic then nothing is
lost because the seed-shapes will be refined in the annealing process, and both slice
intervals should return the same final stope-shapes. If the seed generation returned
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 51
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
only one seed-shape (because the other was found to be sub-economic) then a seed-
slice interval of 1.5 would have been a poor choice.
Figure 2-32 Influence of Slice Interval on Stope Seed-Shape and Pillar Geometry
HW
High High
Grade Pillar Grade
FW
2m 5m 1m 6m 2m 5m 1m
HW
FW
HW
High Marginal
Grade Grade
FW
3m 6.0m 1.5m
High Grade
Dilution Pillar Stope Seed-Shape
Marginal Grade
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 52
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
In the second example, if the lenses above cut-off were always greater than 11.25m (i.e.
9+1.5+0.75) apart, or the seed-shapes were further apart than 11.25m, then a choice of
1.0 would also suffice. If the dilutions were small, say 0.25m each and the seeds were
greater than 9.5m (i.e. 9+0.25+0.25) then using 0.25m as the seed-slice interval would
be the most accurate, but would add significant runtime overhead to seed generation.
If in doubt, then running a test area for a range of slice intervals would be sensible.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 53
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
If the ore lenses have different orientations across the orebody, then no single default
dip and strike would be satisfactory for generating slices for seed generation. This is
illustrated in Figure 2-33. A vertical slice is a compromise orientation but for the right-
hand lens, sampling the orebody with vertical slices yields sub-economic slices because
of the waste carried, so no seed-shape is generated, and consequently no stope-shape
is generated. If a Stope Control Surface that is roughly oriented to the expected stope-
shape is added (as indicated by the red lines on the section), then the slices carry little
waste. The slices will be economic and a seed-shape will be generated for both lenses.
Note that the seed-shape includes the hangingwall and footwall dilution parameters.
Stope Stope
Seed-Shape Seed-Shape
Successful Failed
2m 5m 1m 2m 5m 1m
Wireframe control
Stope Stope
Seed-Shape Seed-Shape
Successful Successful
2m 5m 1m 2m 5m 1m
Control surfaces are best as open surfaces, as a closed surface will have triangles that
close the shape but do not reflect the stope wall orientation. A closed surface might be
the geological wireframe but you have to be careful, especially if there are sharp twists
and bumps that do not reflect a good overall wall angle for stope design. SSO does do
some smoothing to try and avoid this problem but it may not be enough. If the control
surface does not extend right along the extent of the orebody then the default values for
dip and strike will be used beyond the control surface.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 54
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Multiple surfaces are good for different orientations, and the dip angle is interpolated
between surfaces, but otherwise uses the outer surface dip for stopes beyond the outer
surface.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 55
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
W-axis
Smoothing: stope-shape
end-walls are “smoothed”
Strike angle change: the maximum when the gap is less than
relative angle between the stope-shape defined target e.g. this
top/bottom wall edges e.g. this example example <6m.
30 degrees. It typically represents
wall (hw/fw, near/far) “twist”.
Smoothing: stope-shape
>6m end-walls not “smoothed”
Top-edge of fw face.
when the gap is greater
Bottom-edge of fw face. than defined target
30 deg e.g. this example >6m.
45 deg
max
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 56
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The minimum mining width parameter is defined as distance in the horizontal plane
on the framework section along the W-axis (and consequently measures the apparent
width). If the orebody dip is moderate or the strike deviates from the framework axis,
then it would be appropriate to make a correction to the width specified to better
approximate the intended true width. As an example, if the minimum stope width in the
true-width dip-direction was intended to be 10m and the orebody was dipping at 45o,
then setting the minimum stope width to 14.1m (horizontal distance) would approximate
the intended minimum stope width. See Figure 2-35. Note that the true width is a
function of both strike and dip orientation in three dimensions for the general case.
Y(W)
If the stope wall angle ranges are the same for both the hangingwall and footwall, or roof
and floor, then the minimum stope width is checked at the stope corners.
If the stope wall angle ranges are different, then the minimum stope width is checked at
the wall centre, because the optimal seed-shape is measured at the wall centre, and the
annealing shape must be measured in the same manner to ensure that a feasible
annealing shape is available at the start of annealing.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 57
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The maximum mining width parameter is defined as distance in the horizontal plane
(in a similar manner to Figure 2-35) on the framework section along the W-axis (and
consequently measures the apparent width).
An example use for the maximum stope width is to restrict the transverse dimension for
geotechnical purposes (e.g. not to exceed the stable hydraulic radius for the crown face
or the strike-face walls).
There is also the option in post-processing to split the stope width into smaller intervals
without pillars (see Split 2.13.2). The maximum stope width should be interpreted as
maximum stope width between pillars. The post-processing approach is preferred over
the now discouraged approach of specifying a small (non-zero) pillar width, and a
maximum stope width equal to the interval sought, as was used with Version 1 by some
users.
Where the ore grade material is confined to a sharp boundary, surrounded by host rock
with zero grade the stope optimisation engine has no way to locate the stope walls
relative to that sharp boundary - all positions of the stope about the boundary have an
equal optimised value .
A way to resolve this issue is to (slightly) penalize the optimised stope value for those
waste cells that fall between the ore and the preferred wall position. If the ore is to be
centred in the stope then the penalty for one wall should be balanced by the penalty for
the other.
The penalty that is calculated is subtracted from the stope optimised value that
otherwise would be evaluated in the annealing phase but the penalty is not included in
the reported value for the stope. The penalty is calculated as tonnes by a supplied
penalty grade (or value).
waste threshold - a cutoff to identify "waste" for which a penalty should be calculated
waste threshold grade - a grade (or value) to be used in the penalty calculation for all
cells below the waste threshold. This parameter should be non-zero, or else the penalty
will have zero value. The penalty should not be so large that the subtraction of the
penalty renders the stope sub-economic. If the cutoff was 5.0 for example then the
waste threshold grade might be 2.0 (or even the full cutoff of 5.0 for a sharp boundary
on a high grade orebody) and the threshold grade of 0.5 (or higher if required to improve
the penalty to force the narrow ore effect).
position - the required position for the ore, with allowed values being
near|far|centre|roof|floor
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 58
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The technique has been termed "narrow ore" because this would be the primary
application, the width of the material above cutoff is typically less than the minimum
stope width. As shown in the figure below, if there is material below the cutoff, but above
the threshold, and this material falls within the economic stope then that material can be
considered part of the "narrow ore". Note that internal waste within a stope shape will
also be penalized.
Narrow ore processing requires a block model for the below waste threshold material to
be able to calculate the penalty. The penalty is calculated using approximate evaluation
techniques.
Dilution refers to material below cut-off grade that gets blended with ore, thus reducing
the grade of excavated material. Dilution in general is impossible to avoid in stoping due
to geometries of the orebodies and it is therefore divided into planned and unplanned
dilution. The annealed stope shape includes planned dilution which is the waste material
necessary to extract the ore. Unplanned dilution is material that originates outside the
stope boundaries. To factor in unplanned dilution that originates from outside the stope
boundaries from the HW/FW or Near/Far a dilution ELOS/Skin can be specified.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 59
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
A switch is provided to evaluate if dilution will make the stope shape uneconomic, and
only consider shapes that are economic with dilution. The default mode is to optimize
the undiluted shape and then add dilution, but with this control a smaller undiluted
shape will be produced and the dilution will include more above cutoff material.
A pillar will separate seed-shapes or stope-shapes if the maximum stope width would
otherwise be exceeded, or low grade/waste can be isolated from stope shapes.
If the stope wall angle ranges are the same for both the hangingwall and footwall, or roof
and floor, then the minimum pillar width is checked at each corner. If the stope wall
angle ranges are different, then the minimum pillar width is checked at the wall centre.
Note that the pillar width parameter is defined as the distance in the horizontal plane
i.e. the apparent pillar width (in a similar manner to Figure 2-35).
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 60
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The strike angle is the angle of any one of the four stope wall edges (measured relative
to the U axis of the stope orientation plane).
Ideally the strike angles would be loosely defined (i.e. using broad tolerance range) in a
preliminary test SSO run in order to give a reasonable upper limit on the number of
stopes produced or to maximise the stope dimensions. The strike angle parameters
would then be progressively refined as required.
Another example would be the formation of stope-shapes that have rapid or chaotic
changes in wall angles, giving the appearance of being “malformed” (but are actually
not).
The following sub-sections describe the strike angle parameters in more detail.
This defines the strike angle range of either edge (i.e. top or bottom) of either wall of the
stope-shape (i.e. near/far wall or hangingwall/footwall wall) relative to the framework’s
strike axis (i.e. the U-axis). The range can be independently defined as positive and/or
negative relative to the stope shape framework strike axis.
Controls the parallelism tolerance of the near and far edges. The edges are tested
independently at the top and bottom i.e. bottom near vs bottom far and top near vs top
far. The skew between the top and bottom of a stope shape is controlled with maximum
dip angle change.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 61
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The ratio is defined by the end-face wall lengths and the axis direction pairing being
considered, described further in the following sub-sections.
Ideally the side length ratios would be loosely defined (broad range) on a preliminary
SSO run to maximise the number of stopes produced or to maximise the stope
dimensions. The side length ratios would then be progressively refined as required.
An example use of the side length ratio is to force walls (i.e. near/far walls or
hangingwall/footwall walls) to be parallel to each other (i.e. a sectional parallelogram) so
that all production hole drilling is parallel for a narrow tabular orebody. This is achieved
by using a 1:1 ratio, but this ratio should only be used in a final run to ensure that all the
required shapes are generated in the annealing phase. Likewise, in the U-axis direction
plan view parallelograms can also be specified.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 62
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Top Face
U
Bottom Face
W
The upper limit for the ratio (longer/shorter) of the front and back edges of the top and
bottom face of a stope-shape as defined in Figure 2-40.
V Back Face
Front Face U
The maximum waste fraction of stope-shapes can be defined (i.e. proportion of rock with
mineralisation values below specified cut-off included within the stope-shape).
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 63
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The exclusion control can be used to avoid the creation of stope-shapes within say
deleterious-processing material or in poor rock-mass zones as a few examples of its
use. The material in the model is flagged with a (numeric or alphanumeric) field and a
value.
Up to two exclusion fields can be defined in a run. Each exclusion field permits a certain
maximum tolerance of inclusion within a stope-shape.
The exclusion control is defined as the maximum fractional proportion of material (by
volume) in the stope-shape that is flagged as either “exclusion1” or “exclusion2”
material.
The tolerance for each exclusion field “exclusion1” and “exclusion2” is set
independently, and allows for a maximum fractional proportion of the respective
exclusion material to be incorporated into the stope-shape. As an example, you may be
mining a secondary pillar stope and the shape of the adjacent primary backfilled stopes
may bulge into the secondary, so for practical purposes you may allow say up to 5%
(0.05 fraction) of backfill material within the secondary stope-shape.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 64
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
All angle values are specified in degrees. Angles are defined relative to the selected
framework orientation (i.e. XZ|YZ|XY|YX). Table 2.6 summarises the permitted values.
For rotated stope-shape frameworks the strike and dip parameters are measured in the
local co-ordinate system
The Strike angle conventions are the same for the various Slice frameworks (i.e.
XZ|YZ|XY|YX). Strike is measured positive clockwise from the primary strike-axis (U-
axis positive direction) of the selected stope-framework orientation/plane (i.e. 0 degrees
= looking along the strike-axis in the positive co-ordinate direction, +90 degrees =
looking clockwise at right-angles from the positive strike-axis plane, -90 degrees =
looking anti-clockwise at right-angles from the positive strike-axis plane). The strike
angle range is [-90 to + 90] degrees.
The Dip angle for XZ|YZ frameworks is measured as 0 degrees from the left-hand-side
horizontal axis as you look along the primary strike-axis (U-axis) and increases
anticlockwise to +90 degrees vertically down and +180 for the right-hand-side horizontal
axis. The dip angle range is [0 to 180] degrees.
The dip angle for XY|YX frameworks is measured positive downwards from the
horizontal (and negative upwards) on both the primary axes (the first axis in XY|YX
orientation i.e. U-axis) and the secondary axes (the second axis in XY|YX orientation i.e.
V-axis) and are termed the ‘strike dip’ angle, and the ‘transverse dip’ angle respectively.
The dip angle range is [-90 (upwards) to +90 (downward)] degrees.
Dip
[0..+180] [-90..0..+90]
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 65
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Strike and dip convention examples are illustrated in Figure 2-41 to Figure 2-50 for each
framework orientation.
-90
30o
+90
Orebody
-25o
X(U)
Shape Framework
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 66
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Y(U)
-90 +90
Orebody
50o
30o
Shape Framework
X(W)
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 67
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
-20O
Y’ (W)
12 O
Orebody
X’ (U)
-15o
180
Z(V)
90
85o
130o
X(U)
Y(W)
Transverse Direction
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 68
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
180
Z(V) 0
90
Y(U) 100 o
110o
X(W)
Transverse Direction
180
90
Z(V)
90o
100o
Y(W)
X(U)
Transverse Direction
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 69
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
90
Z(V)
120o
90o
X(W)
Y(U)
Transverse Direction
-90
+90 -90
Z(W)
0
Y(U)
-15o
+90
-25o Transverse Direction
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 70
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
-90
0
-90
Z(W)
0
+90
Transverse Direction
+90
25o -25o X(U)
Y(V)
Strike Dip Angle
Transverse Dip Angle
180
Z’ (V)
90
110o
Y’ (W) X’ (U)
Y -15o
X
Z
Transverse Direction
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 71
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The True specification method is added in Version 3 to allow stope width and dip angles
to be specified in a plane perpendicular to the stope strike, and independent of the
Framework rotation, and Stope Orientation Plane.
Angles for dip and strike are specified as true dip (TRDIP), and true dip direction
(TRDIPDIR) respectively. TRDIPDIR ranges [0..360] and TRDIP normally ranges [0..90]
in geological applications. The strike direction is found by adding 90 degrees to the
bearing of TRDIPDIR.
These angles have the angle conventions that the Datamine Dynamic Anisotropy
modelling functions provide in the TRDIP and TRDIPDIR fields, with dip measured
positive downwards, and the dip direction measured as a clockwise bearing, with north
being zero degrees.
When specifying the stope dip angles, the dip range is extended to [0..180] because a
single true dip direction is specified for vertical plane in which the stope dip angles are
measured.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 72
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Dip Direction
105 75
Orebody
Stope walls are referred to as the near or far, and hangingwall or footwall sides for
XZ|YZ oriented stopes and roof or floor sides for XY|YX oriented stopes.
Equal - using the same angle range for both walls (e.g. 45-90o).
Different – using independent angle ranges for each wall. For example, this
allows setting say a minimum rill dip for the footwall side (e.g. 45-90o) and
allowing a flatter minimum dip for the hangingwall side (e.g. 30-90o) – a typical
requirement for flat-dipping orebodies.
Note that the default dip value for seed-slices cannot fall outside of the near wall and far
wall (hangingwall and footwall) range. This requirement also applies to the default strike
angle and the strike angle range.
It is possible for the hangingwall and footwall to tip over and back again over the vertical
extent of an orebody. This behaviour is typical of “banana-shaped” lodes (viewed as a
vertical transverse section). The geometric-dip orientation defines whether it is the
hangingwall or the footwall.
The stope wall-angles, dilution intervals and structure orientation are variable using the
geometric hangingwall and geometric footwall dip orientation definitions in the geometric
case.
In the Geological case, the overall hangingwall and footwall sides are fixed over the
vertical extent of the orebody. The stope wall angles, dilution interval and structure
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 73
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
orientation are constant “geological hangingwall” side and constant “geological footwall”
side using Geological case definitions.
The Geological definitions are near for the lower co-ordinate and far for the higher co-
ordinate, along the W-axis relative to the stope shape framework origin in the local
coordinate system.
The geological and geometric stope-shape wall definitions for vertical frameworks are
depicted in Figure 2-53.
Orebody
Z(V)
Y(W)
X(U)
(0,0,0)
Geologic = NEAR / FAR (Global)
Geometric = Footwall / Hangingwall (Local)
The geological (global) and geometric (local) stope-shape wall definitions for horizontal
frameworks are depicted in Figure 2-54.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 74
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The structure function results in the stope-shape either snapping-to the structure
surface (e.g. include “waste” that would “normally” fall into the stope-void due to the
presence of the structure) or standing-off from the structure surface (e.g. leaving a skin
of “ore” against the structure for dilution control i.e. ore loss). The Stope Shape
Optimiser assesses both options in generating the seed-shape, and applies the same
rules to the annealed shape. If the snapping-to shape is sub-economic, then the Stope
Shape Optimiser will still consider the “standing-off” option. This will depend upon the
relative position of mineralised material and the structure surface.
Where a stope-shape wall corner falls within a nominated minimum distance of the
structure wireframe, the stope projects the stope-shape to that structure surface. If one
or more corners are within the minimum distance, the remaining corners are tested
against the maximum distance.
The stope wall is snapped-to the structure position if it falls within the set criteria
(minimum - target, maximum - range). This can result in a dip angle that is flatter or
steeper than set in the stope geometry parameters.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 75
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Where snapping to the structure wireframe causes angle tests to fail, these stopes
would not be output unless the “output_subeconomic_stopes” parameter is set. Stopes
that do not meet the stope geometry settings are reported as a failed stope (i.e. with
RESULT=0).
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 76
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
1. Before processing
Annealed Stopes
(Optimised Stopes)
Structure
2. First Pass
Gap between
stope shape and
structure greater
than that specified
for first pass
3. Second Pass
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 77
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
2m
V V V
W W W
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 78
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
2.12Shape Refinement
In Version 3, the stope geometry is no longer restricted to 4 point outlines. Either 4, 6 or
8 point outlines are available. The number of points is specified by defining the number
of points on each wall, being either 2, 3 or 4 points. For the Version 3 release the
outlines are restricted to 2+2 (=4), 3+3 (=6) or 4+4 (=8) points. Future releases will
allow other combinations eg 2+3, 2+4 etc.
2.12.1 Vertical
The position of the additional points is defined relative to the original 4 points. The
position is defined by a vertical range, as shown in the diagram, where a range fraction
of 0.2-0.8 is depicted.
A special case where a zero range fraction interval is specified and recognized in the
annealing process is the 6 point shape where the additional points are constrained to
the mid-height by specifying the range 0.5-0.5.
The lateral position of the points can be constrained relative to a line joining the stope
corners (see dotted lines). The lateral position can be constrained to an outwards limit
(the "convex" distance), and/or to an inwards limit (the "concave" distance). In this way
each wall (near, far, hangingwall or footwall) can be constrained to be either concave
only, convex only, or any position in between a convex/concave limit. A straight wall
would logically be specified with a 2 point wall, but until this is available, the
concave/convex distance can be specified as a small non-zero value to restrict the
lateral movement. The "convex" and "concave" distances cannot both be zero.
In the seed generation phase, no lateral or vertical adjustment is made to the additional
points so the seed shape remains effectively a 4 point shape. This means that more
complex shapes can be generated in the annealing phase, but no stope will produced if
an economic 4 point seed shape cannot be found. In this release the number of stopes
for a 6 or 8 point outline run cannot exceed the number of stopes found for an equivalent
4 point outline run. Future releases will have seed shapes with matching number of
points to the selected annealed shape to allow improved and more complex seed
shapes that would honour non-linear ore boundaries between levels.
The stope (and pillar) widths are evaluated at each vertex on the stope outline using a
horizontal projection to the opposite wall.
As with 4 point outlines it is possible to test the ratio of the stope widths at the additional
vertices against the top-bottom widths, and also the ratio of front-back widths.
The dip angle tests continue to be applied on the stope corners, but also to all the
triangles on the walls of the stope shape.
All of these tests are available to constrain the stope geometry to achieve a feasible
stope shape. Additional tests can be added in future releases as further experience is
gained.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 79
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
2.12.2 Horizontal
The horizontal case can be depicted by rotating the diagram by +90 degrees with the
Near wall then being the floor and the Far wall being the roof.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 80
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The three new sets of parameters included to control the allowable stope shape are:
Choose combinations of parameters that are consistent both at the seed stage, and at
the annealing stage. For example the Middle Length Ratio should probably have a
value similar to the Side Length Ratio, or exceed it. If the Ratio tests are not needed to
constrain the stope shape then use a large value eg 10.0. Always do test runs with
parameters that are loose, check the log file for failed stopes, and then tighten the
parameters to that required to produce the expected final design shape
2.13Post-Processing Options
The following post-processing options are only applicable to the SLICE METHOD
(section 2), and for Version 3 are only available for 4 point outlines. The options are
NOT available for 6-8 point outlines.
2.13.1 Smooth
The stope-shapes from the SSO are optimised on a tube-by-tube basis independently,
and consequently, the abutting stope walls will typically not match exactly in position.
This may be ideal for abutting stopes that can be mined independently of each other
(e.g. primary and secondary long-hole stopes) but commonly this does not occur for
geotechnical reasons and/or for the mining method practicalities. A typical example
would be a continuous retreat long-hole benching mining method.
Smoothing is an additional step using the same annealing algorithms. This optimises the
shapes not just in a single tube, but taking into account the adjacent tubes. The “gaps”
between the corners of adjacent stope-shapes will be eliminated / minimised from one
tube to the next in order to:
Create a smooth transition vertically (V-axis) and/or horizontally (U-axis) for
vertical framework orientations, or
Create a smooth transition in the U and/or V axes for the roof/floor for horizontal
framework orientations.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 81
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Smoothing does not “average”. It first tries to minimise the gap while maintaining each
of the user supplied stope geometry constraints. For example, if your stope-wall dip
range was tight, then it may not necessarily “close the gap” if the dip limit was violated.
It cannot make an economic stope sub-economic. It then tries to improve the value of
the resultant stope-shapes without significantly increasing the gaps. So in some runs,
only portions of the stope wireframes may be smoothed. Any gaps between stopes that
are greater than the maximum allowable tolerance will not be changed. Gaps below the
maximum may be partially or completely reduced to zero gaps.
Sub-stope corners are adjusted at the corners adjacent to a full-stope corner, however
sub-stopes are not smoothed with other sub-stopes.
Prior to smoothing the gaps are analysed and stopes with more gaps to adjacent stopes
and sub-stopes are processed first. i.e. stopes at the centre of the orebody are likely to
be smoothed first and stopes at the extremities will be smoothed last. All tubes are
processed in sequence in the first pass. As each tube is smoothed, up to 8 other
adjacent tubes (with stopes or sub-stopes) will be adjusted. The complexity of the
annealing in this additional step can be an order of magnitude greater, and consequently
the smoothing run can often take 5-10 times longer than an unsmoothed run, and
sometimes more, particularly if there are multiple lenses or parallel orebodies.
The first pass is usually enough to give a good result. There are no parameters to
control the time spent on the first pass. Any additional passes are optional, and under
user control. The parameters to control additional runs are either by number of passes
or by time limit (in hours).
Smoothing can be controlled by either comparing the "gaps" between stope corners, or
alternatively the "ratio" of stope edges. The first method has been found to be the most
effective.
An example of the smoothing function is illustrated in Figure 2-59. This is plan view
where the original stope-shapes (grey) are smoothed (red).
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 82
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
2.13.2 Split
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 83
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Split from hangingwall with the final split adjusted to tolerance settings.
Split from footwall with the final split adjusted to tolerance settings.
Vertical or angled internal split walls. The internal walls are either split vertically
or proportionally parallel to the near/far or hangingwall/footwall walls.
Vertical or angled end walls (at the W-axis extremities).
Examples of various split cases are depicted in Figure 2-60 and Figure 2-61. Figure 2-
60 shows plan view examples for an orthogonal framework with regular section spacing.
Figure 2-61 shows “split_equal” result in plan and section view for a rotated framework
with irregular section spacing.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 84
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Figure 2-60 Split from HW, Split from Centre and Split Equal
HW Side
Figure 2-61 Split Equal Applied to Rotated Framework with Irregular Section
Spacing using Sub-Stope Function
A’ Split Equal
Split Equal
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 85
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
2.13.3 Merge
The “merge” function is only applicable for full-stope runs created with SSO Version 2 or
later.
Details of the two available merge options follow. Note that after applying a merge
option, the QUAD number remains the same as prior to the merge. The stope name and
stope number are changed to reflect the agglomerated stopes.
A grid interval, being a multiple of the full stope dimension in the U-axis or V-axis
direction, is selected where the framework U or V origin provides the reference “U” or
"V" value.
With the “grid” interval option, the interval is the grid spacing with stopes grouped to be
aligned on a grid. This is useful if merged (grouped) stopes must be aligned from level-
to-level or section-to-section. The “grid” option requires stopes to be bounded by grid
lines (unless the remaining pieces can be attached within the stope strike-length
min/max range for U or stope height min/max range for V).
The maximum length for the grid option must be less than twice the grid interval.
For the “interval” option, the interval is not constrained to be on a grid. i.e. shapes will
be grouped level by level but not conforming to a grid spacing, just to achieve the target
interval. The “interval” option aims to group the stopes at the interval size (regardless of
the grid position), but otherwise still work within the min/max stope strike-length limits.
With regards to minimum and maximum merge lengths, a whole integer multiple makes
good sense as no other outputs can be generated. For example if you have 5m stopes
and you want to group into 15m stopes, your only options are 5m, 10m, 15m for
minimum, and 15m, 20m, 25m for maximum. If you want the most stopes output you
would have minimum of 5 and maximum of 25 to pick up all the pieces that do not form
full 15m aggregations.
Figure 2-62Figure 2-62 depicts 10m strike-length full stopes, with examples of the grid
and interval merge approaches.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 86
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 87
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Use this in situations where you would want to mine sub-stopes that are adjacent to full
stopes in the W-axis (where the normal practice is to require a pillar). An example of this
function is depicted in Figure 2-63.
Figure 2-63 “Do Not Force a Pillar between the Full-stope and Sub-stope” Example
In the Split post-process operation, there are no pillars between split stopes, but at the
end of a split sequence the pillar is still required. This switch removes the latter
requirement, much like the previous switch.
The complexity and hence the runtime for annealing can increase dramatically when
many lenses are optimised concurrently in the transverse direction. This option allows
the annealing to be decomposed into a number of smaller annealing steps if a
separation distance can be specified. Seed-shapes that are further apart than this
separation distance are annealed independently from others groups of seeds. It is
important to note that the pillar width separation test is only enforced within each subset
of seed-shapes, so the separation distance should exceed the minimum pillar width.
If expanding the seed-shape to the structure surface makes the seed-shape sub-
economic, you don't otherwise know where a potential stope might have been (unless
you do a full run without structure post-processing), so this restricts the expand-to-
structure test to only the anneal phase.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 88
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 89
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The Stope Shape Optimiser provides a tool to produce optimal stope-shapes, with
careful selection of parameters, in a rapid and repeatable fashion. The procedure is not
fully automatic and sensible selection of parameters and controls will assist to improve
the quality of results for complex situations.
A quick summary is provided here and then more detailed guidelines and examples are
provided on specific topics:
Check the model to ensure that missing or absent data is identified and appropriate
defaults are set. A default of zero for a value field is probably not appropriate because
the missing blocks or values are probably intended to be treated as waste (e.g. have
negative values due to processing cost). Flag areas in the model where stopes should
not be optimised e.g. near the surface, close to infrastructure or in poor geotechnical
ground. Use model fields like oretype or resource category to allow later classification
of stopes.
Processing a model with waste cells adds a significant overhead, but this is necessary if
creating full-stopes and sub-stopes. Remove barren waste cells from the input model if
only full-stopes are required.
(2) Framework
For a first run use a restricted framework size on a small test area to verify parameter
selections are appropriate, and that the results generated are those expected.
Alternatively use the full framework but select an (x,y,z) coordinate as a validation test
cell so that only one quad is optimised, or perhaps select several (x,y,z) coordinates to
test several areas. Using a cut down model will also speed up this initial testing.
Always do a visual check when using rotated frameworks. In particular verify that the
framework extent and orientation are the expected ones and that the framework extends
beyond all the mineralisation.
Compare results with manual designs, or have other methods for checking the outputs,
especially when there is a lack of familiarity with the data. It is too easy to do
optimisation work on computers. The modern day challenge is to have techniques to
"prove" that the optimised result is correct.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 90
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
There are many new features for adding controls and fine-tuning the stope optimisation
process. The first run should have the simplest setup. These should then be followed
with more detailed optimisation runs, where functions are added incrementally to
understand the implications of each change (e.g. maximum waste inclusion).
For example prior to doing a design with gradients on the levels, do a run with fixed
sublevels.
Don't do post-processing (smooth, split and merge) on the first run. Smoothing typically
improves the look of the result, but doesn’t significantly affect the overall tonnages that
are optimised.
The Stope Shape Optimiser will only produce stope-shapes if seed-shapes are created.
Seed-shapes define the number and approximate location of stope-shapes. A Stope
Control Surface is used to locally define the strike and dip orientation of the stope-
shapes for the mineralised economic component of the orebody.
Seed-shapes are formed by aggregating seed-slices to model the stope width, pillar
width and dilution. The choice of slice interval will affect the accuracy of the seed-
shape optimisation.
While a geological wireframe can be a good proxy for the Stope Control Surface, in
some cases these wireframes can be large, or have local inflections that can confuse
the Stope Shape Optimiser when generating slices. The geological wireframe may be
well understood by the geologist but should not automatically be adopted by the mining
engineer. It is better to digitise a set of strings section by section to define the local dip,
and create one or more wireframe surfaces. Make sure that these surface(s) extend
past the mineralised zone. One technique for reducing the number of triangles is to use
a “decimate” wireframe function in the Vendor environment.
A Stope Control Surface should be considered mandatory for all but the simplest
orebodies.
The Stope Control Surface need only have a few thousand triangles, and certainly not
20-100,000 triangles.
A stope slice interval where the minimum stope width is 3-5 times the slice interval is
usually a good guide.
The dip and strike orientation taken from the Stope Control Surface, or the Default Dip
and Default Strike parameters, must fall within the minimum and maximum dip and
strike ranges set for the stope geometry.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 91
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
In almost all cases the model discretisation plane and the stope orientation plane for the
framework will be identical, but this is not the case if the rotations for model and stope-
shape framework are different. Beware the case where one is rotated by 90 degrees
relative to the other so that the axes look to be parallel but the XZ plane of one is the YZ
plane of the other.
A good rule for model discretisation number (in U and V) is that the number is twice the
number of sub-stope intervals. The goal is to ensure that there are a minimum of two
discretised cell centres in U and V for each stope or sub-stope shape. The default of
4x4 is suitable for regular sub-stope splits of 2x2. If the model discretisation number is
too small, a more suitable choice will be automatically assigned and noted in the log file.
In the first pass, nominate broad tolerance ranges for dip and strike of stope walls,
and the geometric ratios of end wall or roof/floor dimensions. If the final strike limits are
+/-10 degrees, then still consider a first run with a wider tolerance, even +/-45 deg. This
will typically generate the maximum tonnage and then these values can be tightened up
if this is appropriate for the stoping method. Beware of setting tight dip and strike
ranges if there is a lot of local variability in the orebody dip and strike.
In the second and subsequent runs tighten the tolerance ranges and parameters.
The tighter the stope geometry constraints, the more complex and slower will be the
optimisation. If the side length ratios are set to one to generate parallel sides this can
be a very severe constraint for the optimisation. Do several runs with diminishing side
length ratios to check if stopes are lost, and establish the threshold where stope-shapes
begin to disappear.
Because the Stope Shape Optimiser works off the Block Model, the sub-cell modelling
and its approximation to wireframe surfaces will be a key determinant in the quality of
the output stope-shapes and also the accuracy of the resultant tonnes and grade.
Different mining software packages have different capabilities and approximations in
sub-cell modelling. A full cell model with percentages for the mineralised fraction cannot
be used with the Stope Shape Optimiser - overlay a sub-cell model to model these
fractions and derive the spatial position.
Engineers often align stope sections to the axis of the orebody, but geologists do not
have the same expectation. This will mean that the stope-shape framework will often be
rotated to the block model. For a first pass an un-rotated stope-shape framework should
yield a similar result to a rotated one, with small discrepancies at the end of ore zones.
The Stope Shape Optimiser has three evaluation modes (“Fast”, “Precise” and “Fast
with Precise reporting”). The “Fast” and “Precise” methods will generally yield different
results. The “Fast” method is typically quicker, and it is often more accurate because it
tends to adapt well to the sub-cell approximations in the block model. While the
tonnages will be very similar, the metal content can vary between the two methods by 5-
10%. Significant differences between "Fast" and "Precise" methods will be
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 92
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
reported in the runtime log file for grade, tonnes and metal. The differences are
more exaggerated in narrow orebodies.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 93
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
First check the log file (after running with the verbose output option) to look for
reasons as to why the stope failed or was rejected. Missing stopes might be more likely
for narrower orebodies.
2.15.1 Discretisation
A key consideration regarding discretisation is the cell filling plane. If the cell filling plane
is not generally aligned with the orebody strike then there is potential for anomalous
results to occur. This is particularly true if the cell dimensions are disproportionately
larger in the fill plane (i.e. at right angles to fill plane) when compared to the orebody
width direction.
A case example where tall cell columns represent the orebody geology is illustrated in
Figure 2-64. If the default discretisation parameters are used (4x4) then depending on
the evaluation method applied, Fast Evaluation or Precise Evaluation, the outcomes can
be significantly different. The issue for Fast Evaluation, in this case example, is the
influence each cell column has as the cell’s centroid falls within or outside of the stope-
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 94
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
shape during annealing. The best result would be obtained if subcells are orientated
horizontally, not vertically, for this case.
The easiest, most intuitive and most accurate method of specifying the strike and dip
angles for the initial stope-seed-shapes is to provide a Stope Control Surface wireframe
over the full extent of the orebody where stope-shapes are to be generated. The Stope
Control Surface has priority over the default dip and strike (Vertical XZ|YZ, Section
XZ|YZ) and default strike-dip and transverse-dip (Horizontal XY|YX) angles. Note that
vendor software can generally display the true-dip and strike of the Stope Control
Surface if required to better understand the dip and strike orientations of the Stope
Control Surface.
Stope Control Surfaces can typically use the geology surfaces depending on complexity.
If the surface is overly complex with reversal of dip and/or strike orientations over short
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 95
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
distances the localised surface orientation may be at odds with the practical stope
orientation and hence seed orientation. It is generally good practice to decimate the
surface to simplify it. An excellent alternative is to generate the wireframe from widely
spaced sectional strings that are oriented to the expected stope orientation.
Multiple control surfaces are possible as the slice-seed is interpolated between the two
surfaces. For example, if one surface is at 60 degrees and the other is at 50 degrees - a
slice-seed surface midway between the 2 surfaces would assume 55 degrees and as it
got closer to the 60 degree surface it would approach 60 degrees and vice versa for the
50 degree surface. Outside of the 50 degree surface the seed-slice orientation would be
50 degrees and likewise for the 60 degree surface.
Crossover of control surfaces will have the same function as for separate sub-parallel
control surfaces. However, always remember to check the end result.
Each string type can be uniquely coloured. Note that strings are not produced for the
verification files.
2.15.4.1 Stopes
The Stope Shape Optimiser creates wireframe shapes from two 4-point cross section
strings. Because the wall faces are not planar, an additional point is introduced on the
walls at the centre of the wall using bilinear interpolation (effectively an average of the 4
wall corner points). If one intermediate cross-section is output for each stope-shape,
then this wireframing procedure can be replicated with vendor wireframing software.
Without this additional string (from Version 2) there can be a significant source of
reporting difference between SSO reports and reports from general mine planning
packages that only use the stope end walls for forming the stope wireframe.
It is possible to output and uniquely colour annealed shapes that failed to make it as a
stope (failed stope) due to not meeting cut-off or other geometric / exclusion criteria (e.g.
the stope head-grade fell below the cut-off after dilution skins were added). It is
sometimes very useful to identify the location (e.g. bridging low grade zones) and the
extent of “failed stopes” (e.g. failing due to excessive dilution) regarding setting of the
SSO parameters.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 96
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
These annealed shapes (i.e. stope seeds) will have the field record with “RESULT=0” in
the case log-file and the report results file. They are generally yellow in colour
(COLOUR=4) by default.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 97
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
2.15.4.2 Verification
The verification wireframe output is optional. It can output one or more of the following
types:
Seed-Slice (i.e. the slice intervals based on the default strike and dip or Stope
Control Surface),
Seed-Shape (i.e. the aggregated slices),
Failed Seed-Shape (i.e. aggregated slices that failed to meet stope criteria),
Undiluted_stope (i.e. the annealed stope-shape prior to skin dilutions),
Far dilution (i.e. the far side skin dilution shape for the Global definition case),
Near dilution (i.e. the near side skin dilution shape for the Global definition case),
Hangingwall dilution (i.e. the hangingwall side skin dilution shape for the Local
definition case),
Footwall dilution (i.e. the footwall side skin dilution shape for the Local definition
case).
By filtering, individual features can be extracted for further analysis; a good example of
this is evaluating the annealed stope-shape prior to the dilution skins. Each verification
wireframe type can be uniquely coloured.
The level gradient strings for sectional orientations are digitised in long section (i.e.
along the framework primary strike U-axis). They should be non-overlapping. They
should also intersect every pair of stope sections to locate a stope floor and roof.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 98
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
3 PRISM METHOD
3.1 General Stope-Shape Framework
The Prism method is a different style of stope optimisation to the Slice method. In the
Slice method the stope-shape framework is decomposed into individual geometric tubes
based on the level and section dimension for the Vertical case, and the stope-shape (or
sub-shape) is an optimisation over the width of the orebody, with a two stage process to
The Prism method also requires a stope-shape framework, but uses the decomposition
of the framework extents to define sub-problems. The framework extent is subdivided in
regular intervals, much like regular quadrilaterals, except that the subdivision is three
dimensional rather than two dimensional, and each subdivided volume is referred to as
a region, whereas the Slice method subdivision is two dimensional to form a tube.
Figure 3-1 summarises the stope framework hierarchical structure for the Prism method.
Stope-shapes are defined as a fixed set of shapes defined by the footprint and height,
and the optimisation problem is defined as identifying a combination of non-overlapping
stope-shapes from the set provided to maximise value or grade within each independent
region.
Although the geometric formulation of the problem is different, the same evaluation
options are available for cut-off, optimisation and reporting fields, inclusion/exclusion,
filters etc. as applies to the Slice method.
The solution to the optimisation problem requires a mixed integer solver, and three are
available:
Licences must be separately purchased from the mining software suppliers for
commercial solvers. It is important to remember that the Prism Method can create very
large and difficult optimisation problems. The solution strategy should be to solve a
coarse problem with minimal stope-shapes and decomposition of the framework,
followed by progressive refinement of the framework, stope set and parameters used.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 99
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
XZ orientation
Vertical YZ orientation
V
U
W
V
U
W
Footprint Defined
Fix X, Fix Y, Float Z
V
U
W
Level Defined
Fix Z, Float X, Float Y
V
U
W
Section Defined
Fix X, Float Y, Float Z Fix Y, Float X, Float Z
V V
U U
W W
V
U
W
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 100
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The full framework definition may contain several regions that may be independent or
contiguous abutments. This could be likened to a mine-site with mine sub-districts /
areas / zones. The framework region(s) however must be rectangular in shape. Regions
are user defined to make stoping geometric sense e.g. to span a group of levels or to
span a group of sections or to span a group of levels and sections. The library of stope-
volumes is applied to each region in turn with each region optimised independently. One
use of regions is to force stope-volumes to honour say a regular level spacing or a
regular section width (i.e. regular primary and secondary stopes).
The framework region(s) are further defined by regular grid increments in the X|Y|Z
axes. This allows stopes-volumes to position with the bottom left hand corner at any grid
increment, providing the stope-volume completely fits into the region. This gridding
provides a stope framework for “floating” stope-shape volumes within each framework
region.
Stopes from the library would typically have dimensions that are an integer multiple of
the grid increment, otherwise gaps would occur between adjacent stopes. The size of
the grid increments might in some cases be the minimum stope dimension.
As an example, using a region dimension of [100, 100, 250] (X|Y|Z), stope library
dimensions defined by [30, 40, 10] for X and Y axes (minimum, maximum and step size)
and [50,250,50] for the Z axis (minimum, maximum and step size) and a region grid
increment of [20, 20, 50] (X|Y|Z) the following stope combinations are possible.
The possible X or Y axis combinations are: 1x40 (starting at either 0, 20, 40 or 60 grid
interval in the region), 2x40 (starting at either 0/40, 0/60, 20/60 grid interval in the
region), 1x30 (starting at either 0, 20, 40, 60 grid interval in the region), 2x30 (starting at
either 0/40, 20/60 grid interval in the region), 3x30 (not possible due to 20 grid
increment), 2x30 plus 1x40 (not possible due to 20 increment) in either X or Y axis.
The possible Z axis combinations are: 1x250 (starting at 0 grid interval in the region),
1x200 (starting at either 0, 50 grid interval in the region), 1x150 (starting at either 0, 50,
100 grid interval in the region), 1x100 (starting at either 0, 50, 100, 150 grid interval in
the region), 2x100 (starting at 0/150 grid interval in the region), 1x50 (starting at either 0,
50, 100, 150, 200 grid interval in the region), 2x50 (starting at either 0/100, 0/150, 0/200,
50/150, 50/200, 100/200 grid interval in the region) and 3x50 (starting at 0, 100 and 200
grid intervals). Note that for the 2x100 case the 0/100 and 50/150 grid intervals starts
are made redundant by the 1x200 case with 0 or 50 grid interval starts. This is because
the set of largest stope-volumes is solved for.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 101
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Figure 3-2 illustrates the key aspects of the Prism Method for each of the different
cases:
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 102
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Figure 3-2 Prism – Total Framework, Region Increment and Grid Increment
Examples
U V
Plan View Section View
Single Region
Float shapes in X, Y, Z axes
V
U
W
W W
U V
Plan View Section View
Multiple Regions
Float shapes in X, Y, Z axes
V
U
W
W W
U V
Plan View Section View
Level Regions
Fix Z, Float X, Float Y
V
U
W
W W
U V
Plan View Section View
Section Regions
Fix X, Float Y, Float Z
V
U
W
W W
U V
Plan View Section View
Column Regions
Fix X, Fix Y, Float Z
V
U
W
W W
U V
Plan View Section View
Row-Level-Column Regions
Fix X, Fix Y, Fix Z
V
U
W
W W
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 103
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
3.3 Stope-shapes
The stope-shapes can be either:
Specification of default strike angle and dip angle are not needed in the Prism Method,
however, a framework orientation (i.e. XZ|YZ) is required to define the orientation of the
trough undercut.
The stope-shape sizes in the stope-shape library can be specified quickly by using the
minimum and maximum size and step increments for each axis, or the library can be
explicitly defined giving specific axis dimensions for each stope-shape as depicted in
Figure 3-3. The optimised shape combination can match the shape and position of
stopes from the stope-shape library to the ore outline to maximise ore extraction, and
total value.
Maximum size
Minimum size
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 104
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The two shape configurations are depicted in Figure 3-4, and illustrate the parameters
for the shaped prism trough-undercut stope-volume.
No Trough Trough in
Ore
Wall
angle
Undercut width
A variation on the shape refinement method allows the 4 points on the roof to be
annealed with the points constrained to a vertical path, and the intermediate points
between the stope corners constrained by a convex/concave distance.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 105
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
In the current implementation it is assumed that the seed shape must be economic, and
that the crown shape annealing can then improve the stope shape.
Runtimes will be significantly greater because each feasible shape must be subject to
the crown shape annealing, and then the best non-overlapping solution (based on the
seed shape limits) optimized.
To use approximate evaluation for the Crown anneal, the Stope Orientation Plane
should be either XY or YX for discretization in the horizontal plane.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 106
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Note that GLPK is no longer supported in the commercial version due to licensing
restrictions.
The CPLEX MIP solver provides faster processing and handles larger run-matrices.
CPLEX outperforms Gurobi for Prism optimisations in the current release.
The Prism strings produced are as depicted in Figure 3-6 and include:
the trough profile face strings (when the undercut trough option is enabled),
the section strings,
the intermediate section string(s) (when this option is enabled),
the floor string.
By default the position of stopes is only constrained by the framework extents, the
region boundaries (defined by the axis intervals) and the grid increment. The location of
sublevels is not automatically constrained, and this solution provides the first estimate of
the optimal set of stope dimensions to maximise value or metal. A visual inspection of
the solution might assist to identify optimal level locations.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 107
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The combination of stope-shapes that can be considered within each region can be
further constrained by forcing the sublevel locations to be applied in the solution. Using
these “common sublevel” options is described in the following sub-sections. Note that
solving with these additional options can result in an exponential increase in the problem
size, and long run times, even with a commercial solver. Note that the computer
operating system swap-space, paging file size or virtual memory may need to be
increased (to the available physical memory size) to prevent memory issues. Configure
the system with a large amount of physical memory (RAM) if possible, as this can
significantly improve runtime performance of the MIP solver.
This function anchors the stope floor levels to each region’s minimum Z value.
This function requires that all stopes honour the set of levels found in the optimisation
run (i.e. selects the best of feasible solutions). For example, a stope optimisation
solution where one stope is located at say 10m above a common-level (of say 40m)
shared by other stopes would not be feasible or allowed.
This function allows levels to vary within a region, but vertically over-lapping stopes
within a minimum horizontal separation distance must have the same floor level (i.e.
adjacent stopes that overlap in the vertical sense cannot have an offset in the floor,
although they can optionally be displaced from a regular grid in the X,Y space). The
effect is to cluster stopes into groups with each group having a shared set of sublevels.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 108
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 109
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
For small test runs, an individual region can be selected by defining the index to the
Region (like the QUAD number for Slice except that this index is a three dimensional
index). Alternatively a smaller test problem can be run by specifying one or more three
dimensional (x,y,z) coordinates which will be used to select the Region number that
encloses the point(s), and only the subset of feasible stope-shapes that enclose this
coordinate will be selected for the optimisation. While the latter is not automatically part
of a feasible solution to the full problem, the solution can be inspected and it is still a
useful verification that the Prism process has been formulated as expected.
Only stope-shapes that overlap with one or more of the coordinates will be processed
for the optimisation. Note however, that some options will require the full set of stope-
volume shapes to provide a meaningful optimisation, e.g. if applying the
“common_mine_sublevel” or “common_local_sublevel” options then the results are
meaningless without the full complement of possible stope-shapes.
All optimisation options as detailed in Section 3.8 are available in the Prism Method with
the following exceptions:
The most common difficulty will be that the run times are too long, or the run does not
finish. The complexity of the optimisation problem is directly related to the number of
feasible stope-shapes that need to be considered, and how tightly they are grouped.
There can be a very large number of high value feasible solutions but finding the best
can involve a deep search of the solution space. The best may however be only a very
small improvement on many other solutions.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 110
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The LP_SOLVE solver can solve small test problems, but a commercial solver will be
required for large problems.
Reducing the region size or constraining the search to a subdivision of the space (by
section, level or column) can be very effective. This subdivision of the search space is
recommended because the solutions will be very fast.
Reducing the grid increment in each of the three dimensions can have a dramatic effect
on the problem size. The initial grid increment could be the stope size on that axis to get
a quick run and then the grid increment could continue to be halved. If the stope
footprint was 20x20m then the first run might have an increment of 20m, then the next
10m then 5m, etc.
Often the MIP Solver can obtain a good solution quickly but continue the search with
little or no further improvement. These issues can be resolved with additional
optimisation parameters to set the time limit, integrality tolerance, solution gap tolerance
and the search strategy. To understand these advanced optimisation parameters
please consult the reference material for your preferred solver.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 111
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
(1) The stope-shape annealing algorithm, where the dimension of the stoping units
and sub-units relative to the model cells must be considered, and changes in the
wireframe shape must evaluate to a different volume to identify improvements in
stope value
(2) Maintaining an accurate volumetric estimate of material mined out in stoping
units and sub-units.
Model discretisation also has an influence on accuracy of grade and tonnage estimation,
particularly for the case when model and/or framework are rotated and the rotations are
different.
Discretisation ensures the model cell sizes are small enough to achieve the required
ray-trace density for annealing and evaluating the stope-shape, honouring pillar widths
(especially for sub-stopes) and allowing for the flagging of “mined-out” material. A
minimum of 2 ray-traces on both U and V axes (i.e. for strike and elevation in Vertical
cases) are required per stope or sub-stope shape to allow the annealing process to
identify changes in the stope volume.
The default discretisation setting is 4x4. This setting generally satisfies simple sub-stope
requirements (i.e. 2 vertically and 2 along strike to achieve a minimum of 2 ray-traces
per sub-stope shape). If there are only full-stopes, this parameter could be reduced to
2x2.
The discretisation setting must also take into account the full-stope and sub-stope
intervals as defined by irregular frameworks (i.e. such as irregular level spacing). The
maximum discretisation number is 40x40.
The discretisation number and dimension of the framework on the U and V axes
determines the maximum discretised cell size along U and V axes. Any cell with a
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 112
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
greater size is subdivided into equal intervals so that the discretised cell dimension does
not exceed the maximum. Note that this is not the same as superimposing a fixed grid
of the maximum discretised cell size over the model cells.
Figure 4-1 provides an example of discretisation when considering only a single axis.
The W axis is in the transverse direction and is not split (although when the mined out
model is output the subcells are split in the W direction at the intersection with the stope
wireframe boundaries using the "ray-trace" procedure).
Figure 4-2 highlights the approximations made with the Fast evaluation method when
the model and framework are orthogonal and the second case then model and
framework are not aligned. In the first case the discretised cells are clipped by the (U,V)
limits of the stope shape framework. For the second case the discretised cells are not
clipped, and a higher level of discretisation will yield a more accurate result on a stope
by stope basis, although the "ray-trace" evaluation method will always report material in
either the stope or its adjacent stope.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 113
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 114
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The cut-off grade can be supplied without the head-grade, but a head-grade cannot be
supplied without a cut-off grade.
The optimisation field can either be a grade field or a value field. If the optimisation field
is a value field then the optimisation objective is to maximise the total value of the stope
above the cut-off, and a stope value less than the cut-off would be sub-economic. It is
the maximisation of the profitability of the stope relative to the cut-off. If the optimisation
field is a grade field, then the equivalent objective is to maximise the total metal above
the cut-off.
There is also an optional function that can be applied to the cut-off only or cut-off with
head-grade to optimise total value or total metal while satisfying the cut-off or head-
grade. This function maximises recovery of metal (i.e. kg’s) or total dollar value (i.e. $’s)
and will attempt to recover all possible metal or dollar value while still meeting the
overall cut-off or cut-off with head-grade criteria for the stope. However, it does not
maximise the metal grade per tonne (i.e. gm/t) or value per tonne (i.e. $/t). This option is
likely to be desirable to users who value (i.e. rank) maximising metal recovery above
maximising head-grade. It could be used to answer the question "how many grams can
be mined at a profit" rather than "which grams to mine to maximise profit"
Figure 4-3 illustrates at a high-level the general cut-off, head-grade and optimised total
value / optimised total metal concepts. Intervals above (blue) and below (red) cut-off
identified, and the length of the interval relative to the minimum stope width
(<MMW,>MMW) and the minimum pillar width (MMPW,>MPW) are identified. The area
contributions above the cut-off (blue) have a positive contribution and the areas below
the cut-off (red) have a negative contribution, with the goal to have a net positive area
outcome.
A head-grade is specified in addition to the cut-off grade. Four different outcomes are
possible for this data set:
Interval greater than cut-off grade with optimise total value or total metal option
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 115
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Includes both "Maximised metal as long as >CO" and "Maximised metal as long
as >CO & >HG"
Interval greater than cut-off grade and head-grade with optimise total value or
total metal option
The right-most (blue) interval is above cut-off but is less than the minimum stope width,
and makes no net positive contribution when added to the interval to the left. It will only
be included in a stope if the optimise total value or total metal option is selected.
A fixed number (either as a grade per mass unit e.g. gm/t, or currency value per
mass unit e.g. $/t),
Values from the block model so that the value has a spatial property e.g. to vary
cut-off with depth (with a default value applied if the field value for a given cell is
‘absent’ or if cells are absent from the model),
A relationship between the value and some other variable related to the stope
dimension, specified as points on a curve e.g. the cut-off is a function of stope
width so that narrow stopes have a higher cut-off and wider stopes have a lower
cut-off This option allows the Optimiser to dynamically choose between bulk and
selective mining by making the cut-off and head-grade a function of the stope
size, and choosing the mining shapes that return maximum value.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 116
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Note that where a grade field is supplied, a Calculated Value can be computed taking
into account commodity price, mining and processing costs, mining and process
recoveries, and royalty. The calculated value uses the formula:
Thick, Mass, Height and Area all relate to the stope size or dimension. Apart from mass,
one would expect the other dimensions of the stope (other than the one selected) to be
roughly constant. Mining cost can then be related to Hydraulic Radius (the ratio of area
and perimeter) and hence the cut-off can be used as a proxy to quickly establish
whether larger or smaller stopes are better in the optimisation.
e.g. If the primary dimension controlling the cost is the stope width, (which may vary
according to orebody width, the number of lenses and included waste proportion), then
this method of dynamically specifying the cut-off variable will allow the best stope width
to be chosen on a local area basis, per level and section - as a function of cost.
The cut-off or head-grade value is interpolated between the curve points supplied, and
otherwise uses the minimum or maximum curve point values if the dimension falls
outside the values supplied. Note that the cut-off or head-grade value to be used as a
discriminator is assigned in the seed generation stage, based on the seed-shape.
Therefore the final stope dimension may not exactly match the defined relationship after
annealing.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 117
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
This is the method used traditionally in mine planning software where an exact
geometric (or Boolean) intersection of cells overlapping with the stope wireframe
is made. This is termed “wireframe-cell-evaluation” (and has been labelled
"Exact" or "Precise" in various contexts).
A faster method designed for (discretised) sub-cell block models has been
implemented using ray-tracing techniques. This is termed “cell-centreline-
evaluation” (and has been labelled "Approximate" or "Fast" in various contexts).
Note that the results are not indicative of the name used (“Approximate”) but
rather of the volume calculation technique applied.
The method uses a ray-trace through the sub-cell centroid (along the Model
Discretisation Plane W-axis) to intersect the wireframe shape, and calculate the
portion of the sub-cell (from the trace) that falls within the wireframe shape. The
volume is obtained by multiple that portion (on the W axis) by the fixed
dimension of the subcell on the other two (U,V) axes.
For Datamine Studio block models, the cell-centreline method is used in the
TRIFIL process to create sub-cell models within a wireframe. Using the same
cell-centreline for evaluation of stope wireframes means that the sub-cell
approximations are common between the original model creation procedure and
the stope evaluation technique in SSO. Hence geometric errors are minimised.
This is less the case if model cells are split in the discretisation procedure.
Where smaller sub-cells are used at the wireframe boundary, the better the
approximate method becomes at replicating the wireframe shape for the case of
sharp grade boundaries.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 118
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The volumes and tonnes for the “approximate” and “exact” methods are identical for a
constant model density (with small differences for variable density), but the contained
value or contained metal will be different. The "approximate" method will always report a
better grade/value for each stope. The differences can all be attributed to the sub-cell
approximations used in block modelling of 3D surfaces and shapes (volumes). Each
software vendor will have a different algorithm to produce the spatial distribution of
subcells to model a wireframe volume, so the differences will vary between software
vendors.
Both methods of evaluation are made available, but the runtimes can increase by a
factor of 5-10 for the “exact” method. The run-times for the "approximate" method will
also be slower for the case when the rotation angles for the block model and stope-
shape framework are different (due to the additional geometry calculations required).
Note also that increasing the number of sub-cells will reduce the sampling error at
boundaries, but this will be at the cost of significantly increasing the processing time
taken.
The runtimes for the "approximate" evaluation method are also dependent on the model
and framework orientation, as outlined in Section 4.1, and so in order of increasing
runtime the different methods are:
- "approximate" evaluation with model and framework not orthogonal, and no clipping
- "exact" evaluation where the runtime is the same for the orthogonal and non
orthogonal cases
While two methods are available for evaluation and annealing, three methods are
available for reporting.
Uses the Exact method for wireframe evaluation, and the same results for
reporting
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 119
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Uses the Approximate method for wireframe evaluation, and the same results for
reporting
Uses the Approximate method for wireframe evaluation, but re-evaluates the
final stope wireframes for reporting with the “Exact” method.
Note that for marginal stopes, the differences in exact and approximate
evaluation may result in a stope becoming sub-economic because the exact
evaluation can produce a more conservative result.
Care should be taken to ensure that the default value for the optimisation field is
realistic for ore-only block models.
Figure 4-4 indicates the source of the differences between "approximate" and "exact"
methods of evaluation and reporting. A narrow high grade orebody is modelled with two
subcells on the level, with the horizontal dimension dictated by the wireframe-cell
intersection at the mid-height. For this simple orebody geometry a stope shape could be
generated in the annealing procedure that matches the orebody wireframe. If using the
"approximate" ray tracing evaluation method to evaluate the stope grade, the proportion
of the two subcells that would be reported would be the full subcell, The stope grade
would be the average grade of the two subcells. The stope wireframe would match the
orebody wireframe, and the tonnes and grade of the stope would match the orebody, the
ideal result.
"Exact" evaluation for that same stope shape would intersect the stope shape with the
subcell volume, so that a portion of the subcell volume would fall outside the stope
shape (grade and metal lost), and portion of the stope shape would have no subcell, and
so a default waste grade would be applied to that volume (additional waste included).
The combined effect would be a stope with identical volume and tonnes (assuming
constant density for subcells and waste) but lower grade and metal content.
"Exact" evaluation also has an unexpected outcome. WIth the reported grade being
dependent of the proportion of the subcell inside the stope wireframe, and with the
objective of maximizing the stope value (or metal above cutoff for grade optimisation),
then "exact" optimisaqtion on a high grade orebody will tend to take all high grade
material, and so with "exact" optimisation in the extreme case the stope wireframe will
be the shape that extends to the limit of the subcell corners, taking additional waste.
This waste is however only an unintended consequence of rectangular (or cuboid)
subcell approximation, and the error reduces as subcell size is decreased.
Figure 4-4 also highlights the source of the differences in evaluation and reporting for
the three methods of reporting.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 120
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The differences found in Evaluation and Reporting highlight the need for better
understanding of the limitations of subcell approximations made in geological block
modeling, particularly for narrow high grade orebodies. Communication and sharing of
requirements for geological modeling and stope design by geologists and engineers can
improve the accuracy and robustness of procedures for project evaluation.
Because software vendors have only ever provided "Exact" reporting procedures
engineers have never been cognizant of the general limitations of wireframe subcell
approximations, nor the likely underestimation of grade on any particular project.
Fortunately the "Exact" estimates have been on the conservative side, and only
underestimated grade for the estimation of economics in project evaluation.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 121
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 122
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
the optimisation process) or a value field (which may have negative values in the
optimisation process).
Other optional model reporting fields are allowed. All mandatory and any additional
optional fields are output to the stope wireframe, string file and run report. Each field can
have optional control on scaling applied (1,000’s, millions, imperial to metric 0.3048,
etc.) and accumulation methods (mass average, dominant, ranked, etc.). For alpha
fields, the categories of [dominant, ranked] are available.
Exclusion field to ignore the reporting of items such as voids, topography air, or
backfill. Note, if you have backfill in the “stope void”, do not associate this with
the “report_exclusion_field”. Backfill should have a density and grade, and
should effectively be reported as waste. The VOID field type is the true void or
cavity, as identified by the “report_exclusion_field”.
Separate reporting of the undiluted and diluted stope-shapes (total rock and
metal).
Separate reporting of the undiluted and diluted stope-shapes for rock below cut-
off (i.e. waste) contained within the skin dilution and contained within the stope
design.
Reporting the dominant (majority) code, or the proportion and code of the four
most common values for one reporting field (i.e. “ranking”).
An optional (single line) stope summary file can be output.
An optional mined-out model file can be specified to identify the cells inside (and
outside) the stope wireframes based on the discretised sub-cells used in the
stope optimisation.
Support for imperial/metric units can be implemented in supplier user interfaces
by using grade and tonnage scaling factors. Note that SSO passes through all
values, so units are assumed to be consistent between the model fields and the
nominated user parameter values.
Reports can be saved in vendor file type databases (Datamine, Deswik, and Maptek) or
as a CSV (comma-separated value) text file.
Additional optional model fields can be included in the block model to enable SSO
functions such as spatial location modifiers, the inclusion/exclusion of material types
within a stope-shape, reporting exclusions, head-grade and others.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 123
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The detail report codes produced (in addition to the user selected report fields) are
summarised in Table 4.1.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 124
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The summary report codes produced in addition to the user selected report fields are
summarised in Table 4.2. Note that the summary report provides the total for all
RESULT (i.e. 1 and 0 where 0 represents the sub-economic stopes – if selected to be
outputted).
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 125
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 126
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 127
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Waste reporting uses mass weighted average grade and descriptions for the Version 3
implementation are:
The WASFRAC field is defined as; (volume of rock below cut-off / total volume of the
diluted stope-shape). Note that for the Prism Method there are no dilution skins involved,
so it is just the total stope-volume.
All the reported fields (detail report codes above) are essentially reproduced in the
stope-shape wireframe and stope string files. The verification files however exclude
these fields and report only GROUP, SURFACE, QUAD, PASSTYPE, PASSNUM and
FAILMESS (failed message) fields. The field comparisons are summarised in the
following.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 128
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
(optimisation field} (N) Yes (optimisation field} (N) Yes (optimisation field} (N) Yes (optimisation field} (N) No
STOPE (N) Yes STOPE (N) Yes STOPE (N) Yes STOPE (N) No
STOPENUM (N) Yes STOPENUM (N) Yes STOPENUM (N) Yes STOPENUM (N) No
VOLUME (N) Yes VOLUME (N) Yes VOLUME (N) No VOLUME (N) No
TONNES (N) Yes TONNES (N) Yes TONNES (N) No TONNES (N) No
DENSITY (N) Yes DENSITY (N) Yes DENSITY (N) Yes DENSITY (N) No
FAILMESS (A60) Yes
QUAD (N) Yes {IJK+1} QUAD (N) Yes QUAD (N) Yes QUAD (N) Yes
GROUP (N) Yes GROUP (N) Yes GROUP (N) Yes GROUP (N) Yes
SURFACE (N) Yes SURFACE (N) Yes SURFACE (N) Yes SURFACE (N) Yes
PTYPE (N) Yes
PASSTYPE (N) Yes PASSTYPE (N) Yes PASSTYPE (N) No PASSTYPE (N) Yes
PASSNUM (N) Yes PASSNUM (N) Yes PASSNUM (N) No PASSNUM (N) Yes
PASSSEQ Yes PASSSEQ Yes PASSSEQ Yes PASSSEQ Yes
LENGTH (N) Yes LENGTH (N) Yes LENGTH (N) Yes LENGTH (N) No
WIDTH (N) Yes WIDTH (N) Yes WIDTH (N) Yes WIDTH (N) No
HEIGHT (N) HEIGHT (N) HEIGHT (N) Yes HEIGHT (N) No
COLOUR (N) NA COLOUR (N) Yes COLOUR (N) Yes COLOUR (N) Yes (^ver)
RESULT (N) Yes RESULT (N) Yes RESULT (N) No RESULT (N) No
CUTOFF (N) Yes CUTOFF (N) Yes CUTOFF (N) No CUTOFF (N) No
XSTOPE (N) Yes XSTOPE (N) No XSTOPE (N) No XSTOPE (N) No
YSTOPE (N) Yes YSTOPE (N) No YSTOPE (N) No YSTOPE (N) No
ZSTOPE (N) Yes ZSTOPE (N) No ZSTOPE (N) No ZSTOPE (N) No
XCENTRE (N) Yes XCENTRE (N) No XCENTRE (N) No XCENTRE (N) No
YCENTRE (N) Yes YCENTRE (N) No YCENTRE (N) No YCENTRE (N) No
ZCENTRE (N) Yes ZCENTRE (N) No ZCENTRE (N) No ZCENTRE (N) No
TRIANGLE (N) NA TRIANGLE (N) Yes TRIANGLE (N) NA TRIANGLE (N) Yes
PID1 (N) NA PID1 (N) Yes PID1 (N) NA PID1 (N) Yes
PID2 (N) NA PID2 (N) Yes PID2 (N) NA PID2 (N) Yes
PID3 (N) NA PID3 (N) Yes PID3 (N) NA PID3 (N) Yes
PVALUE (N) Yes
PTN (N) Yes PID (N) Yes
XP (N) Yes XP (N) Yes
YP (N) Yes YP (N) Yes
ZP (N) Yes ZP (N) Yes
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 129
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
An example use for this function is to change the field TONNES to say KTONNE and
multiply the original TONNES field by a 0.001 factor to derive “kilo-tonnes” or “thousands
of tonnes”.
A mined out model can optionally be output to identify the portion of the model that is
mined, is part of a pillar or is otherwise unmined. The output model represents the sub-
cells after the discretisation process, split according to the portion that falls within the
stopes and the pillars.
The mined out model has values of 0 or 1 in the MINED and PILLAR fields to indicate
exclusion or inclusion. The MINED field name can be replaced with a user defined field
name. There is also the option to output only the MINED=1 discretised sub-cells only.
PILLAR=1 is the set of cells comprising the stope and the pillar width external to the
stope. MINED=1 defines the stope shape, and mined_only="yes" will only output these
blocks (and all cells will have PILLAR=1). If mined_only="no" is specified, then
MINED=1 will display the stopes only, and MINED=0,PILLAR=1 will display the pillars
only.
It is useful to review the mined out model to assist understanding what the discretisation
process is doing. The mined out model may also have many other downstream uses.
Beware that the mined out block model can be much larger than the input block model
because it provides the discretised model cells. The mined out model was primarily
designed for test areas or use with validation_test_cell quadrilaterals.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 130
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Note that the stope-names should be defined so as to be unique. For example, using
component parts that describe the mine-name followed by floor-level would result in all
stopes on any particular level to have the same stope name.
Each part will need to have some or all of the following parameters specified:
A reporting field value part can be any of the nominated fields reported from the input
block model or contained in the detailed output report as summarised in Table 4.1. This
could typically be any one of:
STOPENUM,
QUAD, PASSTYPE, PASSNUM, PASSSEQ,
XSTOPE, YSTOPE, ZSTOPE (central coordinate at floor position),
XCENTRE, YCENTRE, ZCENTRE (centroid coordinate)
SLENGTH, SHEIGHT, SAVGWID (or equivalent for horizontal frameworks),
CUTOFF, RESULT,
ISFARHW, (is the far wall the hangingwall - True/False - 1 or 0),
Model evaluation fields (e.g. Au Grade, NSR value, Zone, Rescat, etc.).
These are automatically generated field values that can be used from the following list:
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 131
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The (u,v,w)_local and (x,y,z)_world fields will be identical if the framework is unrotated,
but (x,y,z)_world are required to provide world coordinates for rotated frameworks..
This can be any user defined text e.g. “East_”, “MyProject-“, etc. Commonly used as a
separator between other parts (e.g. “_”, “-“, etc.).
This is a generated value that represents a spatial location. For regular model
frameworks, 'position_counter' evaluates the position of the stope in the framework. It
advances forward/backward from the start/end along the specified 'axis' direction,
counting the number of "steps" in the stope framework. It uses the supplied "start" value
and applies the number of steps (using the "step size") to define a value to assign for
each stope based on its framework position along the defined axis (U|V in the stope
orientation plane and uses the PASSSEQ field value on the W axes), or in the reverse
direction. The start value can be numeric or letter (i.e. 'number_count', 'letter_count').
Letters can be a mixture of upper and/or lower case, and the increment restricted to the
supplied case.
The PASSSEQ field is used to number full stopes, substopes in sequence from the near
to the far side of the framework.
If an XZ framework has sections along the U-axis of 1000, 1100, 1200, 1300, 1400,
1500 and full stopes generated between these sections, then the value generated for
the position counter for the following cases would be:
start at minimum, number count, start = 50, increment = 100
50, 150, 250, 350, 450
start at maximum, number count, start = 450, increment = -10
50, 150, 250, 350, 450
start at maximum, number count, start = 50, increment = 10
450, 350, 250, 150, 50
start at minimum, letter count, start = A, increment = forward
A, B, C, D, E
start at maximum, letter count, start = Z, increment = back
U, V, X, Y, Z
start at maximum, letter count, start = A, increment = back
E, D, C, B, A
If the letter count exceeds A-Z, then multiple letters can be employed with AA
incrementing to AB, AC, .., AZ, BA etc. Aa would increment to Ab, Ac, ..Az, Ba if
lowercase was used for the letter start to signify case sensitivity.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 132
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
For the syntax of the expression text, see the Filter Expression section.
A simple example for using an expression list for naming stopes based on grade range
would be as follows:
Expression Value
"field AU GT 10.0" "HG"
"field AU GT 5.0" "MG"
"field AU GT 2.5" "LG"
The order of the expressions is important as the first expression satisfied will be used to
assign the Value.
An exclusion-distance field can be supplied where stopes must be more than a set
distance away.
A model report-exclusion field allows mined out material or voids to be ignored in the
stope evaluation.
A mixing field and associated values can be supplied to control mixing of material with
different attributes. If a model has multiple ore types then stope-shapes are generated to
not allow mixing of the ore types (as designated in the ore type field). No two field
values from the list specified can be found in a stope.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 133
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Filter expressions provide a way of supplying additional criteria. Filters are applied to the
processing of the seed and annealed stopes. The filters allow evaluated model variables
to constrain the production of stope-shapes e.g. RQD criteria, penalty element criteria,
resource category requirement, etc. as detailed in filter text sub-section.
Filters can only be applied to the optimisation field and the other model fields selected
for reporting, but not the additional standard fields added in stope reporting. If for
example a spatial filter was wanted on stope elevations, then the ZC field from the
model would need to be selected, and evaluated as a numeric field, and the filter applied
to the ZC field rather than the ZSTOPE field which is later calculated for the stope
report.
Filter text (i.e. filter expression) can be used to control the generation of the stope seed
and subsequent stope annealing process. The stope seed and annealing process must
fulfil the filter text requirement to produce a stope-shape.
For example, to only generate stopes that meet a value, range of values or range of
criteria e.g. “RQD>70”.
Another example could be that 90% of the stope-shape must contain measured
resource category (e.g. RESCAT=1). By using the internally generated “ranking” report
fields (up to 4 values) for the RESCAT field and then using the filter text “CLASSV1=1
and CLASSA1>=90.0”. Note that in this example it is only necessary to test the first
ranked field if the percentage is 90.0 because the second ranked field could never have
a value of 90.0. If the limit was thirty then the expression would need to be
“(CLASSV1=1 and CLASSA1>=30.0) or (CLASSV2=1 and CLASSA2>=30.0) or
(CLASSV3=1 and CLASSA3>=30.0)”. The fourth ranked field need not be tested as it
could never have a percentage greater than 30.0 while still being the fourth ranked field.
The keywords FIELD and CONSTANT are optional, and need only be specified where
necessary to avoid confusion (e.g. "ROCKTYPE=FIELD T2" or
ROCKTYPE=CONSTANT T2").
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 134
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The alternative method of expressing these (i.e. >, >=, !=, etc.) have been removed to
avoid conflict with the XML syntax.
The special meaning of a character (e.g. "*") is lost if the character is preceded by "\",
hence to match a literal "*", use "\*".
If the keyword "REGEXP" is used, the pattern specifies a full regular expression.
Regular expressions allow advanced users to make more complex selections than are
possible by using the pattern elements specified above.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 135
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Any result may be inverted by preceding the expression by the keyword "NOT" (e.g.
"NOT BHID MATCHES RHD*").
Two expressions may be joined together by "AND" or "OR" operators. The result is
another expression.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 136
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 137
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Estimation aims to provide the best local grade estimate, which has the effect of
smoothing the grade variance, while
Simulation is specifically designed to reproduce the grade variability and examine
its effects.
The confidence level would be expected to have a high correlation with resource
category. As a consequence, the results of this type of analysis may be very challenging
because the level of confidence associated with stope designs may be significantly
different to the resource classification. The differences however may often be attributed
to categorisation limitations and/or practicalities (such as avoidance of “spotted dog”
classification or QA/QC issues that require re-classification). It however provides an
independent alternative view regarding the certainty of the resource modelling.
There are several alternatives for conditioning the MIK data to a series of simulations:
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 138
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
(2) Provide a set of fields with absent data and default of -1.0 (which is the value
recognised by GSLIB) for UNSET data, and a random distribution of [0, 1] values will be
generated.
(3) Provide no fields and a random distribution of [0, 1] values will be assigned to the
maximum number of conditional fields that can he handled (currently 50).
Option (1) is preferred, and the benefit of supplying the field names in the model file is
that the stope grades based on the simulations generated can be reported.
While this approach can be undertaken with the Stope Shape Optimiser, another
method is to analyse all the simulations concurrently. The criterion for each run is that
the final stope-shapes must satisfy the selected cut-off/head-grade at a selected level of
confidence, and produce the optimal set of stopes to maximise value/metal.
The single set of stope-shapes that return maximum value is reported at the requested
level of confidence, rather than reporting a stope optimisation on each and every
realisation. At 100% confidence the stope-shape will satisfy the cut-off value for every
realisation. At 80% confidence the stope-shape will satisfy the cut-off in 80% of the
realisations. The trade-off between risk and return is found by graphing the stope
tonnage and value against confidence, and is a way to generate a "nested" set of
stopes.
For either method, conditional simulation or multiple indicator kriging, a complete set of
realisations is analysed in a single run of the SSO, with a single set of stope-shapes
output. All the stope grades for each realisation can be reported at that confidence level.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 139
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
5.6 Reporting
For any nominated confidence level, the output stope report file will provide the following
four statistics from evaluating all realisations:
1. Apply 0% Confidence criteria in SSO and export the “CONF-PER” values for
various Kriged fields. This would be the optimised grade (say Au, Cu, EqV,.. etc.)
but could also be for elements which effect process recovery or other elements
which may affect process throughput, and perhaps even a geotechnical
parameter like RMR (which may potentially be used for dilution / stope failure
estimation)..
2. Run a schedule based on optimising project goals
3. Report the CON-PER per field (confidence percentage) by time period and then
using the weight-average “confidence level” to highlight schedule/budget issues
(e.g. potential metal production volatility, areas that require further in-fill
drilling/re-modelling to improve confidence, re-focus of the schedule/sequence
towards higher-confidence areas (while conducting in-fill drilling), only designing
for areas with confidence greater than X%.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 140
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
In some cases, vendors have options to run external executables from within the mining
software interface with scripts or batch files (consult vendor documentation for details).
It is also possible to run the Stope Shape Optimiser engine as a standalone executable.
A vendor license for the Stope Shape Optimiser is required at all times, so the vendor
requirements for concurrent execution need to be understood.
A log file is also generated which summarises the stope optimisation process. It includes
a copy of the parameter settings used in the run, a line for the optimisation of each quad
value, the processing time and a tabulation of results in a similar format to that created
in the stope report file. The tabulated results in the log file include a line for each stope
(RESULT=1) and a value for stopes with RESULT = 0 (the final stopes not generated or
not meeting the defined parameter settings). The log file can report useful diagnostic
information if stopes are not created, and will also give an error message if the run is
aborted.
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 141
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
The XML cases can define the exact path names for the input and output files. If not
specified, then all input and output files are assumed to be in the working directory.
An example batch file for each vendor is provided below. In general the scripts can be
run within
StopeOpt.exe -v test.xml
pause
StopeOpt.exe -v test.xml
pause
StopeOpt.exe -v test.xml
pause
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 142
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Running cases using a command shell with system administrator privileges is not
necessary.
(1) The XML file is structured to allow multiple scenarios in a single file. Typically the
vendor interfaces write a single scenario per XML file. These allow sequential
processing of scenarios from the one XML, and it is possible to select scenarios for
processing with the skip_evaluation="yes | no" option.
It is possible to parallel process scenarios from the one working directory using the one
set of input files but the output file names (and batch files) must be unique for each
case.
This approach is similar to (2) but the batch file uses the ampersand (&) character to
spawn independent jobs. Ensure that two processes do not attempt to write
concurrently to the same log and output files.
In some vendor implementations the user has the option of importing settings into the
vendors interface from any XML file, or saving the parameters for a run in an external
XML file. This might also be a convenient way to modify XML files and have validation
of input and output files, and field names etc
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 143
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Currently the XML editors recommended by AMS (after a detailed review of freeware
and commercial editors) are:
Notepad++ (freeware). If an XML file is not correctly formatted with CR/LF then
using the keys Ctl-Alt-Shift-B
Oxygen XML editor (commercial software available from:
http://www.oxygenxml.com/download_oxygenxml_author.html
File comparison editor (commercial software available from “Beyond Compare”:
http://www.scootersoftware.com/download.php
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016 144
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
APPENDIX A
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Term Definition
Absent value A reserved value for a field to indicate “value unknown”. This
typically should not be zero, as by convention that would mean
that the value is definitely known to be 0.0. Typically for Datamine
Studio the absent value is defined as “-“ (missing value), and for
Maptek Vulcan this is a user-defined large negative value like “-
999”
Default value This is the replacement value that SSO should use whenever the
“Absent” value (q.v.) is encountered in an input field. E.g. for a
model without voids, the value “2.5” might be supplied as the
default Density field value, and this would be used whenever the
Density field for a model cell is flagged as “-“ in Datamine Studio,
or say “-999” for Maptek Vulcan.
Face Refers to either the stope-shape strike extent faces (end walls) or
the stope-shape vertical extent faces (roof or floor).
Model Discretisation Describes the (local) model plane orientation that is used to
Plane discretise or split model cells to aid in the stope-shape annealing
process. The Model Discretisation plane will be the same as the
Stope Orientation plane except for the MODROT=4 case where
the model plane closest to the Stope Orientation plane will be
selected
MODROT Defines the relative rotation of the block model and the Stope-
shape framework:
Quadrilateral A 4 sided polygon that describes the stope face profile in the UV
coordinates of the Stope Orientation Plane. The polygon can be
either a rectangle (for regular frameworks) or a trapezoid (where
two sizes are parallel with the V-axis for irregular frameworks)
Stope Orientation One of the values [XZ | YZ | XY | YX] which defines primary axes
of the Stope-shape Framework in U and V, with U corresponding
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
Plane to the first axis and V the second, with a third axes W in the
transverse direction to the UV plane. In the simplest case of an
un-rotated XZ Stope-shape Framework, the axis equivalence
would be U=X, V=Z and W=Y
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
APPENDIX B
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016
Alford Mining Systems
Stope Shape Optimiser Version 3.0.1
APPENDIX C
AMS Stope Shape Optimiser Ver 3.0.1 Reference Manual.docx : 10 October 2016