MineSight® Tips and Tricks

MineSight® Tips and Tricks

This workshop will highlight a few of the many useful MineSight® 3D (MS3D) and MineSight®
Compass™ (MSCompass) tips and tricks. Most clients should be aware of the overall larger topics as the
workshop only addresses specific details of the topics.
1. General and Viewer
Popup menu - To help organize your menu, you can add as many delimiter lines as needed to split
your commands into groups using the Viewer | Popup menu definition. The delimiter line is the first
line on the Available Functions list (see figure 1a for setup and 1b for result).

Figure 1a. Adding delimiter lines Figure 1b. Resulting menu

Global Hot keys - The L key restarts the last command, the E key saves the edits and continues, the U key
Mining unsets the open edit object, and the key hides the selected data. Also, the regular Microsoft® Windows
Ctrl-A, C, V, and X hot keys are also available. The Ctrl-A can be useful for selecting all objects from a
Software
folder in the Data Manager and for selecting allselection buffer elements from the viewer. For a list of
Solutions all the hot keys, see the MS3D help file.
Since
Show start point - When you don’t have a CAD function active, clicking and holding the left mouse
1970
button gives a read out of the current x, y, and z location; x, y, and z difference; 2D and 3D distance;
and angle change. The values displayed are controlled from the File | Project settings | Status bar.
You can also drop a marker at the start point so it is easier to reference. This is done by File | Project
settings | Properties | Show start point with distance.
Selection properties – If you have multiple objects selected, leaving them all in the selection color
makes it difficult to see who’s who in da zoo. The Selection | Properties | no highlighting will
display them in their original object properties. Figure 2a shows with highlighting and 2b is without
highlighting.

Page 1
MineSight® Tips and Tricks

Figure 2a. Selected data with highlighting. Figure 2b. Selected data without highlighting.
Multiple viewers – If you have multiple viewers and cascade or tile them, each viewer is a limited
size. If you need a larger viewing area for each but want to be able to toggle between them, then you can
cascade them and adjust each to fill almost the full area available (see figure 3). To toggle between viewers,
you just need to click on the required viewer.

Global
Mining
Software
Figure 3. Multiple viewers with maximum viewing area. To toggle, click on the banner or right side. Solutions
Element close object and properties – You can access individual object properties through Element Since
| Properties and also close individual objects through Element | Close Object by clicking on an 1970
element of the required object. You can also close al2l data in the viewer in one step by selecting Element
| Close Object and drawing a box around all of the data. When doing the “global” close, individual
objects can be left open by shift-clicking on them before clicking right.
Materials – Materials are very useful. You can edit a group of materials by selecting them from the
Materials folder, clicking right, and selecting Edit. This will bring up a table as shown in figure 4. You
can then change any of the properties and codes.

Page 2
 MineSight® Tips and Tricks

Figure 4. Materials table from Edit.

There are a number of standard materials that are setup when initializing a MS3D project. The default
material assigned to any new geometry object is Geometry so setting up the default display properties
for geometry can save re-setting the object properties of a new object, i.e., the label and node height, the
faces in a light color, the lines in a darker color, etc.
If you are dealing with a number of model views, then setting the Model View material properties is
also useful. This includes label height, color, line thickness, and line labels.
Important parameter/setup files – Key setup files that should be regularly backed up include:
• Vgalusr8.vr – stores location and size of all dialogs for MS3D and MSCompass. The file is
stored in the following environment variable priority order: HOME, HOMEDRIVE\HOMEPATH,
HKEY_CURRENT_USER, Microsoft® Windows default folder.
• dialogs.ptf\Settings folder – most of the responses for the MS3D dialogs are stored
Global in _msresources\dialogs.ptf. The responses for the newer dialogs are stored in XML
Mining format in the _msresources\Settings folder.
Software • Proj.prj (where proj is the MineSight® project code) – stores all responses including multi-runs
Solutions for MSCompass for each project. Stored in the project folder, this file can also be copied to make
Since your own personal copy to preserve your responses (e.g., comp-dag.prj)
1970
2. Compass Multi-runs
Multi-runs are not only very efficient, they are also very good for ensuring all steps of a task are done
and done in the correct order. The documentation of these is also very important. The following two
multi-run setups will be reviewed to illustrate some of Mintec’s recommendations.
Figure 5. Shows a suggestion for naming key multi-runs by adding a numeric prefix so that the multi-
runs will be listed in the order they should be run.

Page 3
MineSight® Tips and Tricks

Figure 5. List of multi-runs with numeric prefix for run order.

Build model - The “1– build model” multi-run (figure 6) will be reviewed to show documentation
ideas as well as some MSCompass procedures and options of which the clients might not be aware.

Global
Mining
Software
Solutions
Since
1970

Figure 6. “1- build model” multi-run.

Each step in the multi-run is given a name that includes the function type and sequence number. This
makes it easier to document as well as discuss with other users including Mintec tech support. Each step
should have a good description and all external Ascii files should be mentioned. For project workbook

Page 4
 MineSight® Tips and Tricks

documentation, you can just include a screen capture of the multi-run and then describe the steps in
further detail, referencing the type-sequence name.
The runcmd.dat procedure allows the user to run DOS type commands. It can also be used as a
“null” procedure step to add documentation to the multi-run. The first step is purely a documentation
step without any commands being specified in runcmd.dat as shown in figure 7.

Figure 7. Example of runcmd.dat as a documentation step without running any commands.

DH1 tags drillholes that start and end in ore. This should always be run if any thickness interpolation
or surface building is being done so that invalid drillhole zone intervals are not used.
MOD2 (figure 8) shows an example of the new MineSight® version 4.0 external model coding. The
recommended approach when using this is to have a MS3D model view for each coding step and export
the view to an external mscode file. This project has four coding steps: one for the topo solid, one for
the solid of the topo and lowest seam footwall (ftopo), one for coal from the seam polygons, and one for
waste from the same seam polygons. Note that any line starting with rem is a comment so the runcmd.
dat steps can also have additional documentation in them.

Figure 8. MOD2 step for model coding.

MOD4 is needed for the reserve type assignment by distance to the closest composite (i.e., measured,
etc.) because this is a coal project and the actual existence of the seam is the key factor, not whether it was
Global or was not sampled. Some projects are more “grade” driven and the DIST option should be used right in
Mining the grade interpolation step. Some projects are “existence” driven and a separate interpolation should be
Software done to assign the DIST.
Solutions MOD7 and MOD8 (figure 9) are pctrat.dat steps that allow model percentages to be rationalized
Since to ensure that everything balances. The MOD8 step makes sure that all the percentages add up to topo%.
1970 It does this by ensuring the coal percentages cannot change (i.e., they are fixed items that are needed
to add to the total block percentage). The waste percentages are adjusted up or down to maintain the
material balance. They are priority items so the first item (WPCT1) takes the full adjustment. If an
additional adjustment is still required, then the second priority item is adjusted, etc.

Page 5
MineSight® Tips and Tricks

Figure 9. MOD8 step to ensure that all percentages add up to topo%.

MOD10 (figure 10) shows an example of runprg.dat for running a program using an existing
runfile. Note that the runfile has an extension of .run rather than the normal convention of runxxx.
xxx. This is to ensure that it doesn’t accidentally get deleted when doing a cleanup with Microsoft®
Windows Explorer. This step could also have been done with a runcmd.dat using the command:
clyield –fyield.run.

Global
Mining
Software
Solutions
Since
1970

Figure 10. MOD10 step to calculate coal yield using an existing runfile.
MOD13 (figure 11a) is a modcls.dat step for building a new set of codes from existing items. In
this case, it is for combining the seam and reserve type into a new seam/zone item. It uses an external
file (seam.cls, part of which is shown in figure 11b) of the minimum and maximum for each item
(SEAM and DIST) and the code to assign.

Page 6
 MineSight® Tips and Tricks
MOCLS has recently been enhanced with a new AUTO function to build classes using item lists or
increments combinations (figure 11c). It now handles 10,000 combinations and can optionally output a
zone/seam input file for pitres/cmpres.
The building of the codes can sometimes be done with a simple p61201.dat user calculation when
there are just two existing code items that are being combined (e.g., newcode = code1*100+code2).

Figure 11a. MOD13 step to build SMRS codes. Figure 11b. Part of seam.cls file.

Global Figure 11c. Example of modcls.dat AUTO function. Result is 3960 class code combinations.
Mining MOD14 and MOD15 are cmpres.dat total resource runs. A total resource step should always
Software be done after each model build and the resulting report should be renamed to include the date (e.g.,
Solutions total-080505.rpt) and reconciled against the results of the previous run.
Since Project label - It is also recommended that the project label be changed to reflect the new model build
1970 date. This is done using the Compass Project tab, Edit project parameters. The project label appears
on every page of every MSCompass report assisting in determining which reports were generated from
which model version.
MineSight Economic Planner (MSEP) S/R – The “3 – MSEP S/R” multi-run (figure 12) will be
reviewed to show some additional documentation ideas, to show a loop mode multi-run, and to show a
stripping ratio L-G setup.

Page 7
MineSight® Tips and Tricks

Figure 12. “3 – MSEP S/R” multi-run illustrating loop mode.

A regular MSCompass multi-run starts at the first procedure and makes a single top to bottom
pass through each procedure, optionally running individual procedures multiple times. A loop mode
procedure passes through the list of procedures multiple times, running each procedure once in each
pass. The loop mode is generally used when the results from one procedure are needed in the subsequent
procedure. In the MSEP S/R case, the results of setting the NET dollar value in netmod.dat are
needed for msep-design.pyc.
The variables are setup for a loop mode similarly to a regular multi-run. The value for each variable in
run 1 is substituted for all procedures in the first pass. Then run 2, etc.
Note that on figure 13, run 1 is used for documenting the variables and the starting value for the
multi-run is 2, instead of 1. This is a useful documentation tool, especially when there are a large number
of variables involved in a multi-run.

Figure 13. Variable values for MSEP – S/R multi-run.

To do a stripping ratio analysis with MSEP, set all the ore costs to 0 and use $1 for the waste costs.
Setup a model item for each zone that has a value of 1 when the zone is ore in any given block. Use a
price that matches the incremental S/R cutoff and use a factor of 1. This multi-run does an analysis of S/
Rs from 5 to 15. Note that the largest S/R is done first so that the pit generated can be used as a limiting
shell in the next run to reduce run times.
This example is for two seams per block, so netmod.dat is required to set the NET value for each
S/R cutoff.
After the multi-run has completed, the cumulative and incremental reserves can be generated for
each shell using cmpres/pitres.dat and cmpinc/pitinc.dat. The .sum summary files of
all shells can then be summarized into a single .csv file using cmpsum/cmpinc (see figure 14a for Global
cmpsum.dat setup and 14b for results). For L-G summarizing, request totals only. Mining
Note that the raw incremental stripping ratio on the bottom half of the spreadsheet is always between Software
the current shell and the previous one (as it should be). Solutions
Since
1970

Page 8
 MineSight® Tips and Tricks

Figure 14a. Setup for cmpsum.dat. Figure 14b. Results of summarizing.

3. Drillholes
Collar plot – You can get a cleaner looking collar plot with collar symbols by setting up your drillhole
view to display the FROM item with polyline nodes on the 0 cutoff only. Select the node symbol, color,
and size. You can also use Drillhole View Properties | Points | collar. The disadvantage of the Points
option is that it will need to be re-run each time new drilling is added. The advantage is a cleaner plot when
angled holes are involved. The FROM option will put a node on both the start and end of the first interval.
To add a gap between the drillhole id and the symbol, just add a blank in the first delimiter field and
use the Start of hole and Horizontally options.

Figure 15. Setup for Drillhole Collar Plot.

Global Collar Check – You can check the surface drillhole collars against the topo surface utilizing the drape
and free format export tools. Save the drillhole collar points to geometry using a Drillhole View | Points
Mining
with the Attribute points with DH ID option selected. Export the new geometry object to a .csv file
Software
using Export | Survey (Free Form) (figure 16a). Make sure to use the Ignore break code option to
Solutions avoid a blank line between drillholes.
Since
Then select the geometry and drape the points to the topo dtm using Project both directions,
1970 Move elements, and Keep in source object options. Export the result to a second .csv file and
copy the new elevation (which is the draped elevation) to the first .csv file. Do an Microsoft® Excel
difference on the two elevations to produce an .xls file like the one shown in figure 16b.
NOTE: To be 100% sure that the drillholes are both in the same order, sort both .csv files before
merging. Also, if there has been mining, then an original ground surface should be used for original
drillholes only. If possible, the drillholes should be checked against the surface from which they were drilled.

Page 9
MineSight® Tips and Tricks

Figure 16a. Setup for DH Export. Figure 16b. Part of Microsoft® Excel comparison.
Displaying Multiple Drillhole Views – Strips from more than two drillhole views can be displayed by
offsetting the views from each other. This is done by having a dummy item that has the polylines turned
off in all cases. This will allow the shifting of the view. As an example (figure 17), the composite strips are
displayed on the left side, the assay strips on the right closest to the drillhole trace, and the geophysical
log to the right of that. The assays have two 5m strips so the –AI- item of the logs view is set to a width of
10m (with item cutoff polylines off) to “skip over” the assay strips.

Global
Mining
Software
Solutions
Since
1970

Figure 17. Example of setup for viewing three drillhole views.

Page 10
 MineSight® Tips and Tricks

4. Polylines and Surfaces/Solids

Repairing a Surface/Solid – The Check and Condition Surfaces Tool has repair options available
but this can sometimes be cumbersome. If multiple iterations are required, then the Check and
Condition Surfaces Tool will make a new object for each result. Another option is to select the surface/
solid and run the repair steps from the Surface menu one at a time until it is clean. The H hotkey, for
hiding the selection, is useful for identifing the remaining problems.
Clipping solids against a surface – Multiple solids can be clipped against a surface (e.g., mined-out
surface) in one step using Surface | Clip Surfaces and Solids. The recommend method is to copy all
the unclipped solids to a new folder, select them all, and do the clip as show in figure 18. Mintec always
recommends the solids be clipped to the mined-out surface each time the model is rebuilt to ensure
accurate reserves reporting. Making a copy to a new folder preserves the original unclipped solids. Using
this tool is much quicker than the solids intersector when there are multiple solids that need to be clipped.

Figure 18. Clip Surfaces and Solids dialog.

Area and Volume Scripts – Poly2drpt.pyc reports the information on polylines/polygons
including area of polygons. This is useful for reconciling a model build involving polygons. Right after the
model is coded and before any steps that would adjust percentages (like pctrat) are done, a pitres/
cmpres volume run can be done and compared to the poyl2drpt.pyc reported areas multiplied by
the section/plan width.
Similarly, shellrpt.pyc can be used to check solids that are used for model coding. It generates a
.csv file of all solids volumes from a folder and optionally all its sub-folders.
It can also be used for reporting any series of solid volumes, not just model solids. A good example is
end-of-period dyke volumes by internal zone. One client had up to 10 zones in each of 12 periods and
was able to do all the volumes in one run of shellrpt.pyc.
Large Gridded Object (LGO) Import options – The LGO has a number of different options for
Global importing data. This includes importing from another LGO, importing from an existing DTM, importing
Mining 3D point data, and splitting a solid into the upper (hangingwall) and lower (footwall) surfaces. All
importing is done from the Import tab.
Software
Solutions Existing geometry triangulated meshes (DTMs) can be imported directly to the LGO. They can either
Since be used to create a new surface, replace an existing surface, or patch a piece into an existing surface.
1970 Point data can be imported and assigned to the grid nodes using the closest point that falls within
the grid cell (for data denser than the grid spacing), or using a nearest neighbor or octant limiting
interpolation. Note: When importing with the Assign nearest grid point option, if there are gaps in
the point data that are larger than the LGO grid spacing, the resulting LGO surface will have gaps. This
option is strictly for data that is more tightly spaced than the LGO grid size.
Solids can be gridded keeping the very top or very bottom points (not applicable for overturned
solids). The option is available through Import | From geometry as shown in figure 19.

Page 11
MineSight® Tips and Tricks

Figure 19. Example of gridding the bottom (footwall) of a solid using an LGO view.
Splitting closed polygons into hangingwall and/or footwall polylines – Closed polygons can be
split by exporting them to VBM Ascii, running MSCompass procedure VBMBRK, and reimporting
the resulting VBM Ascii file. If the polygons are clockwise, the footwall is kept. If they are counter-
clockwise, the hangingwall is kept. There may be a bit of cleanup as an extra point is sometimes kept
depending upon how sharp the polygon corners are.
Triangulation avoiding flat spots – Certain data sets need to be triangulated with the Minimize flat
faces option to get a proper surface. Examples are topo data that has ridges or gullies, stockpile data, etc.
Figure 20a shows the surface without using the option and figure 20b shows it using the option. The 20a
surface has incorrect flat spots along the ridge.

Global
Mining
Software
Solutions
Since
1970
Figure 20a. Without option. Figure 20b. Surface with minimize flat faces option.

5. Others
Drop Utility Markers – MS3D has a function to drop a marker using Utilities | Markers | Drop
markers. When dropping markers, all the regular snapping functions are available. After a marker has
been dropped, it can also be snapped to. Markers always show up in both 2D and 3D. Markers can be
useful to help avoid clutter by dropping a marker while an object is open and then closing it but still
having a reference to where it was (works well for key locations on surfaces).

Page 12
 MineSight® Tips and Tricks

Gridset perpendicular to polyline – A gridset can be generated perpendicular to a polyline at regular

spacing, at the midpoint of each segment of the polyline, or at the endpoint of each segment. This is
useful for cutting sections through dykes, roads, etc. There is currently one small problem when the
polylines is a 3D line. The planes are generated perpendicular to the line and will thus, not be vertical.
This option will be added in a future release. For now, simply select the polyline, drape it to any level,
generate the gridset, and cancel the selection to restore the original polyline.
Import point data – The recommended approach for importing a large data set of points it to import
them as polylines splitting them at a change of easting, northing, or elevation, or splitting them based on
a number of points. The new object should then be assigned Point material. The Point material has
lines off, nodes on, and has a survey type of point for triangulation. New projects will now have a Point
material setup automatically at initialization.
This approach will reduce the overhead as MS3D keeps information on each element and importing
groups of points to polylines greatly reduces the number of elements.
Pit expansion with variable slopes/berms – Besides the variable slopes and berms for a constant
bench spacing, the pit expansion tool also handles variable benching on different areas of the pit. This is
done by selecting the Use variable sectors by elevation (bench) option from the Optional tab and
selecting the Set Sector Patterns box. The sector patterns allow the user to specify a different set of
slopes and berm widths on each bench. This can make for a lot of data entry, so the sector patterns option
also has a clone option where bench setups can be copied to other benches.
As an example, the west wall can be double benched and the east wall can be triple benched. This will
mean that the bench setup repeats itself every six benches with the following berm setup: none, W, E, W,
none, both. The example is a 12m bench with a pit bottom at 1834. The 1834 bench is setup with the
required sector information. The next five benches are setup copying the sectors from 1834 and changing
the slope and berm information as needed. Each of the first six benches is then cloned (click left, then
right on the bench from the elevations table) with a spacing of 72 (for six benches). Figure 21 shows the
setup with the cloning and the resulting pit.

Global
Mining
Software
Solutions
Since
1970
Figure 21. Variable slopes and berms by bench.
Quick Viewer Movement – If you are viewing a large amount of data, the movement when zooming,
panning, and/or rotating can be slow and “chunky”. To alleviate this, you can use Viewer | Quick Viewer
Movement. This option hides most of the data while you move it, making for faster adjustments.
Disable Mouse Rotation – Certain mouse types sometimes accidentally cause a minor unintended
rotation. (e.g., working in a plan view and having a slight movement to a skewed view). This can lead to
placing/moving points to an incorrect location. The viewer can be locked to a certain view using Viewer
properties | Disable Mouse Rotation to alleviate this problem.

Page 13