Connecting A to B: The modeling path from Assays to Blocks

Connecting A to B:
The modeling path from Assays to Blocks
Deposits are different, but typical methodologies still apply when modeling. This workshop will highlight
the use of MineSight tools in the modeling workflow. We will examine moving from raw drillhole data to
interpolating grades in a 3D model. This will include the use of on-screen interpretation in MineSight 3D,
calculating composite intervals in MineSight Torque, using MineSight Data Analyst to examine statistical
relationships and discuss geologic units, and a review of interpolation in MineSight Basis. The workshop
will demonstrate how to capture knowledge of a deposit and effectively use this information throughout
the modeling process. This workshop will also highlight special considerations when dealing with various
geologic environments, and creating an audit trail for reproducibility.

Loading Drillhole Information MineSight Torque

The modeling process begins with drillhole and sample data. Raw data should be verified for accuracy, and
stored in the MineSight Torque (MSTorque) drillhole database. Blasthole, drillhole, and other sample data
can be stored securely and accessed easily throughout the modeling process. Data can be imported via an
ODBC connection, other SQL databases, raw text files (Figure 1), and existing MineSight projects (Assay and
Survey files). Once inside of MSTorque, data validation tools can be used to check for common issues (e.g.
interval overlaps, grade values outside a set range, and duplicate drillholes). We will return to MSTorque
when compositing data.

Figure 1. General Importer for MSTorque.

Page 1
Connecting A to B: The modeling path from Assays to Blocks

Solid Modeling Methodologies

Based on the available drilling information, geologic knowledge of the deposit, and other constraints
modeling methodologies can vary. This decision affects the remainder of the modeling process, and all
options should be carefully considered. Four common strategies are:
Geologic Solids based on sampled geology information: Geologic boundaries can be used to
control compositing and interpolation. These solids can be based on lithologic unit, alteration
zonation, structural units, or other well sampled divisions. Data stored downhole can be
interpreted graphically on-screen using geologic codes in drillhole logs or using the true thickness
methodology for stratigraphic or vein deposits. This method of modeling will be discussed in the
most detail throughout this paper.
Mineralized Solid(s) based on assay data: A mineralized envelope, consisting of multiple solids (or
zones), can be built by using cutoff grades on assay data. This approach is a reasonable choice if
the geology is constant throughout the deposit, if the statistics have proven the assay data has a
common behavior, or when the project is at an early stage of exploration. For more details on this
type of modeling, check out the MineSight Monitor Mineralized Zones in MineSight, July 2008.
Geostatistical Domains: Domains can be created by grouping data with similar behavior based
on variography and general drillhole statistics. Data that has a similar behavior can be organized
by simply grouping one set of geological codes or by grouping in a more complex fashion, such as
when mineralization is controlled by lithology and alteration. Creating domains is a commonly used
approach at Mintec and for more details see the 2010 Seminar paper Modeling: A Typical Workflow.
Mineralized zones based on probability: Probabilistic mineralized envelopes can be
developed with the help of Indicator Kriging. Indicators can be assigned to a composite
to indicate if an assay belongs to one geologic formation or not. The indicators can then be
kriged after an indicator variogram is developed. The resulting probabilities in a block model at
50% correspond to 50% probability for the block to be part of that geological formation.

Interpreting Solids in MineSight 3D - Preparation

Gridset creation for interpretation
After deciding on the appropriate modeling method for the deposit, the next step is to work towards a
representative 3D solid(s) of the zone. This begins with 2D polygonal interpretation. The 2D planes used are
determined in MineSight 3D (MS3D) via the use of grid sets.
Setting up a grid set with planes that best fit the drillhole data can increase the precision of digitizing
polygons in 2D mode. The grid planes can be unevenly spaced, non-orthogonal, or non-parallel. Fence
diagrams can also be used. This type of view is especially useful at the edges of a deposit as it allows for
more precise creation of polygons for linking where the drillhole data is sparse (Figure 2).

Page 2
 Connecting A to B: The modeling path from Assays to Blocks

Figure 2. Example fence polyline connecting

drillhole collars on the edge of the deposit.
Creating a grid set between polyline end points allows you to create a flexible sectional grid set that has
uneven spacing, and is non-orthogonal, and/or is non-parallel. If the grid planes are parallel, orthogonal, or
non-orthogonal, simply create a 2-point plan polyline (Polyline | create 2D | polyline) along the orientation
that represents the first section plane in the grid set. Using the option Polyline | Offset, adjust the next
section plane in the grid set with an appropriate offset distance and build all necessary section lines. If
the grid planes are non-parallel and non-orthogonal, digitize a set of 2-point plan polylines in different
directions to represent each section. Under the Grid Set Creation dialog, choose the Grid Set Definition
Between Polyline End Points and select the polylines representing the section lines (Figure 3).

Figure 3. Creating grid sets between polyline end

points based on drillhole spacing.
In the case of existing analog sections (e.g., sectional paper geologic maps), grid sets that align with these
locations can also be created. A combination of the texture surface tool for bringing the data into MS3D and

Page 3
Connecting A to B: The modeling path from Assays to Blocks

the above methodology for creating appropriate grid sets between polyline endpoints can be used. This can
allow for the incorporation of analog data with drilling information (Figure 4).

Figure 4. Paper section textured on surface in MS3D with loaded drillholes from MSTorque.
Another approach is to create planar and sectional grid sets, and interpret sequentially in each direction
(e.g., digitize polygons on an EW section, and then use the resultant intersection points for interpretation on
planar sections).
Once the grid set(s) has been created, renaming planes for consistency is useful (especially when using non-
orthogonal and unevenly spaced grids). Rename the grid plane on the Planes tab in the Grid Set Properties;
the use of wildcards with a prefix is useful in this case. Although it is possible to query a grid set plane to
retrieve the plane name, it is also convenient to turn a grid set into a separate polyline geometry object as a
visual indicator. The function Surface | Create | From Grid Set or Edit Grid is a quick way
to turn a grid set into a geometry object. Choose the option to create polygons and check the naming
option Elements by plane. New geometry elements are created containing polygons. A few adjustments

Page 4
 Connecting A to B: The modeling path from Assays to Blocks

in the properties are needed for proper labeling. You can densify the nodes along the polyline in order to
give you better control of the label position (Figure 5).

Figure 5. Renamed grid sets created from

polyline endpoints.

Projection Volume and Viewer Clipping

Now that our planes our ready, setting up the appropriate projection volume and viewer clipping for
interpretation is critical. The correct settings ensure data used is not omitted or duplicated.
The projection volume for each drillhole view is set on the Selection tab. This distance is the window in
which drillholes are projected from each section.
On the Viewer Properties | Clipping tab you can set the plane range when the viewer is in 2D or a volume
range when the viewer is in 3D. The Plane Filter Range shows the number of planes specified before or after
the current plane and has an effect similar to a light and color table if desired. This is a great guide when
digitizing polygons of similar shape from one section to the next.
The Volume Clipping Range controls the clipping of the 3D display. The volume clipping can be set on or off
with the toggle button Viewer Volume Clipping on the MS3D desktop toolbar. Setting the volume clipping
to show a few sections at a time can give a clearer picture of the data under study.

Page 5
Connecting A to B: The modeling path from Assays to Blocks

Multiple Viewer Options

Using multiple viewers can assist in ensuring polygonal interpretations are on track. For example, one Viewer
can display a cross-sectional view in 2D mode while the second Viewer shows a plane view in 3D mode. The
digitizing progress will be displayed simultaneously in the two viewers.
The tri-viewer setup (Viewer Properties | View Options tab) can also be used for sectional interpretation.
Toggling this option on splits the viewer into three tiles, and is used in conjunction with the Plane Filter
option. The top (or left) viewer is the + plane(s), the bottom (or right) is the - plane(s), and the center is
the current plane displayed. This allows the user to see the nearby sections simultaneously while digitizing
(Figure 6).

Figure 6. Tri-viewer setup. Current plane is the center viewer, the + plane is on the left, and the - plane is on the right.

Using the Drillhole Distance Offsection

On the Drillhole View Properties | Survey tab, toggle the label option Display Offsection Distances. This
option activates a label that shows the projection distance of the data on a plane. This can also be activated
for each interval as a Strip (Drillhole View Properties | Strips tab). Decision making while digitizing can be
improved by using this simple marker.
Adjusting the Primary Display Cutoff
Changing the primary display item properties can assist in clarifying code distribution and easily
differentiate between units. For example, changing the line width and style for the code value of
interest can help highlight the area of interest (Figure 7).

Page 6
 Connecting A to B: The modeling path from Assays to Blocks

Figure 7. Setting up a thicker line for Mineralogy attribute codes 3 and 4.

Displaying 2D Strips
Displaying multiple items downhole can be useful during interpretation and in 2D mode Strips are used
to achieve this task. Strips allow you to view several items to the left and/or right of the drillhole trace. The
strips are highly customizable and can include Distance off-section, code/grade items, wiggle trace items,
and geotechnical information (Figure 8).

Page 7
Connecting A to B: The modeling path from Assays to Blocks

Figure 8: A portion of 2D drillhole strips viewing

geotechnical data. From left to right label
showing downhole distance, dip-meter strip
sowing tadpole diagram colored by azimuth and
rose diagram every 10 units down, color strip
showing dip values, geology stick strip showing
orientation disks.

Creating Points between Geologic Contacts

Points marking a geologic contact in a drillhole can be used for snapping polygon points or surface building
later (i.e. top of ore surface). Markers can be created at the contact between two geologic units using the
Drillhole Properties | Points tab. After selecting an appropriate option, and using a filter if necessary, a point
is created where the geologic change occurs and it is stored in a new geometry object. Checking the box
Attribute points with DH ID ensures the source of the newly created point can be referenced back to the
original hole via a query. Points can also be created based on cutoff grades.

Page 8
 Connecting A to B: The modeling path from Assays to Blocks

Figure 9. Left - Surface created from triangulated points at the top of Ash surface for coal. Right Surface created with procedure pdhgrd.
dat and a kriging method based on the same Ash cutoff.

Interpreting Solids in MineSight 3D - Creation

Digitizing Polygons
To build a solid, start by digitizing polygons on sections. If existing analog sections have been loaded into
MineSight, using the Geomap Tool (Geo Tools | Geomap Tool) for face mapping can be an efficient way to
digitize the information. Snapping the polygons to drillhole intervals can increase the precision of your
interpretation. The snapping process is done in 3D. Therefore, it is necessary to first convert the digitized
polyline from 2D to 3D (Polyline | Convert 2D to 3D). After activating the Point Snap function (Snap | Point
Snap), polygon points can be moved and snapped to drillhole intervals. Note, if polygons are converted back
to 2D, the snapping will be lost (Figure 10).

Figure 10. Sectional polygon in plan after being converted

from 2D to 3D and snapped to drillhole intercepts.

Page 9
Connecting A to B: The modeling path from Assays to Blocks

Polygons created on fence planes can also be linked to 2D sectional polygons. As discussed in the section
on gridset creation this can increase precision of the interpretation (especially at the edges of the deposit
where drilling may become sparse). Figure 2.
After the polygons are digitized, you can make the best use of the MS3D CAD functions for smoothing
corners, adjusting point locations, and cleaning up the data.
Next, densify the digitized polygons using the Polyline | Densify function. Using polygons with a
similar point distribution assists in the linking process later (Figure 11). Make sure all the polygons
are in the same direction (Polyline | Redefine | Direction), and ensure that they are all closed (Polyline
| Global Join ).

Figure 11. Three sectional polygons showing one with a much

higher point density than the other two. This polygon should be
thinned before linking.

In the case of stratigraphic seams or vein deposits, digitizing narrow polygons for linking can be challenging.
The use of the True Thickness tools (Geo Tools | True Thickness Tools) can provide a more automated method
for polygon creation. The tool allows you to construct the polygons automatically based on drillhole
information and digitized footwall or hanging wall polylines (Figure 12).

Page 10
 Connecting A to B: The modeling path from Assays to Blocks

Figure 12. Top digitized footwall polylines of seams prepared for the
true thickness tool. Bottom seam polygons created after running the
tool (note polygons can be automatically clipped against topography
and other boundary surfaces, such as faults).

Linking to form Solids

The polygons digitized on sections (snapped to matching drillhole intervals) can be linked to create a solid
via the Linker Tool (Utilities | Linker Tool ). The tool includes a variety of manual and automatic options,
along with quick access to extrude and surface merging functions. Substrings and Strong Nodes allow for
detailed and careful control of the links. When using multiple substring splits (i.e., nested substrings), the
Nearest Element Dialog can be useful for ensuring the proper polygon is selected (Selection | Use Nearest
Element List Dialog) (Figure 13).

Page 11
Connecting A to B: The modeling path from Assays to Blocks

Figure 13. When splitting a substring, using the Nearest Element List Dialog can ensure the correct polygon is split. The same applies
when selecting the proper polygon for linking.
Making the best use of the viewer options discussed previously (2D plane filtering, multiple views, volume
clipping) can all assist in streamlining the linking process. The Open View and object selectability options
in the Data Manager can also prove useful for keeping the view uncluttered.
After linking the first pass polygons, often the Slice View function using an evenly spaced grid set is used
(the Slice View function is accessed in the Data Manager using a right-click on a Folder | Slice View). The
added polygons can then be reworked in section. Once the solid is linked, merged, and assigned an
appropriate material type, drillhole intervals can be coded.

Coding and Backcoding

Backcoding to drillholes is useful for auditing the solid/geologic interpretation (run statistics on intervals
used to build the solids versus intervals backcoded with the resultant solid). Backcoding can sometimes
be necessary to ensure that on-screen interpretation is properly flagged into the drillhole intervals when
downhole drillhole geology information is unavailable. However, if the geology is already available in the
drillhole interval, it should take priority.

Page 12
 Connecting A to B: The modeling path from Assays to Blocks

A new sample attribute should be created in MSTorque to receive the results from coding to prevent the
original geology information from being overwritten (Figure 14). Coding from polygons is a valid method
to quickly move on to compositing without spending time building solids. However, it is important to
emphasize that building solids offers better control and precision.

Figure 14. Creating new sample attributes in MSTorque to receive the backcodes. Note the comments section is useful for clarifying what
is stored in the attribute.
In the following example, both Mineralogy and Rock units were interpreted. Mineralogy is left
as polygons only, while Rock units were linked to form solids.
The Drillhole View Properties | Code DH tab has the drillhole coding options. In this example, we will
code attributes Mineralogy Code and Rock Code using CODE by majority code (Figure 15). The geometry
used to code can be exported and added to a multi-run for model reproducibility; click on the Export
button and the output file will be named with an .mscode or .ini extension. These files are used with
program mscode.exe later on in a multi-run with MineSight Compass (MSCompass) procedure runcmd.dat.

Figure 15. Top: Coding setup for geology solids into Rock Code attribute, Bottom: Coding mineralogy polygons into Minrl Code attribute.

Page 13
Connecting A to B: The modeling path from Assays to Blocks

After the coding is complete, you can visually check the result in 2D via new strips in a drillhole view. Set
up the strips to show the original Mineralogy and Rock intervals used to create the solid on one side of the
drillhole trace and the newly coded attributes on the other (Figure 16).

Figure 16. Left strip on left represents rock codes after backcoding
from solids; strip on the right shows original geology data. Right
visually checking drillhole coding in MS3D against solids.

During this visual checking process, you may run across intervals you would like to manually force as a
different code value. You can quickly return to MSTorque to edit these values manually, or load into MSTorque
a text file with the appended codes, and overlay these codes onto the proper coverage in MSTorque.

MSTorque Coverages
After backcoding is complete creating a master coverage can be a useful tool. By using the Overlay
coverage function in MSTorque, assay and geology information can be brought together properly into
one coverage.
The first step is to copy the target coverage (Tools | Copy Coverage) to a new one. This way, the raw assay
and geology information are preserved in their original state, and the new copied coverage is used for
data manipulation.
When overlaying, you have the option to split intervals, or use the majority code. Splitting intervals will
honor the geologic information exactly, but can cause new intervals to be created when the geologic
contact and assay interval break arent in the same position. By using the threshold percentage, this can
help manage the issue by limiting the number of very small intervals. By using the majority value, the final
coverage will have the same number of intervals as the target (copied assay coverage), but exact geologic
boundaries are not honored (Figure 17).

Page 14
 Connecting A to B: The modeling path from Assays to Blocks

Figure 17. Example overlay coverage dialog and resultant options.

Basic Statistics in MineSight Data Analyst (MSDA)

MSDA can be used to run a variety of statistics on assay information. MSDA links directly to the MSTorque
database via the Data Source. Custom Reports, histograms and scatterplots can all help give you a better
idea of the data properties. Filters based on attributes (e.g., Rock) can summarize the data into bins of
interest. Optionally, outliers can be removed from reporting the majority of the data statistics. The range of
data used can be defined in the basic filtering tab when you set the data source.
Using MSDA to determine geostatisical domains can be accomplished through custom reports and
validated through other charting tools (e.g. histograms, box plots, and cumulative probability plots).
Grouping data based on similar distributions, variation, and ranges is a common approach, and this is
discussed in more detail in the 2010 Seminar paper Modeling: A Typical workflow. After deciding on the
appropriate domains, calculated attributes in MSTorque can be used to populate the domain attribute. Note
that the project geologists advice should also be considered in the creation of domains and that domains
can later be revisited after the variography has been completed.
In our example, data can be analyzed by Mineralogy and Rock properties. Histograms, Box plots, and
Cumulative Probability Plots are all tools available in MSDA to compare the distribution of data values
(Figure 18).

Page 15
Connecting A to B: The modeling path from Assays to Blocks

Figure 18. Box plot of copper grade by

mineralogy. Based on the results below,
the Breccia fault zone has the highest
grade, but is also the most variable.
Contact plots can also prove useful at this stage. The Contact plot in MSDA examines the grade distribution
as a function of distance from a geologic contact (code change in an attribute). These plots can assist with
grouping domains, and on composited data can help the modeler decide if a boundary is hard or soft for
interpolation (Figure 19).

Figure 19. Contact plot showing an

abrupt/sharp contact from Mineral
zone 3 to 4.

Compositing by Honoring Geologic Codes

After the geologic information has been coded in the composite set, compositing can be run inside
MSTorque. Several options are available for compositing, and all composites in MSTorque will be stored at
mid-interval. Composites are used for interpolation to provide a mining basis for modeling, to reduce the
amount of data used, and to provide uniform support for geostatistics. The options in MSTorque are:

Page 16
 Connecting A to B: The modeling path from Assays to Blocks

Bench: The compositing type most frequently used for open pit, massive/porphyry deposit types.
This uses a defined bench table for creating the composites (input manually by the user or read
from an existing MineSight project control file (PCF)).
Fixed length: Creates composites of a specified length. Commonly used when honoring a geologic
or domain change. While compositing with a fixed length, small intervals can occur at the end of a
hole or at a geologic contact when honoring a geology item. Options to deal with small intervals
are available - merging with neighboring intervals, adjusting the lengths to avoid small intervals,
and where these calculations occur (throughout the hole or just at the end). The variability and the
structure of the mineralization can be important factors to consider when deciding a length.
Honor sample attribute: Commonly used in vein deposits. Allows you to create composites where
a sample attribute value changes (i.e. Vein). This creates composites where a vein is present, and
honors the thickness of the vein.
Composite entire sample site: Converts the entire hole into one composite interval. This is
commonly used with blasthole data (each blasthole becomes a composite) or when the user would
like to see the length weighted average grade for the entire hole.
Convert samples to composites: This converts the original intervals into composites. This is
commonly used when already-composited data has been loaded into MSTorque.

Figure 20. Left compositing dialog in MSTorque. Right example compositing results using various methods.

Page 17
Connecting A to B: The modeling path from Assays to Blocks

It is easy to create multiple composite sets examining the various options, and manage the sets inside of
MSTorque.
Other codes can be transferred to the composite set if desired via the Overlay Coverage option.
Simply choose the source coverage with the code value, the attribute to overlay, and the target
composite set (similar to what is shown in Figure 17).
Finally, a Drillhole View of the composite set is made for a visual check of the data. This can be viewed
with a Drillhole View of the raw assay data for comparison (Figure 20 Right side).

Block Model Creation and Coding Highlights

The block model file can contain up to 500 items, and the number of blocks allowed in the model has no
restriction. There are no required items for the block model file; however, several items are common to most
projects. The table below highlights these items:
Name Description Populated via
TOPO Percentage of a block below topography Model coding
CUIDW Grade value from inverse distance weighting interpolation Interpolation procedure
CUPLY Grade value from polygonal interpolation Interpolation procedure
CUKRG Grade value from kriging interpolation Interpolation procedure
KVAR Kriging variance Interpolation procedure
CLSDT Distance to closest composite used to interpolate Interpolation procedure
AVDST Average distance to composite used to interpolate Interpolation procedure
NCOMP Number of composites used to interpolate Interpolation procedure
CLASS Resource classification User calc or modcls.dat procedure
ROCK Geology code information Model coding
ORE% Ore percentage Model coding
DOMN Domain (used for statistics and interpolation) User calc procedure

Model coding should be done using the same geometry objects used to code the drillholes. Model coding
options are located on the Model View Properties | Code Model tab, and are similar to the options available
in drillhole coding, with addition of coding from surfaces.
The geometry used to code the block model can also be exported and added to a multi-run for model
reproducibility. Click on the Export button and the resulting output file will be named with the .mscode or
ini extension. This file can be used with program MSCODE later in a multi-run with MSCompass procedure
runcmd.dat.

Page 18
 Connecting A to B: The modeling path from Assays to Blocks

Block Model Interpolation - Highlights

Variograms
Variography studies are required for kriging, but can also be useful for determining search parameters for
other interpolation methods. Downhole variograms, directional variograms, and variogram models can be
created in MSDA and exported for use in the MSCompass interpolation procedures. Calculated ranges and
rotation angles can be used as a guide when determining the search ellipse. Variograms are calculated for
each geologic unit and the interpolation parameters are variable for each unit. Variograms are
calculated from composited data (versus raw assay data) for equal support.
Directional variograms can be created for each geologic unit in MSDA by enabling the separate filter
option. 3D variogram models with nested structures can be created in the MSDA Variogram 3D Manager.
Auto-fitting and manual adjustments of the model can be used. Previously defined parameters, like nugget,
can be hardwired and honored in the auto-fitting routine (Figure 21).

Figure 21. Example direction variograms by Rock type 1 modeled in the 3D Variogram manager.
The following example examines a few key points from MSCompass procedure pintrpq.dat: Model
Interpolation from MSTorque. This procedure allows you to choose the desired method of interpolation from
several flavors of kriging and inverse distance weighting methods.

Page 19
Connecting A to B: The modeling path from Assays to Blocks

Debug Ellipsoid: When using this option, only one specified block is interpolated. It can be used with
kriging and inverse distance weighting methods. An ellipsoid will be generated for viewing in MS3D which
includes ties lines to composites used, and a list of kriging weights. Using this option can be very helpful
when troubleshooting an interpolation run.
Octant/Quadrant Options: Useful when dealing with clustered data. Several options are available to choose
from for restricting how much data is used from each sector. This allows for better use of clustered data.
Basic Search Parameters: The first three parameters (PAR1, PAR2 and PAR3) define a general search box
around each block (the search will be refined further in a later panel in the procedure). The fourth parameter
(PAR4), the Max 3D distance, should match the major axis of the ellipsoidal search for the interpolation
to work properly. The major axis is the y axis and the minor axis the x axis, regardless of the longest
measurement. If needed, use program Variogram.exe to convert ellipsoid axes and rotation angles to
represent the y axis (major) as the longest (optional).
Anisotropic distance option: This option can be used to further reduce the influence of composites along
the minor axis. This is an important option while doing an inverse distance interpolation as it will influence
the weight of each composite. This option is less important in a kriging interpolation since the variograms
handle sample weighting.
Code Matching: The last two panels in the MSCompass procedure pintrp.dat offer code matching options
to control what data will be used for interpolating each block. The Block limiting option will restrict the
interpolation calculations to only those blocks containing specific codes (such as for a particular geologic
unit). This is practical when we want to use different interpolation parameters for different geologic domains
in our project. The Code matching option uses only those composites for the interpolation calculations that
have the same code as the model blocks. This method is commonly used for hard boundaries, such as in a
particular geologic domain, and prevents a composite value from a different domain from influencing the
block being calculated (Figure 22).

Figure 22. Example use of

Block limiting and Code
matching. In this example,
only blocks with a Rock code
1, 2, or 3 are interpolated
and composites used to
interpolate the block must
have the same matching
code (in the color scheme on
the right, yellow composites
couldnt interpolate purple
blocks).

Page 20
 Connecting A to B: The modeling path from Assays to Blocks

Variogram limiting options: This option is used for soft boundaries such as demonstrated in the contact
plot of Figure 23. The option is used by picking the variogram limit option (i.e. Rock), and then for each rock
type (codes 1 -6), a variogram value can be entered (for instance, in the example below Rock type 1 has a
variogram value of 0.5). When a block attempts to interpolate from a composite with a Rock Code =1, the
variogram value between the block and the composite has to be less than the value entered in the pane.
Theoretically speaking, higher variogram value means less correlation between the two locations (block
and composite).

Figure 23. Example setup for using the Variogram limiting option. This option is used in the case of soft or transitional boundaries.

Storing Confidence Items: During an interpolation run, the closest composited distance, average composite
distance, number of composites used, and the number of drillholes, can be stored for each block. These
items can be useful for resource classification and confidence analysis. Within the same interpolation run, it
is also possible to store polygonal grade assignments. Polygonally interpolated grades are a good base for
model comparison and can aid in evaluating the reliability of other interpolation methods.
Filter criteria: You can restrict the composites to be used in the calculation by setting up the optional
composite data selection option. On the same panel, the RESET or OMIT options are important when doing
interpolation in passes. If a second pass is being run with more restrictive parameters, using the OMIT option
is mandatory in order to keep existing interpolation values previously calculated.
For resource classification, calculate CLASS codes using the MSBasis procedure modcls.dat - Assign
Model Code by Items Ranges. This procedure can quickly assign a code item in different areas of a block
model based on user-specified ranges. Several classification schemes can be used: For example, using a
combination of composite distance, number of composites, and kriging variance as shown below:

Page 21
Connecting A to B: The modeling path from Assays to Blocks

Measured Resources Indicated Resources Inferred Resources

DIST =< 50m DIST = 51-100 m DIST > 100
and and or
NDH > = 3 NDH > =2 KVAR> 0.8
Also, or
DIST = < 50m Other blocks that cannot be
and classified as indicated
NDH < 3

Block model statistics/validation

After interpolation, model statistics and validation can verify the model interpolation options are
reasonable. Several validation methods can be employed, and for more details, see the 2011 Seminar
workshop: Model validation.
A few common statistical checks:
Point validation via procedure p52401q.dat - check correlation and error of estimation.
Grade Tonnage curves via MSDA - compare IDW and kriging against polygonal methods.
Declustering via MSDA on composite data find the cell size that minimizes the mean and compare
to the model mean.
Swath plots compare swaths from the model and composited data. This tool highlights the grade
and tonnage distributions in the deposit (Figure 24).

Figure 24. Swath plot from model showing tonnage and copper grade (green) with composted copper grade overlaid (red). Histogram
bars show tonnage from model.

Page 22
 Connecting A to B: The modeling path from Assays to Blocks

Multi-Runs
Reproducibility and an audit trail are critical components of a modeling project. The multi-run functionality
in MSCompass allows for the preservation of steps taken during the process, and the ability to quickly
reproduce the project from start to finish. Along with the standard MSBasis procedures, runcmd.dat allows
for other programs to be run inside the multi-run (using command line syntax). MSTorque importing,
exporting, and compositing can also be incorporated into a Multi-Run.

Page 23