MineSight®

Proprietary Software: Mintec, inc. VBM - INTRODUCTION SECTION

VARIABLE BLOCK MODEL OPERATIONS

MINESIGHT VBM-Series Programs Program Summaries
The Variable Block Modeling (VBM) system is used to store and M640V1 - Interpolate Seam Thick from Composites
retrieve point data in MINESIGHT®. The point data is stored
in a MINESIGHT® Data File called the VBM file and is only This program is used to interpolate a seam top or bottom into
available through MINESIGHT® routines. a section VBM using true or vertical thickness from sorted
drillhole composites.
Point data is generally comprised of X,Y coordinate pairs, but
3-D point data (XYZ coordinate triplets) can also be stored. Point M649V1 - Load Digitized Data to a VBM File
data may be digitized geology on section, digitized geology on
plane, topography, generated or digitized mine designs, survey This program reads digitized point data and enters the data into
pickup data, etc. Some uses for this data are: a VBM file. The plane and feature code for each string of points
are used to reference the data.
Data Type Uses
M650AR - Outline and Average Reserves
Geology by section Plot cross-sections
Calculate bench intersections This program is designed to aid the geologist in the calculation
Plot bench intersections of sectional or plan reserves.
Calculate Block%
M650BH - Interactive Ore Control Graphic Planner
Geology by bench Plot bench maps
This program is a highly interactive program designed to aid
Calculate section intersections
the ore control engineer in short range planning by the use
Plot section intersections
of digitized ore/waste or routing polygons. It is one of the
Calculate 3-D block codes
MINESIGHT®/ Graphical Interface (MGI) programs.
Calculate Block%
M650DL - Dragline Range Diagrams
Topography Plot plan or sections
Calculate 2-D topo matrix This program is used to slice sections, design range diagrams
Clip pit expansion plots and plot or report the results.

Mine designs Plot plan or section M650ED - Interactive VBM Editor (Version 2)
Calculate block partials
This program is an interactive program used to edit VBM files.
For more information about the VBM, see the Technical Section.
M650IP - Interactive Graphics Planner

This program is designed to aid the mining engineer in the

planning and scheduling of short range mine production.

M650PT - Pit Expansion

M650PT is an interactive program used to do pit expansion.

It is one of the MINESIGHT Graphical Interface Programs.
M650PT geometrically expands a pit from some defined initial
shape. All bottom bench outlines and pushbacks for a pit need
to be digitized

M650SV - Survey Editing

This program is used to edit data in a survey format.

Revised: 13-February-10 Page VBM-i

 MineSight®
VBM - INTRODUCTION SECTION Proprietary Software: Mintec, inc.

M651V1 - Normalize Node Points of VBM Data M654V2 - Plot VBM Pits Merged with VBM Topo (M122)

This program normalizes VBM data by setting node points equal This program is used to create an M122 plot file that contains a pit
if the differences are within a specified tolerance. design merged with topography. The pit design and topography
must be stored in the same VBM file.
M651V2 - Combine/Add VBM Features
M654V3 - Plot VBM Pits Clipped by File 13 Topography
This program is used to add features together from the VBM (M122)
file. The combined feature is stored back in the same VBM file.
This program is used to create an M122 plot file containing a pit
M651V4 -Update Line Segments in the VBM design from the VBM file truncated by the File 13 topographic
matrix. The topography contours are not displayed.
This program updates pit or topo contours within the VBM file.
It uses three functions to perform the updates: line splicing, M654V5 - Plot Clipped VBM Data (M122)
feature deletion and copying.
This program extracts data from a VBM file and plots the data
M652V1 - List a VBM Model Index either inside or outside a closed feature. The closed feature is
stored in one plane only.
This program outputs the VBM index. The index consists of
feature codes, number of points and feature end points for all M655V1 - Calculate Plane Intersections from VBM Data
features on all planes.
This program extracts specified features from a series of specified
M653AC - Convert VBM Data to AutoCAD DXF Format cross-section VBM planes and determines the bench intersection
points based upon a constant elevation. An M122 plot file for
This program converts VBM data to an AutoCAD DXF input plotting or previewing is output.
file. The program will generate a DXF file for Release 10 of
AutoCAD that is true 3-D. Previous versions of AutoCAD M655V2 - Calculate Section Intersections from VBM Data
are also supported in a 2-D format with extrusion in the third
dimension. This program extracts specified features from a series of specified
VBM planes and determines the section intersection points with
M653V0 - Extract VBM Data a specified section. An M122 plot file for graphics or previewing
is output.
This program outputs an ASCII file of VBM data which can then
be used for special programs or transfer to another computer. M657V1 - Extract Intersections of VBM Data with a Grid

M653V1 - List VBM Data in Report Format This program is used to calculate the intersection elevation of
specified grid lines with digitized VBM data (usually contours).
This program lists the VBM file. These intersections are written to an ASCII file for grid
interpolation by other routines.
M653V2 - List VBM and Utility Functions
M657V2 - Create Gridded Data From Intersections
This program is used to print, dump or delete features from
a VBM. Only one of these functions may be performed in a This program takes the output from M657V1 (after it has been
given run. sorted by northing and easting) and computes the grid elevations
for topography. The grid elevation values can be input to the
M654V0 - Plot VBM Contour Data in Plan or Section (M122) topography file (File 13) using M630V1.
This program is used to extract section/bench data from the M658V1 - Plot Cross-Sections from VBM (M122)
VBM file and create an M122 plot file. It centers all labels
within the lines. This program takes contours stored in the VBM file and generates
an M122 plot file containing the cross-section views at specified
M654V1 - Plot VBM Point Data in Plan or Section (M122) section lines. This program is useful for pit designs, topography,
and rationalizing seam structure between plan and section.
This program is used to extract specified features from a specified
plane from the VBM and create an M122 plot file. Various
labeling options are available.

Page VBM-ii Revised: 13-February-10

MineSight®
Proprietary Software: Mintec, inc. VBM - INTRODUCTION SECTION

M658V2 - Plot Pit Cross-Sections from VBM (M122) M665V1 - VBM Cut Generator

This program is used to generate a cross-section through a pit This program is used to generate a specified number of mining
stored in the VBM file. The topography can also be plotted at cuts from a series of coordinate points which define some mining
the same time. limit. The cut geometry is stored back into the VBM file.

M658V3 - Extract Features from a VBM File M667V1 - Compute Model Codes and/or Partials from VBM
Outlines
This program allows the extraction of points for specified
features from a plan or section VBM along specified section or This program calculates block codes and/or block partials
elevation lines. (percentages) using geology data from the VBM file. Codes can
be assigned to a block either as codes at a center of a block or
M658V4 - Reformat M658V3 Points as a majority code.
This program sorts a file output by M658V3 and converts it into
a format for addition to a sectional VBM.

M658V5 - Slice Features from Section VBM VBM Technical Section

This program is used to slice intersection points from a section VBM Data
VBM for posting to plan for plotting and/or contouring.
VBM Orientation
M659V1 - Compute Block Partials from VBM Features
VBM Data Entry
This program takes a feature from the VBM file and determines
the percentage of each mine model block that is within the
feature. This is a necessary step for generating reserves within
a pit design.

M659V2 - Calculate Waste Dump Volumes from VBM Data

This program uses topography and dump outlines stored in the

VBM file to compute dump area, volume and tonnage.

M661V1 - Interpolate Intermediate VBM Planes

This program will interpolate linear features into a new VBM

plane between existing VBM planes.

M662V1 - Truncate Mining Cuts Stored in the VBM

This program is used to exclude areas from mining cuts. The

cuts to be truncated must be in separate planes in the VBM file.

M663V1 - Compute Seam Length for 3-D Blocks from VBM

Data

This program computes the length of a VBM feature within each

block in a 3-D Block Model.

M664V1 - Compute Outcrop Intersections for VBM Data

This program computes the intersection of two VBM features

and creates an M122 plot file.

Revised: 13-February-10 Page VBM-iii

 MineSight®
VBM - INTRODUCTION SECTION Proprietary Software: Mintec, inc.

Page VBM-iv Revised: 13-February-10

MineSight®
Proprietary Software: Mintec, inc. M640V1-INTERPOLATE SEAM THICKNESS FROM COMPOSITES

M640V1 INTERPOLATE SEAM THICKNESS INTO VBM

USING DRILLHOLE COMPOSITES
PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS
M640V1 is used to interpolate a seam top or bottom into a section In M640V1, the original seam top (or bottom) doesn’t have to
VBM using true or vertical thickness from the sorted drillhole be previously clipped at topo and fault features. This program
composites (File 8). If interpolating the top, the thickness is clips/extends both the original feature and the new interpolated
added to the bottom. If interpolating the bottom, the thickness feature. The extending distance is a user controlled parameter
is subtracted from the top. The interpolated seam top (or bottom) as is the number of points to check for clipping features.
can be stored as an open feature, or combined with the seam
bottom (or top) to make a closed feature (for using in M667V1). Before interpolating the new feature, the old interpolated features
should be deleted, using the choices in IOPs 13, 14 and 17. As
M640V1 also clips and extends the seams to up to 50 topography an example, the seam top is modelled in the VBM as feature
and fault features on the section. This ensures that the seam 1nnn where nnn is the feature code for each seam. An
isn’t in the air and that it doesn’t fall short of the subcrop. interpolation was done to create a seam bottom and make a closed
feature of it with a code of 1nnn minus 1000. (i.e., leaving a
PROGRAM FLOW DIAGRAM closed feature using the right side code only). To delete these
old features, set IOP17 to 2, and IOP13 and IOP14 to 1 and 899.
RUN FILE: This will delete all the old closed features but leave the original
- Seams to interpolate
open tops intact.
- Interpolation parameters
-Options for storing, extending, Since M640V1 modifies and deletes VBM data, it is strongly
clipping suggested that a backup copy of the VBM file be made prior to
running this program.

The interpolation is done to each point on the selected features.

If using a true thickness, the thickness is applied to the original
feature perpendicular to the dip of the seam at that point. The
INPUT: CALCS: composites used for each interpolation can be based upon the
- Old seam features are deleted
seam code only or both the seam and fault codes.
- PCF
- VBM - Seams are interpolated,
- Sorted drillhole clipped/ extended, stored The interpolated feature can be stored as an open feature or
composites combined with the original feature to make a closed feature for
use in M667V1 for 3-D block model building.

The sections can be at any orientation. If interpolated to E-W or

N-S sections, the sections can be specified using PAR8-10. If
interpolating to non-orthogonal sections, then the section plane
OUTPUT: number, x-origin, y-origin, azimuth, and length must be specified
after the END statement, one section per line.
- Updated VBM
- Optional ASCII VBM-ready file
- Printer Output File

Revised: 8-June-01 Page 640-1

 MineSight®
M640V1-INTERPOLATE SEAM THICKNESS FROM COMPOSITES Proprietary Software: Mintec, inc.

Page 640-2 Revised: 8-June-01

MineSight®
Proprietary Software: Mintec, inc. M640V1-INTERPOLATE SEAM THICKNESS FROM COMPOSITES

M640V1—INTERPOLATE SEAM THICKNESS FOR VBM FROM

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-640V1 10=filename 8 (or 9)=filename 25=filename;

MEDS-640V1 20=filename 3=filename
where

MEDS-640V1 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
8 = the name of the SORTED COMPOSITE FILE -OR-
9= the name of the UNSORTED COMPOSITE FILE
25 = the name of the VBM GEOMETRY FILE
20 = the name of the ASCII Output File (If IOP6=1)
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = FIRST COMPOSITE DATA UNIT TO ACCESS

IOP2 = LAST COMPOSITE DATA UNIT TO ACCESS (default = last composite data unit)

IOP3 = 1 OCTANT SEARCH

= 2 QUADRANT SEARCH

IOP4 = MAX # OF COMPOSITES PER OCTANT/QUADRANT (default = 1)

Note: IOP4 used if IOP3 > 0.

IOP5 = MIN # OF QUADRANTS (OCTANTS) WITH COMPOSITES (default = 1)

Note: IOP5 used if IOP3 > 0.

IOP6 = 0 OMIT OPENING A VBM OUTPUT FILE

= 1 OPEN A VBM READY OUTPUT FILE

IOP7 = MAX # OF COMPOSITES TO INTERPOLATE (default = none)

Note: Used ONLY if IOP3 = 0.

IOP8 = 0 INTERPOLATE SEAM TOP

= 1 INTERPOLATE SEAM BOTTOM

IOP9 = 0 STORE INTERPOLATED SEAM AS OPEN FEATURE

= 1 STORE INTERPOLATED SEAM AS CLOSED FEATURE

IOP10 = 0 USE 2D DISTANCE FOR SEARCH AND INTERPOLATION (default)

= 1 USE 3D DISTANCE FOR SEARCH INTERPOLATION
Note: 3D distance will automatically be used when limiting number of composites per hold (IOP37 > 0).

Revised: 11-May-07 Page 640-3

 MineSight®
M640v1-INTERPOLATE SEAM THICKNESS FROM COMPOSITES Proprietary Software: Mintec, inc.

IOP11 = 0 WRITE TO VBM

= 1 DO NOT WRITE TO VBM

IOP12 = CONSTANT TO ADD TO SEAM FOR TOP/BOTTOM

IOP13 = MIN FEATURE TO DELETE (use with IOP17)

IOP14 = MAX FEATURE TO DELETE (use with IOP17)

IOP15 = 0 HONOR FAULT BOUNDARIES FOR MATCHING COMPOSITES

= 1 IGNORE FAULT BOUNDARIES
= 2 FAULTS ARE NOT APPLICABLE

IOP16 USED FOR MATCHING SEAM CODES FROM VBM TO COMPOSITES

= 0 USE SEAM CODES AS LLL SIDE OF FEATURE (i.e., fault is RRR)
= 1 USE SEAM CODES AS RRR SIDE OF FEATURE
= 2 USE SEAM CODES AS FULL FEATURE CODE

IOP17 USED FOR MATCHING FEATURES TO DELETE (i.e., when using IOP13-IOP14)
= 0 USE SEAM CODES AS LLL SIDE OF FEATURE
= 1 USE SEAM CODES AS RRR SIDE OF FEATURE
= 2 USE SEAM CODES AS FULL FEATURE CODE

IOP18 = 0 READ SEAMS AS A LIST AFTER END STATEMENT

= 1 READ SEAMS AS A RANGE FROM IOP19-IOP20

IOP19 = MIN FEATURE TO SELECT (if IOP18=1)

IOP20 = MAX FEATURE TO SELECT (if IOP18=1)

IOP21 = 0 INTERPOLATE VERTICAL THICKNESS

= 1 INTERPOLATE TRUE (PERPENDICULAR) THICKNESS

IOP22-IOP31 = TOPO/FAULT FEATURE CODES FOR EXTENDING/CLIPPING FEATURES

IOP32 = MAX NUMBER OF POINTS TO CHECK FOR CLIPPING (default=5)

IOP33 = 0 KEEP ALL FEATURES EVEN IF ALL POINTS HAVE 0 THICKNESS
= 1 DON’T KEEP FEATURES IF ALL POINTS HAVE 0 THICKNESS

IOP34 = 0 READ SECTION AND ORIENTATION INFO AFTER END STATEMENT

= 1 SECTIONS ARE E-W (get from PAR8-10)
= 2 SECTIONS ARE N-S (get from PAR8-10)

IOP35 = MIN FAULT CODE TO USE (IOP16 & IOP17 must be 0 or 1)

IOP36 = MAX FAULT CODE TO USE

IOP37 = 1 ONLY USE CLOSEST POINT FROM EACH COMPOSITE. IF USING IOP37=1 THEN THE
ELEVATION ITEM (ELEV.) MUST BE SPECIFIED AFTER THE NORTH ITEM ON THE
GET08 LINE.

IOP38 = 0 USE IOP22—31 FAULT/TOPO CODES AS INDIVIDUAL CODES

= 1 USE IOP22—23 AS A RANGE FOR SELECTING FAULT/TOPO CODES
AND THEN USE IOP24—31 AS INDIVIDUAL CODES

IOP39 = OPTIONAL FACTOR TO ADD TO COMPOSITE SEAM# TO MATCH VBM SEAM#

Page 640-4 Revised: 11-May-07

MineSight®
Proprietary Software: Mintec, inc. M640V1-INTERPOLATE SEAM THICKNESS FROM COMPOSITES

PAR1 = X SEARCH DISTANCE (Default=500)

PAR2 = Y SEARCH DISTANCE (Default=500)
PAR5 = INVERSE DISTANCE POWER (Default=2)

PAR6 = MINIMUM MINEABLE COAL THICKNESS

PAR7 = DISTANCE FOR EXTENDING SEAMS TO TOPO FEATURE

PAR8 = START SECTION PLANE NUMBER FOR E-W OR N-S SECTIONS

PAR9 = END SECTION PLANE NUMBER FOR E-W OR N-S SECTIONS
PAR10 = SECTION SPACING FOR E-W OR N-S SECTIONS
PAR11 = 1 ELIMINATE WRAP BACK (OVERLAPS, CURLY Q’S)

PAR12 = MIN DISTANCE TO USE FOR INVERSE DISTANCE CALCULATION.

If distance is less than PAR12, then (1/PAR12) will be used (default = 1).

GET08 = LABELS OF ITEMS TO BE RETRIEVED FROM FILE 8 -OR-

GET09 = LABELS OF ITEMS TO BE RETRIEVED FROM FILE9:
REF# EAST NORTH ELEV. LNGTH SEAM FAULT
If 2D search:
GET08 = REF# EAST NORTH LNGTH SEAM FAULT
or
GET09 = REF# EAST NORTH LN GTH SEAM FAULT
If 3D search:
GET08 = REF# EAST NORTH ELEV. LNGTH SEAM FAULT
or
GET09 = REF# EAST NORTH ELEV. LNGTH SEAM FAULT

NOTE: 1) All items except 3-D elevation and fault are mandatory.
2) Composites can be further filtered/selected by using ITM# = Item RANGE/OMIT min max
and adding the item name to the end of the GET08 list.

END

4. SEAM CODE LINES (if IOP18=0)

List the allowable seam codes—Max 100, 10 per line; last code = –1

5. SECTION AND ORIENTATION LINES (if IOP34=0)

section vbm id, xorigin, yorigin, azim, distance (if IOP34=0)

Revised: 11-May-07 Page 640-5

 MineSight®
M640v1-INTERPOLATE SEAM THICKNESS FROM COMPOSITES Proprietary Software: Mintec, inc.

M640V1 SAMPLE RUN FILE

MEDS-640V1 10=[Link] 25=[Link] 8=[Link];
MEDS-640V1 3=[Link]
** INTERPOLATE SEAM THICKNESS TO VBM

USR = ABC

IOP1 = 10 /COMPOSITES TO USE

IOP6 = 0 /1=OPEN A VBM READY OUTPUT FILE
IOP8 = 1 /0=INTERPOLATE SEAM TOP, 1=BOTTOM
IOP9 = 1 /0=STORE INTERPOLATED SEAM AS OPEN FEATURE, 1=CLOSED
IOP11 = 0 /0=WRITE TO VBM, 1=DON’T
IOP12 = -1000 /CONSTANT TO ADD TO SEAM FOR TOP/BOTTOM

IOP13 = 10 /MIN FEATURE TO DELETE

IOP14 = 899 /MAX FEATURE TO DELETE
IOP15 = 2 /0=TO HONOR FAULT BOUNDARIES,1=IGNORE,2=NA
IOP16 = 1 /0=USE SEAM AS LLL FOR MATCHING COMPS, 1=RRR, 2=FULL
IOP17 = 2 /0=USE SEAM AS LLL FOR DELETING, 1=RRR, 2=FULL
IOP18 = 1 /0=READ SEAMS AS A LIST AFTER END STATEMENT, (use with IOP17)
/1=USE IOP19-IOP20

IOP19 = 010 /MIN FEATURE TO SELECT (if IOP18=1)

IOP20 = 899 /MAX FEATURE TO SELECT (if IOP18=1)

IOP21 = 1 /0=INTERPOLATE VERTICAL THICKNESS,1=TRUE THICKNESS

IOP22 = 979 999/TOPO FEATURE CODES FOR CLIPPING

IOP34 = 1 /1=SECTIONS ARE E-W

PAR1 = 350 /X SEARCH DISTANCE

PAR2 = 350 /Y SEARCH DISTANCE
PAR5 = 1.2 /INVERSE DISTANCE POWER
PAR6 = 0. /MINIMUM MINEABLE THICKNESS
PAR7 = 50 /DISTANCE FOR EXTENDING SEAMS TO TOPO FEATURE

PAR8 = 36000 40000 25 /START,END, SPACING OF SECTIONS

GET08 = REF# EAST NORTH LNGTH SEAM

END

HOW TO DEBUG AN M640V1 RUN

1. Required File 8 item XXXXXX is missing

This message will appear, listing all the missing items, if you have left some out of the GET08 line.

2. Check the MineSight® error messages in the Appendix.

Page 640-6 Revised: 11-May-07

MineSight®
Proprietary Software: Mintec, inc. M649V1 - LOAD DIGITIZED DATA TO A VBM FILE

M649V1 LOAD DIGITIZED DATA TO A VBM FILE

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M649V1 reads digitized point data and enters the data into a M649V1 is used to load point data into VBM MineSight® Data
VBM file. The input file is called a VBM-ready file. The plane Files (File 25).
and feature code for each string of points are used to reference
the data. Several options are available that control how data is to be
loaded into the VBM file. The input data can be in the run file
or it can be in a separate file. The data can be read in and listed
but not loaded to the VBM file. This may be useful as a check
PROGRAM FLOW DIAGRAM to make sure that feature codes and plane numbers have been
entered correctly.
RUN FILE:
When IOP3=0, point data that is being loaded will be the initial
- Format data for each plane. If data already exists for that plane, the
- Load options
- Window specification existing data will be deleted. If you want to add features to an
existing plane, set IOP3=1.

Extraneous data points (i.e., those points on a straight line which

are not necessary to maintain the curvature of a feature) can
be deleted with IOP4 = 0. This option is useful in reducing the
amount of storage in the VBM file.
INPUT: CALCS:
There is also an option, IOP5 = 0 to combine strings of points
- PCF - Read ASCII digitized data
with the same feature code. When points are digitized, it is
- VBM-ready file - Load it into the VBM file
- File 25 difficult to repeat the exact point. Often, two strings that should
be combined into one will have a small error when comparing
points that should coincide. PAR2 is the tolerance for combining
strings. IOP11 allows you to either average the endpoints when
combining or simply connect them. All strings with the same
feature code are compared to see if the end points are coincident
within the tolerance. PAR2 should be in user units.
OUTPUT:
To force each feature to close, set IOP7=1. Feature closure is
- Updated File 25
- Printer Output File
accomplished by copying the first data point and appending it
to the feature after the last point.

If the VBM file was initialized with a precision of <1.0, then real
plane numbers can be entered. When IOP10=1, M649V1 expects
to read the plane number as a real value from the input data. The
real value will be stored according to the precision of the VBM.

By default, VBM input data is read in free format. However, you

may specify a format (FMT1) which can be used to read data
from a file that has extraneous data fields (i.e. output from Talos/
Calcomp digitizer). All of the fields in FMT1 must be real (i.e.
2F10.0). Another command allows coordinate data to be input
as either east then north (CMD=READ EAST NORTH) or north
then east (CMD=READ NORTH EAST). A dummy field can also
be input with the line CMD=READ DUMMY EAST NORTH.
The dummy field may appear as any of the fields. Dummy data
is read but not processed. It is used to skip fields.

Revised: 5-November-11 Page 649-1

 MineSight®
M649V1 - LOAD DIGITIZED DATA TO A VBM FILE Proprietary Software: Mintec, inc.

Points that are outside the VBM file limits or the optional data
window will be clipped at the boundary.

NOTE: Zero (0) is not a valid feature code. An error will result
if the program reads a feature code of 0.

Page 649-2 Revised: 5-November-11

MineSight®
Proprietary Software: Mintec, inc. M649V1 - LOAD DIGITIZED DATA TO A VBM FILE

M649V1 LOAD DIGITIZED DATA TO A VBM FILE

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-649V1 10=filename 25=filename 19=filename;

MEDS-649V1 3=filename
where

MEDS-649V1 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM GEOMETRY FILE
19 = the name of the INPUT FILE OF DIGITIZED DATA (if IOP1>0)
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = 0 DATA IS IN RUN FILE

> 0 DATA IS IN SEPARATE FILE

IOP2 = 0 WRITE TO VBM FILE

= 1 DO NOT WRITE TO VBM FILE

NOTE: IOP2 =1, checks input data for errors only (i.e., out of range values). Use in conjunction with I-O=2.

IOP3 = 0 INITIAL FILE ENTRY (OR OVERWRITE)

= 1 UPDATE BY APPENDING DATA TO PLANES
NOTE: If you use the overwrite option (IOP3 =0) on an existing VBM file, only planes with new input data
will be overwritten. For example, suppose you have an existing VBM with feature 901 on plane 2800 and
features 300 and 400 on plane 2900. If the overwrite option is used and your new input data contains only
feature 901 on plane 2900, then the resulting VBM file will have the original feature 901 on plane 2800 and the
new feature 901 on plane 2900. The original data for features 300 and 400 on plane 2900 will be completely
overwritten.

IOP4 = 0 DELETE EXTRANEOUS POINTS

= 1 DO NOT DELETE
NOTE: This is for removing feature points that do not contribute to the feature definition. For example, a string
of collinear points. This option is not available for the 3-D VBM.

IOP5 = 0 COMBINE STRINGS OF POINTS (FEATURES) WITH LIKE FEATURE CODES

= 1 DO NOT COMBINE STRINGS
IOP6 = 0 DO NOT PRINT DETAIL
= 1 PRINT DETAILED OUTPUT

Revised: 31-January-00 Page 649-3

 MineSight®
M649V1 - LOAD DIGITIZED DATA TO A VBM FILE Proprietary Software: Mintec, inc.

IOP7 = 0 DO NOT CLOSE FEATURES

= 1 CLOSE ALL FEATURES (SUCH AS FOR PITS)

IOP9 = 0 READ DATA AS FREE FORMAT

= 1 READ DATA USING FMT1 FORMAT

IOP10 = 0 CLOSE FEATURE IF IOP5 =1 AND ENDPOINTS ARE WITHIN TOLERANCE (PAR2)
= 1 DO NOT CLOSE FEATURE
NOTE: IOP10 =1 avoids features closing on themselves.

IOP11 = 0 AVERAGE ENDPOINTS WHEN COMBINING STRINGS

= 1 DO NOT AVERAGE ENDPOINTS (CONNECT ENDPOINTS)

IOP12 = 1 SET DEFAULT ORIENTATION TO WE

= 2 SET DEFAULT ORIENTATION TO SN
= 3 SET DEFAULT ORIENTATION TO PLANAR
= 4 SET DEFAULT ORIENTATION TO NON-ORTHOGONAL
NOTE: IOP12 is only available for expanded-limit VBM files (see VBM Technical Section). Additional
parameters are set with PAR35-40.

IOP13 = 0 USE ORIENTATION SPECIFIED ON THE FEATURE HEADER LINE, IF ANY.

= 1 REMOVE INDIVIDUALLY-SPECIFIED ORIENTATION FOR ALL PLANES IN THE VBM
= 2 REMOVE INDIVIDUALLY-SPECIFIED ORIENTATION FOR ALL PLANES SPECIFIED IN THE
DIGITIZED DATA
NOTE: IOP13 is used to remove individually-specified orientation and allow planes to use the default plane
orientation. IOP13 cannot be used on original-limit VBM files.

IOP14 = 0 DO NOT ACTIVATE THIS OPTION

= -1 RENAME VBM CODE BASED ON EQUIVALENT CODE ON INPUT
READ EQUIVALENT CODE AFTER “END” LINE
= N>0 STORE FEATURE CODE AS N REGARDLESS OF INPUT CODE

IOP15 = 0 DO NOT READ FEATURE SEQUENCE NUMBER

= 1 READ FEATURE SEQUENCE NUMBER
NOTE: It’s possible to create a VBM-ready file where the feature sequence number is appended on the Header
Line (e.g., IOP7 =1 in M653V0). IOP15 is used to assign this sequence number to the corresponding feature
when the feature is processed in M649V1. Retaining the sequence number is important if, for example, you are
converting an original-limit VBM to an expanded-limit VBM and you need to preserve the feature-sequence
number correspondences in a Cut Cross Reference file (see M650IP).

If IOP15 =1, then EACH feature must have a sequence number.

You cannot append (IOP3 = 1) a feature and its sequence number to a plane on which that particular feature
code/sequence number combination already exists.

When reading both a sequence number (IOP15 = 1) and the VBM orientations, the sequence number should be
inserted at the end of the feature header line.

Page 649-4 Revised: 31-January-00

MineSight®
Proprietary Software: Mintec, inc. M649V1 - LOAD DIGITIZED DATA TO A VBM FILE

IOP16 = 0 ALLOW UP TO 99 FEATURES WITH THE SAME CODE ON A SINGLE PLANE

= 1 IF THERE ARE MORE THAN 99 FEATURES ON A SINGLE PLANE, THEN GIVE
THE ADDITIONAL FEATURES A SEQUENCE NUMBER OF 99
NOTE: The extra feature with sequence number 99 cannot be accessed by most MINESIGHT® programs.

IOP17 = 0 ONLY DIN ANGLES (PAR39 & 40) ARE TAKEN FROM THE RUN FILE. PLANE
AZIMUTH AND DIP ARE COMPUTED ACCORDING TO THE CONVERSION TABLE
FROM THE VBM TECHNICAL SECTION
= 1 ONLY DEFAULT PLANE ANGLES ARE READ FROM THE RUN FILE. DIN ANGLES
ARE COMPUTED ASSUMING THAT DIN IS ORTHOGONAL TO THE PLANE AND
X-pln, Y-pln and DIN MAKE RIGHT-HANDED ORIENTATION OF THE SPACE (PAR 32 & 33)
= -1 SIMILAR TO IOP17=1 BUT THE ORIENTATION WILL BE LEFT-HANDED (PAR 32 & 33)
= 2 BOTH PAIRS OF ANGLES (ALL FOUR PARS, PAR 32 & 33, PAR 39 & 40)
ARE TAKEN FROM THE RUNFILE

IOP18 = 0 ALL INDIVIDUAL ORIENTATION DATA WILL BE STANDARDIZED FOR ORTHOGONAL

AND VERTICAL PLANES
= 1 READ ALL INDIVIDUAL ORIENTATION DATA AS IS (used if IOP13 = 0)

FMT1 = INPUT DATA FORMAT (If IOP9 =1)

Example: (2F10.0) DEFAULT=FREE FORMAT

Specify X & Y input positions by:

CMD = READ field1 field2 (optional)

(default=READ EAST NORTH)
NOTE: Field1, etc. can be EAST or NORTH for pertinent data and anything else for “dummy” fields (e.g.,
CMD = READ DUMMY EAST NORTH). Must match the number of items on the FMT1 line.

Specify X, Y & Z input positions by (for 3-D VBM):

CMD = READ field1 field2 field3

NOTE: To specify field location for X & Y coordinates other than 1st or 2nd, respectively, enter the CMD line.
For example, “CMD = READ DUMMY EAST NORTH” to read three fields with X in the second field and Y
in the third field.

PAR2 = TOLERANCE FOR COMBINING STRINGS WITH SAME FEATURE CODE

(default = 5.0/precision of coordinates)

PAR3 = CONSTANT TO ADD TO X COORDINATES (default=0.0)

PAR4 = CONSTANT TO MULTIPLY THE X COORDINATE (default=1.0)

PAR5 = CONSTANT TO ADD TO Y COORDINATES (default=0.0)

PAR6 = CONSTANT TO MULTIPLY THE Y COORDINATE (default=1.0)
NOTE: Constants are applied only to the map coordinates read for rotation.

PAR11 = MINIMUM X COORDINATE FOR DATA WINDOW

PAR12 = MAXIMUM X COORDINATE FOR DATA WINDOW

Revised: 31-January-00 Page 649-5

 MineSight®
M649V1 - LOAD DIGITIZED DATA TO A VBM FILE Proprietary Software: Mintec, inc.

PAR13 = MINIMUM Y COORDINATE FOR DATA WINDOW

PAR14 = MAXIMUM Y COORDINATE FOR DATA WINDOW
NOTE: Defaults for PAR11-14 are File 25 limits.

PAR15 = TOLERANCE FACTOR FOR EXTRANEOUS POINT DELETION

NOTE: As PAR15 decreases, fewer points will be deleted. Reasonable PAR15 values for X,Y coordinates in
the ten thousand range are from 0.02 - 0.05.

Allow translation/dilation of coordinates independent of 4-point set-up

PAR23 = CONSTANT TO ADD TO X COORDINATES

PAR24 = CONSTANT TO MULTIPLY X COORDINATES
PAR25 = CONSTANT TO ADD TO Y COORDINATES
PAR26 = CONSTANT TO MULTIPLY Y COORDINATES
NOTE: These constants are applied before the rotation based on the 4-point set up.

PAR32 = DEFAULT PLANE AZIMUTH (used only if IOP12=4 and IOP17>0)

PAR33 = DEFAULT PLANE DIP (used only if IOP12=4 and IOP17>0)
PAR34 = PLAN NUMBER MULTIPLIER FOR NON-ORTHOGONAL DEFAULT ORIENTATION (Default= 1)
(used only if IOP17>0)
PAR35 = STARTING PLANE FOR DEFAULT VBM ORIENTATION (required if IOP12 > 0)
PAR36 = X-ORIGIN OF NON-ORTHOGONAL DEFAULT VBM ORIENTATION
PAR37 = Y-ORIGIN OF NON-ORTHOGONAL DEFAULT VBM ORIENTATION
PAR38 = Z-ORIGIN OF NON-ORTHOGONAL DEFAULT VBM ORIENTATION
PAR39 = AZIMUTH FOR NON-ORTHOGONAL DIRECTION OF INCREASING NUMBERING (DIN)
PAR40 = DIP FOR NON-ORTHOGONAL DIRECTION OF INCREASING NUMBERING (DIN)

NOTE: PARs 32 thru 40 are required for non-orthogonal default orientation (IOP12=4). Otherwise they are
unused. Zero is a legitimate value for PARs 32, 33 and 35 thru 40.

The Plane Number Multiplier (PAR34) is used to convert a plane number to the distance the plane is located
away from the default origin.

See the VBM Technical Section of the DOC.

END

4. NUMBER OF CODES LINES (free format, if IOP14=-1)

ncode
where

ncode = number of geology/feature codes that will be specified by the Feature Codes Lines (1-50)

Page 649-6 Revised: 31-January-00

MineSight®
Proprietary Software: Mintec, inc. M649V1 - LOAD DIGITIZED DATA TO A VBM FILE

5. FEATURE CODES LINE (free format, if IOP14=-1)

codes
where

codes = geology/feature codes to be used (max=50)

NOTE: Codes are feature codes from the ASCII VBM (file 19). Enter 8 codes per line.

6. EQUIVALENT CODES LINE (free format, if IOP14=-1)

ecodes
where

ecode = equivalent codes (max=50)

NOTE: Enter the VBM feature code to be loaded into VBM file 25 for each geology/feature code listed above.
Enter 8 codes per line.

Revised: 31-January-00 Page 649-7

 MineSight®
M649V1 - LOAD DIGITIZED DATA TO A VBM FILE Proprietary Software: Mintec, inc.

M649V1 SAMPLE RUN FILE #1

MEDS-649V1 10=[Link] 25=[Link] 3=[Link];
MEDS-649V1 19=[Link]
** SAMPLE PROJECT TOPOGRAPHY ENTRY **

USR = ABC

IOP1 = 1 / 1 = DATA IN FILE #19, 0 = DATA IN THIS FILE

IOP2 = 0 / 0 = WRITE TO VBM, 1= DO NOT WRITE

IOP3 = 0 / 0 = INITIAL FILE ENTRY 1 = UPDATE

IOP4 = 1 / 0 = DELETE EXTRA POINTS, 1=DO NOT DELETE EXTRA POINTS

IOP5 = 1 / 0 = COMBINE FEATURES, 1=DO NOT COMBINE FEATURES

PAR1 = 1 / TOLERANCE FOR POINT DELETION TESTS

PAR2 = 1 / TOLERANCE FOR COMBINING FEATURES
I-O = 0 / 0 = NO DETAILS PRINTED
END

M649V1 SAMPLE RUN FILE #2

MEDS-649V1 10=[Link] 25=[Link] 3=[Link];
MEDS-649V1 19=[Link]
** SAMPLE PROJECT TOPOGRAPHY ENTRY USING POINT DELETION **

USR = ABC

IOP1 = 1 / 1 = DATA IN FILE #19, 0 = DATA IN THIS FILE

IOP2 = 0 / 0 = WRITE TO VBM, 1= DO NOT WRITE

IOP3 = 0 / 0 = INITIAL FILE ENTRY 1 = UPDATE

IOP4 = 0 / 0 = DELETE EXTRA POINTS, 1=DO NOT DELETE EXTRA POINTS
IOP5 = 1 / 0 = COMBINE FEATURES, 1 = DO NOT COMBINE FEATURES

PAR1 = 1 / TOLERANCE FOR POINT DELETION TESTS

PAR2 = 1 / TOLERANCE FOR COMBINING FEATURES

I-O = 0 / 0 = NO DETAILS PRINTED

END

Page 649-8 Revised: 31-January-00

MineSight®
Proprietary Software: Mintec, inc. M649V1 - LOAD DIGITIZED DATA TO A VBM FILE

M649V1 SAMPLE RUN FILE #3

MEDS-649V1 10=[Link] 25=[Link] 19=[Link];
MEDS-649V1 3=[Link]
** LOAD ASCII DATA TO VBM FILE [Link] **

USR = ABC / 06-08-95 08:57:38

IOP1 = 1 / 1 = DATA IS IN FILE 19

IOP2 = 0/0 WRITE TO VBM FILE

IOP3 = 1 / 1 = APPEND FEATURES

IOP4 = 1 / 1 = DO NOT DELETE EXTRANEOUS POINTS
IOP5 = 1 / 1 = DO NOT COMBINE STRINGS

IOP6 = 0 / 0 = DO NOT PRINT DETAILED OUTPUT

IOP7 = 0 / 0 = DO NOT CLOSE FEATURES
IOP9 = 0 / 0 = READ DATA IN FREE FORMAT

IOP10 = 1 / 1 = DO NOT CLOSE FEATURES

IOP14 = -1/ 0 = NO IMPACT
COM -1 = LOAD EQUIVALENT FEATURE CODES (RENAME)
COM ACCORDING TO TABLE AFTER “END” LINE
COM N = LOAD ALL INPUT FEATURES AS FEATURE N
COM FORCE A CONSTANT FEATURE CODE

END
8 / NUMBER OF FEATURE CODES
804 807 811 815 819 821 823 905
704 707 711 715 719 721 723 901

Revised: 31-January-00 Page 649-9

 MineSight®
M649V1 - LOAD DIGITIZED DATA TO A VBM FILE Proprietary Software: Mintec, inc.

M649V1 SAMPLE RUN FILE #4

MEDS-649V1 10=[Link] 25=[Link] 19=[Link];
MEDS-649V1 3=[Link]
** LOAD ASCII DATA TO VBM FILE [Link] **

USR = ABC / 06-08-95 09:00:29

IOP1 = 1 / 1 = DATA IS IN FILE 19

IOP2 = 0 / 0 =WRITE TO VBM FILE

IOP3 = 1 / 1 =APPEND FEATURES

IOP4 = 1 / 1 =DO NOT DELETE EXTRANEOUS POINTS
IOP5 = 1 / 1 =DO NOT COMBINE STRINGS
IOP6 = 0 / 0 =DO NOT PRINT DETAILED OUTPUT
IOP7 = 0 / 0 =DO NOT CLOSE FEATURES
IOP9 = 0 / 0 =READ DATA IN FREE FORMAT

IOP10 = 1 / 1 =DO NOT CLOSE FEATURES

IOP14 = 901/ 0=NO IMPACT
COM -1=LOAD EQUIVALENT FEATURE CODES (RENAME)
COM ACCORDING TO TABLE AFTER “END” LINE
COM N=LOAD ALL INPUT FEATURES AS FEATURE N
COM FORCE A CONSTANT FEATURE CODE
END

Page 649-10 Revised: 31-January-00

MineSight®
Proprietary Software: Mintec, inc. M649V1 - LOAD DIGITIZED DATA TO A VBM FILE

HOW TO DEBUG AN M649V1 RUN

1. If the program terminates normally, but no data is loaded to the VBM, check the coordinates of the setup lines (lines 2-9 in input
file). If the setup lines are incorrect, digitized data may be outside the limits of the VBM.

2. If you load data with IOP3=0, any existing data on a plane will be deleted and replaced by new data. Be careful that you do not
delete existing data in the VBM.

3. To check that the data was loaded successfully into the VBM, plot out all features on all planes that were loaded. You can also
ASCII dump all features on all planes with either M653V0 or M650ED.

4. ? M649A1: ERROR IN COORDINATE CONVERSION

Check the coordinates given in the setup lines. Make sure that the four digitized boundary points are the same as those entered.

5. ? M649V1: ERROR. YOU’VE EXCEEDED THE MAXIMUM NUMBER OF PLANES: 2000

You may only have 2000 planes per VBM. Create a new VBM file (you are allowed more than one VBM per project) and load
the data into it.

6. ? M649V1: ERROR. FEATURE CODE ON PLANE xxx EXCEEDS THE MAXIMUM: 999999
The feature code must be an integer in the range 1 to 999999. Change all feature codes which fall outside these limits.

7. ?M649V1: ERROR. THERE ARE MORE THAN 20000 POINTS IN FEATURE xxx, PLANE xxx.
The maximum number of points allowable in a single feature is 20000. Use one of the extraneous point deletion options to
reduce the number of points in the feature.

8. M649V1: ERROR. FEATURE xxx ON PLANE xxx EXCEEDS THE MAXIMUM: 99.
You are only allowed to have 99 features with the same code per plane. Either eliminate some of the unnecessary features of this
code, or load some to another plane.

9. %M649V1: WARNING. YOU’VE EXCEEDED THE MAXIMUM NUMBER OF FEATURES: 2000.

DATA STARTING WITH FEATURE xxx ON PLANE xxx WILL BE IGNORED.
Only 2000 features can be loaded to a plane. Either eliminate some of the unnecessary features of this code, or load some to
another plane.

10. ? M649V1: ERROR. SECTION xxx EXCEEDS THE MAXIMUM NUMBER OF POINTS PER PLANE: 20,000.
The maximum number of points allowable for any plane is 20,000. Use one of the extraneous point deletion options to remove
unnecessary points.

11. ? M649V1: ERROR. FEATURE CODE OUT OF RANGE 1-999999 ON PLANE xxxx NO FEATURES OCCURRING
AFTER THE ABOVE PLANE HAVE BEEN LOADED.
This error is caused by trying to load a feature with a code of zero (0) or greater than 999999. valid feature codes are from 1 to
999999. Any features after this error will not be loaded. Correct the feature codes and reload.

12. Check the MINESIGHT® error messages in the Appendix.

Revised: 31-January-00 Page 649-11

 MineSight®
M649V1 - LOAD DIGITIZED DATA TO A VBM FILE Proprietary Software: Mintec, inc.

Page 649-12 Revised: 31-January-00

MineSight®
Proprietary Software: Mintec, inc. M650AR - OUTLINE AND AVERAGE RESERVES

M650AR OUTLINE AND AVERAGE RESERVES

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M650AR is a highly interactive program designed to aid the The program acts as a sophisticated grade and tonnage calculator:
geologist in the calculation of reserves on drillhole data. It is design various polygonal outlines on the screen, and the program
one of the MineSight® Graphical Interface (MGI) programs. will calculate reserves interactively. In order to use it, you must
have already loaded a MineSight® assay or composite file (Files
11/12 or Files 9/12). You must then extract the desired items
from the model in a format suitable for M650AR. The extraction
PROGRAM FLOW DIAGRAM routines are M819V1 (for assay data), M829V2 (for normal
composite data) or M829V3 for composite data that contains
RUN FILE: the 3-D endpoints of each composite. M650AR will then access
- Selection options the slices extracted from the drillhole files, bench by bench or
- Display options section by section.

Cut is the term used to describe a user-defined polygon which

outlines an area (volume) of material removed from the bench
or section. A cut is created by outlining an area in the project
window using the mouse.

Overlapping cuts are allowed so that the best initial design and
INPUT: CALCS: sequence of cuts can be found quickly. To avoid overlapping
- PCF - Calculate tons and grade on the final design, use the point, string and grid snap features
- File 25 within cuts so that new cuts are exactly coincident with other cuts and VBM
- Slice files from 3-D or features. This prevents sections of reserves from being counted
GSM model
twice.

Cuts can be edited using the EDIT CUT button and the functions
under Menu Strip 2 of M650. This option allows manipulation
of cuts that have been already designed.
OUTPUT: All cuts are considered permanent. When you exit the program,
- Area Index File you will be asked “Save IGP Cuts?” All cuts are either saved or
- Parameter File discarded. To discard cuts individually, use the DEL CUT
- Cut Cross-Reference File function before exiting.
- Report File
- Printer Output File
This documentation includes general operation and samples of
the files used by M650AR. Detailed information on individual
features is found in the on-line help.

An overview of the common features of all MineSight ®

Graphical Interface programs can be found in the Getting Started
section of the Introduction to MineSight®, Volume I.

Revised: 18-May-06 Page 650AR-1

 MineSight®
M650AR - OUTLINE AND AVERAGE RESERVES Proprietary Software: Mintec, inc.

Page 650AR-2 Revised: 18-May-06

MineSight®
Proprietary Software: Mintec, inc. M650AR - OUTLINE AND AVERAGE RESERVES

M650AR - OUTLINE AND AVERAGE RESERVES

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-650V1 10=filename 25=filename 27=filename 3=filename;

MEDS-650V1 19=filename 30=filename
where

MEDS-650V1 must be the first 10 columns

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
27 = the name of the 3-D CONNECTION FILE (optional)
19 = the name of the AREA INDEX FILE (default = [Link])
30 = the name of the PARAMETER FILE (default = [Link])
3= the name of the PRINTER OUTPUT FILE
NOTE: If Files 19 and 30 are not specified, the default file names will be used.

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free field format)

Run options are identical to M650ED.

GENERAL OPERATION
Move to the M650AR menu by either selecting the AVER RESR button on Menu 1 or the Menu 4 button at the bottom of the menu
strip. The INIT AR function must be picked first before any reserves operations can be run. Upon completion of a schedule, EXIT
AR must be picked to save all the changes. If any cuts have been generated in a previous run of M650AR, they will appear as
standard VBM features.

CHECKS

Once the INIT AR button is picked, M650AR checks for a valid Area Index File (default [Link]) containing a list of areas
on which to operate. Areas correspond to slice index files generated by M819V1, M819V2 or M819V3. If none are found, a panel
will prompt for at lease one slice index file. M650AR then checks for a valid Parameter File (default [Link]). If one is
found, and it has enough information, it may be used. Otherwise, a series of panels must be filled in for the run.

To ensure that reserve report files are up to date, the Cross Reference File is processed as soon as INIT AR is selected. A complete
new set of reserves files (RPT) is then generated. This accounts for any changes that may have occurred to both the cuts in the VBM
file and the Cross Reference File.

Revised: 30-September-92 Page 650AR-3

 MineSight®
M650AR - OUTLINE AND AVERAGE RESERVES Proprietary Software: Mintec, inc.

PROCESS

All AR functions are then performed from the fourth menu strip in M650. Standard functions such as NEW CUT, QUERY CUT,
QUERY DH, DELETE CUT, EDIT CUT are available. Only one slice at a time can be loaded into M650AR. Operations that require
a slice file (i.e. NEW CUT) can only be performed on the current slice.

After reserves are calculated and EXIT AR is picked, you will be asked if you want to save the reserves report. This allows you to run
in a temporary mode.

You will then be asked if you want to save the cuts. If you answer yes, all cuts are saved in the VBM file, and a Cross Reference File
is generated ([Link]). This file contains a list of cuts that were created, the area, slice, and period to which they belong, and their
VBM feature code and plane number. Upon exit, the current period is recalculated.

SAMPLE FILES
RUN FILE (input)

– standard M650 run file

– File 30 is used to specify the Parameter File (default = [Link])
– File 19 is used to specify the Area Index File (default = [Link])
– specify overlay and cut feature codes with IOP2,3,4 ... 16

SLICE FILES (input)

– generated with M819Vx

– PCF independent (for multiple area planning)
– slice files from different areas must contain the same items
– incompatible with M820V1 slice files

SLICE INDEX FILES (input)

– standard Slice Index Files produced by M819Vx

– contain the following information: slice file name, slice number, northing/easting/elevation; extra column for
seam name

grad1.5 5 95.00 N/A

grad1.6 6 90.00 N/A

Page 650AR-4 Revised: 30-September-92

MineSight®
Proprietary Software: Mintec, inc. M650AR - OUTLINE AND AVERAGE RESERVES

AREA INDEX FILE - default [Link] (input/output - File 19)

– up to 10 model areas
– areas can be from the same PCF or from different PCFs
– areas are defined as groups of slice files
– name of each Slice Index File must be in the Area Index File
– file will be created and maintained by M650AR
– contains the following information

# M650AR Area Index File

# Refer to documentation before editing this file
[Link]
[Link]
[Link]
[Link]
[Link]

PARAMETER FILE - default [Link] (input/output - File 30)

– used in addition to the run file because of the large number of options
– if file does not exist, panels will prompt for necessary parameters
– free format
– parameter lines can be in any order
– keyword at the end of the line must remain unchanged
– required items include initial slice, starting period number, starting period name, plane name, feature code for
cuts, display item, at least one color cutoff, and at least one material class
– a typical PARAMETER FILE looks like:

# M650AR Parameter File

# Refer to documentation before editing this file
11 /INITIAL-SLICE
1 /START-PERIOD
92mn1 /PERIOD-NAME
a /PLAN-NAME
800 /FEATURE-CODE
T /REVERSE-FLAG
GOLD /DISPLAY-ITEM
GOLD /REPORT-ITEM
TOPO /TOPO-ITEM
ZONE /CODE-ITEM1
ROCK1 1 2.00 0.40 0.80 1.20 1.60 2.00 /MATERIAL-CLASS
ROCK2 2 2.00 0.80 0.80 1.20 1.60 2.00 /MATERIAL-CLASS
WASTE 3 2.00 0.00 /MATERIAL-CLASS
3 /DEFAULT-CLASS
SG /TON-CALC
0.40 0.0000 0.9775 0.9775 /DISPLAY-CUTOFF
0.80 0.0000 0.0000 1.0000 /DISPLAY-CUTOFF
1.20 0.0000 1.0000 0.0000 /DISPLAY-CUTOFF
1.60 0.9852 0.9930 0.0147 /DISPLAY-CUTOFF
2.00 0.8998 0.4107 0.4301 /DISPLAY-CUTOFF
2.40 0.9658 0.0000 0.7795 /DISPLAY-CUTOFF

For a detailed description of the parameter file contents, see the ParamPanel 1-4 choices in the help file.

Revised: 30-September-92 Page 650AR-5

 MineSight®
M650AR - OUTLINE AND AVERAGE RESERVES Proprietary Software: Mintec, inc.

CUT CROSS REFERENCE FILE - default [Link] (input/output)

This file is the key to M650AR as it provides the only reference as to what VBM features are cuts. This file may be edited outside the
program, but care should be taken when doing so.

– if exists, every cut that is defined is processed and the reserves calculated
– automatically sorted by M650AR when it is created and should be in the sort order area, slice, period
– contains the following information:

# M650AR Cut Cross Reference File

# Refer to documentation before editing this file
# IA IS IP AREA SLICE PER GSM CUT#FEAT LAB1 LAB2 LAB3
1 10 1 [Link] 70.00 91m01 N/A 1 10001 stock N/A N/A
1 11 1 [Link] 65.00 91m01 N/A 2 10002 stock N/A N/A
1 11 1 [Link] 65.00 91m01 N/A 1 10001 mill N/A N/A
2 10 1 [Link] 70.00 91m01 N/A 2 10002 mill N/A N/A
3 13 1 [Link] 55.00 91m01 N/A 1 10002 dump N/A N/A

IA is the area index GSM is the name of the GSM level (if not 3-D model)
IS is the slice index CUT# is the number of the cut on the slice
IP is the period index FEAT is the VBM feature code.
AREA is the slice index file for the area LAB1 is a 5 character cut descriptor
SLICE is the coordinate of the slice LAB2 is a 5 character cut descriptor
PER is the Period name LAB3 is a 5 character cut descriptor

REPORT FILES - default [Link] (output)

– name is based on plan name (m) and period name (nnnnn)

– generated for each period in the plan
– contain reserves for each cut and the cumulative reserves for the period
– format has been changed from the M820V1 format due to increased number of cutoffs
– contains the following information:

CUT 1 SLICE 11 COORD 65.00 AREA 1 PERIOD 1 92mn1 asdf

MATERIAL ITEM CUTOFFS ON GOLD
0.80 1.20 1.60 2.00
Rock1 TONNES 0.0 946.0 770.0 66.0
B.C.M. 0.0 430.0 350.0 30.0
GOLD 0.00 1.59 1.85 2.66
SILVR 0.00 10.47 11.21 14.88
0.80 1.20 1.60 2.00
Rock2 TONNES 2838.0 8217.0 1914.0 0.0
B.C.M. 1290.0 3735.0 870.0 0.0
GOLD 1.07 1.56 1.66 0.00
SILVR 11.19 11.06 11.72 0.00
EQUIV 1.09 1.54 1.64 0.00

M820 COMPATIBILITY FILES

To allow compatibility with M820V1 (version 3 of IGPAVG), two files are generated - the NDX file and the CUT file. The NDX file
contains a summary of reserves for each cut and the CUT file contains the cut outlines in M122 format (for plotting).

Page 650AR-6 Revised: 30-September-92

MineSight®
Proprietary Software: Mintec, inc. M650BH - ORE CONTROL GRAPHIC PLANNER

M650BH ORE CONTROL GRAPHIC PLANNER

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M650BH is a highly interactive program designed to aid the The concept behind modeling and ore/waste selection is based
ore control engineer in short range planning by the use of on either a series of “floating” project control files (PCF) based
digitized ore/waste or routing polygons. It is one of the on map or planning areas or a standard 3-D Block Model. Each
MEDSYSTEM® Graphical Interface (MGI) programs. planning area has an associated model file (file 15), which is
created whenever a new area (shovel) file is read in from either
an existing cut index file or a new index file. Geological or
metallurgical data can be loaded into the model just after it is
PROGRAM FLOW DIAGRAM created, for use in the design of the cuts. Interpolation of the
blasthole grades is only performed within a digitized cut.
RUN FILE:
- Selection options M650BH can calculate tons and grade for various polygonal
- Display options outlines (cuts) designed interactively, and can output a report
of these grades by cut, a survey file of the cut outlines, and plots
of the cuts for a shot showing the shot number and routing for
each cut. Cut is the term used to describe a user-digitized polygon
which outlines an area (volume) of material removed from the
mining bench or section.

In order to use M650BH, you must have built a composite file

INPUT: CALCS: 9. Some of the features of M650BH, such as ore routing, area
- PCF - Calculates tons and interpolation and block display, are only accessible if you also
- File 23 grades within cuts have created a 3-D block model (File 15) and have included it
- Slice Files from File 9 - Updates model with ore
- File 15 (optional) routing code
in the names line of your M650BH run file.
- Config.819
- Config.829 This program requires multiple setup files which are explained
- Shovel File(s) in detail later in this section:

config.819— sets up parameters for creating slices from

OUTPUT: File 9
- Area Index File
- Parameter Index File config.829— sets up parameters for creating slices from
- Cut Cross-Reference File File 15
- Report File
- Printer Output File
- Survey Files(s) shovel files— files defining shovel areas
- Plot File(s)

slice index file(s) from M819V2/V3 run

slice(s) from M819V2/V3 run — data representing one

bench of your File 9

[Link]— batch file to do interpolation on the model

in background

Revised: 18-May-06 Page 650BH-1

 MineSight®
M650BH - ORE CONTROL GRAPHIC PLANNER Proprietary Software: Mintec, inc.

[Link]— batch file to update model slice in back- The third initialization panel contains all the BH options and
ground special functions. You must initialize BH mode, select an area
index and shovel or area file, and fill out initialization parameters
One shot can be worked on at a time, displaying both composite in order to access these functions. If cuts from a past session
and block values for the shot and then outlining potential cuts exist the question will be asked, “process existing cuts?”A NO
to calculate the grade for the cut. Cuts can be edited if desired. answer to this question will result in all the existing cuts being
Once the cut is satisfactory, a material routing code can be discarded, but the VBM features corresponding to the cuts are
assigned to the cut and stored in the model file for all blocks left intact.
within the cut. Once all cuts for the shot are completed, a report
of grades and tonnages for all cuts for the shot can be created. While in BH mode, the cuts can be digitized for various shots
on a bench. Shots on a different bench can be accessed by
choosing “New Area” and selecting a new shovel file.

The option is given to save all cuts for the present session as the
“Exit BH” button is pressed; if cuts are not saved at this time,
the features will be converted to VBM features with no cut
information saved. “VBM to Cut” can be selected to convert
these features back to cuts in a future session of BH, one cut at
a time.

NOTE: You should always minimize the graphic1 window

when entering BH mode.

To avoid overlapping cuts use the point, string and grid snap
features so that new cuts are exactly coincident with other cuts
and VBM features. This prevents material from being double
accounted.

The program has the same functionality and interface as the

standard M650 series of programs, as the first three menus are
the same as the other M650 programs.

The second initialization panel contains the material class table.

For each material, it is preferable to check the “series” option.
This allows sequential numbering of cuts by sequence number.
If the “series” option is not checked, all cuts will be labeled by
the routing code only.

Page 650BH-2 Revised: 18-May-06

MineSight®
Proprietary Software: Mintec, inc. M650BH-ORE CONTROL GRAPHIC PLANNER

M650BH INTERACTIVE OCS GRAPHIC PLANNER

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-650V1 10=filename 25=filename 3=filename;

MEDS-650V1 15=filename 19=filename 30=filename
where

MEDS-650V1 must be in the first 10 columns

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
3= the name of the PRINTER OUTPUT FILE
15 = the name of the 3-D BLOCK MODEL FILE
19 = the name of the AREA INDEX FILE (default = [Link])
30 = the name of the PARAMETER FILE (default = [Link])

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order and free format)

All the run options listed for M650ED are identical for this program. In addition, M650BH has the following special run options:

IOP14 = 0 USE COLOR CODED BOXES

= 1 USE COLOR CODED CIRCLES
= 2 USE STANDARD SYMBOL SET BASED ON CUTOFFS

IOP15 = 0 PERMANENT MODEL

= 1 FLOATING MODEL

NOTE: The floating model must be set up by Mintec; base run files must be set up for property boundaries, etc.

IOP21 = 0 BHS PROJECT (File 12 = shot index)

= 1 3-D PROJECT (standard file 12)

NOTE: This option tells M650BH whether to run M819V3 for a BHS project, or M819V2 to update File 9
slices for a 3-D project.

IOP25 = 0 STANDARD MEDSYSTEM PLOT FILE (for use with M122V1)

Run file created based on a zoom window; plots active cuts and blast holes
= 1 SAME AS 0 EXCEPT EVERYTHING ON THE SCREEN WILL BE
DUMPED TO THE PLOT FILE
= 2 HPGL OR POSTSCRIPT DUMP
= 3 USE [Link] TO CREATE PLOTS
= 4 USE [Link] TO CREATE PLOTS

NOTE: This option comes into play when “PLOT FILE” is chosen from menu 4.

Revised: 18-February-00 Page 650BH-3

 MineSight®
M650BH-ORE CONTROL GRAPHIC PLANNER Proprietary Software: Mintec, inc.

IOP30 = 0 CUT FEATURES LABELED WITH A 1 TO 5-DIGIT SHOT NUMBER

PLUS A 1 DIGIT ROUTING CODE (0-9)
= 1 CUT FEATURES LABELED WITH A 1 TO 4-DIGIT SHOT NUMBER
PLUS A 2 DIGIT ROUTING CODE (0-99))
= 2 CUT FEATURES LABELED WITH A LLL CODE OF A 3-DIGIT SHOT NUMBER
AND A RRR CODE OF THE ROUTING (0-999)

IOP31 = 0 RECALCULATE CUT RESERVES AS BH IS INITIALIZED

1 DO NOT RECALCULATE CUT RESERVES AS BH IS INITIALIZED; CUTS FROM PAST SESSIONS
WILL NOT BE EDITABLE

Used only when IOP15 = 1:

PAR25 = DX for model
PAR26 = DY for model

GENERAL OPERATION
Files needed for M650BH:

CONFIG.819 User created file; specifies items to extract from File 9 in M819V2/V3 run done in background; editable.

CONFIG.829 User created file; specifies items to extract and/or interpolate from File 15 in M829V1 and M620V1 runs
done in background; editable.

[Link] This file is only needed if IOP25 = 4. This file contains custom settings used in plot creation.

SHOVEL FILES(S) Shovel index file created by M819V3 run (OCS project) or M819V2 (3-D project).

[Link] Parameter file created by the parameter setup panels when initializing BH in M650BH.

[Link] Index of shovel areas; created when initializing M650BH.

[Link] A batch file which is run in background from M650BH to create slices from the model; editable.

[Link] Batch file to sort the composite file and interpolate blocks in the model, which is run in background from
M650BH; editable.

[Link] Used when IOP25 = 3 or 4. This batch file is used to create plot files.

[Link] Batch file used to generate custom reports.

Page 650BH-4 Revised: 13-February-12

MineSight®
Proprietary Software: Mintec, inc. M650BH-ORE CONTROL GRAPHIC PLANNER

Detailed description of file CONFIG.819:

line 1: PCF
line 2: file 9, blasthole composite file
line 3: file 8, sorted composite file
line 4: items to extract from file 9; must be in same order as items to extract in file CONFIG.829

NOTE: Put items that you are going to report first. Code item that defines material classes cannot be reported.
The maximum number of reporting items is 15.

Detailed description of file CONFIG.829:

line 1: PCF
line 2: file 15, blasthole model file
line 3: file 8, sorted composite file
line 4: items to extract from file 15; must be in same order as items to extract in file CONFIG.819
line 5: interpolation parameters; 1st: 0=no geol matching, rest = items to match
line 6: if nonzero, non-isotropic search parameters (must be 6)
line 7: IDW search parameters: east, north and elevation search distances, max 3-D distance, IDW power, max # of composites
to be used
line 8: items to interpolate; must have same item names in files 8 and 15 and must have identical item names to the items in file 9
line 9: defaults to INVWT for inverse distance weighting; type of interpolation for each item (from M620V1)
line 10: specifies how many items on line 4 should be reported
line 11: logical var used for multiple destinations on a vertical slice; not used for OCS - always F
line 12: used if line 11 = T; lengths
line 13: used if line 11 = T; reporting labels

NOTE: Items that you want to report should be interpolated from File 9, and should have the same names in
Files 15 and 9. The maximum number of reporting items is 15.

Detailed description of [Link]:

This file is used by M650BH to create custom plots. This file is set up through the procedure [Link].

Detailed description of [Link]

This batch file runs M620V1 to do IDW interpolation in background from the “INTERP. AREA” command in M650BH. It gets the
benches to interpolate from M650BH; it runs M506V1 to sort the composite file, then M620V1 to do the interpolation.

If you prefer kriging to IDW, this batch file can be edited to call program BHM600 to add the proper rows, columns and bench from
the standard M620V1 run file that is created to a standard M624V1 run file; then insert the line M624V1 /[Link] in
[Link] to interpolate. BHM600 is a utility program that can update the benches, rows, and columns in one runfile based on
the columns, rows, and benches specified in another runfile. Since [Link] is being dynamically created every time you click on
“INTERP AREA” in M650BH, this is usually used as the input file. The types of runfiles that can be updated by BHM600 are:

option 0: M620XX runfile

1: other 600-series runfile (like M612V1)

2: param file

3: M656XX runfile (precursor to M667V1)

4: M508RP runfile

Revised: 18-February-00 Page 650BH-5

 MineSight®
M650BH-ORE CONTROL GRAPHIC PLANNER Proprietary Software: Mintec, inc.

To run this program from the command prompt. You need:

an input file: usually [Link]
a base runfile: this is the runfile which you want updated for cols, rows, benches
Program BHM600 asks 3 questions:
input file name? ([Link]
base runfile name? (enter your base runfile name)
type of file? (give the correct option # above)

To run BHM600 from a command prompt window, with base runfile RUN612.A and standard runfile [Link], run the
program and answer the prompts as follows:
BHM600
Enter the imput file name [Link]
Enter the base runfile name RUN612.A
What type of file is the base runfile? 1

To automate this process, you can create a command file containing the answers to the questions, and then run BHM600, piping
in this command file [Link] contents:
[Link]
RUN612.A
1

5:M612RP runfile

BHM600 < COMMANDFIL

Works the same as the manual method.

In batch file [Link], input is piped into BHM600, and output is sent to the NUL processor so it doesn’t pop up on the screen.

M506V1 -[Link] > NUL

ECHO [Link] > [Link]

ECHO RUN612.A >> [Link]

ECHO 1 >> [Link]

BHM600 < [Link]

M612RP -FRUN612.A > NUL

This batch file sorts the file 9 into file 8, creates the command file to answer BHM600’s questions, runs BHM600 to update the
runfile for M612RP (RUN612.A), and then runs M612RP in the newly updated benches, rows, and columns desired.

A single > writes to a file, overwriting old stuff

a double >> appends to an existing file

a single < pipes information in from the file listed on the right

Page 650BH-6 Revised: 18-February-00

MineSight®
Proprietary Software: Mintec, inc. M650BH-ORE CONTROL GRAPHIC PLANNER

Detailed description of [Link]

This batch file runs M829V1 to recreate the slice from the model in the area specified by the user when “display blocks” is chosen.

M650BH requires three files before an area can be initialized.

1. SLICE INDEX FILE (usually called by bench elevation, e.g. 2320). File is the 30= in an M819V2 or V3 run.
Contents:
srplan.9 9 2320.00

(EXISTING SLICE FILE BENCH REF# BENCH TOE ELEVATION)

This file can be named anything within the following restrictions:

PREFIX 4 CHARACTERS OR LESS

SUFFIX 3 CHARACTERS OR LESS

The standard convention is to name this by the bench elevation, or by a shovel number.

2. BINARY SLICE FILE FROM M819V2/V3 (always called srplan. + bench#) This must be the slice file which is
specified in the SLICE INDEX FILE. M650BH reads the header info from the slice file at initialization to see what items
were extracted. The slice file is then recreated in the background by M819V2 (3-D project) or V3 (BHS project) when
“display blocks”is selected.

3. SHOVEL LOCATION FILE (usually called SH + bench elevation)The name of this file is tied to the slice index file. If
the chosen slice index file is 2320, then the program looks for a shovel location file named sh2320. If the slice index file
is named [Link], the program looks for [Link].

The shovel location file has the following format:

1 2320.00 9811.00 834.00 1000 1000 1000 1000

(area 1, bench 2320, center at (9811.,834.) and the area of influence extends 1000 feet in the E, N, S, and W
directions.)

Special notes about M650BH set up

There are a few things that should be set up before using M650BH.

When running M650BH, the items which are going to be extracted from File 9 and File 15, should match in both name and precision.
these items must be included in both Files.

REF# Shot number (INTEGER ITEM) **STORED BY M500BHS**

BHS# Blasthole number (ALPHANUMERIC ITEM)
MINED Flag showing that a hole has been mined out (INTEGER ITEM)
Note: This item must be placed second to last in the list of items to extract.
EAST Easting of blasthole location (REAL ITEM)
NORTH Northing of blasthole location (REAL ITEM)
OTYPE Routing (destination) of blasthole (INTEGER ITEM)
Note 1: This does not have to be called OTYPE, but an item MUST exist.
Note 2: OTYPE cannot be reported. If you wish to extract your code item, it must be listed AFTER all the report
items.

Revised: 18-February-00 Page 650BH-7

 MineSight®
M650BH-ORE CONTROL GRAPHIC PLANNER Proprietary Software: Mintec, inc.

ELEV. Elevation of TOE of Blasthole

ELVBH Elevation of Collar of Drillhole from Survey data
LNGTH Length of Drill Hole calculated from ELVBH - ELEV.
DHTOE Length of blasthole (REAL ITEM). An item with this name is required if using a standard MEDSYSTEM® Survey
File (File 12). This item is the same as ELVBH, but needed for the M650BH program.

The item used as the report item in M650BH must be listed as the first item to extract.

GENERAL OPERATION
I. You must first do an M819V2/V3 run to create a composite slice file.

II. Now you can run M650BH:

a. Use run file [Link] to enter M650BH.

b. Initialize BH.

1. Upon initialization of BH, you will choose a Cut Index File. By default, this file is called
[Link]. This file lists up to 10 shovel areas or locations. Each project may contain multiple
Cut Index Files. During the first setup, the panel listing the areas will be blank. Enter a new shovel
name and BH will prompt you through the steps to build a new shovel location.

2. Next, you will choose to use the existing parameter file [Link], or fill in new responses in the
parameter setup screens. Fill out BH display item, report item, code item, model display item and an
initial slice.

3. In the material class panel, don’t put any spaces in the material class names; it will cause problems.

c. SHOT IDS to display shot numbers.

d. DISPLAY BLOCKS to see what has been interpolated; usually you will select the whole area of interest.

e. INTERP. AREA to interpolate the new shot(s). Digitize the boundary of the area to be interpolated.
This selection runs batch file [Link] and uses CONFIG.829 to set up the runfile for
M620V1, then does the interpolation. Note that the items to be interpolated on line 8 of config.829
must have the same item names as their counterparts in file 8/9.

f. DISPLAY BLOCKS to update the screen with the results of your interpolation.

g. ORE ROUTING is the selection to make a new cut, save the cut and get the reserves report. Give it a planning
name, usually the shot# (up to 4 characters), then digitize the cut to be reported on. The reserves report will
appear on the screen. Use repetitively to outline all cuts for the shot.

h. PLOT FILES to plot the output and to send cut outlines to a survey format file for use in the field.

i. HARDCOPY - use zoom window - select shot of interest -plot blast holes - dump holes - specify shot #, scale
and grid (NOTE: integers only here!) -send out to a file for use in the field. Each time you do this, run files
[Link]# and [Link]# are created, with the # increasing for each new choice. Use these run files
with the 122 program that matches your plotter to plot cut outlines and grade values.

j. Exit BH - SAVE CUTS and SAVE REPORT! The cuts will be saved as VBM features, and a cross reference
file will also be created which keeps track of them as cuts.

k. Next M650BH session: ALWAYS USE EXISTING CUTS or your cuts created in prior sessions will be deleted.

Page 650BH-8 Revised: 18-February-00

MineSight®
Proprietary Software: Mintec, inc. M650BH-ORE CONTROL GRAPHIC PLANNER

Other options in M650BH include:

NEW AREA To choose a different slice to work with.

NEW INDEX To choose a new area index file containing a new series of slices.

LOAD CODES To load codes to the model or blasthole file based on an outline.

CREATE REPORT To createsa written copy of the reserves report seen on the screen from ore routing cuts ; this also
happens if you save the report on the way out of BH.

POSITION SHOV. To move the shovel to a different location.

NEW MINING FACE To get reserves of a mined-out area. These cuts must be made in a separate plan from the ore
routing plan.

To change the area extracted without selecting a new slice:

1. Select MAKE SHOVEL FILE to edit the shovel file. Change the Easting, Northing or extents to the
desired limits.

2. POSITION SHOVEL to make the new limits take effect.

M650BH SAMPLE RUN FILE

MEDS-650V1 10=[Link] 25=[Link] 3=[Link] 5=[Link];
MEDS-650V1 30=[Link] 19=[Link]
*** VBM EDITOR PLANES 2345. - 2570.

USR = ocs / Fri Mar 15, 1996 3:14:25 PM MST

IOP1 = 0 / 0=SHOW LIKE FEATURES IN SAME COLOR

COM /1=SHOW COPLANAR FEATURES IN THE SAME COLOR

IOP2 = 4 / FLAG 1=LLL RANGE, 2=RRR RANGE, 3=FULL RANGE, 4=ALL, 5=LIST
IOP3 = / FEATURE CODE RANGE/LIST

IOP14 = 0 /0= USE COLOR CODED BOXES 2=USE SYMBOLS

IOP15 = 0 /0 = USE PERMANENT MODEL

IOP21 = 2
IOP25 = 0 / 2 = OUTPUT HPGL OR POSTSCRIPT PLOTS

IOP30 = 1 / 0 = NAME CUTS BY SHOT NUMBER

COM 1 = NAME CUTS BY SHOT NUMBER (MORE THAN 9 ROUTING CODES)

COM 2 = NAME CUTS BY SHOT AND MATERIAL TYPE

PAR1 = 2345. / START PLANE TO EDIT

PAR2 = 2570. /LAST PLANE TO EDIT
PAR3 = 1. /INCREMENT

END

Revised: 18-February-00 Page 650BH-9

 MineSight®
M650BH-ORE CONTROL GRAPHIC PLANNER Proprietary Software: Mintec, inc.

Page 650BH-10 Revised: 18-February-00

MineSight®
Proprietary Software: Mintec, inc. M650DL - DRAGLINE RANGE DIAGRAMS

M650DL DRAGLINE RANGE DIAGRAMS

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M650DL involves a number of programs and procedures for M650DL uses a step by step approach to range diagrams instead
slicing sections, doing the range diagram, plotting, volume of a more automated method because it gives the mining engineer
reporting and posting to plan. It is one of the MineSight® full control of the sequence of mining steps. Any mining polygon
Graphical Interface (MGI) programs. can be subdivided for both mining and spoiling. Spoil piles can
be rehandled and leveled. Extended benches can be built and
sized as spoil polygons. Chopdown is just another mining
polygon. The approach also honors the precise geology (multi-
PROGRAM FLOW DIAGRAM seam, dipping seams, variable thickness) from the GSM or plan
VBMs as compared to simply inputting representative
RUN FILE: thicknesses.
- Selection options
- Display options The VBM geology sections are created from the GSM, plan
VBMs and/or the gridded Surface File (File 13). Any internal
removable partings and/or losses are handled in the GSM by
creating an MTOP/MBOT for minable top/bottom or in
M650DL by applying a recovery. Mining benches can be setup
in File 13 or added with M650DL.

OVERVIEW OF PROCEDURES
INPUT: CALCS:

- PCF - Mining and spoiling The dragline procedures can be run either from the menu system
- Section VBM data functions or directly from the command line. (See the MINER section for
more information.)

DLSECT—Slice Sections

Sections can be cut from the GSM, the File 13 Surface File and
plan VBMs. The surfaces and zones to slice can be selected.
They are then loaded into a sectional VBM.
OUTPUT:
- Volume Audit File DLRANG—Run M650DL
- Updated VBM
After VBM sections are created, range diagrams can be
developed using interactive graphics on these sections. The first
time range diagrams are done for a particular project, the external
files (section, feature, and equipment) must be set up (EDIT
FILES option). The Section File contains information such as
section start and endpoints and range into and out of the section.
The Feature Code File contains the feature codes, description,
material type and plotting parameters. It is used for the right
side code only; the left side code is used for the cut#. The
Equipment File contains equipment parameters such as reach,
tub radius, dig depth and dump height. After the first run, the
external files can be updated as needed. (See the sample files
section.)

Revised: 18-May-06 Page 650DL-1

 MineSight®
M650DL - DRAGLINE RANGE DIAGRAMS Proprietary Software: Mintec, inc.

Cuts are then laid out as passive features for assisting with the DLPLOT—Plot Range Diagrams
outlining of mining polygons (LAYOUT CUT option). This only
needs to be done once per section. Once all the cuts and zones have been mined, the range diagram
can be plotted using different pen colors, line types, and shading
The main part of the range diagrams is now ready to be done. patterns. Labels can also be created by using the Metafile
The next cut (NEXT CUT option) to mine is selected, the manager and then overlaid on the plot.
equipment is located (EQUIP LOCN option) and mining begins
(MINE option). DLVOLM—Produce Reports

The MINE step involves outlining a mining polygon (e.g., coal, The Volume Audit File can be used to produce a report with
waste, rehandle) that is on the current mining surface, applying various sorting and subtotaling options. This report shows the
the swell factor (from the Feature Code File) and spoiling it original location and the destination of the material moved from
using one of five options: the various mining polygons on the selected sections. Rehandle
volume and percentage of total waste are also reported.

spoil toe (SPOIL TOE option) DLPOST—Post to Plan

dump point (DUMP POINT option)
automatic polygon sizing (AUTO POLY option) At any stage of the mining, the range diagram can be posted to
polygon fill (POLY FILL option) plan and plotted. This procedure can also create a 3-D data file
remove from pit (REMOVE option) of the posted points for contouring into a File 13 surface.

If the material doesn’t fit, it can be dumped onto an adjacent Documentation

section or removed from the range diagram completely. Each
mining step is output to an Volume Audit File for reporting. This documentation includes general operations, information
on individual features and samples of all the files used by
There is also an option for mining an entire cut in one polygon. M650DL. Details on individual features can also be found in
In this case, the mining polygon is digitized as the entire cut, the on-line help files.
and then each individual ore zone is digitized and handled
separately. This speeds up the range diagrams when used for An overview of the common features of all MineSight ®
simpler geology. Graphical Interface programs can be found in the Getting Started
section of the Introduction to MineSight®, Volume I.
After all the material from a mining polygon has been mined,
the step can be saved to the VBM and the Volume Audit File.
During the mining, spoils can be canceled/deleted as required
or the complete mining step can be canceled.

At any stage of the mining, the current mining surface can be

saved as a VBM feature. Also, mining for entire cuts can be
deleted using the UNDO option. The associated VBM features
and Volume Audit records are also deleted.

Page 650DL-2 Revised: 18-May-06

MineSight®
Proprietary Software: Mintec, inc. M650DL - DRAGLINE RANGE DIAGRAMS

MineSight® Range Diagrams

Revised: 18-May-06 Page 650DL-3

 MineSight®
M650DL - DRAGLINE RANGE DIAGRAMS Proprietary Software: Mintec, inc.

Page 650DL-4 Revised: 18-May-06

MineSight®
Proprietary Software: Mintec, inc. M650DL - DRAGLINE RANGE DIAGRAMS

M650DL — DRAGLINE RANGE DIAGRAMS

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-650V1 10=filename 25=filename 3=filename 31=filename;

MEDS-650V1 32=filename 33=filename 34=filename
where

MEDS-650V1 must be the first 10 columns

10= the name of the PROJECT CONTROL FILE
25= the name of the VBM FILE
31= the name of the Section File
32= the name of the Feature Code File
33= the name of the Equipment Parameters File
34= the name of the Volume Audit File
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free field format)

USR = USER INITIALS (e.g. ABC)

NOTE: IOP’s 1–30 and PAR’s 1–30 are the same as M650V1. IOP’s 31–40 and PAR’s31–40 are reserved
for M650DL.

IOP31 = 0 WORK IN AREAS

= 1 WORK IN VOLUMES (Using the Section Area of Influence)

IOP32 = FEATURE CODE OF CURRENT MINING SURFACE (Default=995)

IOP33 = FEATURE CODE OF START OF CUT (Default=990)

IOP34 = FEATURE CODE OF END OF CUT (Default=991)

IOP35 = 0 MINING DIRECTION IS RIGHT TO LEFT

= 1 MINING DIRECTION IS LEFT TO RIGHT

IOP36 = FEATURE CODE OF ACTUAL CUT (Usually 0)

IOP37 = 0 MULTIPLE POLYGONS PER CUT

= 1 ONE POLY PER CUT

IOP38 = 0 DO NOT UPDATE END OF CUT FEATURE FOR OFF-SECTION SPOILS

= 1 UPDATE END OF CUT FEATURE FOR OFF-SECTION SPOILS

NOTE: Use this option only if you are using different cut numbers for the same cut on each section.

Revised: 22-August-01 Page 650DL-5

 MineSight®
M650DL - DRAGLINE RANGE DIAGRAMS Proprietary Software: Mintec, inc.

PAR19 = VERTICAL EXAGGERATION FACTOR ( FACTOR < 1.0 SHRINKS AND > 1.0 EXPANDS THE
VERTICAL SCALE).

PAR30 = DIAMETER OF SCALABLE CURSOR

PAR31 = SWING ANGLE FOR ON SECTION(Default=90)

PAR32 = SPOIL ANGLE OF REPOSE(Default=37)

PAR33 = TOLERANCE ON TARGET VOLUMES(Default=10)

If spoil pile is within tolerance of mining polygon, the remaining volume is zeroed.

PAR34 = SNAPPING TOLERANCE FOR MINING SURFACE(Default=5)

If a point is within tolerance of the current mining surface, it is snapped on to the surface.

PAR35 = DEFAULT PERCENTAGE OF ORE IN EACH CUT FOR ONE POLY PER CUT CARE

This parameter is used if the user knows the ore percentage in each cut (e.g., from a stripping ratio
report). It saves having to digitize the individual ore zones when using the one polygon per cut case.

PAR36 = SWELL FACTOR FOR ORE IN ONE POLY CASE

END

DLSECT—GENERATE SECTIONS FROM A GSM AND SURFACE FILE

DLSECT is used to generate a section from a Gridded Seam Model (GSM), a Surface File (File 13), and/or a plan VBM at any
orientation, and load it to a section VBM for the Dragline Range Diagram program and procedure (M650DL & DLRANG). (The
sectional VBM file with an X origin of 0 must first be created with M102TS). Since most range diagrams are done on sections that
are non-orthogonal to the grid, DLSECT resets the VBM origin of the section to 0 for the x and whatever for the y (elevation). (ie:
the same as M609V1 normally does). The M650DL Section File is used to specify what the actual origin of the section is. This
allows a user to put a series of sections at any orientation into the one section VBM.

Enter the starting and ending

Easting and Northing for the
section and a VBM plane number
for it.

Page 650DL-6 Revised: 22-August-01

MineSight®
Proprietary Software: Mintec, inc. M650DL - DRAGLINE RANGE DIAGRAMS

If you will be doing off-section spoiling, then the sections should be created in the order in which they will be mined so that the
swing angle calculation will be done correctly.

Continuation Screen
Screen 2 of 2

The user selects the two endpoints for the section and a section plane number to be used in the VBM, along with the section name
and area of influence into and out of the section. This information is automatically added/updated in the DL Section File if the user
selects to the REPLACE SECTION option. In addition, the appropriate records from the DL Volume Audit File are deleted.

The user must also supply a names conversion file that gives the seam/File 13 name and the VBM feature code to translate it to.
(one entry per line in free format). DLSECT uses the names/feature codes to convert and translate the USERF files from M609V1
into VBM ready format for loading to the section VBM.

The data from the GSM/File 13/plan VBM can replace the entire VBM section (usually the case) or can just update it. The update
option is useful for extracting an updated file 13 surface and adding to an existing range diagram section.

Either the ore fraction (BLK%) item or the topo item are used for clipping the seams properly. If the GSM has already been
rationalized to topo, you can leave these blank.

DLSECT runs:
— DLSGEN using [Link] to update the DL Section and Vol Audit Files
— M609V1 using RUN609.TM1 to create USERF of file 15 (GSM) seam top/bot
— M609V1 using RUN609.TM2 to create USERF of file 13 topo & other items
— M609V1 using RUN609.TM3 to create USERF of file 13 other items
— CLUFVB using [Link] to convert the USERFs into VBM ready format
— M649V1 using RUN649.TM1 to load the GSM/file 13 data into the section VBM
— M658V1 using RUN658.TM1-TM5 to slice up to 5 features from a plan VBM
— M649V1 using RUN649.TM2 to load the sliced plan VBM data into the section VBM

Revised: 22-August-01 Page 650DL-7

 MineSight®
M650DL - DRAGLINE RANGE DIAGRAMS Proprietary Software: Mintec, inc.

DLRANG—BUILD THE RUN FILE AND RUN M650DL

The procedure DLRANG provides panels for entering the options and parameters required by M650DL. It then builds the run file
and starts the program.

The first panel requests the names of the

various startup files and the normal
M650ED editing options.

Enter the file names, sections, feature

codes, color, vertical exaggeration and
zoom window.

The second panel requests data used

strickly for range diagrams.

Enter the data for IOP31-38 and PAR31-

36.

Select whether to work in areas or volumes (i.e., whether or not to use the range of influence of the section). Select the mining
direction (left to right or right to left for locating equipment, spoil toes, etc.).

Enter the features codes for the mining surface and the cuts. These must also be set up in the Feature Code File. They are all
three digit codes for the right hand side which get combined with the cut number (used for the left hand side) except for the
current mining surface which is strictly a three digit code.

Page 650DL-8 Revised: 22-August-01

MineSight®
Proprietary Software: Mintec, inc. M650DL - DRAGLINE RANGE DIAGRAMS

Select whether or not you are mining each cut with one non-homogeneous polygon (i.e., then ore must be subtracted out).

There are also a number of default parameters, such as spoil angle of repose, that must be entered. The tolerance for targeting is
used to give a bit of leeway on matching the spoil areas/volumes to the mining polygon. The snapping tolerance to the current
mining surface is used for snapping mining and spoil polygons. At least two points from any polygon must be on the mining surface
so that the mining surface merging can occur.

A sample run file is included in the sample files section at the end of this program documentation.

USING THE DRAGLINE PROGRAM—M650DL

Click on RANG DIAG or Menu 4 to start the dragline range diagram program. The dragline menu appears and the project area
shows the first section in the range you have specified. This screen shows a section with the cut layout done but no mining started
yet.

The first time range diagrams are done for a particular project, the external files (section, feature and equipment) must be set up
before any other work is done. See EDIT FILE for specifics.

Revised: 22-August-01 Page 650DL-9

 MineSight®
M650DL - DRAGLINE RANGE DIAGRAMS Proprietary Software: Mintec, inc.

The functions described below are also described in the on-line help files.

NEW SECTN

Go to a new mining section and store the cut from the current section. This option is used when the range diagram on one section
is complete and another will be started.

NEXT CUT

Select the cut to be mined. The mining surface will be highlighted. If you have a current cut being mined, it must be finished before
the next one is selected. It will be stored when you choose the next cut. Cuts must be mined in numerical order. The cuts previously
mined can be listed with FEATURE INDEX choice on the Main Menu.

EQUIP LOCN

Select the piece of equipment to use and the setback. Pick a point on the topo surface to select that feature then locate the dragline
at the mining crest. A template of the dragline is drawn. This option is used each time the equipment needs to be moved. As a
minimum, this would be after each cut.

MINE

Outline the mining polygon and go into the **SPOIL** options for spoiling. These options are described in the next section.

SAVE SURF

Save the current mining surface as a VBM feature. This option allows any intermediate surfaces to be saved as a user specified
feature code.

UNDO

Delete VBM features and Volume Audit records on specified sections back to a specified cut. If there is any off-section spoiling,
those sections must be within the range of sections being “UNDONE”. An error will occur if this is not done.

CUT DESIGN

Layout mining cuts as passive features so that when the mining polygon is digitized/ input, it can be snapped to the cut. The cuts can
be laid out from top down or bottom up. Berms can also be added. After the first cut has been laid out, the other cuts can be input
using the same pattern of highwall angles and features to extend to. When doing the first side of the box cut, the highwall angle must
be input as a negative value, as it goes the opposite direction of the normal highwall.

FTR LIST

Display information window of feature, material type, zone and recovery.

Page 650DL-10 Revised: 22-August-01

MineSight®
Proprietary Software: Mintec, inc. M650DL - DRAGLINE RANGE DIAGRAMS

EDIT FILE

Edit section, feature or equipment files. These files must be set up the first time M650DL is run for a particular project. Add a new
record by moving to the end of the file and pressing NEXT REC. The data in the previous record will be repeated to facilitate
entering several similar records. Records can be changed by typing over the information in the chosen field.

See the sample file section for additional information about these files.

EXIT DL

Exit the range diagram portion but stay in the main M650V1. If you EXIT in the middle of a cut, you will have to do an UNDO when
you come back into M650DL because NEXT CUT always wants the next cut in the sequence.

Revised: 22-August-01 Page 650DL-11

 MineSight®
M650DL - DRAGLINE RANGE DIAGRAMS Proprietary Software: Mintec, inc.

** SPOIL ** OPTIONS
GENERAL INFORMATION

Information Window—This window gives the total of all spoils and the detail on either the last spoil or the edit spoil (if edit is
active).

One Polygon Per Cut—This case is used when the entire cut is being mined in one polygon. Always mine the ore first using a
fraction of the total cut material. Outline the seams on the first cut if you do not already know the stripping ratio. PAR35 gives a
default percentage of ore in each cut. This value is updated with each cut for which you outline ore areas.

Digitizing—The BACKSPACE or DEL key can be used to delete the last point digitized. The mouse is normally used to input
points, but they can also be input from the keyboard, depending on how the ABSOLUTE/RELATIVE/DIST, ANGLE toggle is set.
This is particularly useful in the AUTO POLY option for inputting an extended bench. The first point is digitized and the second and
third can be determined using a DIST, ANGLE of, for example, 20090 (for a flat bench)and then 135, for example, for a slope off
the bench to the current mining surface.

This screen illustrates a cut being mined. The current mining polygon and the spoil pile are shaded.

Page 650DL-12 Revised: 22-August-01

MineSight®
Proprietary Software: Mintec, inc. M650DL - DRAGLINE RANGE DIAGRAMS

SWTCH SEC

Go to a new section for spoiling. This option is used for off-section spoiling from a mining polygon on one section to a spoil on
a different section.

SPOIL TOE

Create spoil pile by picking toe. The spoil pile is then drawn from the toe out to the limit of the dragline reach or height using the
angle of repose. If the spoil pile is larger than the loose volume being mined, then the pile is adjusted until the volumes match. The
adjustment is done using a height adjustment where the peak of the pile is moved up and down, or a width adjustment where the toe
of the pile is kept fixed and the peak moves back and forth. There is also an option with spoil toe to force dump height which
extends the pile out beyond the reach to the limit of the height. This is useful for determining the size to build an extended bench
to rehandle the material beyond the reach.

DUMP PT

Create spoil pile by picking dump point. This option uses a user specified dump point to build the spoil pile using the angle of
repose to the current mining surface. If the selected dump point is within 10 units of the end of the dragline boom, it is snapped to
the boom. The dump point does not necessarily have to be on the end of the boom. It is up to the planner to ensure that the range
diagram is reasonable.

AUTO POLY

Create spoil pile by automatically sizing. This option is mainly used for extended benches and coal piles. For extended benches,
three points are input, two of which must be on the mining surface, and M650DL sizes the bench to the requested volume. When
inputting the points, the usual procedure is to put a point on the mining surface at the top of the bench, use the distance/ angle
option to add a point horizontally (e.g., 100 270 for 100 ft/m at an azimuth of 270), and then use the face slope angle to add a third
point (the angle must be in azimuth format with 0 as up). Once the three points have been input, click right and the bench is sized
automatically by moving it up or by extending it horizontally.

The coal pile option involves inputting four points, two of which must be on the current mining surface. M650DL then sizes the
pile upwards or downwards until the target volume is met.

POLY FILL

Create spoil pile by outlining a polygon. This option involves free form inputting of any polygonal shape, but requires two points on
the mining surface. It is up to the user to build a feasible pile and to match the required volume using the standard M650 editing
options such as point move.

REMOVE

Remove mining material from the pit. This option is usually used for removing ore or certain interburdens from the pit using
miscellaneous equipment. The volume removed shows up on the Volume Report but not on any of the spoils on the range diagram.
To “unremove” volume, put in a negative number.

EDIT POLY

Edit the mining polygon or the last spoil on the current section. To ensure the integrity of the range diagram, only the last spoil can
be edited. To edit prior spoils, undo the mining steps until the chosen spoil is reached. The editing involves the usual M650 options
such as point move. After each edit, the volume in the information window is recalculated and updated.

Revised: 22-August-01 Page 650DL-13

 MineSight®
M650DL - DRAGLINE RANGE DIAGRAMS Proprietary Software: Mintec, inc.

SAVE MINE

Save the current mine step to the VBM and to the Volume Audit File. In the one polygon per cut case, the first menu will reappear.
In multiple polygons per cut, the user will be prompted for the feature code of the next mining polygon. M650DL will not let the
user save the current mining polygon until the volume spoiled matches the volume mined. (i.e., the volume remaining is 0).

CANCL/DELT

Cancel the entire current mine step, all spoils, or the last spoil on the current section. This option allows the user to cancel a spoil
that doesn’t meet his expectations.

Page 650DL-14 Revised: 22-August-01

MineSight®
Proprietary Software: Mintec, inc. M650DL - DRAGLINE RANGE DIAGRAMS

DLPLOT—PLOT A RANGE DIAGRAM

DLPLOT is used to extract and plot a range diagram from a section VBM. Both binary (DATAF) and ASCII (USERF) files can be
generated. Binary files are much smaller and more efficient.

DLPLOT uses the Advanced User

standatd plotting panel. This
panel allows you to rotate the
plot, apply a scale factor to
enlarge (<1.0) the plot, create a
deferred plot file, choose the
ccurrent plotter, plot the
advanced user standard title
block and overlay USERF/ DATAF
files created in other runs.

Enter plotting information as

requested in the two screens.

The Feature Code File is used to

build the spec lines for plotting
in M654V1. Select features to
plot based on a range of right or
left had codes or on individual
codes.

Adding a -1 -1 will include all

the remaining features and plot
htem in a solid line with pen #1.

DLPLOT runs:

— DLPLOT using [Link] to build the M654V1 run file

— M654V1 using [Link] to create USERF/DATAF files of the VBM range diagram
— M122xx using [Link] to plot the results

Revised: 22-August-01 Page 650DL-15

 MineSight®
M650DL - DRAGLINE RANGE DIAGRAMS Proprietary Software: Mintec, inc.

DLVOLM—GENERATE RANGE DIAGRAM VOLUME REPORTS

DLVOLM is used to report volumes from the Volume Audit File. M650DL outputs a record to this file each time material is moved
on the range diagram. The record contains which section and cut it was, what the material type and zone was, how much was moved,
where it was moved to and how much of it was rehandle.

Specify the report order and

subtotaling. Select which
equipment, section, cut and zone
to report.

Since M650DL allows mining using one polygon per cut, there can be a mix of ore and waste in the same mining block. In order to
report the ore in the right part of the report, all the material types that are ore must be listed. The first type specified will be used
for the report heading.

A sample Volume Audit File and a sample Volume Report are included in the sample files section.

DLVOLM runs:

—DLVSRT using [Link] to select applicable records from the Volume Audit File and to reorder them to match the
specified order.
—DLVOLM using [Link] to report

Page 650DL-16 Revised: 22-August-01

MineSight®
Proprietary Software: Mintec, inc. M650DL - DRAGLINE RANGE DIAGRAMS

DLPOST—POST RANGE DIAGRAMS TO PLAN

DLPOST is used to slice/extract section range diagram data and output it to a 3-D data file for contouring, a survey file for creating
a triangulated DTM using M635V1, or an M122 USERF for plotting. Only one of these can be done at a time.

First fill in the Advanced User

standard plotting panel.

Enter the file names:

Sectional VBM
Section File
Output File

Enter the feature code to post

and the cuts and sections to use.
Usually the feature will be the
end of cut feature (e.g., 991)

DLPOST automatically posts all inflection and end points. There is also an option to specify the angle change between segments
for outputting additional points. The true inflection points that are posted are defined as points that have an up slope on one side and
a down slope on the other. Sometimes this means that the crest of a cut may not be posted as it may have a small down slope on one
side and a steep down slope on the other (i.e., not an up/down combination). The angle change parameter would pick up this point
because of the change in angle.

Additional points can also be sliced at a user specified x-distance spacing along the section. This is useful for contouring the post
mining topo.

Revised: 22-August-01 Page 650DL-17

 MineSight®
M650DL - DRAGLINE RANGE DIAGRAMS Proprietary Software: Mintec, inc.

DLPOST uses the range diagram Section File to build the list of sections to post using M658V5.

DLPOST runs:

— DLSPST using [Link] to build the section specs lines for M658V5

— M658V5 using [Link] to create 3-D/Survey/USERF files of inflection and sliced points

— M122xx using [Link] to plot the results

SAMPLE NAMES CONVERSION FILE—[Link]

RED 10
BLUE 20
GREEN 30
TOPOG 901
DLBEN 902
BEN1 903
BEN2 904

SAMPLE RUN FILE FOR M650DL

MEDS-650V1 10=[Link] 25=[Link] 3=[Link] 31=[Link];
MEDS-650V1 32=[Link] 33=[Link] 37=[Link]
*** DRAGLINE RANGE DIAGRAMS

USR = ABC

IOP1 = 0 /1=SET COLOR BY PLANE

IOP2 = 4 /1 = LLL, 2 = RRR, 3 = FULL CODE, 4 = ALL FEATURES 5=LIST

IOP3 = /IF IOP2 = 1,2 OR 3 THEN SPECIFY CODE RANGE WITH IOP3,IOP4

PAR1 = 10 100 /START & END PLANES & SPACING

PAR10 = /PRE-ZOOM WINDOW : XMIN, XMAX
PAR12 = /PRE-ZOOM WINDOW : YMIN, YMAX
PAR19 = /VERTICAL EXAGGERATION

IOP31 =0 /0=AREAS,1=VOLUMES
IOP32 = 995 /CURRENT MINING SURFACE
IOP33 = 990 /START OF CUT FEATURE CODE
IOP34 = 991 /END OF CUT FEATURE CODE
IOP35 =1 /MINING DIRECTION 0=RIGHT TO LEFT, 1=LEFT TO RIGHT
IOP36 =0 /RIGHT SIDE CODE FOR ACTUAL CUT
IOP37 =1 /0=MULTIPLE POLYGONS PER CUT,1=ONE POLY PER CUT

PAR31 = 90 /SWING ANGLE FOR ON SECTION

PAR32 = 37 /SPOIL ANGLE OF REPOSE
PAR33 = 10 /TOLERANCE ON TARGET VOLUMES
PAR34 = 3 /SNAPPING TOLERANCE FOR MINING SURFACE
PAR35 = 20 /DEFAULT PCT OF ORE IN EACH CUT FOR 1 POLY PER CUT CASE
PAR36 = 1.2 /SWELL FACTOR FOR ORE IN 1 POLY CASE

END

Page 650DL-18 Revised: 22-August-01

MineSight®
Proprietary Software: Mintec, inc. M650DL - DRAGLINE RANGE DIAGRAMS

SAMPLE SECTION FILE—[Link]

# Sample of comment in the Section File Order of values is:
# No. Name X1 Y1 X2 Y2 Azim Into Out of
100.00 A 11000.0 10000.0 19000.0 10000.0 90.00 200.0 200.0
200.00 B 11000.0 12000.0 19000.0 12000.0 90.00 200.0 200.0
300.00 C 11000.0 14000.0 19000.0 14000.0 90.00 200.0 200.0
400.00 D 11000.0 16000.0 19000.0 16000.0 90.00 200.0 200.0
500.00 E 11000.0 20000.0 19000.0 20000.0 90.00 200.0 200.0
600.00 F 11000.0 24000.0 19000.0 24000.0 90.00 200.0 200.0
700.00 G 11000.0 28000.0 19000.0 28000.0 90.00 200.0 200.0

SAMPLE FEATURE CODE FILE—[Link]

# Sample of comment in the Feature Code File. Order of values is:
# Code Material Zone swell reh tf rec pen line label shade
10 COAL RED 1.200 N 1.00 90.00 3 -1 0 0.00 0.00 0.00 0.00
20 COAL BLUE 1.200 N 1.00 90.00 4 -1 0 0.00 0.00 0.00 0.00
30 COALGREEN 1.200 N 1.00 90.00 2 -1 0 0.00 0.00 0.00 0.00
110 COAL RED 1.200 N 1.00 90.00 3 -1 2 0.05 45.00 0.00 0.00
120 COAL BLUE 1.200 N 1.00 90.00 4 -1 2 0.05 45.00 0.00 0.00
130 COALGREEN 1.200 N 1.00 90.00 2 -1 2 0.05 45.00 0.00 0.00
210 WASTE RED 1.300 N 1.00100.00 3 -1 2 0.05 45.00 0.05 -45.00
220 WASTEBLUE 1.300 N 1.00100.00 4 -1 2 0.05 45.00 0.05 -45.00
230 WASTEGREEN 1.300 N 1.00100.00 2 -1 2 0.05 45.00 0.05 -45.00
310 SPOIL RED 1.300 N 1.00100.00 3 -1 2 0.05 45.00 0.05 -45.00
320 SPOIL BLUE 1.300 N 1.00100.00 4 -1 2 0.05 45.00 0.05 -45.00
330 SPOILGREEN 1.300 N 1.00100.00 2 -1 2 0.05 45.00 0.05 -45.00
410 SPLOFFRED 1.300 N 1.00100.00 3 -1 2 0.05 45.00 0.05 -45.00
420 SPLOFFBLUE 1.300 N 1.00100.00 4 -1 2 0.05 45.00 0.05 -45.00
430 SPLOFFGREEN 1.300 N 1.00100.00 2 -1 2 0.05 45.00 0.05 -45.00
510 REHANDLEN.A. 1.300 Y 1.00100.00 3 -1 2 0.05 45.00 0.05 -45.00
990 SURF N.A. 1.000 N 1.00100.00 1 -1 0 0.00 0.00 0.00 0.00
991 SURF N.A. 1.000 N 1.00100.00 1 -1 0 0.00 0.00 0.00 0.00
901 TOPO N.A. 1.000 N 1.00100.00 1 -1 0 0.00 0.00 0.00 0.00
0 CUT N.A. 1.000 N 1.00100.00 1 -1 1 0.00 0.00 0.00 0.00

The open features, (e.g., the ore zones and the topo/mining surfaces) do not need to be in this file unless they are to be plotted
with a pen other than pen #1. If these features are omitted here, a –1 –1 command in DLPLOT will plot them in a solid line with
pen #1. Each ore zone and interburden polygon can have its own feature. An example of a coding scheme is:

0nn — ore zone nn from geology section (LLL=0)

901,902,... — original file 13 surfaces (LLL=0)
000 — cut design (LLL=cut#)
1nn — ore mined from zone nn (LLL=cut#)
2nn — interburden/overburden mined from zone nn
3nn — spoil polygon on section from zone nn
4nn — spoil polygon off section from zone nn
5nn — spoil polygon from zone nn rehandled
999 — current topo/mining surface
990 — topo/mining surface at start of cut
991 — topo/mining surface at end of cut

Revised: 22-August-01 Page 650DL-19

 MineSight®
M650DL - DRAGLINE RANGE DIAGRAMS Proprietary Software: Mintec, inc.

SAMPLE EQUIPMENT PARAMETERS FILE—[Link]

# Sample of comment in the Equipment File. Order of values is:
# No. Name Setback1 2 Tub reach dpht maxdig
1 DRAG1 20.0 25.0 15.0 250.0 150.0 300.0 1032.5 3987.2
2 DRAG2 20.0 30.0 50.0 150.0 120.0 140.0 0.0 0.0
3 SCRAPER 1.0 1.0 1.0 1.0 1.0 1.0 0.0 0.0

SAMPLE VOLUME AUDIT FILE—[Link]

These items are included in the Volume Audit File:

—Section number
—Cut number
—Feature code for mining polygon
—Material type and zone name
—Spoil polygon number for this mining polygon
—Section number for spoil polygon
—Feature code for spoil polygon
—Bank volume mined
—Loose volume mined
—Flag to indicate volume mined losses, ore in one poly case, or neither
—Rehandle percentage
—Mining equipment number
—Mining equipment location (x, y, and pad elevation)
—Swing angle and spoil distance (calculated from polygon centroids)

This shows a partial Volume

Audit File. The report extends
to the left for six more
columns.

Page 650DL-20 Revised: 22-August-01

MineSight®
Proprietary Software: Mintec, inc. M650DL - DRAGLINE RANGE DIAGRAMS

SAMPLE VOLUME REPORT—[Link]

RUN# 873. PAGE 2 COAL DLVOLDATE 04-30-92TIME 13:22:31
———————————————————————————————————
** MINTEC SAMPLE PLAINS COAL PROJECT **

SAMPLE VOLUME REPORT

=====================================================================================================
EQUIP SECTION CUT ZONE COAL LOSSES ON SECT OFF SECT REMOVED REHANDLE TOT WASTE REH%
=====================================================================================================

DRAG1 10.0 1 RED 0. 0. 1222. 0. 0. 0. 1222. 0.0

——————————————————————————————————————————————————————————————————————
TOTALS: 0. 0. 1222. 0. 0. 0. 1222. 0.0
———————————————————————————————————————————————————————————————————————————
DRAG1 10.0 TOTALS: 0. 0. 1222. 0. 0. 0. 1222. 0.0

DRAG1 12.0 1 RED 0. 0. 2067. 0. 0. 0. 2067. 0.0

———————————————————————————————————————————————————————————————————————
TOTALS: 0. 0. 2067. 0. 0. 0. 2067. 0.0

DRAG1 12.0 2 RED 0. 0. 0. 633. 0. 0. 633. 0.0

———————————————————————————————————————————————————————————————————————
TOTALS: 0. 0. 0. 633. 0. 0. 633. 0.0
———————————————————————————————————————————————————————————————————————————
DRAG1 12.0 TOTALS: 0. 0. 2067. 633. 0. 0. 2700. 0.0

DRAG1 14.0 1 ALLCUT 0. 0. 1712. 0. 0. 0. 1712. 0.0

———————————————————————————————————————————————————————————————————————
TOTALS: 0. 0. 1712. 0. 0. 0. 1712. 0.0

DRAG1 14.0 2 ALLCUT 0. 0. 1731. 0. 0. 0. 1731. 0.0

DLBEN 0. 0. 778. 0. 0. 0. 778. 0.0
———————————————————————————————————————————————————————————————————————
TOTALS: 0. 0. 2509. 0. 0. 0. 2509. 0.0

DRAG1 14.0 3 ALLCUT 0. 0. 1745. 0. 0. 0. 1745. 0.0

DLBEN 0. 0. 592. 0. 0. 0. 592. 0.0
———————————————————————————————————————————————————————————————————————
TOTALS: 0. 0. 2337. 0. 0. 0. 2337. 0.0
———————————————————————————————————————————————————————————————————————————
DRAG1 14.0 TOTALS: 0. 0. 6558. 0. 0. 0. 6558. 0.0
——————————————————————————————————————————————————————————————————————————————————
DRAG1 TOTALS: 0. 0. 9847. 633. 0. 0. 10480. 0.0

SCRAPER 14.0 1 ALLCUT 205. 0. 0. 0. 0. 0. 0. 0.0

———————————————————————————————————————————————————————————————————————
TOTALS: 205. 0. 0. 0. 0. 0. 0. 0.0

SCRAPER 14.0 2ALLCUT 315. 0. 0. 0. 0. 0. 0. 0.0

———————————————————————————————————————————————————————————————————————
TOTALS: 315. 0. 0. 0. 0. 0. 0. 0.0
———————————————————————————————————————————————————————————————————————————
SCRAPER 14.0 TOTALS: 520. 0. 0. 0. 0. 0. 0. 0.0
——————————————————————————————————————————————————————————————————————————————————
SCRAPER TOTALS: 520. 0. 0. 0. 0. 0. 0. 0.0
————————————————————————————————————————————————————————————————————————————————————————————
*TOTALS: 520. 0. 9847. 633. 0. 0. 10480. 0.0

Revised: 22-August-01 Page 650DL-21

 MineSight®
M650DL - DRAGLINE RANGE DIAGRAMS Proprietary Software: Mintec, inc.

Page 650DL-22 Revised: 22-August-01

MineSight®
Proprietary Software: Mintec, inc. M650ED - INTERACTIVE VBM EDITOR

M650ED INTERACTIVE VBM EDITOR

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M650ED is the interactive program used to edit VBM files. It is M650ED provides both single feature and global VBM editing
one of the MineSight® Graphical Interface (MGI) programs. type functions. In addition, it allows any number of VBM planes
and feature types to be loaded at one time. However, program
PROGRAM FLOW DIAGRAM performance will deteriorate if an excessive amount of data is
loaded. Therefore, limit the data to that which is essential for
editing operations.
RUN FILE:
M650ED is the foundation for all the 650–series programs.
- Selection options These include:
- Display options
M650AR Outline and Average

M650DL Dragline

M650IP Interactive Graphics Planner

M650PT Pit Expansion

INPUT: CALCS:
- Display functions
M650SV Survey Editing
- PCF
- File 25 - Editing functions
- 2-D VBM data All the editing features available in M650ED are also available
- 3-D VBM data in these other programs.

This documentation includes run file options, overall program

structure and samples of all the files used by M650ED. Detailed
information on individual features is found in the on-line help
file.
OUTPUT:
An overview of the common features of all MineSight®
- Updated File 25 Graphical Interface programs can be found in the Getting Started
- 2-D VBM data section of the Introduction to MineSight®, Volume I.
- 3-D VBM data

Revised: 18-May-06 Page 650ED-1

 MineSight®
M650ED - INTERACTIVE VBM EDITOR Proprietary Software: Mintec, inc.

Page 650ED-2 Revised: 18-May-06

MineSight®
Proprietary Software: Mintec, inc. M650ED - INTERACTIVE VBM EDITOR

M650ED - INTERACTIVE VBM EDITOR

RUN FILE OPERATION
1. NAMES LINE (must be the first line entered)

MEDS-650V1 10=filename 25=filename 27=filename 3=filename

where

MEDS-650V1 must be the first 10 columns

10= the name of the PROJECT CONTROL FILE
25= the name of the VBM FILE
27= the name of the 3-D connection file(optional)
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = 0 SHOW LIKE FEATURES IN SAME COLOR

= 1 SHOW COPLANER FEATURES IN SAME COLOR

IOP2 = 1 RANGE OF FEATURES SPECIFIED BY LEFT SIDE CODE

= 2 RANGE OF FEATURES SPECIFIED BY RIGHT SIDE CODE
= 3 RANGE OF FEATURES SPECIFIED BY FULL CODE
= 4 LOAD ALL FEATURES
= 5 RANGE OF FEATURES SPECIFIED BY A LIST
IOP3 = MINIMUM CODE RANGE
IOP4 = MAXIMUM CODE RANGE

NOTE: IOP3 and IOP4 apply only when IOP2 = 1, 2 or 3.IOP3 thru IOP13 provide a list of items when
IOP2 = 5.

IOP16 = NUMBER OF EDITS BETWEEN AUTOMATIC FILE SAVES

PAR1 = START PLANE

PAR2 = END PLANE
PAR3 = INCREMENT (Set this to 0 to allow global copying to new planes. Otherwise, you can only copy to existing
planes.)

PAR10 = XMIN FOR PRE-ZOOM WINDOW

PAR11 = XMAX FOR PRE-ZOOM WINDOW
PAR12 = YMIN FOR PRE-ZOOM WINDOW
PAR13 = YMAX FOR PRE-ZOOM WINDOW

PAR16 = LINE SNAP TOLERANCE(Project Units)

PAR17 = POINT SNAP TOLERANCE(Project Units)
PAR18 = SET AUTO-STEP DISTANCE
PAR19 = VERTICAL EXAGGERATION FACTOR ( > 1 STRETCHES, < 1 SHRINKS VERTICALLY)

PAR 30 = DIAMETER OF SCALABLE CURSOR

END
Revised: 23-July-96 Page 650ED-3
 MineSight®
M650ED - INTERACTIVE VBM EDITOR Proprietary Software: Mintec, inc.

PROGRAM STRUCTURE
Menu 1 Contains display features and general operation features

Menu 2 Contains single feature editing features

Menu 3 Contains global editing features

Each of the 650–series programs has Menus 1–3 so that feature editing is standard throughout the series.

TOGGLE SWITCHES

The following toggle switches are used throughout the 650–series. They appear across the bottom right of the display screen.
Additional details on their usage can be found in the help file.

Snap Mode—Point Coordinate Mode—Relative

Snap Mode—String Coordinate Mode—

Distance/Angle

Snap Mode—Grid Intersect Mode—Line

Coordinate Intersect Mode—Point

Mode—Absolute

Page 650ED-4 Revised: 23-July-96

MineSight®
Proprietary Software: Mintec, inc. M650ED - INTERACTIVE VBM EDITOR

SAMPLE [Link] FILE

In the M650 programs, a feature’s graphical display properties (eg. node color or line type) are stored in a Feature Table file. If you
have an old-format VBM file then your Feature Table file must be named [Link]. If you have a new-format VBM your Feature
Table file will be named [Link] by default, but can be renamed using the Featr Tab key under the Utilities button on the first
menu strip of any M650 program (See VBM Technical Section for the distinction between old and new VBM files). In this way,
several VBM files can use a single Feature Table file or each VBM can have a unique Feature Table file.

On a PC, your Feature Table file should be in your current working (local) directory. On a workstation, your Feature Table file will
created in your home directory but can be overridden by a Feature Table file in your current working directory.

The values in the Feature Table file are determined by a feature’s graphical display properties selected under the Feature Props key
of the first menu strip. After choosing a set of properties, the information is transferred to the Feature Table file when the program
is exited. You can reset a feature’s properties to the plain default values using the Default key on the Feature Props panel. Features
with plain default values are not stored in the Feature Table file.

Example VBM Feature Table file (version 3.0) (Note: These are fixed format records)

899 0.9520.3670.9410.0000.0001.0000.0000.0000.000— solid 0

901 0.5070.9880.9880.0000.0001.0000.9560.9700.000— solid 0

1002 0.9520.5570.0000.0000.0001.0000.0000.0000.000— solid 0

2003 0.9950.9840.0000.0000.0001.0000.0001.0000.000— solid 0

NOTE: The Feature Table file has a specific format and should not be edited manually. Use the Feature
Props key on the first menu strip to change feature properties.

Revised: 23-July-96 Page 650ED-5

 MineSight®
M650ED - INTERACTIVE VBM EDITOR Proprietary Software: Mintec, inc.

SAMPLE [Link] FILE

[Link] is an index file used to manage all the metafiles in use in a particular project. For each metafile, this index
contains the metafile name, its elevation or section, its group and a one line description.

Programs M122MF, M126MF and M650ED will all create this index the first time a metafile function is run. Thereafter, each
metafile function used will update the index file. This file can also be created and edited with your system’s text editor.

#
# [Link]
## File Group List
group;COMMON ;
group;ANNOTATE ;
#
# file items format:
# file;file name;elevation/section;group name;
# desc;file description record;
#
file;[Link] ; 4600.00;COMMON ;
desc;drillhole collars ;
file;[Link] ; ;COMMON ;
desc;stripper pit ;
file;[Link] ; ;COMMON ;
desc;composites ;
file;[Link] ; ;ANNOTATE ;
desc;title block for plot ;

M650ED SAMPLE RUN FILE

MEDS-650V1 10=[Link] 25=[Link] 3=[Link]
*** VBM EDITOR PLANES 2600 – 4600

USR = ABC
IOP1 = 0 / 0=SHOW LIKE FEATURES IN SAME COLOR
COM / 1=SHOW COPLANAR FEATURES IN THE SAME COLOR

IOP2 =4 / FLAG 1=LLL RANGE, 2=RRR RANGE, 3=FULL RANGE, 4=ALL

IOP3 = / START OF FEATURE CODE RANGE

IOP4 = / END OF FEATURE CODE RANGE

PAR1 = 2600 / START PLANE TO EDIT

PAR2 = 4600 / LAST PLANE TO EDIT
PAR3 = 50 / INCREMENT

PAR10 = / PRE-ZOOM WINDOW: XMIN, XMAX, YMIN, YMAX

END

Page 650ED-6 Revised: 23-July-96

MineSight®
Proprietary Software: Mintec, inc. M650IP - INTERACTIVE GRAPHICS PLANNERLE

M650IP INTERACTIVE GRAPHICS PLANNER

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M650IP is a highly interactive program designed to aid the M650IP acts as a sophisticated grade and tonnage calculator:
mining engineer in the planning and scheduling of short range design various polygonal outlines on the screen, and the program
mine production. M650IP can also be used for long range will calculate reserves interactively. In order to use it, you must
planning. It is one of the MineSight® Graphical Interface (MGI) have already built a 3-D block or GSM model. You then extract
programs. the desired items from the model in a format suitable for M650IP.
The extraction routines are M829V1 (plan) or M829V2 (section).
PROGRAM FLOW DIAGRAM M650IP will then access the extracted slices from the model,
bench by bench, section by section or seam by seam.
RUN FILE: Cut is the term used to describe a user-defined polygon which
- Plane numbers outlines an area (volume) of material removed from the mining
- Feature codes bench or section. A cut is created by outlining an area in the
- Weight conversion factor project window using the mouse.

Overlapping cuts are allowed so that the best initial design and
sequence of cuts can be found quickly. To avoid overlapping
on the final design, use the point, string and grid snap features
so that new cuts are exactly coincident with other cuts and VBM
features. This prevents sections of reserves from being counted
INPUT: CALCS:
twice.
- PCF - Calculate the partials
- File 25 between topo and dump An option is also available to check to see if a block has already
surface been mined out. If this option is turned on, then a block that has
-Calculate the area, volume 100% of its material removed cannot be mined a second time. If
and tonnage of the dump
- Output a file of paritals this situation is encountered, the cut will not be allowed.

Cuts can be edited using the EDIT CUT button and the functions
under Menu Strip 4 of M650. This option allows manipulation
of cuts that have been already designed.
OUTPUT:
All cuts are considered permanent. When you exit the program,
- ASCII file of partials you will be asked “Save IGP Cuts?” All cuts are either saved or
- Printer Output File
discarded. To discard cuts individually, use the DEL CUT
function before exiting.

This documentation includes general operations and samples

of all the files used by M650IP. Detailed information on
individual features is found in the on-line help.

An overview of the common features of all MineSight®

Graphical Interface programs can be found in the Getting Started
section of the Introduction to MineSight®, Volume I.

Revised: 18-May-06 Page 650IP-1

 MineSight®
M650IP - INTERACTIVE GRAPHICS PLANNER Proprietary Software: Mintec, inc.

Page 650IP-2 Revised: 18-May-06

MineSight®
Proprietary Software: Mintec, inc. M650IP-INTERACTIVE GRAPHICS PLANNER

M650IP—INTERACTIVE GRAPHICS PLANNER

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-650V1 10=filename 25=filename 27=filename 3=filename;

MEDS-650V1 19=filename 30=filename
where

MEDS-650V1 must be the first 10 columns

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
27 = the name of the 3-D CONNECTION FILE (optional)
19 = the name of the AREA INDEX FILE (default = [Link])
30 = the name of the PARAMETER FILE (default = [Link])
3= the name of the PRINTER OUTPUT FILE

NOTE: If Files 19 and 30 are not specified, the default file names will be used.

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free field format)

All options from M650ED are valid.

Additional Options:

IOP17 = Number of passes through a block to compute partials (Default = 10)

IOP18 = 0 Block partial is the minimum of the cut partial and TOPO%
= 1 Block partial is the product of the cut partial and topo%

IOP19 = 0 Count waste up to 100%

= 1 Count waste only up to topo%

NOTE: IOPs 18 and 19 are used only when ORE% is used.

IOP20 = 1 Report standard deviations of grades in a cut report

= 0 Do not report standard deviations (default)

GENERAL OPERATION
Move to the M650IP menu by either selecting the IGP button on Menu 1 or the Menu 4 button at the bottom of the menu strip. The
INIT IGP function must be chosen first each time the program is run. If any cuts have been generated in a previous run of M650IP,
they will appear as standard VBM features.

Revised: 24-October-03 Page 650IP-3

 MineSight®
M650IP-INTERACTIVE GRAPHICS PLANNER Proprietary Software: Mintec, inc.

CHECKS

Once the INIT IGP button is picked, M650IP checks for a valid Area Index File (default [Link]) containing a list of area/
parameter file pairs on which to operate. Areas correspond to the slice index files generated by M829V1 or M829V2. If none are
found, a panel will prompt for at least one slice index file. M650IP then prompts for a Parameter File to associate with the Area File.
If it is found, and it has enough information, it may be used. Otherwise, a series of panels must be filled in for the run.

To ensure that reserve report files are up to date, the Cross Reference File is processed as soon as INIT IGP is selected. A complete
new set of reserves files (RPT) is then generated. This accounts for any changes that may have occurred to both the cuts in the VBM
file and the Cross Reference File.

PROCESS

All IGP functions are then performed from the fourth menu strip in M650. Standard functions such as NEW CUT, QUERY CUT,
QUERY BLOCK, DELETE CUT, EDIT CUT are available. Only one slice at a time can be loaded into M650IP. Operations that
require a slice file (i.e. NEW CUT) can only be performed on the current slice.

After a schedule is generated and EXIT IGP is picked, you will be asked if you want to save the reserves report. This allows you to
run in a temporary mode.

You will then be asked if you want to save the cuts. If you answer yes, all cuts are saved in the VBM file, and a Cross Reference File
is generated ([Link]). This file contains a list of cuts that were created, the area, slice, and period to which they belong, and their
VBM feature code and plane number. Upon exit, the current period is recalculated.

M650IP contains logic for maintaining a partials map for each slice that is processed. This provides a number of options. A partials
map, in combination with STRING SNAP, removes the need for cut clipping logic. Also, mining out an overlay will not be allowed
if a cut already exists within the overlay. When the partials save option is on, slice files will be saved in temporary work files named
[Link] where mm is the area number of the slice and nnn is the slice number.

The option to use variable height cuts uses the partials logic, and allows you to make a partial cut of a slice.

Page 650IP-4 Revised: 21-September-01

MineSight®
Proprietary Software: Mintec, inc. M650IP-INTERACTIVE GRAPHICS PLANNER

SAMPLE FILES
RUN FILE (input)

— Standard M650 run file

— File 30 is used to specify the PARAMETER FILE (default = [Link])
— File 19 is used to specify the AREA INDEX FILE (default = [Link])
— Specify overlay and cut feature codes with IOP2,3,4 ... 16
— File 31 is the name of the EQUIPMENT CYCLE TIME FILE (default = [Link])
— File 32 is the name of the EQUIPMENT FACTOR FILE (default = [Link])

IOP1 = 0 SHOW LIKE FEATURES IN SAME COLOR

1 SHOW COPLANER FEATURES IN SAME COLOR

IOP2 = 1 RANGE OF FEATURES SPECIFIED BY LEFT SIDE CODE

= 2 RANGE OF FEATURES SPECIFIED BY RIGHT SIDE CODE
= 3 RANGE OF FEATURES SPECIFIED BY FULL CODE
= 4 LOAD ALL FEATURES
= 5 RANGE OF FEATURES SPECIFIED BY A LIST

IOP3 = MINIMUM CODE RANGE

IOP4 = MAXIMUM CODE RANGE

NOTE: IOP3 and IOP4 apply only when IOP2 = 1, 2 or 3. IOP3 through IOP13 provide a list of items
when IOP2 = 5

IOP16 = NUMBER OF EDITS BETWEEN AUTOMATIC FILE SAVES

IOP17 = NUMBER OF PASSES THROUGH A BLOCK TO COMPUTE PARTIALS (default = 10)

IOP18 = 0 USE MINIMUM OF TOPO PERCENT AND OF THE CUT PARTIAL TO DETERMINE BLOCK ORE
PERCENT
= 1 USE THE PRODUCT OF TOPO PERCENT AND CUT PARTIAL

NOTE: IOP18 is used only if ore percent is used. Product is taken in other cases.

IOP19 = 0 Count waste up to 100%

= 1 Count waste only up to topo%

NOTE: IOPs 18 and 19 are used only when TOPO% is used.

IOP20 = 1 Report standard deviations of grades in a cut report

= 0 Do not report standard deviations (default)

IOP22 = ORIENTATION OF SLICES IN ROTATED MODEL

= 1 XZ MODEL SECTIONS
= 2 YZ MODEL SECTIONS
= 3 XY MODEL SECTIONS

NOTE: Used with rotated models ONLY.

PAR1 = START PLANE TO LOAD FROM VBM

PAR2 = END PLANE TO LOAD FROM VBM
PAR3 = INCREMENT OF LOADED PLANES

PAR4 = MINIMUM DISPLAYABLE PLANE

Revised: 21-September-01 Page 650IP-5

 MineSight®
M650IP-INTERACTIVE GRAPHICS PLANNER Proprietary Software: Mintec, inc.

PAR5 = MAXIMUM DISPLAYABLE PLANE

PAR6 = INCREMENT OF DISPLAYABLE PLANE

PAR10 = XMIN FOR PRE-ZOOM WINDOW

PAR11 = XMAX FOR PRE-ZOOM WINDOW
PAR12 = YMIN FOR PRE-ZOOM WINDOW
PAR13 = YMAX FOR PRE-ZOOM WINDOW

PAR16 = LINE SNAP TOLERANCE (Project Units)

PAR17 = POINT SNAP TOLERANCE (Project Units)

PAR18 = SET AUTO-STEP DISTANCE

PAR19 = VERTICAL EXAGGERATION FACTOR

PAR30 = DIAMETER OF SCALABLE CURSOR

SLICE FILES (input)

— the SLICE FILE names are stored in AREA (SLICE INDEX) FILES.
— generated with M829V1 (plan) or M829V2 (e-w section)
— binary files that store selected File 15 items
— PCF independent (for multiple area planning)
— slice files from different areas must contain the same items
— incompatible with M830V1 slice files

AREA or SLICE INDEX FILES (input)

— standard SLICE INDEX FILES are generated by M829V1 (plan) or M829V2 (e-w section) along with SLICE FILES
— the M829 SLICE INDEX FILES are called AREA FILES in M650IP
— the current AREA FILE (if any) is shown in the Information Window
— contains list of SLICE FILES within one area run of M829V1 or M829V2
— contains the SLICE FILE name, slice number, elevation (plan) or northing/easting (section), and seam name (N/A for
metal projects)

grad1.5 5 95.00 N/A

grad1.6 6 90.00 N/A

AREA INDEX FILE — default [Link] (input/output—File 19)

— file will be created and maintained by M650IP

— contains a list of AREA (SLICE INDEX) and PARAMETER FILE pairs.
— each AREA FILE can be linked to one or more PARAMETER FILES
— there can be up to 30 AREA/PARAMETER FILE pairs in one AREA INDEX FILE
— areas can be from multiple PCFs
— contains the following information:

Page 650IP-6 Revised: 21-September-01

MineSight®
Proprietary Software: Mintec, inc. M650IP-INTERACTIVE GRAPHICS PLANNER

PARAMETER FILE — default [Link] (input/output—File 30)

— used instead of run file because of the large number of options

— the current PARAMETER FILE (if any) is shown in the Information Window
— the PARAMETER FILE specified in the run file will be the default
— if no PARAMETER FILE is in the run file, [Link] will be the default
— if an AREA FILE is not linked to a PARAMETER FILE in the AREA INDEX FILE, then the Default PARAMETER
FILE will be used
— required items include: initial slice, starting period number, starting period name, plane name, feature code for cuts,
display item, at least one color cutoff, and at least one material class
— if file does not exist, panels will prompt for necessary parameters
— free format
— parameter lines can be in any order
— keyword at the end of the line must remain unchanged
— typical PARAMETER FILE contains the following:

# M650IP Parameter File

# Refer to documentation before editing this file
11 /INITIAL-SLICE
1 /START-PERIOD
92mn1 /PERIOD-NAME
a /PLAN-NAME
800 /BASE-FEATURE-CODE
T /REVERSE-FLAG
GOLD /DISPLAY-ITEM
GOLD /REPORT-ITEM
TOPO /TOPO-ITEM
ZONE /CODE-ITEM1
ROCK1 1 2.00 0.40 0.80 1.20 1.60 2.00 /MATERIAL-CLASS
ROCK2 2 2.00 0.80 0.80 1.20 1.60 2.00 /MATERIAL-CLASS
WASTE 3 2.00 0.00 /MATERIAL-CLASS
3 /DEFAULT-CLASS
SG /TON-CALC
0.40 0.0000 0.9775 0.9775 /DISPLAY-CUTOFF
0.80 0.0000 0.0000 1.0000 /DISPLAY-CUTOFF
1.20 0.0000 1.0000 0.0000 /DISPLAY-CUTOFF
1.60 0.9852 0.9930 0.0147 /DISPLAY-CUTOFF
2.00 0.8998 0.4107 0.4301 /DISPLAY-CUTOFF
2.40 0.9658 0.0000 0.7795 /DISPLAY-CUTOFF
rpt /REPORT-FILE-EXT
F /VARIABLE-CUT-FLAG

For a detailed description of the parameter file contents, see the Param Panel 1-4 choices in the on-line help file.

CUT CROSS REFERENCE FILE - default [Link] (input/output)

This file is the key to M650IP as it provides the only reference as to which VBM features are cuts. This file may be edited outside the
program, but care should be taken when doing so.

— if exists, every cut that is defined is processed and the reserves calculated
— automatically sorted by M650IP when it is created and should be in the sort order area, slice, period
— contains the following information:

Revised: 21-September-01 Page 650IP-7

 MineSight®
M650IP-INTERACTIVE GRAPHICS PLANNER Proprietary Software: Mintec, inc.

# M650IP Cut Cross Reference File

# Refer to documentation before editing this file
# IA IS IP AREA SLICE PER GSM CUT# FEAT LAB1 LAB2 LAB3 HGT
1 10 1 [Link] 70.00 91m01 N/A 1 10001 stock N/A N/A 50
1 11 1 [Link] 65.00 91m01 N/A 2 10002 stock N/A N/A 50
1 11 1 [Link] 65.00 91m01 N/A 1 10001 mill N/A N/A 50
2 10 1 [Link] 70.00 91m01 N/A 2 10002 mill N/A N/A 25
3 13 1 [Link] 55.00 91m01 N/A 1 10002 dump N/A N/A 30

IA is the area index GSM is the name of the GSM level (if not 3D model)
IS is the slice index CUT# is the number of the cut on the slice
IP is the period index FEAT is the VBM feature code
AREA is the slice index file for the area LAB1 is a 5 character cut descriptor
SLICE is the coordinate of the slice LAB2 is a 5 character cut descriptor
PER is the Period name LAB3 is a 5 character cut descriptor
HGT is the height of the cut

REPORT FILES — default [Link] (output)

— name is based on plan name (m) and period name (nnnnn)

— generated for each period in the plan
— contain reserves for each cut and the cumulative reserves for the period
— format has been changed from the M830V1 format due to increased number of cutoffs
— contains the following information:

CUT 1 SLICE 11 COORD 65.00 AREA 1 PERIOD 1 92mn1 asdf

MATERIAL ITEM CUTOFFS ON GOLD
0.80 1.20 1.60 2.00
Rock1 TONNES 0.0 946.0 770.0 66.0
B.C.M. 0.0 430.0 350.0 30.0
GOLD 0.00 1.59 1.85 2.66
SILVR 0.00 10.47 11.21 14.88
0.80 1.20 1.60 2.00
Rock2 TONNES 2838.0 8217.0 1914.0 0.0
B.C.M. 1290.0 3735.0 870.0 0.0
GOLD 1.07 1.56 1.66 0.00
SILVR 11.19 11.06 11.72 0.00
EQUIV 1.09 1.54 1 .64 0.00

M830 COMPATIBILITY FILES

To allow compatibility with M830V1 (version 3 of IGP), two files are generated — the NDX file and the CUT file. The NDX file
contains a summary of reserves for each cut and the CUT file contains the cut outlines in M122 format (for plotting).

Page 650IP-8 Revised: 21-September-01

MineSight®
Proprietary Software: Mintec, inc. M650PT - PIT EXPANSION

M650PT PIT EXPANSION

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M650PT is an interactive program used to do pit expansion. It
M650PT geometrically expands a pit from some defined initial
is one of the MineSight® Graphical Interface (MGI) programs.
shape. To use it, all bottom bench outlines and pushbacks for a
It allows you to expand the pit one bench or multiple benches at
pit need to be digitized.
a time and see the results immediately on the screen. It also
allows the graphical definition of all pit characteristics, including To remain consistent within MineSight®, this program assumes
slope, berms, roads and slots. An enhanced version is available that bench outlines are referenced by the bench toe. The midpoint
that allows the calculation of tons and grade at the same time as outline of the bench, with respect to elevation, is used for
the pit expansion. This enhanced version (M650PX) is a subsequent volume calculations.
combination of M650PT (pit expand) and M650IP (IGP).
M650PT expands the input pit bottoms up at the slope specified
PROGRAM FLOW DIAGRAM at each point and combines the interacting slopes from multiple
pit bottoms as the expansion progresses. Each pushback is also
combined with the generated bench outline to form a new shape
RUN FILE: for expanding the next bench.
- Plane numbers
The generated bench outlines are stored in a VBM file. The
- Feature codes
- Weight conversion factor feature code will be the same as that of the pit bottom.

Plots of the pit can be created with any VBM plotting program.

Current program features include:

• expand one or more pit bottoms

INPUT: CALCS:
• include pushbacks
- PCF - Calculate the partials
- File 25 between topo and dump • combine multiple shapes as they expand & interact
surface
-Calculate the area, volume
and tonnage of the dump
• generate one or more road system
- Output a file of paritals
• write pit to the VBM file for a more detailed interaction
with the topography in pit display and block partial
computations

OUTPUT: • change pit wall slope in different rock types

- ASCII file of partials

- Printer Output File

Revised: 18-May-06 Page 650PT-1

 MineSight®
M650PT - PIT EXPANSION Proprietary Software: Mintec, inc.

Two digitizing rules must be applied to insure correct operation

of M650PT.

1. Pit bottom outlines must be digitized in a clockwise direction

and must close.

2. Digitize pushbacks such that the first and last points are inside
the generated outline for that bench. Again, digitize in a
clockwise direction. A pushback can be closed like pit
bottoms and will actually ensure better results than unclosed
shapes.

Sometimes it may be easier to input a completely new pit bottom

rather than multiple pushbacks if the shape of the bench is much
different from the previous generated bench.

SETUP—Selection of Pit Expansion

Parameters
Each time you begin a pit expansion session, the setup panel
must be chosen first. Define the parameters you wish to use.
These parameters will be saved for future sessions. The next
time you use M650PT, select SETUP and, if there are no changes
to be made, click on OK and the previous parameters will be
used.

A thorough discussion of the geometry parameters (min and

max angles and distances) is included in the M701V1
Requirements and Considerations section.

This documentation includes program operation and a sample

run file. Detailed information on individual features is found in
the on-line help file.

An overview of the common features of all MineSight®

Graphical Interface programs can be found in the Getting Started
section of the Introduction to MineSight®, Volume I.

Page 650PT-2 Revised: 18-May-06

MineSight®
Proprietary Software: Mintec, inc. M650PT – PIT EXPANSION

M650PT – PIT EXPANSION

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-650V1 10=filename 25=filename 27=filename;

MEDS-650V1 15=filename 3=filename 34=filename
where

MEDS-650V1 must be the first 10 columns

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
27 = the name of the 3D CONNECTION FILE (optional)
15 = the name of the MINE MODEL FILE (optional)
3 = the name of the PRINTER OUTPUT FILE
34 = the name of the PIT PARAMETER FILE (optional e.g., [Link])

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = 0 SHOW LIKE FEATURES IN SAME COLOR

= 1 SHOW COPLANER FEATURES IN SAME COLOR

IOP2 = 1 RANGE OF FEATURES SPECIFIED BY LEFT SIDE CODE

= 2 RANGE OF FEATURES SPECIFIED BY RIGHT SIDE CODE
= 3 RANGE OF FEATURES SPECIFIED BY FULL CODE
= 4 LOAD ALL FEATURES
= 5 RANGE OF FEATURES SPECIFIED BY A LIST

IOP3 = MINIMUM CODE RANGE

IOP4 = MAXIMUM CODE RANGE
NOTE: IOP3 and IOP4 apply only when IOP2=1,2 or 3. IOP3 throughIOP13 provide a list of items when
IOP2=5

IOP16 = NUMBER OF EDITS BETWEEN AUTOMATIC FILE SAVES

IOP17 = 0 CONNECT NEXT TOE LINE TO THE CREST LINE AT THE ROAD LINE END (default)
= 1 MAKE NEXT TOE LINE PARALLEL TO THE CREST LINE UP TO THE ROAD END
NOTE: 1) Used for the toe midline crest expansion only.
2) Used in M650PT only. Use IOP27 in M650PX.

IOP18 = 0 LEAVE THE OUTER FEATURE ONLY WHEN MERGING PITS (default)
= 1 LEAVE ONE FEATURE INSIDE THE OTHER IF THEY GO IN OPPOSITE DIRECTIONS
NOTE: Used in M650PT only. Use IOP28 in M650PX.

Revised: 22-September-98 Page 650PT-3

 MineSight®
M650PT – PIT EXPANSION Proprietary Software: Mintec, inc.

The next two options are used in M650PX ONLY:

IOP27 = The same as IOP17.
IOP28 = The same as IOP18.

PAR1 = START PLANE

PAR2 = END PLANE
PAR3 = INCREMENT
PAR10 = XMIN FOR PRE-ZOOM WINDOW
PAR11 = XMAX FOR PRE-ZOOM WINDOW
PAR12 = YMIN FOR PRE-ZOOM WINDOW
PAR13 = YMAX FOR PRE-ZOOM WINDOW

PAR16 = LINE SNAP TOLERANCE (project units)

PAR17 = POINT SNAP TOLERANCE (project units)
NOTE: SLOPES ARE TAKEN FROM INPUT PARAMETER FILE [Link].

GET15 = label-15 (item for controlling slope)

NOTE: Must specify 15= on Names Line.

END

PROGRAM OPERATION
Move to the Pit Expansion Menu by either selecting the PIT XPAND button on Menu 1 or the Menu 4 button at the bottom of the
menu strip. The SETUP function must be chosen first each time the program is run. If you do not choose it first, it will automatically
appear when you choose PICK FTR or SET SLOPE.

Details on the use of each function can be found below. A diagram on designing a road within the pit is shown on the next page.

STEPS FOR USING PIT EXPANSION FUNCTIONS

1. Set up pit expansion parameters.

2. Pick Pit bottom and define slope.

3. Define expansion information: Berm -WidthRoad - Width, direction, grade, start pointSlot -Trace, width, grade and wall slope.

4. Repeat Steps 2 and 3 for each pit bottom.

5 Use EXPAND to create the next bench.

If using the variable slope option, only one starting pit may be chosen. Also if working with variable slopes, the face slope of the
bench is the slope being varied.

Alternatively, a berm table, a road table, a slot table, a table of benches can be created, and automatic expansion can be done with
MULT EXP. Berm and slope control information can also be read from MineSight® 3-D Block model.

If running M650PX, then the IGP options must also be setup before any expansions are run. See the documentation for IGP for a full
description of these options.

Page 650PT-4 Revised: 22-September-98

MineSight®
Proprietary Software: Mintec, inc. M650PT – PIT EXPANSION

PARAMETER SETUP (REQUIRED)

This option is used to edit the pit expansion parameters. PARAMETER SETUP must be chosen and the parameters verified each
time PIT EXPAND is run. This must be done before any other function can be performed.

The items required are:

PIT EXPANSION PARAMETERS PANEL

Base feature code

Toe feature code
Midline feature code
Crest feature code
Road width (default = 100, 30 for metric)
Road grade (default = 0.10 - 10 percent)
Bench height (default = PCF bench height) Negative bench height to expand down
Bank angle (default = 70 degrees)
X constant (default = 0)
Y constant (default = 0)
Default Pit Slope (default = 45.0 degrees)
Default Berm Width (default = 0)
Max angle between rays (default = 15.00)
Min concave angle (default = 60.00)
Max distance between pts (default = 100.00, 30.0 for metric)
Min distance - convex pts (default = 5, 2 for metric)
Max distance - concave pts (default = 5, 2 for metric)
Min area in curve (default = 9999, 999 for metric)

The first group of input fields are the parameters required to start expansion.

First you must select a Base feature code. The expansion will start from the features having the base code that you selected. All the
features with the base code on successive benches will be picked up automatically. If you want just toe outlines for each bench then
enter a Toe feature code, which is optional. The program will default the toe feature code to the base feature code, but it may be
beneficial to select a different code for toes. If you want to outline midlines and crests you must select codes for Midline features and
Crest outlines as well. You must select both of these codes to start a midline-toe-crest type pit expansion.

The next two important parameters are Bank angle and Bench height.

Bank angle (which is also called Face slope angle or just Face slope) is constant for all pits in the expansion.

Bench height is the elevation step between two successive expansion toe lines. If you want to perform downward expansion, enter
a negative value for the bench height.

Finally, among the required parameters are default values for the Road width, Road grade (as a fraction of 1, e.g., enter 0.1 for 10%),
Default pit slope angle (in degrees), and Default berm width. These default values may be overridden by subsequent instructions
during your work, but they must be set for the program to have some values as a “last resort.”

Revised: 22-September-98 Page 650PT-5

 MineSight®
M650PT – PIT EXPANSION Proprietary Software: Mintec, inc.

Figure 1- Default parameter values (metric project)

The second group of parameters govern the geometry of expansion. Although default values are provided for these parameters, you
should not ignore them. There are six parameters: Maximum distance between points, Maximum angle between rays, Minimum
distance between concave points and Minimum distance between convex points, Minimum concave angle, and Minimum area for
inclusion.

These geometry parameters are very important. Angle parameters can be left at default values on the first pass if you are not yet
familiar with M650PT. The distance parameters, however, should be adjusted according to the scale of your project.

Figures 2 through 6 illustrate how the geometry parameters work. Arrows show the direction of expansion.

Maximum angle between rays defines how many points are inserted when rounding a convex angle. The angles between inserted
points are equal and cannot be larger than the value specified for the maximum angle (Figure 2).

Figure 2 - Maximum angle between rays

Page 650PT-6 Revised: 22-September-98

MineSight®
Proprietary Software: Mintec, inc. M650PT – PIT EXPANSION

Minimum concave angle sets the lower limit on the concave angle that the program will expand. If a point is the vertex of a concave
angle that is less than the value entered, then the point will be deleted from the expanded feature (Figure 3).

Figure 3 - Minimum concave angle

Maximum distance between points defines how dense nodes on the pit features should be. If the distance between two points on the
expanded feature is greater than the value entered for the maximum distance, additional point(s) will be inserted on the interval
between those points (Figure 4). You should make this value small enough to ensure smoothness of the features, but the value should
not be too small because the more points you have, the slower the expansion. Also, there is a limit of 2000 for the total number of
points in the pit features on one level.

Figure 4 - Maximum distance between points

Revised: 22-September-98 Page 650PT-7

 MineSight®
M650PT – PIT EXPANSION Proprietary Software: Mintec, inc.

Minimum distance between convex points sets the lower limit on the distance between points on a convex part of the expanded
feature. The vertex of a convex angle will be deleted from the expanded feature if the distance from it to the previous point is less
than the value entered as the minimum distance between convex points (Figure 5).

Figure 5 - Minimum distance between convex points

Similarly, Minimum distance between concave points sets the lower limit on the distance between concave points (Figure 6). This
distance (as well as Minimum concave angle) helps to avoid self-intersections that can appear when expanding concave parts of the
feature.

Figure 6 - Minimum distance between concave points

Page 650PT-8 Revised: 22-September-98

MineSight®
Proprietary Software: Mintec, inc. M650PT – PIT EXPANSION

Store midlines, crest at toe elevation? Yes or No

If no, then will be stored at correct elevations.

Delete Features? Yes or No

When doing an expansion, choose whether to delete existing features with the same feature code as toe, midline, crest features.
This is useful when doing repetitive expansion as you do not have to do a global delete between each expansion.

Calc Reserves? Yes or No

Only used in conjunction with IGP mode. If IGP mode is on, then the choice is whether to use the slice files as overlays only, or
to calculate reserves as well.

User Cam? Yes or No

When specifying roads in the pit, the choice is whether to have the program modify the starting shape and add the road start, or
have the user design the road cam on the starting bench. This starting shape must exist on the feature before the start of
expansion.

Constant Berms? Yes or No

Using this option will use the berm table, berms from the model or the default berm when expanding. The expansion is calculated
from the face slope and berm, the default pit slope is ignored. If this option is not on, the program calculated the required berm
width from the face angle, and default pit slope plus any remaining berm which may not yet have been taken into account by the
calculation.

Fast Expansion? Yes or No

With this on, expansions are done very quickly without checking for loops. This method is recommended for rough work and
not for the final product. When expansions are done this way, there may be considerable editing to expansions. For the final
product, turn this option off and the results will not need to be edited.

Once entered, all of these items are written to a parameter file (default = [Link]). An alternate name for this file may be specified
on the Names Line of the M650 run file as file 34. These items will be the defaults until they are modified with PARAMETER
SETUP.

FEATURE CODES

The base feature code is required as the basis to any expansion. The toe, mid-line and crest feature codes are optional. The toe feature
code defaults to the base code and is used to expand a feature into the same code. A duplicate will always be present for the pit
bottoms and any pushbacks encountered. If either one of the midline or crest codes equals zero, only a toe expansion will be done.
If they are greater than zero the expansion will be done with all three contours.

The mid-line and crest can be stored at their actual elevations or on the same elevation as the toe.

Revised: 22-September-98 Page 650PT-9

 MineSight®
M650PT – PIT EXPANSION Proprietary Software: Mintec, inc.

PUSHBACKS

Any feature encountered on the expansion onto a new bench will be picked up by the expansion and joined or merged into the
expanding pit. The limitation on the number of unjoined features that can be handled in the expansion is 20. Certain features will not
be joined properly. See the drawing below for an example.

BANK ANGLE

This angle is used in the determination of the slope from the toe to the mid-line and the mid-line to the crest. it is assumed to be
constant for all walls for one expansion.

WALL SLOPE vs BERM WIDTH DESIGN

If you are designing a pit with toe, crest and mid-line, the program will calculate the correct berm width, given an overall pit slope
(i.e., a pit with a 45 degree average slope, a 70 degree face angle and a 5 meter bench height will put a crest to toe berm of 3.18
meters (5m - 5m * tan70). To get an exact berm width, use Constant Berm.

Conversely, if you specify the average pit slope to be the same as the face angle, you may specify the berm with width, which in turn
will dictate the average overall wall slope. Putting a berm width of 0.0 is an easy way to specify double benching. For example, a
face slope and pit slope of 70 degrees, a bench height of 5 meters, and a specified berm width of 4 meters will give a crest to toe berm
of 5 meters and an overall pit slope of 40.66 degrees. The simpler way, or course is to specify constant berm and use the berm table
to setup on which benches you want berms.

Page 650PT-10 Revised: 22-September-98

MineSight®
Proprietary Software: Mintec, inc. M650PT – PIT EXPANSION

EXPANSION RULES

Normally a pit is expanded up from a clockwise pit bottom, using a positive bench height. To expand a pit down, use a counterclockwise
pit bottom and a negative bench height. For dumps, use a counterclockwise feature and a positive bench height to expand a dump up
and a clockwise feature and a negative bench height to expand a dump down.

Pits and dumps can be designed with roads going up or down.

PICK FEATURE (required)

This option is used to select a pit bottom(s). The selected feature must have the same feature code as the base feature code defined
in PARAMETER SETUP. This must be done before slope, berm and road characteristics are defined. You are asked to verify that
the correct pit bottom has been selected. If NO, then pick another feature or click right to exit the function. If YES, then you must
also define the slope for the feature. The slope definition is described below.

SET SLOPE (optional)

When a feature is PICKed, the slope is defined at the same time. The SET SLOPE function is used to modify the slope after the
expansion has started. Three options apply here

Definition of constant slope

Definition of variable slope OR
Definition of slope from model

In defining a constant slope, enter the angle required. The default is taken from the setup parameter panel.

Variable slope is defined by using the mouse to define face slope sectors. With the left mouse button, define a series of points around
the pit perimeter to mark the endpoint of each slope segment. Click the right button when you have finished marking the points. The
program then highlights each segment and asks you to enter the slope for that segment. If using this option you can expand from one
pit bottom only. Also when using variable slopes be sure you have defined all berms.

Model slope must be predefined by specifying the name of the model file (File 15) on the NAMES line of the M650PT run file. A
GET15 item must also be specified to identify the model item that contains lookup codes. The codes must be in the range 1 to 30 and
correspond one to one to the slopes defined on the MODEL SLOPE INFORMATION PANEL. If retrieving Slope and Berm codes
from the model, the slope code must come first on the GET15 line.

Pit slopes for model code option.

A maximum of 30 slope codes can be read from the model. The item that contains the slope codes must be defined in the run file
for M650PT/PX with a GET15 command.

Read 1st Bench of Model Only? Yes or No.

Used to read slope codes from 1st model bench only

Change slopes gradually? Yes or No

Used when reading slope codes from the model. If yes, then the transition between slopes is smoothed over a number of benches
to provide a more reasonable pit design. The slope can never go steeper than the specified slope for that block.

Revised: 22-September-98 Page 650PT-11

 MineSight®
M650PT – PIT EXPANSION Proprietary Software: Mintec, inc.

SET BENCH

Use this option to define a range of starting and ending benches and bench heights for multiple expansion. The starting and ending
values are bench toes. For example, to generate a set of 5 meter benches starting at 1010 and a set of 10 meter benches starting at
1040, enter

1010 1035 5
1040 1070 10

The last 5 meter bench will start at and have a crest at 1040. The 10 meter bench will then have a toe at 1040 and continue up. Up to
10 sets of benches can be specified during one run. This information is saved to the parameter file on exit.

To define a downward multiple expansion, put in the start and end benches in reverse order and a negative bench height. (i.e., to
expand a pit down from 1000 to 800 with 6).

1000 800 -5

BERM

Berms can be specified one at a time for each bench in a single step expansion mode. Use CONSTANT BERM WIDTH to specify
a berm for an individual pit. A berm table can also be created to define a set of berms for multiple expansion. Berm codes can also
be read from a 3–D block model in the same way that slope codes can be read.

Berms in a berm table are defined by a start, end, increment between benches with berms, and a berm width. To define berms for
negative expansion, put in the start and end in reverse order and a negative berm increment.

Model berms must be predefined by specifying the name of the model file (File 15) on the NAMES line of the M650PT run file. A
GET15 item must also be specified to identify the model item that contains lookup codes. The codes must be in the range 1 to 30 and
correspond one to one to the berms defined on the MODEL BERM INFORMATION PANEL. If retrieving Slope and Berm codes
from the model, the Slope code must come first on the GET15 line.

Berm widths for model code option.

A maximum of 30 berm codes can be read from the model. The item that contains the berm codes must be defined in the run file
for M650PT/PX with a GET15 command

Read 1st Bench of Model Only? Yes or No

Used to read berm codes from 1st model bench only.

Page 650PT-12 Revised: 22-September-98

MineSight®
Proprietary Software: Mintec, inc. M650PT – PIT EXPANSION

Defining The Start Point Of A Road

Road direc

Road widt

Starting Po

Added by

SET ROAD (optional)

To do a pit expansion with roads, the following information is required.

Road number Used as a label

Road width Width in project units (feet or meters)
Road grad Grade in percentage (i.e., 0.1 for 10%)
Road start point Defined using the mouse

The road will build itself from the starting point on the pit bottom. The road cam may or may not be designed in advance. If the
USER CAM flag is set on the first panel, then the cam should be defined in advance. If an expansion is in progress, then the direction,
width and grade of an existing road can all be changed. The road can also be stopped at any elevation, and another road started at
another location.

A road table can also be built. This table will be saved on program exit. Use the DIGITIZE button on the road table panel to enter a
road start point into the panel. When picking a road start for a pit that already has a cam in it, or restarting a road from an existing one,
pick a point that is slightly back of the tip of the cam, opposite in direction from the direction of the road.

Multiple definitions for the same road can exist, that is

Number Direc Start End East North Width Grade

1 clock 1000 1200 2201 3402 20 .1
1 anti 1200 1400 0 0 20 .1
1 clock 1400 1500 0 0 20 .09

The above will define a road that switches back twice and changes grade. You only need to define the starting point of the road. the
easting and northing coordinates of the switchback locations will be calculated automatically.

Revised: 22-September-98 Page 650PT-13

 MineSight®
M650PT – PIT EXPANSION Proprietary Software: Mintec, inc.

A road can also be defined to start on a bench that is not the starting bench for the expansion.

Roads specified interactively or through a road table will be used in either single expand mode or multiple expand mode. To cancel
the use of the Road Table, answer No the the USE ROAD TABLE question, then hit <ESC> when asked for the road number.

SET SLOT

Up to 10 slots can be defined and more that one slot can originate in a pit bottom. Slots can be defined from a slot table or interactively
by entering the required information.

If using a slot table, the midline trace of the slot must have been previously defined and entered as a VBM feature. It is a good idea
to uniquely identify the slot traces (by plane and feature) so they will not get accidentally erased. A slot can have up to 11 unique
segments, each with its own wall slope, grade and width.

When defining a slot with a slot table, first use the PICK FTR function to identify the slot trace feature. Once the pick has been done,
the feature code, plane number and slot trace coordinates are written to the panel. The wall slope defaults to the pit slope, the grade
of the slot defaults to the road grade and the feature code, plane or coordinates of the slot.

To change the coordinates use the edit feature function under menu strip 2. The wall slope, grade and width can be changed. An entry
need only appear for the first slot segment. All other segments will have the same values. However, you can modify the slope, grade
or width of any segment. and this new value will be used for the rest of the segments. To turn on or off the use of a slot, toggle the
USE SLOT? button.

To define another slot, use NEXT REC to access the next record in the slot information. When all slots are defined, use OK to exit
the panel. All the slot information except for the coordinates are written to the parameter file. The coordinates are saved in the VBM
features associated with the slot trace.

If not using a slot table, one-time slots can be created by digitizing the midline trace of the slot and entering the wall slope, grade and
width. A carriage return on any segment except the first one will get the default parameters. These slots may be input ant any time
before or after any expansion. A slot entered before an expansion will be picked up on the next expansion.

HINTS:

Avoid too tight an angle in the slot trace as intersections may not be found between the slot and the pit. If this is a problem, define a
few more segments at tight corners to smooth out the slot trace.

SET BASE FEATURE

When a RESET is hit, you may wish to carry on the expansion using the already expanded feature as the starting base feature. Use
SET BASE FEATURE to do this. You will be prompted for the new base feature code. This should be the same as the original TOE
CODE.

EDIT PIT

At anytime in an expansion, the purple highlighted segment may be edited. Use the standard MENU2 edit functions (point move,
add, del) as well as splice to modify the pit shape before continuing with expansion. Avoid introducing thigh angles into the pit shape
with the e splice. Use SAVE or CANCEL from MENU2 when finished editing.

EXPAND PIT

This option creates single benches up from the pit bottom or down from the top of the pit. If any pit expansion parameter is modified,
EXPAND must be selected again to put the modifications into effect.

Page 650PT-14 Revised: 22-September-98

MineSight®
Proprietary Software: Mintec, inc. M650PT – PIT EXPANSION

MULTIPLE BENCH EXPANSION

This option is used to expand multiple benches in one pass. A bench table must be predefined with the SET BENCH function.
Optionally, a berm table may be used.

Click right or hit the <ESC> key to escape from the multiple expand mode when it is in process.

PIT EXPANSION SUMMARY

This is used to toggle the information window back to display the PIT EXPAND options.

IGP EXPANSION SUMMARY

This is used to toggle the information window back to display the IGP reserve summary. This is only available when the IGP mode
has been turned on in M650PT and reserves toggle has been turned on.

SHOW DATA

This is used to show the location of road starting points and slot traces. Toggle this button.

RESET

This de-selects the pit bottom chosen with PICK FEATURE so that another expansion feature can be selected.

M650PT SAMPLE RUN FILE

MEDS-650V1 10=[Link] 25=[Link] 3=[Link];
MEDS-650V1 15=[Link]

* * PIT EXPANSION USING FILE 15 CODES FOR VARIABLE SLOPES * * *

USR = ABC

IOP1 = 0 /SHOW LIKE FEATURES IN SAME COLOR

IOP2 = 4 /ALL FEATURES

IOP3 = /START OF FEATURE CODE RANGE
IOP4 = /END OF FEATURE CODE RANGE

PAR1 = 2600 /START PLANE TO EDIT

PAR2 = 4600 /END PLANE TO EDIT
PAR3 = 50 /INCREMENT
PAR10 = /PRE-ZOOM WINDOW: XMIN,XMAZ,YMIN,YMAX

GET15 = CODE

END

Revised: 22-September-98 Page 650PT-15

 MineSight®
M650PT – PIT EXPANSION Proprietary Software: Mintec, inc.

Page 650PT-16 Revised: 22-September-98

MineSight®
Proprietary Software: Mintec, inc. M650SV - INTERACTIVE SURVEY FILE EDITOR

M650SV — INTERACTIVE SURVEY FILE EDITOR

PROGRAM SUMMARY REQUIREMENTS & CONSIDERATIONS

M650SV is an interactive program used to graphically edit M650SV has an interface that appears and functions very similar
survey data and generate shot patterns for ore control. It is a to other 650-series programs. This program operates on specially
MineSight® Graphical Interface (MGI) program that is used formatted ASCII survey data files while all other 650-series
in both the Ore Control System and Survey modules. programs operate on MineSight® VBM databases.

PROGRAM FLOW DIAGRAM There is no limitation on the number of survey data points that
can be used. As the number of points being edited increases,
the speed of the program will decrease as would be expected.
The number of points in a string will also affect program speed.
See comments below on handling groups of individual points.

The program is designed to maintain current surveyed surfaces,

to create and/or edit shot patterns for ore control and to facilitate
the flow of data for surveying and other MineSight®
RUN FILE:
applications. Surfaces can be updated by merging in new survey
- Edit window limits data points and deleting outdated survey data. For ore control,
- Survey parameter filename existing shot patterns can be completed from a partial survey
of the pattern or new shot patterns can be designed for layout.

M650SV uses a single survey data file for input and a different
single survey data file for output. There are functions to merge
in additional input from multiple files and write selected data
to multiple output files during program usage. The data output
function supports multiple formats.
INPUT: CALCS:

- ASCII Survey data - Display functions Each survey point in the specially formatted survey data file
- Survey parameters - I/O functions contains a Point Code, Point Number, Easting, Northing and
- Display attributes - Editing functions Elevation. A Point Code is a 4 character alphanumeric label
- Shot pattern functions
that specifies the type of data. Typical codes are TOE, CST,
RAMP, B.H., ELEV, etc. The Point Number is optional for
survey data points other than blasthole locations and may range
from 0 to 999999. Survey data points, unlike VBM data, can
be treated as individual points or string points. Individual survey
points represent locations such as stations, spot elevations,
OUTPUT: shovels or blastholes while string survey points represent
locations such as toes, crests or ramps.
- ASCII survey data
- ASCII VBM-ready data
- Layout data The type of survey data affects the display of data on the screen
and digital terrain modeling of the surface. Individual points
are displayed by a symbol at the survey location. String points
are displayed as a connected line with a symbol at each point
location. String points define a continuous line on a surface
and are referred to as breaklines. Breaklines force the known
geometry of a surface to be honored in digital terrain modeling.

Revised: 30-September-93 Page 650SV-1

 MineSight®
M650SV - INTERACTIVE SURVEY FILE EDITOR Proprietary Software: Mintec, inc.

A breakline/string is displayed for each group of sequential

points having the same code in the input file. String points that
occur separate from other string points of the same type in the
input will be displayed like individuals points. Editing functions
can be used to tie string points together or break connections as
needed.

Although individual points are displayed as separate points,

they are grouped into quasi-strings for data management within
the M650SV program. A request to edit a single point will result
in an edit string that connects a group of individual points and
appears as a string. When the edit string is saved or canceled,
the points will again display as individuals. The program
efficiency and speed will drop if too many points are contained
in any string. If the program seems slow, try breaking edit strings
of individual points into smaller strings.

This documentation includes run file options, general operations

and samples of files used by M650SV. Detailed information on
individual features is found in the on-line help.

An overview of the common features of all MineSight®

Graphical Interface (MGI) programs can be found in the Getting
Started section of the Introduction to MineSight®, Volume I.

Page 650SV-2 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M650SV - INTERACTIVE SURVEY FILE EDITOR

M650SV — INTERACTIVE SURVEY FILE EDITOR

1. NAMES LINE (must be the first line entered)

MEDS-650V1 10=filename 30=filename 3=filename

where
MEDS-650V1 must be the first 10 columns
10 = the name of the PROJECT CONTROL FILE OR enter -10=TEMP to use a dummy PCF
30 = the name of the run parameters file (default is [Link] if file 30 not specified)
3 = the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free field format)

USR = USER INITIALS (e.g., ABC)

NOTE:PAR10 through PAR13 are required. Values DO NOT default to the PCF limits.

PAR10 = XMIN FOR WINDOW

PAR11 = XMAX FOR WINDOW
PAR12 = YMIN FOR WINDOW
PAR13 = YMAX FOR WINDOW
PAR19 = YSCALE FACTOR (PAR191 STRETCHES, PAR19 SHRINKS VERTICALLY)
PAR 30 = DIAMETER OF SCALEABLE CURSOR.

END

PROGRAM STRUCTURE

Menu 1 Data input and display and general program operations functions
Menu 2 String editing functions and a point query function
Menu 3 Global editing functions
Menu 4 Ore control shot pattern generation and editing functions
Each of the 650–series programs has Menus 1–3 so that feature editing is standard throughout the series. Menus 1-3 in the
M650SV program provide similar functions with slight differences to accommodate the type of data (survey versus VBM).

Revised: 30-September-93 Page 650SV-1

 MineSight®
M650SV - INTERACTIVE SURVEY FILE EDITOR Proprietary Software: Mintec, inc.

M650SV SAMPLE RUN FILE

MEDS-650V1 -10=TEMP 30=[Link] 3=[Link]
** EDIT SURVEY DATA **
USR = ABCCOM PAR10 THROUGH PAR13 ARE REQUIRED!PAR10= 5300 6100 3400 4200 /
XMIN,XMAX, YMIN,MAXPAR19 = 1.0 /YSCALE FACTOR COM (1=DO NOT CHANGE YSCALE,
1=EXAGGERATE, =SHRINK)PAR30 = 50 /SCALEABLE CURSOR DIAMETER
END

RUN PARAMETERS FILE

The run parameters file specifies information for the 2 startup panels presented when the program starts and for the Blast Pattern
Setup Panel. If the file does not exist, the program will create the file. The file will be updated with information from the above
mentioned panels. Modifications to this file may be made with a text editor as well.

Sample Run Parameter File, [Link]

# M650sv Parameter File

# Refer to documentation before editing this file
[Link] /SURVEY-CODE-FILE
[Link] /INPUT-FILE
[Link] /OUTPUT_FILE
F /INCLUDE-STATIONS
T /INCL-NON-SEL-POINTS
F /BH-INCL-IN-PATTERN
F /STANDARD-DATA-FLOW
F /LAYOUT-IN-DECIMAL
F /SPECIFIED-BOUNDARY
[Link] /BOUNDARY-FILE
/BLST-OUTPUT-FILE
0.000 /MINIMUM-ELEVATION
99999.000 /MAXIMUM-ELEVATION
2320.000 /DEFAULT-ELEVATION
0.000 /DRILL-DEPTH
0.050 /CHARACTER-HEIGHT
50.000 /SNAP-TOLERANCE
0.000 /SUBGRADE-DEPTH-BP
0 /NUMBERING-SYSTEM-BP
/DEFAULT-BP-ID
0 /BH-ROW-NUMBERING-A
0 /BH-ROW-NUMBERING-B
0 /BH-ID-INCREMENT
0 /BH-DIRECTION
0 /BH-ALTERNATE

Page 650SV-2 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M650SV - INTERACTIVE SURVEY FILE EDITOR

SURVEY CODE FILE

The Survey Code file contains display specifications for survey data by code for up to 100 codes per file. For each point code,
specifications for display attributes (type of line, symbol and associated colors) and whether to treat the data as part of a string (i.e,
bench toes) or as individual points (i.e., blastholes) are listed.

Modifications for existing codes made during the program will be updated in the Survey Code file. New codes must be added to the
file either by a procedure in the Medtool Survey group or with a text editor. A code to represent string data will have a positive pen
number specified for the line color. A code to represent individual points will have a negative pen number specified for line color.
Symbols at point locations will be suppressed when the pen number for the symbol color is negative.

The first line of a Survey Code file contains the Minimum Easting, Easting precision, Minimum Northing and Northing precision.
Each line thereafter contains a Point code, Point Number, Linetype, Pen# for line, Size of dash pattern, Symbol Number, Pen# for
Symbol, Size of Symbol and Keyword if applicable.

Data types that need special consideration will also include a keyword to map the user specified code to the appropriate program
logic. The special data types are: Blasthole, Blasthole shot boundary, Temporary marker, Control point, Comment and Break point.
Keywords (fixed character strings) defined by the program are:

STATION A permanent control point.

BREAK Indicates a break in a string - no coordinate read.
COMMENT Indicates a comment - no coordinate read.
BLASTHOL Indicates a blasthole point.
PERIMETE Indicates a shot boundary for blastholes.
TEMPORAR Indicates a temporary point code for the Marker function.

The first line of a parameter file is free format. The Fortran format for lines containing point code information is (A4,1X, 2(2I4,
F8.3), 1X,A8). The columnar format for a parameter file is:

Line 1 [Link], Precision, [Link], Precision

Lines 2-101

Columns Data
1-4 Alphanumeric point code
5 Blank space
6-9 Linetype
10-13 Pen # (use “-1” to suppress linetype)
14-21 Dash size for linetype in plotter units
22-25 Symbol #
26-29 Pen # (use “-1” to suppress symbol)
30-37 Size for symbol in plotter units
38 Blank space

39-46 Keyword (optional)

Revised: 30-September-93 Page 650SV-3

 MineSight®
M650SV - INTERACTIVE SURVEY FILE EDITOR Proprietary Software: Mintec, inc.

Sample Survey Code File, [Link]

0.00 0.00100 0.00 0.00100
TOPO 0 2 0.100 2 1 0.080
BPRM 0 3 0.100 2 1 0.080 PERIMETER
B.H. 0 -1 0.100 5 1 0.080 BLASTHOLE
EDRD 1 4 0.100 11 1 0.080
CST -1 3 0.050 4 1 0.080
STA 0 -1 0.100 1 3 0.100 STATION
TOE 0 2 0.100 3 1 0.080
TEMP 0 -1 0.100 0 -1 0.100 TEMPORARY
$ 0 -1 0.100 0 -1 0.080 BREAK
ROAD 1 4 0.100 11 1 0.080
BND -1 4 0.050 5 1 0.040
BERM 1 4 0.100 11 1 0.080
EDGE 1 4 0.100 11 1 0.080
ELEV 0 -1 0.050 4 1 0.080
PLUG 0 2 0.10 3 1 0.080

Page 650SV-4 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M650SV - INTERACTIVE SURVEY FILE EDITOR

INPUT/OUTPUT FILES, SURVEY FORMAT

Data files used in M650SV are specially formatted ASCII survey data files. The format is described below and an example is shown.
Data that is not in this format can be converted with a procedure in the Medtool Survey group.

The Fortran format for survey data is (A4,2X, I6, 3F12.3). The columnar format of a Survey file is:

Columns Description
1-4 Point code
5-6 Blank spaces
7-12 Point number
13-24 Easting coordinate
25-36 Northing coordinate
37-48 Elevation

Sample Survey File

TOE 309 5656.900 3777.590 1800.007
TOE 310 5675.680 3787.970 1800.390
TOE 311 5677.490 3826.310 1800.323
TOE 183 5696.780 3854.350 1800.012
TOE 184 5703.120 3851.420 1800.225
TOE 185 5702.970 3815.930 1800.873
TOE 186 5711.530 3812.130 1800.615
TOE 187 5728.780 3824.630 1800.448
TOE 188 5744.420 3812.350 1801.134
TOE 189 5765.230 3788.470 1800.832
TOE 190 5775.420 3767.370 1800.860
TOE 191 5784.130 3751.980 1800.880
TOE 192 5792.420 3747.720 1800.888
TOE 193 5799.850 3741.250 1801.326
CST 351 5805.000 3735.000 1809.900
CST 5785.710 3711.490 1810.000
CST 5741.280 3705.560 1810.000
CST 5702.030 3719.380 1810.000
ELEV 2 5671.950 3741.050 1809.190
CST 339 5656.000 3768.000 1809.500
TOE 309 5656.900 3777.590 1800.007

Revised: 30-September-93 Page 650SV-5

 MineSight®
M650SV - INTERACTIVE SURVEY FILE EDITOR Proprietary Software: Mintec, inc.

SURVEY CODE CROSS REFERENCE FILE, [Link]

M650SV allows 42 symbols, 16 line types and 16 colors to be used to display survey data. Specifications for these are contained
in the cross reference file, [Link]. The cross reference file is updated with changes made to these display attributes.

GENERAL SUPPORT FILES

The MineSight® Graphical Interface (MGI) programs access a number of support files. Files that are used by M650SV but not
exclusive to the program are described below. These files will be accessed from the current directory if they exist. Some of them
may also be accessed from more central locations as well.

Filename Description

[Link] Controls color options for background & menus in all MGI programs.
[Link] Controls display attributes of VBM data for 650-series programs.
[Link] Index of metafiles - see metafile icon in on-line help.
[Link] Controls communication with digitizer when digitizer input selected - see digitizer icon in on-line help.

Page 650SV-6 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M651V1 - NORMALIZE NODE POINTS OF VBM DATA

M651V1 NORMALIZE NODE POINTS OF VBM DATA

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M651V1 normalizes VBM data by setting node points equal if Normalization of VBM data is the process of making sure all
the differences are within a specified tolerance. nodes (defined as beginning and end points of the strings
representing the features) are exactly coincident. The tolerance
PROGRAM FLOW DIAGRAM allowed is PAR2.

This program is required only for digitized features which have

common end points. Topography, pit designs and closed
geologic features usually do not require M651V1.
RUN FILE:
The normalized data is written to an output VBM file. This output
- Tolerance value
- Planes to access file can be the same as the input file. If the output file is not the
same as the input, you must have initialized a new VBM file
with M102TS.

NOTE: The original and destination VBM should have the same
dimensions.

INPUT: CALCS:

- PCF - Normalize features in File 25

- File 25 - Output results to a new
File 25

OUTPUT:
- Updated or new File 25
- Printer Output File

Revised: 20-October-95 Page 651-1

 MineSight®
M651V1 - NORMALIZE NODE POINTS OF VBM DATA Proprietary Software: Mintec, inc.

Page 651-2 Revised: 20-October-95

MineSight®
Proprietary Software: Mintec, inc. M651V1 - NORMALIZE NODE POINTS OF VBM DATA

M651V1 NORMALIZE NODE POINTS OF VBM DATA

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-651V1 10=filename 25=filename 26=filename;

MEDS-651V1 3=filename
where

MEDS-651V1 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
26 = the name of the VBM FILE OUTPUT (may be the input file)
3 = the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = 0 DO NOT STORE RESULTS

= 1 STORE RESULTS

IOP2 = 0 DO NOT CREATE POLYGONAL FEATURES

= 1 CREATE NEW POLYGONAL FEATURES FROM EXISTING LEFT
AND RIGHT CODED FEATURES AFTER NORMALIZING
(MAX=25 feature codes)

IOP3 = 0 STORE ALL POLYLINES AND POLYGONS

= 1 STORE ONLY CLOSED POLYGONS
NOTE: Existing features will also be stored.

PAR1 = TOLERANCE TO DETERMINE COMMON NODES (in user units)

(DEFAULT = 0.499)
END

Revised: 15-April-99 Page 651-3

 MineSight®
M651V1 - NORMALIZE NODE POINTS OF VBM DATA Proprietary Software: Mintec, inc.

4. PLANE SPECIFICATION LINE (free-field format) (If IOP2=1)

plane#1 plane#2 code1 ... code5

where
plane#1= first plane to normalize RANGE
plane#2= last plane to normalize

NOTE: Specify up to 25 codes at five per line. End code input with a blank line.

M651V1 SAMPLE RUN FILE #1

MEDS-651V1 10=[Link] 25=[Link] 3=[Link];
MEDS-651V1 26=[Link]
** NORMALIZE DATA IN TOPO FILE **

USR = ABC

IOP1 = 1 / 0=DON’T STORE RESULTS, 1=STORE RESULTS

PAR1 = 25 / TOLERANCE DISTANCE FOR NORMALIZING (IN USER UNITS)

END
4300 4500
890 901 902 903

HOW TO DEBUG AN M651V1 RUN

1. If you want to update the original VBM, specify the same filename for the 25= and 26= reference on the NAMES LINE.

2. To check that all features were normalized correctly, plot out the features with M654.

3. Check the MINESIGHT® error messages in the Appendix.

Page 651-4 Revised: 15-April-99

MineSight®
Proprietary Software: Mintec, inc. M651V2 - COMBINE/ADD VBM FEATURES

M651V2 COMBINE/ADD VBM FEATURES

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M651V2 is used to add features together from the VBM file. This program is usually used to ensure that successive pit designs
The combined feature is stored back in the same VBM file. within a series of pits are equal to or larger than the preceding
design. The features to be combined must be stored in a VBM
file, and the combined features are stored back into the same
PROGRAM FLOW DIAGRAM VBM file.
RUN FILE: M651V2 can also be used to merge a pit with a seam footwall.
- Store / no store option The original pit must be outside the footwall in the applicable
- Feature numbers areas so that intersection points exist. To use footwall merging,
- Plane numbers set IOP15=3 and IOP16=1.

This program can handle complex shapes, but it may have

problems if the designs are exactly coincident or if the shapes
being combined are unclosed. The smaller pit/footwall can be
in more than one piece in the VBM. If this is the case, the pieces
that are going to interact with the pit must intersect each other
INPUT: CALCS:
in order to successfully create the proper merged pit. Pits should
- PCF - Add pits together in the be digitized in a clockwise direction.
- File 25 VBM
The feature codes to add and the planes they are on are specified
at the end of the run file.

OUTPUT:

- Updated File 25
- Printer Output File

Revised: 30-September-93 Page 651-5

 MineSight®
M651V2 - COMBINE/ADD VBM FEATURES Proprietary Software: Mintec, inc.

Page 651-6 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M651V2 - COMBINE / ADD VBM FEATURES

M651V2 COMBINE / ADD VBM FEATURES

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-651V2 10=filename 3=filename

where

MEDS-651V2 (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
3= the name of the PRINTER OUTPUT FILE
NOTE: The VBM filename is listed after the END line.

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = 0 DO NOT STORE

= 1 STORE RESULTANT PIT IN VBM GEOMETRY FILE

IOP15 = 1 ADD PITS

= 2 SMALLER PIT INSIDE LARGER PIT
= 3 SMALLER PIT OUTSIDE LARGER PIT
= 4 LARGER PIT NOT INSIDE SMALLER PIT

IOP16 = 0 PROCESS NON-INTERSECTING SECTIONS OF SMALLER PIT (FW)

= 1 IGNORE NON-INTERSECTING SECTIONS OF SMALLER PIT (FW)

IOP18 = 0 PROCESS NON-INTERSECTING SECTIONS OF LARGER PIT

= 1 IGNORE NON-INTERSECTING SECTIONS OF LARGER PIT

END

Revised: 11-September-98 Page 651-7

 MineSight®
M651V2 - COMBINE / ADD VBM FEATURES Proprietary Software: Mintec, inc.

4. PITS SPECIFICATION LINE (free-field format)

filename plane1 plane2 inc labi labj newl

where

filename=VBM File

plane1 = First plane to access

plane2 = Last plane to access
inc = Increment between planes
labi = VBM code for larger pit (6-digit or right-side code)
labj = VBM code for smaller pit (6-digit or right-side code) -OR- VBM code of the footwall
newl = VBM code for combined pit (6-digit or right-side code)
ptoff = optional plane offset for smaller pit (i.e. footwall)

NOTE: When merging a pit midpoint, an offset of half a bench is required as the pit midpoint is stored on the
plane with the bench toe elevation while the footwall will be stored at its exact elevation.

M651V2 SAMPLE RUN FILE #1

MEDS-651V2 10=[Link] 3=RPT651.LA2
** ADD PITS IN VBM **

USR = ABC

IOP1 = 1 / 0=DON’T STORE RESULTS, 1=STORE RESULTS

I-O = 3
END
[Link] 4700 4800 20 500 501 560

HOW TO DEBUG AN M651V2 RUN

1. ERROR RETURN FROM VBMRGM

will appear if there is no data in your VBM or a specified plane is not found. Check that you are using the correct VBM.

2. To check this routine, you should plot out the original pit outlines along with the new pit outline.

3. Check the MineSight® error messages in the Appendix.

Page 651-8 Revised: 11-September-98

MineSight®
Proprietary Software: Mintec, inc. M651V4 - UPDATE LINE SEGMENTS IN THE VBM

M651V4 UPDATE LINE SEGMENTS IN THE VBM

PROGRAM SUMMARY Splice a feature

M651V4 updates pit or topo contours within the VBM file. It To splice a feature, digitize the splice so that the first and second
uses three functions to perform the updates: line splicing, feature points plus the last two points of the splice cut the original feature.
deletion and copying. The splice must be digitized in the same direction as the original
feature. The Operation Request Line should be filled out such
PROGRAM FLOW DIAGRAM that:

labi = Original feature

RUN FILE: labj = Splice feature
- Store/no store option newl = New feature (labi + labj)
- Feature numbers jop1 = 0 Delete any NEWL features that exist
- Plane numbers
Copy a feature

To copy a feature, fill out the Operation Request Line as:

labi = Original feature to be copied

labj = 0
INPUT: CALCS: newl = New feature
- PCF - Splice a feature OR
- File 25 - Copy a feature OR Delete a feature
- Delete a feature
To delete a feature, digitize a short segment that cuts the feature
to be deleted. The first point should be on one side of the feature
to be deleted and the second point should be on the other side of
the feature. The Operation Request Line should be filled out
such that:

OUTPUT: labi = Original feature

labj = Delete feature
- Updated File 25 newl = New feature
- Printer Output File
This option does not delete existing features. It will delete
features that are the result of an operation, such as copying.
This option would normally be used when you want to delete a
feature from just a few planes as you are copying a feature on
many planes (i.e., deleting one or two topo lines from the entire
set of topo lines).
REQUIREMENTS AND CONSIDERATIONS
After updates are made, there is a tolerance that can be applied,
M651V4 can be used to splice a segment into an existing feature, within which like features are combined.
copy a feature or delete a feature. This program does not change
existing features in a VBM. It works on new features. Therefore,
the delete option will not delete original features. It will delete
only features that are a result of a copy operation.

Revised: 31-May-91 Page 651-9

 MineSight®
M651V4 - UPDATE LINE SEGMENTS IN THE VBM Proprietary Software: Mintec, inc.

Page 651-10 Revised: 31-May-91

MineSight®
Proprietary Software: Mintec, inc. M651V4 - UPDATE LINE SEGMENTS IN THE VBM

M651V4 UPDATE LINE SEGMENTS IN THE VBM

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-651V4 10=filename 3=filename

where

MEDS-651V4 (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = 0 DO NOT STORE

= 1 STORE RESULTANT FEATURES IN VBM

IOP2 = 0 COMBINE LIKE FEATURES AFTER UPDATES MADE

= 1 DO NOT COMBINE

PAR1 = TOLERANCE FOR COMBINING LIKE FEATURES (in user units)

(DEFAULT = 0)

PAR2 = TOLERANCE TO TEST FOR NEAREST POINT AND USE AS INTERSECTION IF

NO INTERSECTION IS FOUND OTHERWISE (in user units) (DEFAULT=0.5)

END

4. OPERATION REQUEST LINES (free-field format)

filename plane1 plane2 inc labi labj newl jop1

where

filename =VBM filename

plane1 =First plane
plane2 =Last plane
inc =Increment between planes. The planes are: plane1, plane1 + inc, plane1 + 2*inc, to plane2
labi =Right side label of old feature or feature to be copied
labj =Right side label of update feature for splicing & deletion
newl =New feature label
jop1 =0Delete old newl features in file
=1Do not delete old newl features in file

Revised: 31-May-91 Page 651-11

 MineSight®
M651V4 - UPDATE LINE SEGMENTS IN THE VBM Proprietary Software: Mintec, inc.

M651V4 SAMPLE RUN FILE #1

MEDS-651V4 10=[Link] 3=SAM651.LA4
** JOIN DIGITIZED DUMP CONTOURS TO TOPO **

USR = SFW
IOP1 = 1 / 0=NO WRITE; 1=WRITE TO VBM
IOP2 = 0 / 0=COMBINE LIKE FEATURES; 1=DON’T COMBINE
PAR1 = 20. / TOLERANCE IN USER UNITS
END
[Link] 4250 4550 10 901 701 751 0

HOW TO DEBUG AN M651V4 RUN

1 In this routine, only right side codes are used to identify features. This may cause some ambiguities if more than one
feature with the same right side code exists. Check that you are using the correct feature(s) in this program.

2. To check the results from this routine, plot the features with one of the M654 programs.

3. Check the MineSight® error messages in the Appendix.

Page 651-12 Revised: 31-May-91

MineSight®
Proprietary Software: Mintec, inc. M652V1 - LIST A VBM INDEX

M652V1— LIST A VBM MODEL INDEX

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M652V1 outputs the VBM index. The index consists of feature This routine is used to print the index of a VBM file. The only
codes, number of points and feature end points for all features items to specify in the run file are the VBM filename, plane
on all planes, as well as optional plane orientation data. specifications, and feature summary option.

PROGRAM FLOW DIAGRAM

RUN FILE:
- VBM filename
- Plane Specifications

INPUT: CALCS:

- PCF - Output VBM plane index

- File 25 - Output feature summary
(optional)

OUTPUT:
- Printer Output File

Revised: 23-July-96 Page 652-1

 MineSight®
M652V1 - LIST A VBM INDEX Proprietary Software: Mintec, inc.

Page 652-2 Revised: 23-July-96

MineSight®
Proprietary Software: Mintec, inc. M652V1-LIST A VBM MODEL INDEX

M652V1 - LIST A VBM MODEL

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-652V1 10=filename 25=filename 3=filename

where

MEDS-652V1 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
3 = the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

PAR1 = MINIMUM PLANE TO LIST (default = minimum plane in the VBM file)

PAR2 = MAXIMUM PLANE TO LIST (default = maximum plane in the VBM file)

NOTE: PAR1 and PAR2 are considered to be not entered if they are less than 0.1*(VBM plane precision).

PAR3 = PLANE NUMBER INCREMENT

IOP1 = 0 /PRINT THE FEATURE SUMMARY

= 1 /SUPPRESS THE FEATURE SUMMARY
= 2 /REPORT AREAS OF SELECTED FEATURES
= 3 /REPORT A LIST OF FEATURES FOR ENTIRE VBM

IOP2 = 0 DO NOT REPORT ORIENTATION DATA

= 1 PRINT ORIENTATION DATA FOR EACH PLANE
= 2 REPORT PLANE ORIENTATION INFO + EXTRA ASCII FILE FOR USE BY M217V2 & M640V1

NOTE: IOP2 is used only if IOP1= 0.

IOP3 = 0 USE FULL 6-DIGIT CODE

= 1 USE LEFT SIDE CODE
= 2 USE RIGHT SIDE CODE

NOTE: IOP3 is used only if IOP1=2.

END

Revised: 17-May-06 Page 652-3

 MineSight®
M652V1-LIST A VBM MODEL INDEX Proprietary Software: Mintec, inc.

4. FEATURE CODE SELECTION (if IOP1=2)

ncodicod1. icod2 ...

ncod = The number of Feature Codes to be selected (max=50)

icodn = List of Feature Codes to use for selection (10 per line)

M652V1 SAMPLE RUN FILE #1

MEDS-652V1 10=[Link] 25=[Link] 3=[Link]
** INDEX OF VBM [Link]

USR = ABC

END

HOW TO DEBUG AN M652V1 RUN

1. Check the MineSight® error messages in the Appendix.

Page 652-4 Revised: 17-May-06

MineSight®
Proprietary Software: Mintec, inc. M653AC - CONVERT VBM DATA TO AutoCAD™

M653AC CONVERT VBM DATA TO AutoCAD™

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M653AC is a conversion routine that allows VBM data to be M653AC will generate a DXF file for Release 10 of AutoCAD
converted into an AutoCAD DXF input file. that is true 3-D. Previous versions of AutoCAD are supported
in a 2-D format with extrusion in the third dimension. M653AC
will operate most effectively on a single feature for a given run.
In this manner, features can be loaded into individual AutoCAD
PROGRAM FLOW DIAGRAM layers with a unique color attribute.

RUN FILE: When using this program, you must set AutoCAD’s
- Feature codes FLATLAND variable to 1.
- Plane numbers

INPUT: CALCS:
- PCF - Convert VBM file to
- File 25 AutoCAD DXF format

OUTPUT:

- AutoCAD DXF format

- Printer Output File

Revised: 30-September-93 Page 653-1

 MineSight®
M653AC - CONVERT VBM DATA TO AutoCAD™ Proprietary Software: Mintec, inc.

Page 653-2 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M653AC - CONVERT VBM DATA TO DXF FORMAT

M653AC CONVERT VBM DATA TO DXF FORMAT

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-653AC 10=filename 19=filename 25=filename;

MEDS-653AC 3=filename
where

MEDS-653AC (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
19 = the name of the DXF OUTPUT FILE
25 = the name of the VBM FILE
3 = the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = 1 USE IOP2 AND IOP3 AS INCLUSIVE RANGE OF FEATURE CODES FOR OUTPUT
= 2 SELECT AGAINST RIGHT SIDE OF FEATURE CODE ONLY
(Right Side Of Code = IOP2)
= 3 SELECT AGAINST LEFT SIDE OF FEATURE CODE ONLY
(Left Side Of Code = IOP2)
= 4 SELECT ALL FEATURES WITHIN THE SPECIFIED PLANES
= 5 SELECT INDIVIDUAL FEATURES (Using IOP16 thru IOP20)

IOP2 = LOWEST FEATURE CODE FOR OUTPUT (If IOP1=1)

= RIGHT SIDE CODE (If IOP1=2)
= LEFT SIDE CODE (If IOP1=3)

IOP3 = HIGHEST FEATURE CODE FOR OUTPUT (If IOP1=1)

IOP4 = 0 READ NUMBER OF PLANES TO DUMP AND WHICH PLANES TO DUMP

(See #4 below)
= 1 DUMP ENTIRE FILE
= 2 DUMP SELECTED FEATURES WITHIN RANGE OF PLANES AS SPECIFIED
BY PAR5, PAR6 AND PAR7

NOTE: IOP4=1 dumps all features and all planes—you need not specify line #4 below or IOP1-3. INPS
and plane numbers are not specified.

IOP5 = FIRST PLANE TO DUMP (integer plane number)

IOP6 = LAST PLANE TO DUMP (integer plane number)
IOP7 = INCREMENT BETWEEN PLANES (integer plane number)

NOTE: IOP 5, 6, and 7 will be used (with IOP4 = 2) ONLY if all three PAR 5, 6, and 7 are 0 AND if VBM
plane precision is equal to 1.

Revised: 21-September-01 Page 653-3

 MineSight®
M653AC - CONVERT VBM DATA TO DXF FORMAT Proprietary Software: Mintec, inc.

IOP10 = 0 DO NOT USE THICKNESS ATTRIBUTE

= 1 GENERATE FEATURE WITH A SPECIFIED THICKNESS (HEIGHT)

IOP11 = 0 FEATURE IS ASSUMED AT MIDPOINT OF THICKNESS ATTRIBUTE

> 0 FEATURE IS ASSUMED AT BASE
< 0 FEATURE IS ASSUMED AT CREST

IOP12 = AutoCAD LAYER NAME FOR FEATURE (MAXIMUM 999)

IOP13 = INDEX FOR AutoCAD COLOR

IOP14 = 0 RELEASE 10 AutoCAD DXF FILES

= 1 VERSION 2.82, VERSION 9 AutoCAD DXF FILES

IOP15 = 0 GENERATE FEATURE AS A SERIES OF LINES

(IOP14=1)OR 3-D LINES (IOP14=0)
= 1 GENERATE FEATURE AS A POLYLINE (IOP14=1)
OR 3-D POLYLINE VERTICE SET (IOP14=0)

NOTE: For ease of trimming within AutoCAD set IOP14=1 & IOP15=1

IOP16 THRU IOP20 = SELECTED FEATURE CODES WHEN IOP1=5

IOP21 = 0 ACAD RELEASE 2 THROUGH ACAD RELEASE 10 DXF FORMAT OUTPUT (see IOP4)
= 1 ACAD RELEASE 12 DXF FORMAT OUTPUT

PAR5 = FIRST PLANE TO DUMP

PAR6 = LAST PLANE TO DUMP

PAR7 = INCREMENT BETWEEN PLANES (DEFAULT = 1)

NOTE: 1) Used only if IOP4 = 2

2) If range and increment are all 0, then all planes will be used.

PAR10 = FEATURE THICKNESS (HEIGHT)

END

4. PLANE SPECIFICATION LINES

inps
plane numbers
where

inps = Total number of planes

plane
numbers = Total number must match inps; 1 per line

NOTE: The ASCII output is in a form compatible for entry back to the VBM file.

Page 653-4 Revised: 21-September-01

MineSight®
Proprietary Software: Mintec, inc. M653AC - CONVERT VBM DATA TO DXF FORMAT

M653AC SAMPLE RUN FILE #1

MEDS-653AC 10=[Link] 25=[Link] 19=[Link] 3=[Link]
** EXTRACT VBM DATA IN DXF FORMAT FOR 2D POLYLINES **

USR = ABC

IOP1 = 4 / SELECT ALL FEATURES WITHIN THE SPECIFIED PLANES

IOP4 = 1 / DUMP ENTIRE FILE

IOP10 = 0 / DO NOT USE THICKNESS ATTRIBUTE

PAR10 = 0 / FEATURE THICKNESS (HEIGHT)
IOP11 = 0 / FEATURE IS AT MIDPOINT OF THICKNESS ATTRIBUTE

IOP12 = 2 / LAYER NAME FOR FOR FEATURE (MAX=999) (MUST BE NUMERIC)

IOP13 = 3 / INDEX FOR AUTOCAD COLOR

IOP14 = 1 / AUTOCAD RELEASE 2.62 - 9 DXF FILE

IOP15 = 1 / POLYLINES IF IOP14=1 OR 3D-POLYLINE VERTICE SET IF IOP14=0

IOP21 = 1/0 0 = ACAD REL. 2.62 THRU REL. 10 DXF FORMAT, 1= ACAD REL. 12 DXF FORMAT

END

HOW TO DEBUG AN M653AC RUN

1. **ERROR* NO PLANE # nnn

will appear if a specified plane does not exist.

2. Check the output file to ensure that you have dumped all of the intended features.

3. Check the MineSight® error messages in the Appendix.

Revised: 21-September-01 Page 653-5

 MineSight®
M653AC - CONVERT VBM DATA TO DXF FORMAT Proprietary Software: Mintec, inc.

Page 653-6 Revised: 21-September-01

MineSight®
Proprietary Software: Mintec, inc. M653V0 - EXTRACT VBM DATA

M653V0 EXTRACT VBM DATA

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M653V0 outputs an ASCII file of VBM data which can then be M653V0 is used to dump VBM point data to an ASCII file.
used for special programs or transferred to another computer. You can select on a range of feature codes, a left side code, or
all features on selected planes. There is also an option for
dumping all features on all planes.

PROGRAM FLOW DIAGRAM If the VBM plane numbers have a precision of less than 1.0,
specify the plane numbers as real numbers.
RUN FILE:
- Feature codes This program is useful when making many changes to an existing
- Plane numbers VBM file.

1. Dump VBM data to an ASCII file with M653V0.

2. Correct errors in the VBM data.

3. Reload the VBM file with M649V1.

INPUT: CALCS:
If you have performed extensive editing on your VBM with
- PCF - Output ASCII file of
- File 25 points for selected M649TS, it may be larger than it has to be (because deleted
features of selected features and planes are still stored in the VBM). Dump the entire
planes VBM with this routine and then reload it with M649V1 and you
will save some disk space.

OUTPUT:
- File of ASCII point data
- Printer Output File

Revised: 30-September-93 Page 653-7

 MineSight®
M653V0 - EXTRACT VBM DATA Proprietary Software: Mintec, inc.

Page 653-8 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M653V0 - EXTRACT VBM DATA

M653V0 - EXTRACT VBM DATA

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-653V0 10=filename 19=filename 25-filename;

MEDS-653V0 3=filename
where

MEDS-653V0 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
19 = the name of the ASCII OUTPUT FILE
25 = the name of the VBM FILE
3 = the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = 1 USE IOP2 AND IOP3 AS INCLUSIVE RANGE OF FEATURE CODES FOR OUTPUT
= 2 SELECT AGAINST RANGE ON RIGHT SIDE OF FEATURE CODE ONLY
(Right side lowest code = IOP2, highest = IOP3)
= 3 SELECT AGAINST LEFT SIDE OF FEATURE CODE ONLY
(Left side lowest code = IOP2, highest = IOP3)
= 4 SELECT ALL FEATURES WITHIN THE SPECIFIED PLANES
= 5 SELECT INDIVIDUAL FEATURES
= 6 SELECT FULL FEATURE CODES AND SEQUENCE NUMBER
NOTE: Specify the selected features with IOP11 to IOP20.

IOP2 = LOWEST FULL FEATURE CODE FOR OUTPUT (if IOP1=1)

= LOWEST RIGHT SIDE CODE (if IOP1=2)
= LOWEST LEFT SIDE CODE (if IOP1=3)

IOP3 = HIGHEST FULL FEATURE CODE FOR OUTPUT (if IOP1=1)

= HIGHEST RIGHT SIDE CODE (if IOP1=2)
= HIGHEST LEFT SIDE CODE (if IOP1=3)

NOTE: If IOP3 = 0 and IOP1 = 1,2, or 3, then IOP3 is set to IOP2

IOP4 = 0 READ NUMBER OF PLANES TO DUMP AND WHICH PLANES TO DUMP (see #4 below)
= 1 DUMP ENTIRE FILE
= 2 DUMP SELECTED FEATURES WITHIN RANGE OF PLANES AS SPECIFIED BY PAR3 AND PAR4
NOTE: IOP4=1 dumps all features and all planes - you need not specify line #4 below or IOP1-3. INPS and
plane numbers are not specified.

Revised: 31-July-01 Page 653-9

 MineSight®
M653V0 - EXTRACT VBM DATA Proprietary Software: Mintec, inc.

IOP6 = 0 OUTPUT STANDARD ASCII FILE

NOTE: When IOP6=0, the ASCII output is in a form compatible for entry back to the VBM file.

IOP7 = 0 DO NOT OUTPUT FEATURE SEQUENCE NUMBER

= 1 OUTPUT SEQUENCE NUMBER
NOTE: IOP7 = 1 only works when IOP6 = 0. The sequence number is listed at the end of the feature header
line.

IOP8 = 0 DO NOT DUMP PLANE ORIENTATION

= 1 DUMP PLANE ORIENTATION DATA
= 2 DUMP INDIVIDUAL ORIENTATION ONLY
NOTE: If IOP8 = 1 and there is no orientation data you will get an error. (See VBM Technical Section for a
discussion of orientation data).

IOP9 = 0 DUMP DUPLICATE FEATURES

= 1 DO NOT DUMP DUPLICATE FEATURES

IOP10 = 1 APPEND TO FILE 19

NOTE: IOP10 = 1 only works when IOP6 = 0.

IOP11-IOP20= SPECIFIC FEATURE CODES (if IOP1=5)

PAR3 = MINIMUM PLANE FOR SELECTING (if IOP4=2)

PAR4 = MAXIMUM PLANE FOR SELECTING (if IOP4=2)

PAR5 = INCREMENT FOR THE RANGE OF PLANES (if IOP4=2)

NOTE: If PAR5=n, then every nth plane is selected, starting from PAR3 and continuing up to (at most) PAR4.
If PAR5 is not specified, every plane from PAR3 to PAR4 is selected.

PAR6 = CONSTANT TO ADD TO EASTING COORDINATE

PAR7 = CONSTANT TO ADD TO NORTHING COORDINATE

END

4. PLANE SPECIFICATION LINES

inps
plane numbers
where

inps = Total number of planes

plane
numbers = Total number must match inps; 1 per line
NOTE: The ASCII output is in a form compatible for entry back to the VBM file.

Page 653-10 Revised: 31-July-01

MineSight®
Proprietary Software: Mintec, inc. M653V0 - EXTRACT VBM DATA

M653V0 SAMPLE RUN FILE #1

MEDS-653V0 10=[Link] 25=[Link] 19=[Link]
MEDS-653V0 3=[Link]
EXTRACT USER SELECTED FEATURES TO ASCII FILE FOR EDIT

USR = ABC

IOP1 = 2 / TEST AGAINST RIGHT SIDE OF FEATURE CODE ONLY

COM = 1 / USE IOP2 & IOP3 AS INCLUSIVE RANGE OF FEATURE CODES

COM = 2 / IOP2 SET TO RIGHT SIDE CODE FOR TESTING
COM = 3 / IOP2 SET TO LEFT SIDE CODE FOR TESTING
COM = 4 / SELECT ALL FEATURES ON SPECIFIED PLANES

IOP2 = 901 / RIGHT SIDE CODE FOR TESTING

IOP3 = 0 / NOT USED UNLESS IOP1=1

IOP4 = 0 / 0=SELECT ON SPEC. FEATURE

COM = 1=DUMP ALL FEATURES ON ALL PLANES

END
1
4300

HOW TO DEBUG AN M653V0 RUN

1. **ERROR* NO PLANE # nnn

will appear if a specified plane does not exist.

2. Check the output file to ensure that you have dumped all of the intended features.

3. Check the MineSight® error messages in the Appendix.

Revised: 31-July-01 Page 653-11

 MineSight®
M653V0 - EXTRACT VBM DATA Proprietary Software: Mintec, inc.

Page 653-12 Revised: 31-July-01

MineSight®
Proprietary Software: Mintec, inc. M653V1 - LIST VBM DATA IN REPORT FORMAT

M653V1 LIST VBM DATA IN REPORT FORMAT

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M653V1 lists the VBM file. M653V1 is used to list the X,Y points for all features that fall
on specified planes. The listing is written to the Printer Output
File.

PROGRAM FLOW DIAGRAM

RUN FILE:
- Plane numbers

INPUT: CALCS:

- PCF - List speccified planes in

- File 25 Printer Output file

OUTPUT:
- Printer Output File

Revised: 30-September-93 Page 653-13

 MineSight®
M653V1 - LIST VBM DATA IN REPORT FORMAT Proprietary Software: Mintec, inc.

Page 653-14 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M653V1 - LIST VBM DATA IN REPORT FORMAT

M653V1 LIST VBM DATA IN REPORT FORMAT

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-653V1 10=filename 25=filename 3=filename

where

MEDS-653V1 (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
25= the name of the VBM FILE
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

END

4. PLANE SPECIFICATION LINES (free-field format)

plane#1 plane#2
where

plane#1= first plane to list

Plane#2 = last plane to list

Revised: 30-September-93 Page 653-15

 MineSight®
M653V1 - LIST VBM DATA IN REPORT FORMAT Proprietary Software: Mintec, inc.

M653V1 SAMPLE RUN FILE #1

MEDS-653V1 10=[Link] 25=[Link] 3=[Link]
EXTRACT SELECTED DATA FROM VBM

USR = ABC
END
4300 4300

HOW TO DEBUG AN M653V1 RUN

1. Check the MineSight® error messages in the Appendix.

Page 653-16 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M653v2 - LIST VBM AND UTILITY FUNCTIONS

M653V2 LIST VBM AND UTILITY FUNCTIONS

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M653V2 is used to print, dump or delete features from a VBM. Print Function
Only one of these functions may be performed in a given run.
The PRINT function is used to list points from selected features
or list the entire index from the VBM. The command is:

PROGRAM FLOW DIAGRAM CMD = PRINT INDEX (to list VBM index)
or
CMD = PRINT POINTS (to list points)
RUN FILE:
- Feature selection The command must be used with CMD = SELECT CODES...
- Plane selection and CMD = USE PLANES...

If you want to list all features, use CMD = PRINT FILE.

Dump Function

The DUMP function is used to output data to an ASCII file.

The filename must be specified on the Names Line as
INPUT: CALCS: 19=filename. You can dump points for selected features with:
- PCF - Print, dump or delete
- File 25 features from VBM CMD = DUMP POINTS

The command must be used with CMD = SELECT CODES...

and CMD = USE PLANES...

To dump the entire file, use CMD = DUMP FILE. This function
will create an ASCII output file suitable to reload into a VBM
or for use with other programs. The output file has the form:
OUTPUT:
plane# feature# (line 1)
- ASCII output file of points easting northing pt# (line 2+)
- Printer Output File .
.
0. 0. (ending)

Revised: 30-September-93 Page 653-17

 MineSight®
M653v2 - LIST VBM AND UTILITY FUNCTIONS Proprietary Software: Mintec, inc.

Dump Cuts Delete Function

To create an ASCII file suitable for use with M708SM, specify The delete function allows selected features to be deleted from
the output filename on the NAMES LINE as 19=filename. The specified planes of the VBM. This function is the same as the
command format is: M649TS SDEL function and is invoked with the command:

CMD = DUMP CUTS CMD = DELET FEATURES

The command must be used with CMD = SELECT CODES... The command must be used with CMD=SELECT CODES...
and CMD = USE PLANES... and CMD=USE PLANES...

The output file has the form: A new VBM index will be printed automatically after features
are deleted.
description from IDENT line of run file (line 1)
1 plane# (line 2) If there are several features with the same code on a given plane,
1 easting northing pt# (line 3+) all will be deleted. The program will output a terminal message
. that will inform you how many features were deleted.
.
-1 (ending) Feature Selection Options

Graphics Dump Use one of the following commands to specify the features to
be used in the run:
To create an ASCII file suitable for use with M122V1, the
command format is: CMD = SELECT RIGHT CODES #1 #2
CMD = SELECT LEFT CODES #1 #2
CMD = DUMP ARAY1 CMD = SELECT FULL CODES #1 #2
or or
CMD = DUMP ARAY2 CMD = SELECT ALL CODES

The command must be used with CMD = SELECT CODES... The right or left side feature codes may range from 1 through
and CMD = USE PLANES... 999. A full feature code (combined left & right code) may range
from 1 through 99999. If the second code (#2) is not given,
The output file has the form of: only features with code #1 will be selected. If both codes #1
and #2 are given, all features within these limits will be selected.
ARAY11 easting1 northing1 1. (line 1)
ARAY11 easting2 northing2 2. (line 2) Plane Specification
.
. Use one of the following commands to specify the VBM planes
ARAY11 eastingnnorthingn n. (line n) to be used in the run:

There are no header or ending lines. If more than one feature is CMD = USE PLANES #1 (single plane)
selected in a run, each will immediately follow the previous CMD = USE PLANES #1 #2 (multiple planes)
feature. CMD = USE PLANES #1 #2 #inc (plane increment)

Page 653-18 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M653V2 - LIST VBM AND UTILITY FUNCTIONS

M653V2 — LIST VBM AND UTILITY FUNCTIONS

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-653V2 10=filename 25=filename 19=filename;

MEDS-653V2 3=filename
where

MEDS-653V2 (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
25= the name of the VBM FILE
19= the name of the ASCII Output File
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

Use one and only one of the following:

CMD = PRINT INDEX

POINTS
FILE
or

CMD = DUMP POINTS

FILE
CUT
ARAY1
ARAY2
or

CMD = DELET FEATURES

Revised: 30-September-93 Page 653-19

 MineSight®
M653V2 - LIST VBM AND UTILITY FUNCTIONS Proprietary Software: Mintec, inc.

Optional Commands

CMD = SELECT RIGHT CODES #1 #2

LEFT
FULL
ALL

CMD = USE PLANES # 1 # 2 # inc

I-O = 3 EXIT AFTER PROGRAM SETUP

FMT1 = OPTIONAL FORMAT FOR OUTPUT

Ex: (2F12.1,F6.0)

NOTE: You must have format fields for east and north coordinates as well as point#.

END

Page 653-20 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M653V2 - LIST VBM AND UTILITY FUNCTIONS

M653V2 SAMPLE RUN FILE #1

MEDS-653V2 10=[Link] 25=[Link] 3=[Link];
MEDS-653V2 19=[Link]
EXTRACT SELECTED DATA FROM VBM

USR = ABC
CMD = DUMP POINTS
CMD = SELECT RIGHT CODES 901
CMD = USE PLANES 4250 4300
END

M653V2 SAMPLE RUN FILE #2

MEDS-653V2 10=[Link] 25=[Link] 3=[Link];
MEDS-653V2 19=[Link]
** DUMP CUTS FOR M708SM **

USR = ABC
CMD = DUMP CUTS
CMD = SELECT RIGHT CODES 901
CMD = USE PLANES 4250 4300
END

M653V2 SAMPLE RUN FILE #3

MEDS-653V2 10=[Link] 25=[Link] 3=[Link];MEDS-653V2
19=[Link]** OUTPUT ARAY1 COMMANDS FOR M122 **

USR = ABC
CMD = DUMP ARAY1
CMD = SELECT RIGHT CODES 901
CMD = USE PLANES 4250 4300
END

Revised: 30-September-93 Page 653-21

 MineSight®
M653V2 - LIST VBM AND UTILITY FUNCTIONS Proprietary Software: Mintec, inc.

HOW TO DEBUG AN M653V2 RUN

1. Check your syntax commands for the run function (DUMP, PRINT, DELET), the feature SELECtion and the PLANE
specifications. Compare your commands against the appropriate example.

2. Check page 2 of the Printer Output File for the PARAMETERS FOR FEATURE SELECTION: to make sure the
program has read the plane and feature selections that you think you entered.

3. To check if the features you want are in the VBM, use the command CMD=PRINT INDEX and check the Printer Output
File.

4. If all else fails, set I-O=2 on your run and watch the screen output for the planes and features that the program is trying to
use.

5. Check the MineSight® error messages in the Appendix.

Page 653-22 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M654V0 - PLOT VMB CONTOUR DATA

M654V0 — PLOT VBM CONTOUR DATA IN PLAN OR

SECTION (M122)

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M654V0 is used to extract section/bench data from the VBM M654V0 is usually used for digitized data, such as topography
file and create an M122 plot file. It centers all labels within the or pits, where there is only a right side code for the feature. For
lines. a line segment going from A to B, the code will be labeled as

PROGRAM FLOW DIAGRAM A ——————nnn————> B

where nnn is the feature code.

RUN FILE: Features that pass out of the selected map area will be clipped at
- Plot scale & map limits the boundary.
- Features & plane
numbers You can either plot one feature with IOP4 or multiple features
- Highlighting & annotation with IOP10—IOP19. For multiple features, IOP7 controls
parameters
whether the labels plotted are feature codes or plane numbers.

The plot file that is created can be either an ASCII M122 plot
file or a binary M122 plot file. The binary file is more efficient.
Use this option when plotting a large amount of topography
INPUT: CALCS: data. If the plot file is binary, specify the filename in M122 with
- PCF - Retrieve selected features a DATAF command. If the plot file is ASCII, specify the
- File 25 from VBM file filename in M122 with a USERF command.
- Generate an M122 plot
file You can also change the orientation of the plot by 180o.
Normally, north—south sections are viewed looking west and
east—west sections are viewed looking north. This view can be
changed so that the X coordinate decreases for the plot by setting
IOP3=1. If you do this, X coordinates will be relative to the
map edge, not the true coordinates. Specific planes can be
OUTPUT: highlighted by changing pens. This option is particularly useful
when displaying topography.
- M122 plot file
- Printer Output File

Revised: 30-September-93 Page 654-1

 MineSight®
M654V0 - PLOT VBM COUNTOUR DATA Proprietary Software: Mintec, inc.

Page 654-2 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M654V0-PLOT VBM CONTOUR DATA

M654V0—PLOT VBM CONTOUR DATA (M122)

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-654V0 10=filename 25=filename 19=filename;

MEDS-654V0 3=filename
where

MEDS-654V0 (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
25= the name of the VBM FILE
19= the name of the M122 Plot File
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = FIRST INTEGER PLANE TO HIGHLIGHT (by changing PEN#)

NOTE: Highlighting is only turned on if IOP10. OR par130.

IOP2 = INCREMENT BETWEEN PLANES TO HIGHLIGHT

IOP3 = 0 X COORDINATE INCREASES LEFT TO RIGHT FOR PLOT

(i.e., E-W section looking north or N-S section looking west)
= 1 X COORDINATE DECREASES IN PLOT
(i.e., E-W section looking south or N-S section looking east)

IOP4 = FEATURE CODE or 0

NOTE: If IOP4=feature code, only that feature code will be plotted on the selected planes. The labels will be
plane numbers.

If IOP4=0, multiple feature codes can be specified by IOP10–19. The labels will be either plane numbers or
features codes, depending on IOP7.

IOP5 = 0 INPUT PLANES FROM SCREEN PROMPTS

= 1 READ PLANES FROM RUN FILE

IOP6 = 0 ASCII OUTPUT OF M122 PLOT COMMANDS

= 1 BINARY OUTPUT OF M122 PLOT COMMANDS

IOP7 = 0 LABELS WILL BE FEATURE CODES

= 1 LABELS WILL BE PLANE NUMBERS

NOTE: IOP7 is only used when IOP4=0

Revised: 01-August-97 Page 654-3

 MineSight®
M654V0-PLOT VBM CONTOUR DATA Proprietary Software: Mintec, inc.

IOP8 = PEN# FOR HIGHLIGHTING (used if IOP1>0; default=3)

IOP9 = 0 READ IN CODES AND PENS (IOP10-19 and IOP20-29)
> 0 DEFAULT PEN NUMBER (default=2)

IOP10-19= FEATURE CODES

NOTE: For the feature codes specified by IOP10-19 to be processed, IOP4 must be zero. Multiple feature codes
can be processed with multiple planes. The labeling can be either by feature code or plane number(See IOP7).

IOP20-29 = PEN#s CORRESPONDING TO THE FEATURE CODES SPECIFIED IN IOP10-19.

NOTE: Specified codes will be plotted with specified pens.

PAR1 = MINIMUM X COORDINATE FOR PLOT (default=XMIN)

PAR2 = MAXIMUM X COORDINATE FOR PLOT (default=XMAX)
NOTE: Defaults will be used only if both PAR1 and PAR2 are not set.

PAR3 = MINIMUM Y COORDINATE FOR PLOT (default=YMIN)

PAR4 = MAXIMUM Y COORDINATE FOR PLOT (default=YMAX)
NOTE: Defaults will be used only if both PAR3 and PAR4 are not set.

PAR5 = PLOT SCALE IN USER UNITS PER PLOTTER UNIT (no default)

PAR6 = ANNOTATION SIZE (Plotter units; Default=0.07)

PAR11 = ANNOTATION DISTANCE FOR LABELING (user units)

PAR12 = 0 OUTPUT STANDARD LINE SEGMENTS

> 0 OUTPUT DASHED LINE SEGMENTS OF PAR12 LENGTH
< 0 OUTPUT SMOOTHED LINE SEGMENTS
NOTE: If the distance between points is greater than PAR12 plotter units, then insert intermediate points.

PAR13 = FIRST PLANE TO HIGHLIGHT (by changing PEN#)

PAR14 = INCREMENT BETWEEN PLANES TO HIGHLIGHT
NOTE: You must use PAR13 and 14 if you want to highlight non-integer planes. Par13 and 14 are given
preference over IOP1 and 2.

END

4. PLANE LINES (free-field format)

plane# 1plane#2 inc

where

plane#1 = First plane to display

plane#2 = Last plane to display
inc = Increment between planes

NOTE: If IOP5=0, planes for run are requested from the screen prompts; if IOP5=1, planes for run are entered
after the END line.

Page 654-4 Revised: 01-August-97

MineSight®
Proprietary Software: Mintec, inc. M654V0-PLOT VBM CONTOUR DATA

M654V0 SAMPLE RUN FILE #1

MEDS-654V0 10=[Link] 25=[Link] 3=[Link]; MEDS-654V0 19=[Link]
** EXTRACT AND PLOT TOPO DATA IN PLAN; LABEL WITH PLANE NUMBERS **
USR = ABC
IOP1 = 3000 / FIRST PLANE TO HIGHLIGHT IOP2 = 100 / INCREMENT BETWEEN PLANES
TO HIGHLIGHT IOP4 = 901 / FEATURE CODE TO PLOT IOP5 = 1 / READ PLANES
FROM FILE
PAR1 = 10000.15000.10000.15000./ XMIN,XMAX,YMIN,YMAX PAR5 = 1000 / PLOT SCALE IN USER
UNITS PAR6 = .05 / ANNOTATION HEIGHT FOR ELEVATIONS PAR11 = 2000 /
ANNOTATION DISTANCE ALONG LINE
END 3000500050

M122V1 SAMPLE RUN FILE #1

MEDS-122V1 10=[Link] 3=[Link]
* PLOT OF SAMPLE TOPO AND DH LOCATIONS AT 1" = 1000’ *

USR = ABC MAP = 9000 16000 1000 9000 16000 1000

END BORDR 1 10000 15000 10000 15000 0 BORDR 1 10015 14985 10000 14985 0 PEN# 3 GRID 1
10000 15000 10000 15000 1000 PEN# 1 TICKS 1 10000 10000 10000 15000 1000 .08 TICKS 1
10000 15000 15000 15000 1000 .08 COORD 1 9700 10025 9700 15025 1000 .05 0 0 10000 1000
COORD 1 9975 15025 14975 15025 1000 .05 90 0 10000 1000 BORDR 1 10000 15000 9500
10000 0 BORDR 1 10015 14985 9515 9985 0 LINE 1 13500 9500 13500 10000 0 LINE 1
13500 9800 15000 9800 0 LINE 1 15000 9600 13500 9600 0 LABEL 1 13910 9880 0 .04 17/
WIDGET MINING CO. LABEL 1 13850 9680 0 .04 20/DIGITIZED TOPOGRAPHY LABEL 1 13910 9540
0 .04 17/SCALE: 1" = 1000’ PEN# 2 USERF [Link] PEN# 1 USERF [Link]

M654V0 SAMPLE RUN FILE #2

MEDS-654V0 10=[Link] 25=[Link] 3=[Link]; MEDS-654V0

19=[Link]

** EXTRACT AND PLOT TOPO DATA IN PLAN; LABEL WITH FEATURE CODE **

USR = ABC

IOP1 = 3000 / FIRST PLANE TO HIGHLIGHT IOP2 = 100 / INCREMENT

BETWEEN PLANES TO HIGHLIGHT IOP4 = 0 / PLOT FEATURE CODE FROM
IOP10; LABEL ACCORDING TO IOP7IOP5 = 1 / READ PLANES FROM FILEIOP7
= 0 / LABEL WITH FEATURE CODEIOP10 = 901 / PLOT TOPOGRAPHY

PAR1 = 10000.15000.10000.15000./ XMIN,XMAX,YMIN,YMAX PAR5 = 1000 /

PLOT SCALE IN USER UNITS PAR6 = .05 / ANNOTATION HEIGHT FOR ELEVATIONS
PAR11 = 2000 / ANNOTATION DISTANCE ALONG LINE

END 3000500050

M654V0 SAMPLE RUN FILE #3

Revised: 01-August-97 Page 654-5

 MineSight®
M654V0-PLOT VBM CONTOUR DATA Proprietary Software: Mintec, inc.

Page 654-6 Revised: 01-August-97

MineSight®
Proprietary Software: Mintec, inc. M654V1 - PLOT VBM POINT DATA

M654V1 — PLOT VBM POINT DATA

IN PLAN OR SECTION (M122)

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M654V1 is used to extract specified features from specified M654V1 is used to plot digitized data that has been stored in
planes from the VBM and create an M122 plot file. Various the VBM. The feature code is plotted so that the right side of
labeling options are available. the feature code is plotted on the right side of the line and the
left side code is plotted on the left side of the line. For example,
PROGRAM FLOW DIAGRAM for the line that goes from A to B, 101 is the right side code and
102 is the left side code of the feature 102101.

102
A——————————>B
101
Different features can be plotted with either a different dash
line pattern or with a different color. A restricted map area can
also be specified. Features that fall outside this area are truncated
RUN FILE: at the map edge.

- VBM code of features(s) The plot file that is created can be either an ASCII M122 plot
to plot file or a binary M122 plot file. The binary file is more efficient.
- Map boundaries
- Range of planes to plot
Use this option when plotting a large amount of VBM data. If
the plot file is binary, specify the filename in M122 with a
DATAF command. If the plot file is ASCII, specify the filename
in M122 with a USERF command.

By default, the coordinates in the plot commands are based on

CALCS: the actual project coordinates and are not relative to the map
INPUT:
area. However, if IOP2=1, the X coordinates in the plot
- PCF - Extract VBM features commands will be in user units, but relative to the left edge of
- File 25 from given planes the map. In either case, the Y (or Z) coordinates are always in
- Create plot commands
actual project units and are not relative to the map edge. Note
that if plotting bench maps, the X coordinates will always be in
actual project coordinates no matter what value IOP2 has.

The program has the ability to change the orientation of the plot
180o. Normally, north-south sections will be viewed looking
west, so that the X coordinates increase from left to right (east-
OUTPUT: west sections looking north are similar). However, by setting
- M122 plot file
IOP3 to 1, the orientation is reversed so that the X coordinates
- Printer Output File decrease for the plots. In this case, plot commands are generated
with X coordinates relative to the left edge of the map area, no
matter what value IOP2 is.

Revised: 1-August-94 Page 654-7

 MineSight®
M654V1 - PLOT VBM POINT DATA Proprietary Software: Mintec, inc.

POLYGON FILL
M654V1 has the capability of producing a map with the features
solidly colored, to enhance the look of the map and highlight
certain features.

NOTE: This option is for closed features only!

Using IOP7 = 1 and adding a feature spec line for each feature
to be filled is required for separate colors. The polygon feature
will be filled if the pen number used in the feature spec line is
set to a negative pen number.

Using IOP7 = 3 and IOP9 = 1 all polygons will be filled with

the same color (PAR9 = fill color).

Page 654-8 Revised: 1-August-94

MineSight®
Proprietary Software: Mintec, inc. M654V1-PLOT VBM POINT DATA

M654V1 PLOT VBM POINT DATA

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-654V1 10=filename 25=filename 19=filename;

MEDS-654V1 3=filename
where

MEDS-654V1 (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
25= the name of the VBM FILE
19= the name of the M122 PLOT FILE
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = 0 DO NOT PLOT ARROWS

= 1 PLOT ARROWS AT FIRST AND LAST POINT OF EACH FEATURE
IOP2 = 0 PLOT X COORDINATES IN PROJECT UNITS
= 1 PLOT DISTANCE IN SECTION

NOTE: If IOP2=1, X coordinates in plot commands will be relative to the left edge of the map.

IOP3 = 0 X COORDINATE INCREASES LEFT TO RIGHT FOR PLOT

(i.e., east-west section looking north, or north-south section looking west)
= 1 X COORDINATE DECREASES LEFT TO RIGHT IN PLOT
(i.e., east-west section looking south, or north-south section looking west)

IOP4 = 0 LABEL BY FEATURE CODE

(for plotting multiple features from a single plane such as for bench geology)
= 1 LABEL BY PLANE NUMBER
(for plotting single feature from multiple planes such as for topo contours)
= 2 LABEL BY BOTH PLANE NUMBER AND FEATURE CODE (only used if IOP9=0)
(This option will label all strings with plane# and feature code. The labeling can also be controlled by
feature using IOP24=0, IOP9=- and a label type=9 on the plotting specs lines.)

IOP5 = DEFAULT PEN# (if PEN=0 on Feature Specification Line) (default= 1)

IOP6 = 0 READ PLANE NUMBERS FROM SCREEN PROMPTS

= 1 READ PLANE NUMBERS FROM RUN FILE

Revised: 27-December-99 Page 654-9

 MineSight®
M654V1-PLOT VBM POINT DATA Proprietary Software: Mintec, inc.

IOP7 = 0 USE SOLID LINES TO DRAW THE FEATURES

= 1 USE LINE, COLOR & SHADING FROM FEATURE SPECIFICATION LINE TO DRAW FEATURES
= 2 USE SHADING TO FILL ALL CLOSED FEATURES (based upon PAR11-14)
= 3 USE SOLID SHADING TO FILL ALL CLOSED FEATURES (using PAR9 as pen color)

NOTE: Dashed line length is specified by PAR15 which defaults to PAR6. Dashed line type is specified by the
7th parameter on the Feature Specification Line.

NOTE: If IOP7 = 0 then you can not use any of the shading or filling functions on the specification lines.

IOP8 = 0 WRITE ASCII OUTPUT OF M122 PLOT COMMANDS, M122 OUTPUT

= 1 WRITE (BINARY) M122 OUTPUT

IOP9 < 0 READ LEFT SIDE CODE RANGES AND THEN PLOT SPECS LINES
= 0 READ PLOT SPECIFICATIONS FROM FEATURE SPECIFICATION LINES
= 1 PLOT ALL FEATURES

IOP10 = 1 COLOR PLANE BY BENCH STEP DESIGNATED IN PAR20

= 2 READ PLANE COLOR SPECIFICATION LINES FOR PLANE COLOR

NOTE: If PAR20 is not set, colors will be cycles based on planes with features. IOP10 will override any color
selections made in feature specification lines.

IOP11 = 0 OUTPUT ANNOTATION IN PLOTTER UNITS

= 1 OUTPUT ANNOTATION IN PROJECT UNITS

IOP12 = 1 DO NOT PLOT DECIMAL PLACES FOR PLANE LABEL

IOP13 = 1 PLOT SEQUENCE NUMBER AS WELL

PAR1 = MINIMUM X COORDINATE FOR PLOT (default = PCF(21)), XMIN

PAR2 = MAXIMUM X COORDINATE FOR PLOT (default = PCF(22)), XMAX

NOTE: Defaults will be used only if both PAR1 and PAR2 are not set.

PAR3 = MINIMUM Y COORDINATE FOR PLOT (default = PCF(25)), YMIN

PAR4 = MAXIMUM Y COORDINATE FOR PLOT (default = PCF(26)), YMAX

NOTE: Defaults will be used only if both PAR1 and PAR2 are not set.

PAR5 = PLOT SCALE IN USER UNITS PER PLOTTER UNITS (default = 2.0 * DX)

PAR6 = ANNOTATION SIZE IN PLOTTER UNITS (default = 0.07)

PAR7 = DISTANCE BETWEEN FEATURE CODE ANNOTATION (in user units)

PAR8 = DISTANCE FROM THE FIRST POINT IN THE FEATURES TO FIRST ANNOTATION (default=SCALE)
(in user units)
PAR9 = PEN COLOR TO SHADE FEATURES (if IOP7 = 3)

Page 654-10 Revised: 27-December-99

MineSight®
Proprietary Software: Mintec, inc. M654V1-PLOT VBM POINT DATA

PAR11 = DISTANCE BETWEEN SHADE LINES (default = SCALE)

PAR12 = ANGLE FOR SHADE LINES (default=45o)
PAR13 = DISTANCE BETWEEN SHADE LINES (SECOND SET)
PAR14 = ANGLE FOR SHADE LINES (SECOND SET)

NOTE: Use PAR11 - 14 if IOP7=2.

PAR15 = DASH LINE LENGTH (default = PAR6)

PAR20 = BENCH STEP VALUE (USED WITH IOP10=1) (for default, see IOP10)

END

4A. LEFT SIDE FEATURE SPECIFICATION LINES (if IOP9<0)

left1 left2 (up to 20 range lines)

-2 (flags end of left side code ranges)
where

left1 = min left side code for feature selection

left2 = max left side code for feature selection

If left side ranges are used, then the detailed specs lines (below) must also follow. Each left feature code in the specs lines should be
set to -1. M654V1 selects on the left side range first, then on the detailed specs lines.

4B. FEATURE SPECIFICATION LINES (if IOP9=0)

left right pen# label dummy1 dummy2 itype dist1 angle1 dist2 angle2
-2 (flags end of Feature Specification Lines)
where

left = Left feature code

= -1 wild card
= -2 end input of Feature Specification Lines (may be omitted if IOP6=0)

right = Right feature code

= -1 wild card

pen# = Pen number to be used for this code only

= (Use negative pen# for polyfill solid shading)

NOTE: Pen number will be overridden if IOP10 is set greater than 0 (color by plane).

label = 0 Plot label on line

= 1 Plot no label
= 2 Plot label at center of closed features
= 3 Plot full label on right side of line
= 4 Plot full label on left side of line
= 5 Plot right label only on right side of line
= 6 Plot right label only on left side of line
= 7 Plot left label only on right side of line
= 8 Plot left label only on left side of line
= 9 Plot both feature code and plane# labels (Planes are labeled with integers only)

Revised: 27-December-99 Page 654-11

 MineSight®
M654V1-PLOT VBM POINT DATA Proprietary Software: Mintec, inc.

dummy1= No longer used, but you must enter a value for the program to run properly
dummy2= Same as dummy1

itype = Dash line type code-see M122V1 documentation, under DASHL, for dash line
patterns (if IOP7=1)

NOTE: This function is deactivated when IOP7=0.

dist1 = Distance between shade lines for first shade direction (in inches if dist1 <1, in project units if dist1 >1).
angle1 = Angle of first shading direction (Valid angles are –90E to +90E)

dist2 = Distance between shade lines for second shade direction (in inches if dist2 <1, in project units if dist2 >1).
angle2 = Angle of second shading direction (Valid angles are –90E to +90E)

Optional Shading Parameters for itype

itype = 10 shade no outline

= 11 shade solid outline
= 12 shade dashed outline

Examples

-1 901 1 0 0 0 5
Plot all features with a right code of 901 with pen #1, right/left side codes and dash line type 5.

-1 901 1 0 0 0 11 .05 45
Same as Example 1 except with a solid outline and shade .05" at 45o.

-1 901 1 0 0 0 11 .05 45 .05 -45

Same as Example 2 except shade is cross-hatch.

5. PLANE COLOR SPECIFICATION LINES (if IOP10=2)

plane# pen#
-2 (flags end of Plane Color Specification lines)
where

plane# = Designated plane for color

pen# = Designated pen to use on plane

NOTE: The plane numbers are requested from the terminal if IOP6=0.

6. PLANE SPECIFICATION LINES (if IOP6=1)

plane#1 plane#2
where

plane#1 = First plane to be plotted - inclusive

plane#2 = Last plane to be plotted - inclusive

NOTE: The plane numbers are requested from the terminal if IOP6=0.

Page 654-12 Revised: 27-December-99

MineSight®
Proprietary Software: Mintec, inc. M654V1-PLOT VBM POINT DATA

M654V1 SAMPLE RUN FILE #1

MEDS-654V1 10=[Link] 25=[Link] 3=[Link];
MEDS-654V1 19=[Link]
** EXTRACT BENCH 3000 GEOLOGY FOR PLOTTING WITH M122V1 **

USR = ABC

IOP2 = 0/ 0=PLOT ACTUAL X-COORDS; 1=X-COORDS REL. TO MAP EDGE

IOP4 = 0/ 0=LABEL BY FEATURE CODE; 1=LABEL BY PLANE NUMBER
IOP6 = 1/ 0=READ PLANES FROM TERM, 1=READ PLANES FROM RUN FILE

IOP7 = 1/ 0=DRAW ALL FEATURES WITH SOLID LINES;

COM 1 = USE DASHED LINES

IOP8 = 0/ 0=MAKE ASCII PLOT COMMANDS FILE;

COM 1=MAKE BINARY PLOT FILE

IOP9 = 0/ 0=USE FEATURE SPEC LINES,

COM 1=PLOT ALL FEATURES ON SPEC PLANES

PAR1 = 10000 15000 / XMIN AND XMAX

COM (LEFT AND RIGHT EDGE OF MAP AREA)

PAR3 = 10000 15000 / YMIN AND YMAX

COM (BOTTOM AND TOP EDGE OF MAP AREA)

PAR5 = 1000 .04 / MAP SCALE & ANNOTATION SIZE

PAR7 = 10000 / DISTANCE BETWEEN FEATURE CODE ANNOTATIONS

PAR8 = 100 / DISTANCE FROM THE FIRST POINT IN THE FEATURE TO

COM THE FIRST ANNOTATION IN USER UNITS

END
1 -1 2 0 0 0 -1 / PLOT ALL FEATURES WITH LEFT SIDE CODE 1 WITH PEN 2
-1 3 3 0 0 0 0 / PLOT ALL FEATS WITH RIGHT SIDE CODE 3 WITH PEN 3
-2 / END FEATURE SPECIFICATION INPUT
3000 3000

Revised: 27-December-99 Page 654-13

 MineSight®
M654V1-PLOT VBM POINT DATA Proprietary Software: Mintec, inc.

M122V1 SAMPLE RUN FILE #1

MEDS-122V1 10=[Link] 3=[Link]
* PLOT OF SAMPLE GEOLOGY CODES AND OUTLINES AT 1" = 1000’ *

USR = ABC
MAP = 9000 16000 1000 9000 16000 1000

END
BORDR 1 10000 15000 10000 15000 0
BORDR 1 10015 14985 10000 14985 0
GRID 1 10000 15000 10000 15000 1000
TICKS 1 10000 10000 10000 15000 1000 .08
TICKS 1 10000 15000 15000 15000 1000 .08
COORD 1 9700 10025 9700 15025 1000 .05 0 0 10000 1000
COORD 1 9975 15025 14975 15025 1000 .05 90 0 10000 1000
BORDR 1 10000 15000 9500 10000 0
BORDR 1 10015 14985 9515 9985 0
LINE 1 13500 9500 13500 10000 0
LINE 1 13500 9800 15000 9800 0
LINE 1 15000 9600 13500 9600 0
LABEL 1 13910 9880 0 .04 17 /WIDGET MINING CO.
LABEL 1 13850 9680 0 .04 21 /GEOLOGY CODES & LINES
LABEL 1 13910 9540 0 .04 17 /SCALE: 1" = 1000’
PEN# 2
DATAF [Link] / PLOT COMMANDS FOR GEOLOGY LINES FROM M654V1
PEN# 3
IDENT
IDENT NOTE THAT THE PLOT COMMANDS MUST BE SHIFTED 50 FEET
IDENT IN BOTH X AND Y DIRECTIONS TO BE PLOTTED IN THE PROPER
IDENT MAP LOCATION
IDENT
SHIFT 1-50 -50 / SHIFT HALF A BLOCK TO CENTER THE CODES
USERF [Link] / PLOT COMMANDS FOR GEOLOGY CODES FROM M656V1
ENDOC

Page 654-14 Revised: 27-December-99

MineSight®
Proprietary Software: Mintec, inc. M654V1-PLOT VBM POINT DATA

M654V1 SAMPLE RUN FILE #2

MEDS-654V1 10=[Link] 25=[Link] 3=[Link];
MEDS-654V1 19=[Link]
** EXTRACT N-S SECT. GEOLOGY FOR PLOTTING ON SECT. LOOKING WEST

USR = ABC

IOP2 = 0/ 0=PLOT ACTUAL X-COORDS;

1=X-COORDS REL. TO MAP EDGE
IOP3 = 0/ 0=X-COORDS INC. FOR PLOT;
1=X-COORDS DEC. FOR PLOT
IOP4 = 0/ 0=LABEL BY FEATURE CODE;
1=LABEL BY PLANE NUMBER

IOP6 = 1/ 0=READ PLANES FROM TERM,

1=READ FROM RUN FILE
IOP7 = 1/ 0=DRAW ALL FEAT. WITH SOLID LINES;
1=USE LINES FROM FEARURE SPECS.
IOP8 = 1/ 0=MAKE ASCII PLOT FILE;
1=MAKE BINARY PLOT FILE
IOP9 = 0/ 0=SELECT FEATURES FOR PLOTTING WITH FEAT. SPEC. LINES
COM 1 = PLOT ALL FEATURES ON SPECIFIED PLANES

PAR1 = 10000 15000 / XMIN AND XMAX

COM (LEFT AND RIGHT EDGE OF MAP AREA)

PAR3 = 1000 6000 / YMIN AND YMAX

COM (BOTTOM AND TOP EDGE OF MAP AREA)

PAR5 = 500 .08 / MAP SCALE & ANNOTATION SIZE

PAR7 = 5000 / DISTANCE BETWEEN FEATURE CODE ANNOTATIONS

PAR8 = 50 / DISTANCE FROM THE FIRST POINT IN THE FEATURE TO

COM THE FIRST ANNOTATION IN USER UNITS

END
1 -1 2 0 0 0 -1 / PLOT ALL FEATS WITH LEFT SIDE CODE 1 WITH PEN 2
-1 3 3 0 0 0 0 / PLOT ALL FEATS WITH RIGHT SIDE CODE 3 WITH PEN 3
-2 / END FEATURE SPECIFICATION INPUT
12250 12250 /PLANE SPECIFICATIONS

Revised: 27-December-99 Page 654-15

 MineSight®
M654V1-PLOT VBM POINT DATA Proprietary Software: Mintec, inc.

M122V1 SAMPLE RUN FILE #2

MEDS-122V1 10=[Link] 3=[Link]
* PLOT GEOLOGY & TOPO PROFILE; N-S SECT. LOOKING WEST @ 12250 E *

USR = ABC

MAP = 0 5000 500 1500 5000 500 PLT

= .07

END
USERF GRIDEW.122 / PLOT COMMANDS FOR STANDARD MAP
PEN# 2 / GREEN
USERF PLX658.122 / TOPO PLOT COMMANDS FROM M658V1
SHIFT 1 -10500 0 / GEOLOGY PLOT COMMANDS IN ACTUAL X-COORDS
IDENT MUST BE SHIFTED TO FIT INTO MAP (RELATIVE X-CCORDS)
PEN# 3 / RED
DATAF [Link] / GEOLOGY PLOT COMMANDS FROM M654V1 (BINARY FILE)
ENDOC

Page 654-16 Revised: 27-December-99

MineSight®
Proprietary Software: Mintec, inc. M654V1-PLOT VBM POINT DATA

M654V1 SAMPLE RUN FILE #3

MEDS-654V1 10=[Link] 25=[Link] 3=[Link];
MEDS-654V1 19=[Link]
** EXTRACT E-W SECT. GEOLOGY TO PLOT ON SECT. LOOKING N @12250 N

USR = ABC

IOP2 = 0 / 0=PLOT ACTUAL X-COORDS; 1=X-COORDS REL. TO MAP EDGE

IOP3 = 0 / 0=X-COORDS INC. FOR PLOT; 1=X-COORDS DEC. FOR PLOT

IOP4 = 0 / 0=LABEL BY FEATURE CODE; 1=LABEL BY PLANE NUMBER

IOP6 = 1 / 0=READ PLANES FROM TERM, 1=READ PLANES FROM RUN FILE

IOP7 = 1 / 0=DRAW ALL FEATURES WITH SOLID LINES;

COM 1=USE DASHED LINES

IOP8 = 1 / 0=MAKE ASCII PLOT FILE; 1=MAKE BINARY PLOT FILE

IOP9 = 0 / 0=SELECT FEAT. FOR PLOTTING WITH FEAT. SPEC. LINES;

COM 1=PLOT ALL FEATURES ON SPECIFIED PLANES

PAR1 = 10000 15000 / XMIN AND XMAX

COM (LEFT AND RIGHT EDGE OF MAP AREA)

PAR3 = 1000 6000 / YMIN AND YMAX

COM (BOTTOM AND TOP EDGE OF MAP AREA)

PAR5 = 500 .08 / MAP SCALE & ANNOTATION SIZE

PAR7 = 5000 / DISTANCE BETWEEN FEATURE CODE ANNOTATIONS

PAR8 = 50 / DISTANCE FROM THE FIRST POINT IN THE FEATURE TO

COM THE FIRST ANNOTATION IN USER UNITS

END
1 -1 2 0 0 0 -1 / PLOT ALL FEATS WITH LEFT SIDE CODE 1 WITH PEN 2
-1 3 3 0 0 0 0 / PLOT ALL FEATS WITH RIGHT SIDE CODE 3 WITH PEN 3
-2 / END FEATURE SPECIFICATION INPUT
12250 12250

Revised: 27-December-99 Page 654-17

 MineSight®
M654V1-PLOT VBM POINT DATA Proprietary Software: Mintec, inc.

M122V1 SAMPLE RUN FILE #3

MEDS-122V1 10=[Link] 3=[Link]
*PLOT GEOLOGY & TOPO PROFILE; E-W SECTION LOOKING NORTH @ 12250 N

USR = ABC
MAP = 0 5000 500 1500 5000 500
PLT = .07

END
USERF GRIDEW.122 / PLOT COMMANDS FOR STANDARD MAP
PEN# 2 / GREEN
USERF PLX658.122 / TOPO PLOT COMMANDS FROM M658V1
SHIFT 1-10500 0 / GEOLOGY PLOT COMMANDS IN ACTUAL X-COORDS
IDENT MUST BE SHIFTED TO FIT INTO MAP (RELATIVE X-CCORDS)
PEN# 3 / RED
DATAF [Link] / GEOLOGY PLOT COMMANDS FROM M654V1 (BINARY FILE)
ENDOC

Page 654-18 Revised: 27-December-99

MineSight®
Proprietary Software: Mintec, inc. M654V1-PLOT VBM POINT DATA

M654V1 SAMPLE RUN FILE #4

COAL-654V1 10=[Link] 25=[Link] 3=[Link];
COAL-654V1 19=[Link]
EXTRACT TRUNCATED CUTS FOR PLOTTING

USR = ABC

IOP2 = 0/ 0=PLOT ACTUAL X-COORDS;

1=X-COORDS REL. TO MAP EDGE

IOP3 = 0/ 0=X-COORDS INC. FOR PLOT;

1=X-COORDS DEC. FOR PLOT

IOP4 = 0/ 0=LABEL BY FEATURE CODE;

1=LABEL BY PLANE NUMBER

IOP5 = 1 / DEFAULT PEN NUMBER (= 1 if NOT SPECIFIED)

IOP6 = 0/ 0=GET PLANE RANGE TO PLOT FROM TERMINAL;

COM 1=GET RANGE OF PLANES FROM RUN FILE

IOP7 = 0/ 0=DRAW ALL FEAT. WITH SOLID LINES;

1=USE LINES IN FEATURE SPECS.

IOP8 = 0/ 0=MAKE ASCII PLOT FILE;

1=MAKE BINARY PLOT FILE

IOP9 = 0/ 0=SELECT FEATURES FOR PLOTTING WITH FEAT. SPEC. LINES

COM 1 = PLOT ALL FEATURES ON SPECIFIED PLANES

PAR1 = 3000 / XMIN (LEFT EDGE OF MAP AREA)

PAR2 = 23000 / XMAX (RIGHT EDGE OF MAP AREA)
PAR3 = 5000 / YMIN (BOTTOM EDGE OF MAP AREA)
PAR4 = 30000 / YMAX (TOP EDGE OF MAP AREA)
PAR5 = 1000 .08 / MAP SCALE & ANNOTATION SIZE

PAR7 = 10000 / DISTANCE BETWEEN FEATURE CODE ANNOTATIONS

PAR8 = 100 / DISTANCE FROM THE FIRST POINT IN THE FEATURE TO

COM THE FIRST ANNOTATION IN USER UNITS

END
-1 777 1 0 0 0 0 / PLOT ALL FEAT. W/RIGHT SIDE CODE 777 W/PEN 1
-2 /END FEATURE SPECIFICATION INPUT

Revised: 27-December-99 Page 654-19

 MineSight®
M654V1-PLOT VBM POINT DATA Proprietary Software: Mintec, inc.

M122V1 SAMPLE RUN FILE #4

MEDS-122V1 10=[Link] 3=[Link]
** MINE DESIGN #1 CUTS GENERATED FROM M662V1 **

USR = ABC
MAP = 3500 22500 2500 5500 28500 2500

END
BORDR 1 3500. 22500. 5500. 28500.
PEN# 3
GRID 1 4000. 22000. 6000. 28000. 2000. 2000.
PEN# 1
COORD 1 5995 6005 20000 6005 2000 0.07 90 -1 6000 2000
COORD 1 4005 8005 4005 26500 2000 0.07 0 -1 8000 2000
USERF [Link] / PLOT COMMANDS FOR TRUNCATED CUTS FROM M654V1
ENDOC

Page 654-20 Revised: 27-December-99

MineSight®
Proprietary Software: Mintec, inc. M654V1-PLOT VBM POINT DATA

M654V1 SAMPLE RUN FILE #5

MEDS-654V1 10=[Link] 25=[Link] 3=[Link] 19=[Link];
** SOLID SHADE CLOSED FEATURE WITH UNIQUE COLORS FOR EACH FEATURE **

USR = ABC
IOP1 = 0/ 1=PLOT ARROWS AT FIRST AND LAST POINT OF EACH FEATURE;
0=DON’T
IOP4 = 0/ 0=LABEL BY FEATURE CODE;
1=LABEL BY PLANE NUMBER
IOP5 = 1/ 0=DEFAULT PEN NUMBER (default =1)
IOP6 = 1/ 0=READ PLANES FROM TERM,
1=READ PLANES FROM RUN FILE
IOP7 = 1/ 0=DRAW ALL FEATURES WITH SOLID LINES;
COM 1=USE LINES, COLOR, AND SHADING FROM FEATURE SPECIFICATION
COM LINES (SEE DOCUMENTATION) TO DRAW FEATURES
COM 2=USE SHADING TO FILL CLOSED FEATURES (based on PAR11-14)

IOP8 = 1/ 0=MAKE ASCII PLOT FILE;

1=MAKE BINARY PLOT FILE
IOP9 = 0/ 0=SELECT FEAT. FOR PLOTTING WITH FEAT. SPEC. LINES;

IOP11 = 0/ 0=OUTPUT ANNOTATATION IN PLOTTER UNITS;

1=IN PROJECT UNITS
IOP12 = 0/ 0=PLOT DECIMAL PLACES FOR PLANE LABEL;
1=DON’T
IOP13 = 0/ 0=DON’T PLOT SEQUENCE NUMBER FOR THE FEATURE;
1=DO PLOT
COM 1=USE DASHED LINES AND SHADING FROM FEATURE

PAR1 = 10000 15000 / XMIN AND XMAX

COM (LEFT AND RIGHT EDGE OF MAP AREA)

PAR3 = 2600 4600 / YMIN AND YMAX

COM (BOTTOM AND TOP EDGE OF MAP AREA)

PAR5 = 200. / MAP SCALE

PAR6 = 0. / ANNOTATION SIZE
PAR7 = 0 / DISTANCE BETWEEN FEATURE CODE ANNOTATIONS (default = SCALE*5)
PAR8 = 0 / DISTANCE FROM THE FIRST POINT IN THE FEATURE TO
COM THE FIRST ANNOTATION IN USER UNITS (default = SCALE*5)

PAR11 = 0 / DISTANCE BETWEEN 1ST SHADE LINES (default=SCALE) (if IOP7=2)

PAR12 = 0 / ANGLE FOR 1ST SHADE LINES (default=45) (if IOP7 = 2)
PAR13 = 0 / DISTANCE BETWEEN 2ND SHADE LINES (default=SCALE) (if IOP7=2)
PAR14 = 0 / ANGLE FOR 2ND SHADE LINES (default=45) (if IOP7 = 2)

END
-1 502 -1 0 0 0 -1 0 0 0 0 / SOLID OUTLINE AND SHADE FEATURE 502 WITH PEN #1
-1 501 -2 0 0 0 -1 0 0 0 0 / SOLID OUTLINE AND SHADE FEATURE 501 WITH PEN #2111 503
-3 0 0 0 -1 0 0 0 0 / SOLID OUTLINE AND SHADE FEATURE111501 WITH PEN #3
-2 / END FEATURE SPECIFICATION INPUT
11000. 12000. / PLANE SPECIFICATIONS

Revised: 27-December-99 Page 654-21

 MineSight®
M654V1-PLOT VBM POINT DATA Proprietary Software: Mintec, inc.

M654V1 SAMPLE RUN FILE #6

MEDS-654V1 10=[Link] 25=[Link] 3=[Link] 19=[Link];
** POLY FILL ALL FEATURES SAME COLOR **

USR = ABC

IOP1 = 0/ 1=PLOT ARROWS AT FIRST AND LAST POINT OF EACH FEATURE;

0=DON’T
IOP4 = 0/ 0=LABEL BY FEATURE CODE; 1=LABEL BY PLANE NUMBER
IOP5 = 1/ 0=DEFAULT PEN NUMBER (default =1)
IOP6 = 1/ 0=READ PLANES FROM TERM, 1=READ PLANES FROM RUN FILE
IOP7 = 3/ 0=DRAW ALL FEATURES WITH SOLID LINES;
COM 1=USE LINES, COLOR, AND SHADING FROM FEATURE SPECIFICATION
COM LINES (SEE DOCUMENTATION) TO DRAW FEATURES
COM 2=USE SHADING TO FILL CLOSED FEATURES (BASED ON PAR11-14)
COM 3=USE SOLID SHADING TO FILL CLOSED FEATURES, USE PAR9 FOR COLOR.

IOP8 = 1 / 0=MAKE ASCII PLOT FILE; 1=MAKE BINARY PLOT FILE IOP9 = 1 / 0=SELECT FEAT. FOR
PLOTTING WITH FEAT. SPEC. LINES; COM 1=PLOT ALL FEATURES ON SPECIFIED PLANES
IOP11 = 0 / 0=OUTPUT ANNOTATATION IN PLOTTER UNITS; 1=IN PROJECT UNITSIOP12 = 0/
0=PLOT DECIMAL PLACES FOR PLANE LABEL; 1=DON’T IOP13 = 0/ 0=DON’T PLOT SEQUENCE
NUMBER FOR THE FEATURE; 1=DO PLOTPAR1 = 10000 15000 / XMIN AND XMAX COM
(LEFT AND RIGHT EDGE OF MAP AREA)
PAR3 = 2600 4600 / YMIN AND YMAX COM (BOTTOM AND TOP EDGE OF MAP AREA)
PAR5 = 200. / MAP SCALE PAR6 = 0. / ANNOTATION SIZE PAR7 = 0 /
DISTANCE BETWEEN FEATURE CODE ANNOTATIONS (default = SCALE*5)PAR8 = 0 /
DISTANCE FROM THE FIRST POINT IN THE FEATURE TO COM THE FIRST ANNOTATION IN USER
UNITS(default = SCALE*5)PAR9 = 4 / COLOR FOR POLY FILL COMMAND IF IOP7 = 3

END
11000. 12000. /PLANE SPECIFICATIONS

Page 654-22 Revised: 27-December-99

MineSight®
Proprietary Software: Mintec, inc. M654V1-PLOT VBM POINT DATA

HOW TO DEBUG AN M654V1 RUN

1. READ ERROR ON PLOT FEATURE LINE xxx
will occur if there is a problem with the xxx Feature Specification Line. Check the line in question against the documentation.

2. The best way to check the results from M654V1 is to plot the M122 plot file. A common error is a mismatch between the Map
Specification Line in the M122 run file and the minimum and maximum X & Y specified in the M654V1 run file.

3. If you specify a binary file in M654V1, make sure you use a DATAF command in M122.

4. Check the MineSight® error messages in the Appendix.

Revised: 27-December-99 Page 654-23

 MineSight®
M654V1-PLOT VBM POINT DATA Proprietary Software: Mintec, inc.

Page 654-24 Revised: 27-December-99

MineSight®
Proprietary Software: Mintec, inc. M654V2 - PLOT VBM PITS MERGED WITH TOPO

M654V2 PLOT VBM PITS MERGED WITH TOPO (M122)

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS
M654V2 is used to create an M122 plot file that contains the M654V2 is used to produce plot commands for a plan map of a
commands to plot a pit design merged with topography. The pit mine design that is truncated by the surface topography. Prior
design and topography must be stored in the same VBM file. to using the program, both the mine design bench outlines and
the surface topography contours must be stored in the same VBM
The merged surface can be output to a file in M649V1 format. file.

The program has three options (IOP6-8) that control the number
of topography contour lines that may be plotted. The program
PROGRAM FLOW DIAGRAM defaults to plotting all of the topography contours for the
specified planes which are outside of the pit. The program will
RUN FILE: automatically truncate the topography contours at the edge of
- Clipping options the pit. To plot the pit truncated by topography without plotting
- Topo item any of the topography contours, set IOP6=l. IOP7 and 8 control
the number of topography lines that are plotted. To plot only
the topo contours that intersect the pit, set IOP7=1. To plot the
topography above the pit, set IOP8=1. To plot only the clipped
topography lines above the pit, set both IOP7 and 8 to 1.

The program works as follows:

INPUT: CALCS:
1. For each bench, the topography points are tested against
- PCF - Generate plot commands
- File 25 of plan view of mine the pit limits for intersections. If no intersections are found,
design truncated by the contour is plotted if it does not lie completely inside the
topography and part or all pit. If the topography contour intersects the pit, the portion
of the topography
of the contour outside the pit is plotted.

2. For each bench, the pit limits are tested against the topogra-
phy for intersections. If no intersections are found, the pit
limits are tested against each topography contour to deter-
OUTPUT: mine if the pit limit is above or below the surface. If inter-
- M122 plot file sections are found, only the portion of the pit below the
- Printer Output File topography is plotted.
NOTE: It is essential that the topography contours are
digitized in the correct direction (i.e. clockwise
enclosing the ground surface, or ground on the
right side of the topo contour and air on the left).
Also, if pit limits are hand drawn and digitized for
entry with M649V1, the direction must be
clockwise enclosing the mined material.

Revised: 30-November-95 Page 654-25

 MineSight®
M654V2 - PLOT VBM PITS MERGED WITH TOPO Proprietary Software: Mintec, inc.

Page 654-26 Revised: 30-November-95

MineSight®
Proprietary Software: Mintec, inc. M654V2 - PLOT VBM PITS MERGED WITH TOPO

M654V2 - PLOT VBM PITS MERGED WITH TOPO

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-654V2 10=filename 19=filename 30=filename;

MEDS-654V2 3=filename
where

MEDS-654V2 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
19 = the name of the M122 PLOT FILE
30 = the name of the OUTPUT FILE FOR MERGED SURFACE
3 = the name of the PRINTER OUTPUT FILE
NOTE: The VBM filenames are specified in the Bench Specification Lines. If File 30 is included in the Names
Line, the merged surface will be output to this file in M649V1 format. If File 30 is not included, then
all operations to this file are bypassed.

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = PEN# FOR TOPO (default = 2)

IOP2 = PEN# FOR PIT (default = 3)

IOP4 = 0 DO NOT USE PRECEDING PLANES TO CLIP CURRENT PLANES

= 1 USE PRECEDING PLANES TO CLIP CURRENT PLANES IF NO PIT FEATURES ARE PRESENT

IOP6 = 0 PLOT PIT CLIPPED BY TOPO; DISPLAY TOPO LINES

= 1 PLOT PIT CLIPPED BY TOPO; DO NOT DISPLAY TOPO LINES
= 2 PLOT TOPO TRUNCATED BY PIT; DO NOT DISPLAY PIT

IOP7 = 0 PLOT TOPO LINES WHICH DO NOT INTERSECT THE PIT

= 1 PLOT ONLY TOPO LINES WHICH INTERSECT THE PIT

IOP8 = 0 DO NOT PLOT TOPO LINES ABOVE THE PIT

= 1 PLOT TOPO LINES ABOVE THE PIT

IOP9 = 0 ASCII OUTPUT OF M122 PLOT COMMANDS

= 1 BINARY OUTPUT OF M122 PLOT COMMANDS

IOP10 = ALTERNATE FEATURE CODE IF FILE 30 IS INCLUDED (default = Topo Feature Code)

IOP12 = 0 LABEL LINES = 1 DO NOT LABEL

NOTE: This option is useful for avoiding label cluttering when overlaying pit toes and crests clipped with topo
(i.e., only one of crest and toe needs to be labeled).

Revised: 18-February-00 Page 654-27

 MineSight®
M654V2 - PLOT VBM PITS MERGED WITH TOPO Proprietary Software: Mintec, inc.

IOP13 = 0 NO IMPACT
= 1 COPY MULTIPLE PITS INTO ONE SINGLE PIT, NO TOPO MERGE

PAR1 = MINIMUM X COORDINATE FOR PLOT (default=XMIN)

PAR2 = MAXIMUM X COORDINATE FOR PLOT (default=XMAX)

PAR3 = MINIMUM Y COORDINATE FOR PLOT (default=YMIN)

PAR4 = MAXIMUM Y COORDINATE FOR PLOT (default=YMAX)

PAR5 = PLOT SCALE IN USER UNITS PER PLOTTER UNITS (no default)

PAR6 = ANNOTATION SIZE IN PLOTTER UNITS (default=0.07)

PAR11 = DISTANCE BETWEEN LABELS (in user units)

PAR12 = 0 OUTPUT STANDARD LINE SEGMENTS

> 0 OUTPUT DASHED LINE SEGMENTS OF PAR12 LENGTH
< 0 OUTPUT SMOOTHED LINE SEGMENTS
NOTE: If the distance between points is greater than PAR12 plotter units, then insert intermediate points.

END

4. BENCH SPECIFICATION LINES

filename plane#1 plane#2 topinc topo pit offset plt_pen merge keep
where

filename= File 25 filename

plane#1 = First plane to plot
plane#2 = Last plane to plot
topinc = Increment between planes
topo = Feature code of topo stored in VBM (right-side code only)
pit = Feature code of pit outlines stored in VBM
(6-digit or right-side code. If feature is closed, use right-side code only)
offset = Offset/constant to add to pit plane# to get topo plane#
plt_pen = Optional pen # for plotting pit. If not specified, IOP2 will be used (default = 3).
NOTE: Multiple Bench Specification Lines can be used. This is necessary if you have variable bench heights
and want to use the offset/constant to add to the pit plane #. This can only be used to perform multiple
pit merges. See note below.

merge = Optional feature code (right-side only) of merged pit to store in the VBM. If this is specified,
the VBM will be updated after each merge. This must not be a previously used code.
NOTE: Multiple merge requests: M654V2 can be used to perform multiple merge requests by adding extra
plane specification lines after the end of the run file. Each merge request is independent and any valid
feature codes may be used. However, a useful application is the merging of multiple independent pits
with a topo. In this case, one would specify a merge feature code at the end of each line to ensure that
the VBM is updated after each merge. The merged pit feature code from one merge would then be
used as the topo code in the next request. This can be accomplished automatically by using 0 as the
topo code for subsequent requests. Note that although the VBM will contain all merge features, File 30
and the plot file will only contain the final merge.

Page 654-28 Revised: 18-February-00

MineSight®
Proprietary Software: Mintec, inc. M654V2 - PLOT VBM PITS MERGED WITH TOPO

filename plane#1 plane#2 topoinctopo pit#1 offset plt_pen merge1

filename plane#1 plane#2 topoincmerge1 (or 0) pit#1 offset plt_pen merge2
filename plane#1 plane#2 topoincmerge2 (or 0) pit#1 offset plt_pen merge3
.
.
.

Keep = optional flag for when “merge” code is defined, 1= keep the current merge, 0 = do not keep the current merge.

NOTE: keep is meant for year-end-map plots and where independent phases are involved. When topography elevations are
below the lowest mining elevation of a phase, to obtain a complete updated topography merge between the topography and the
mined benches, two merges need to be carried out.

Merge one:
The topography (e.g., 901) and the phase (e.g., 821) will be merged for all elevations where both exist. This merged code (e.g.,
701) is an updated topography and is stored in a VBM file.

Merge two:
The topography (901) will be merged with a code 0 for all of the elevations below the bottom bench of the phase (821) to
produce a merged code (701). This is equivalent of copying topography (901) on the defined elevations to a new code (701).

By defining keep = 1 in merge one, the topography elevations (701) obtained in merge two will be appended to the merged code
(701) in merge one.

M654V2 SAMPLE RUN FILE #1

MEDS-654V2 10=[Link] 19=[Link] 3=[Link]
** PLOT STRIPPER PIT FROM VBM WITH TOPO **

USR = ABC

IOP5 = 0 / 0=PLOT FEATURE CODE ONLY; 1=PLOT LINE # ALSO

IOP6 = 0 / 0=PLOT PIT CLIPPED BY TOPO W/ TOPO;
COM 1=PLOT PIT CLIPPED BY TOPO W/O TOPO

PAR1 = 10000 15000 / MIN & MAX X-COORDS FOR PLOTTING

PAR3 = 10000 15000 / MIN & MAX Y-COORDS FOR PLOTTING

PAR5 = 1000. / SCALE IN UNITS PER INCH

PAR6 = 0.05 / ANNOTATION SIZE IN INCHES
PAR11 = 4000. / DIST BETWEEN ANNOT. IN USER UNITS

END
[Link] 3500 4550 50 901 899

Revised: 18-February-00 Page 654-29

 MineSight®
M654V2 - PLOT VBM PITS MERGED WITH TOPO Proprietary Software: Mintec, inc.

M654V2 SAMPLE RUN FILE #2

MEDS-654V2 10=[Link] 19=[Link] 3=rpt654.la2
MEDS-654V2 30=dat654.5
** PLOT YEAR END MAP ASSUMING INDEPENDENT VBM PITS AND TOPO **
USR = wlc / Thu Feb 3, 2000 4:53:01 PM US Mountain Standard Time

IOP1 = 2 2 / PEN# FOR TOPO & PIT

IOP10= 703 / RESULTING FEATURE CODE
COM iop10 feature code is for output to dat654.5 only.
IOP13= 0. / 0=regular plot,
COM / 1=dump selected pits without merge with topo
PAR1 = 1000. 4000. / MIN,MAX EASTINGS
PAR3 = 4000. 6500. / MIN,MAX NORTHING

PAR5 = 76.2 / SCALE FOR PLOTTING

PAR6 = 0.15 / ANNOTATION SIZE IN INCHES

END
[Link] 2360 2960 15 901 807 0 2 701 1
[Link] 2000. 2345. 15 901 0 0 2 701 0
[Link] 2510 2960 15 701 815 0 2 702 1
[Link] 2000. 2495. 15 701 0 0 2 702 0
[Link] 2570 2960 15 702 819 0 2 703 1
[Link] 2000. 2555. 15 702 0 0 2 703 0

M654V2 SAMPLE RUN FILE #3

MEDS-654V2 10=[Link] 19=[Link] 3=rpt654.la2
MEDS-654V2 30=dat654.5
** PLOT YEAR END MAP BASED ON NESTED VBM PITS AND TOPO **
USR = wlc / Thu Feb 3, 2000 4:51:20 PM US Mountain Standard Time

IOP1 = 2 3 / PEN# FOR TOPO & PIT

IOP10= 905 / RESULTING FEATURE CODE
COM iop10 feature code is for output to dat654.5 only.
IOP13= 0. / 0=regular plot,
COM / 1=dump selected pits without merge with topo
PAR1 = 1000. 4000. / MIN,MAX EASTINGS
PAR3 = 4000. 6500. / MIN,MAX NORTHING

PAR5 = 76.2 / SCALE FOR PLOTTING

PAR6 = 0.15 / ANNOTATION SIZE IN INCHES

END
[Link] 2360 2495 15 901 807 0 3 0 0
[Link] 2000. 2345. 15 901 0 0 3 0 0
[Link] 2510 2555 15 901 815 0 4 0 0
[Link] 2570 2960 15 901 819 0 5 0 0

Page 654-30 Revised: 18-February-00

MineSight®
Proprietary Software: Mintec, inc. M654V2 - PLOT VBM PITS MERGED WITH TOPO

M122V1 SAMPLE RUN FILE #1

MEDS-122V1 10=[Link] 3=[Link]
** STRIPPER PIT DESIGN **

USR = ABC
MAP = 9000 16000 1000 9000 16000 1000

END
BORDR 1 10000 15000 10000 15000 0
BORDR 1 10015 14985 10000 14985 0
GRID 1 10000 15000 10000 15000 1000
TICKS 1 10000 10000 10000 15000 1000 .08
TICKS 1 10000 15000 15000 15000 1000 .08
COORD 1 9700 10025 9700 15025 1000 .05 0 0 10000 1000
COORD 1 9975 15025 14975 15025 1000 .05 90 0 10000 1000
BORDR 1 10000 15000 9500 10000 0
BORDR 1 10015 14985 9515 9985 0
LINE 1 13500 9500 13500 10000 0
LINE 1 13500 9800 15000 9800 0
LINE 1 15000 9600 13500 9600 0
LABEL 1 13910 9880 0 .04 17/WIDGET MINING CO.
LABEL 1 13850 9680 0 .04 21/STRIPPER PIT DESIGN
LABEL 1 13910 9540 0 .04 17/SCALE: 1" = 1000’
USERF [Link]
ENDOC

HOW TO DEBUG AN M654V2 RUN

1. ** ERROR RETURN FROM VBMRGM **

will appear if there is no data in your VBM or a specified plane is not found. Check that you are using the correct VBM.

2. If unexpected results occur, make sure that both topo contours and pits outlines are digitized clockwise. M649TS can be used to
reverse the direction of VBM features.

3. For the program to work correctly, the pit outlines must be stored on the same planes as the topo for a particular elevation. Also
ensure that the correct VBM planes are specified.

4. Check the MineSight® error messages in the Appendix.

Revised: 18-February-00 Page 654-31

 MineSight®
M654V2 - PLOT VBM PITS MERGED WITH TOPO Proprietary Software: Mintec, inc.

Page 654-32 Revised: 18-February-00

MineSight®/
Proprietary Software: Mintec, inc. M654V3 - PLOT VBM PITS CLIPPED BY FILE 13 TOPO

M654V3 PLOT VBM PITS CLIPPED

BY FILE 13 TOPOGRAPHY (M122)

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M654V3 is used to create an M122 plot file containing a pit M654V3 is used to plot the interaction between pit designs stored
design from the VBM file truncated by the topography matrix. in a VBM file and topography stored in File 13. The pit is
The topography contours are not displayed. “truncated” by the topography, but the topography contours are
not displayed. A plot generated by M654V3 will not necessarily
match a plot generated by M654V2 because the topography used
is in a different form for each program. M654V3 requires fewer
computer resources than M654V2.
PROGRAM FLOW DIAGRAM
The plot file that is created can be either an ASCII M122 plot
file or a binary M122 plot file. The binary file is more efficient.
Use this option when plotting a large amount of data.

RUN FILE: If the plot file is binary, specify the filename in M122 with a
- Feature code of pit DATAF command. If the plot file is ASCII, specify the filename
- Map limits in M122 with a USERF command.
- topography item

INPUT: CALCS:
- PCF - Plot a pit design from a
- File 13 VBMclipped by File 13
- File 25 topography

OUTPUT:
- M122 plot file
- Printer Output File

Revised: 18-February-00 Page 654-33

 MineSight®/
M654V3 - PLOT VBM PITS CLIPPED BY FILE 13 TOPO Proprietary Software: Mintec, inc.

Page 654-34 Revised: 18-February-00

MineSight®
Proprietary Software: Mintec, inc. M654V3 - PLOT VBM PITS CLIPPED BY FILE 13 TOPO

M654V3 PLOT VBM PITS CLIPPED BY FILE 13 TOPO

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-654V3 10=filename 13=filename 25=filename;

MEDS-654V3 19=filename 3=filename
where

MEDS-654V3 (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
13= the name of the 2-D SURFACE FILE
25= the name of the VBM FILE
19= the name of the M122 Plot File
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = PIT CODE TO PLOT (6-digit or right-side code)

IOP2 = PEN NUMBER FOR LINE LABELS (DEFAULT=1)

IOP3 = PEN NUMBER FOR LINES (DEFAULT=1)

IOP4 = 0 PLANES ENTERED FROM SCREEN PROMPTS

= 1 PLANES ENTERED IN RUN FILE

IOP5 = 0 ASCII OUTPUT OF M122 PLOT COMMANDS

= 1 M122 OUTPUT

ITM1 = label-13 TOPO

where label-13 is the File 13 topography item.

PAR1 = MINIMUM X COORDINATE FOR PLOT (DEFAULT=PCF(21)), XMIN

PAR2 = MAXIMUM X COORDINATE FOR PLOT (DEFAULT=PCF(22)), XMAX

PAR3 = MINIMUM Y COORDINATE FOR PLOT (DEFAULT=PCF(25)) , YMIN

PAR4 = MAXIMUM Y COORDINATE FOR PLOT (DEFAULT=PCF(26)) , YMAX

PAR5 = PLOT SCALE IN USER UNITS PER PLOTTER UNIT (NO DEFAULT)

PAR6 = ANNOTATION SIZE (plotter units) (DEFAULT=0.07)

PAR11=DISTANCE BETWEEN ANNOTATION LABELS (in user units)

Revised: 18-February-00 Page 654-35

 MineSight®
M654V3 - Plot VBM PITS CLIPPED BY FILE 13 TOPO Proprietary Software: Mintec, inc.

PAR12 = 0 OUTPUT STANDARD LINE SEGMENTS

> 0 OUTPUT DASHED LINE SEGMENTS OF PAR12 LENGTH
< 0 OUTPUT SMOOTHED LINE SEGMENTS

NOTE: If the distance between points is greater than PAR12 plotter units, then insert intermediate points.

END

4. PLANE REQUEST LINE

plane# 1 plane # 2 inc

where

plane# 1= First plane to access (inclusive)

plane# 2= Last plane to access (inclusive)
inc = Increment of planes

Page 654-36 Revised: 18-February-00

MineSight®
Proprietary Software: Mintec, inc. M654V3 - PLOT VBM PITS CLIPPED BY FILE 13 TOPO

M654V3 SAMPLE RUN FILE #1

MEDS-654V3 10=[Link] 13=[Link] 25=[Link];
MEDS-654V3 19=[Link] 3=[Link]
** PLOT PIT FROM VBM TRUNCATED BY FILE 13 TOPO **

USR = ABC

IOP1 = 899 / PIT CODE

IOP2 = 3 / PEN # FOR LABELS
IOP3 = 1 / PEN # FOR LINES

ITM1 = TOPOG TOPO / FILE 13 ITEM (TOPOG)

PAR1 = 10000 15000 / XMIN & XMAX FOR PLOTTING

PAR3 = 10000 15000 / YMIN & YMAX FOR PLOTTING
PAR5 = 1000 .05 5000 / MAP SCALE,ANNOT SIZE,&DIST BETWEEN LABELS

END

M122V1 SAMPLE RUN FILE #1

MEDS-122V1 10=[Link] 3=[Link]

** STRIPPER PIT DESIGN - TRUNCATED BY FILE 13 TOPO **

USR = ABC
MAP = 9000 16000 1000 9000 16000 1000

END
BORDR 1 10000 15000 10000 15000 0
BORDR 1 10015 14985 10000 14985 0
GRID 1 10000 15000 10000 15000 1000
TICKS 1 10000 10000 10000 15000 1000 .08
TICKS 1 10000 15000 15000 15000 1000 .08
COORD 1 9700 10025 9700 15025 1000 .05 0 0 10000 1000
COORD 1 9975 15025 14975 15025 1000 .05 90 0 10000 1000
BORDR 1 10000 15000 9500 10000 0
BORDR 1 10015 14985 9515 9985 0
LINE 1 13500 9500 13500 10000 0
LINE 1 13500 9800 15000 9800 0
LINE 1 15000 9600 13500 9600 0
LABEL 1 13910 9880 0 .04 17/WIDGET MINING CO.
LABEL 1 13850 9680 0 .04 21/STRIPPER PIT DESIGN
LABEL 1 13910 9540 0 .04 17/SCALE: 1" = 1000’
USERF PLT654.PV3
ENDOC

Revised: 18-February-00 Page 654-37

 MineSight®
M654V3 - Plot VBM PITS CLIPPED BY FILE 13 TOPO Proprietary Software: Mintec, inc.

HOW TO DEBUG AN M654V3 RUN

1. ** ERROR RETURN FROM VBMRGM **

will appear if there is no data in the VBM or a specified plane is not found. Check that you are using the correct VBM.

The PIT and the TOPO can not have any coincident segments or points or irregular merging will occur. Make sure the PIT and
the TOPO overlap each other. The PIT should be closed and digitized in a clockwise direction.

2. Check the MineSight® error messages in the Appendix.

Page 654-38 Revised: 18-February-00

MineSight®/
Proprietary Software: Mintec, inc. M654 - PLOT OR PUTPUT CLIPPED VBM DATA

M654V5 PLOT OR OUTPUT CLIPPED VBM DATA (M122)

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M654V5 extracts data from a VBM file and plots or outputs the This program is used to clip a VBM feature (usually topography)
data either inside or outside a closed feature. The closed feature by another closed VBM feature. The clipping or window feature
is stored in one plane only. must be stored on a specific plane. For example, it can be used
to plot or output contours with subcrop or plot contours outside
the daylight limit of the pit.

PROGRAM FLOW DIAGRAM The clipping can be done such that features either inside or
outside the window feature are displayed. Optionally, only
features that are clipped may be displayed.

The VBM data may be plotted or output within a user defined

rectangular window. Features that intersect this boundary will
RUN FILE:
be clipped.
- Feature code for clipping
- Plane Numbers
- Map limits
The file that is created can be either an ASCII M122 plot file or
a binary M122 plot file. The binary file is more efficient. Use
this option when plotting a large amount of data. An ASCII file
of points ready for loading with M649V1 may optionally be
created. Feature code and plane number is the same as input
specification line.

CALCS:
If the plot file is binary, specify the filename in M122 with a
INPUT:
DATAF command. If the plot file is ASCII, specify the filename
- PCF - Clip topography or some
- File 25 other feature with another
in M122 with a USERF command.
closed feature
The clipping feature may be read from an ASCII input file.

OUTPUT:
- M122 plot file
- Printer Output File

Revised: 18-February-00 Page 654-39

 MineSight®/
M654V5 - PLOT OR OUTPUT CLIPPED VBM DATA Proprietary Software: Mintec, inc.

Page 654-40 Revised: 18-February-00

MineSight®
Proprietary Software: Mintec, inc. M654V5 - PLOT OR OUTPUT CLIPPED VBM DATA

M654V5 PLOT OR OUTPUT CLIPPED VBM DATA

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-654V5 10=filename 19=filename 3=filename

where

MEDS-654V5 (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
19= the name of the M122 Plot File -or- ASCII output file of points
3= the name of the PRINTER OUTPUT FILE
30= the name of the optional input ASCII file containing clipping feature

NOTE: The VBM file is listed after the END line.

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

IOP5 = 0 PLOT/OUTPUT PLANE NUMBER ONLY

= 1 PLOT/OUTPUT PLANE NUMBER & FEATURE SEQUENCE NUMBER
(Only if VBM plane prec = 1)

IOP6 = 0 PLOT/OUTPUT CLIPPING FEATURE(S) & CLIPPED FEATURE(S)

= 1 PLOT/OUTPUT CLIPPING FEATURE(S) ONLY
= 2 PLOT/OUTPUT CLIPPED FEATURE(S) ONLY

IOP7 = 0 PLOT/OUTPUT ALL FEATURES THAT ARE CLIPPED AND NOT CLIPPED
= 1 PLOT/OUTPUT FEATURES THAT ARE CLIPPED ONLY

IOP8 = 0 PLOT/OUTPUT FEATURES OUTSIDE CLIPPING FEATURE

= 1 PLOT/OUTPUT FEATURES INSIDE CLIPPING FEATURE

IOP9 = 0 ASCII OUTPUT OF M122 PLOT COMMANDS

= 1 BINARY OUTPUT OF M122 PLOT COMMANDS
= 2 ASCII OUTPUT OF POINTS FOR VBM INPUT

IOP11 = PLANE NUMBER CONTAINING CLIPPING FEATURE

(ignored if file 30 specified)

IOP12 = CLIPPING FEATURE RIGHT SIDE CODE OR FULL 6-DIGIT FEATURE CODE
(ignored if file 30 specified)

Revised: 18-February-00 Page 654-41

 MineSight®
M654V5 - Plot PLOT OR OUTPUT CLIPPED VBM DATA Proprietary Software: Mintec, inc.

IOP13 = PEN # FOR CLIPPED FEATURE

IOP14 = PEN # FOR CLIPPING FEATURE

IOP15 = 0 LABEL CLIPPED FEATURE WITH PLANE #

= 1 LABEL CLIPPED FEATURE WITH FEATURE CODE
= 2 SUPPRESS CLIPPED FEATURE LABEL

IOP16 = 0 LABEL CLIPPING FEATURE WITH FEATURE CODE

= 1 LABEL CLIPPING FEATURE WITH PLANE #
= 2 SUPPRESS CLIPPING FEATURE LABEL

IOP31 = 1 ADDITIONAL DEBUG INFORMATION

PAR1 = MINIMUM X COORDINATE FOR PLOT (Default=XMIN)

PAR2 = MAXIMUM X COORDINATE FOR PLOT (Default=XMAX)

PAR3 = MINIMUM Y COORDINATE FOR PLOT (Default=YMIN)

PAR4 = MAXIMUM Y COORDINATE FOR PLOT (Default=YMAX)

PAR5 = PLOT SCALE IN USER UNITS PER PLOTTER UNIT (No Default)

PAR6 = ANNOTATION SIZE (Plotter units; Default=0.07)

PAR11 = DISTANCE BETWEEN LABELS (User units; Default=PAR5*5)

PAR12 = 0 OUTPUT STANDARD LINE SEGMENTS

> 0 OUTPUT DASHED LINE SEGMENTS OF PAR12 LENGTH
< 0 OUTPUT SMOOTHED LINE SEGMENTS

NOTE: If the distance between points is greater than PAR12 plotter units, then insert intermediate points.

PAR13 = PLANE # IF REAL # (Overrides IOP11)

END

4. PLANE SPECIFICATION LINE

filename plane#1 plane#2 inc RRR LLL

where

filename = File 25 filename

plane#1 = First plane to plot
plane#2 = Last plane to plot
inc = Increment between planes
RRR = Right side of feature code in VBM that is to be clipped (usually topo) (-1 is wildcard)
LLL = Left side of feature code in VBM that is to be clipped (-1 or blank is wildcard)

Page 654-42 Revised: 18-February-00

MineSight®
Proprietary Software: Mintec, inc. M654V5 - PLOT OR OUTPUT CLIPPED VBM DATA

M654V5 SAMPLE RUN FILE #1

MEDS-654V5 10= SAM [Link] 19= [Link] 3= [Link]

** PLOT TOPO OUTSIDE WINDOW **

USR = ABC

IOP8 = 0 / 0 = PLOT OUTSIDE WINDOW; 1 = PLOT INSIDE WINDOW

IOP11 = 2600 / PLANE # CONTAINING FEATURE WINDOW
IOP12 = 3 / WINDOW FEATURE CODE

PAR1 = 10000 15000 / MIN & MAX X-COORDS FOR PLOTTING

PAR3 = 10000 15000 / MIN & MAX Y-COORDS FOR PLOTTING
PAR5 = 1000. / SCALE IN UNITS PER INCH
PAR6 = 0.05 / ANNOTATION SIZE IN INCHES
PAR11 = 4000. / DIST BETWEEN ANNOT. IN USER UNITS

END
[Link] 3500 4550 50 901

M122V1 SAMPLE RUN FILE #1

MEDS-122V1 10= [Link] 3= [Link]

** M654V5 TEST - PLOT TOPO OUTSIDE PIT 899 ON LEVEL 3500 **

USR = ABC
MAP = 9000 16000 1000 9000 16000 1000

END
BORDR 1 10000 15000 10000 15000 0
BORDR 1 10015 14985 10000 14985 0
GRID 1 10000 15000 10000 15000 1000
TICKS 1 10000 10000 10000 15000 1000 .08
TICKS 1 10000 15000 15000 15000 1000 .08
COORD 1 9700 10025 9700 15025 1000 .05 0 0 10000 1000
COORD 1 9975 15025 14975 15025 1000 .05 90 0 10000 1000
BORDR 1 10000 15000 9500 10000 0
BORDR 1 10015 14985 9515 9985 0
LINE 1 13500 9500 13500 10000 0
LINE 1 13500 9800 15000 9800 0
LINE 1 15000 9600 13500 9600 0
LABEL 1 13910 9880 0 .04 17/WIDGET MINING CO.
LABEL 1 13850 9680 0 .04 21/TOPO OUTSIDE AREA
LABEL 1 13910 9540 0 .04 17/SCALE: 1" = 1000’
USERF [Link]
ENDOC

Revised: 18-February-00 Page 654-43

 MineSight®
M654V5 - Plot PLOT OR OUTPUT CLIPPED VBM DATA Proprietary Software: Mintec, inc.

HOW TO DEBUG AN M654V5 RUN

1. ** ERROR RETURN FROM VBMRGM **

will appear if there is no data in the VBM or a specified plane is not found. Check that you are using the correct VBM.

2. The clipping feature should be digitized clockwise as should the features to be clipped.

3. Check the MineSight® error messages in the Appendix.

Page 654-44 Revised: 18-February-00

MineSight®
Proprietary Software: Mintec, inc. M655V1 - CALCULATE VBM PLANE INTERSECTIONS

M655V1— CALCULATE PLANE INTERSECTIONS

FROM VBM DATA

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M655V1 extracts specified features from a series of specified M655V1 is used to extract bench intersections from the VBM
VBM cross-section planes and determines the bench intersection cross-section files. The bench plan that is produced is used to
points based upon a constant elevation. An M122 plot file for interpret bench geology. Both N-S and E-W intersection data
plotting or previewing is output. can be plotted for the specified benches. (Note: For other
projections, any orientation of vertical sections can be plotted
PROGRAM FLOW DIAGRAM showing their bench intersections.) The benches to be plotted
are specified by the user.

RUN FILE: The map area to be plotted is specified along with the plot scale
and annotation size. The VBM section planes to use in the
- Map limits and plot scale calculation are specified at the end of the run file. The starting
- Feature codes
- Plane numbers
X coordinate on this Section Request Line is usually specified
as the minimum X value for the VBM file. If a different X
coordinate is used, the location of the bench intersections will
be offset from their true coordinate.

INPUT: CALCS:

- PCF - Calculate plan

- File 25 intersections from
digitized cross-sections
- Generate an M122 plot
file of intersection points

OUTPUT:
- M122 plot file
- Printer Output File

Revised: 31-May-91 Page 655-1

 MineSight®
M655V1 - CALCULATE VBM PLANE INTERSECTIONS Proprietary Software: Mintec, inc.

Page 655-2 Revised: 31-May-91

MineSight®
Proprietary Software: Mintec, inc. M655V1-CALCULATE PLANE INTERSECTIONS FROM VBM DATA

M655V1—CALCULATE PLANE INTERSECTIONS FROM VBM DATA

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-655V1 10=filename 25=filename 19=filename;

MEDS-655V1 3=filename
where

MEDS-655V1 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
19 = the name of the M122 Plot File
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = SYMBOL NUMBER FOR PLOTTING (default=5)

IOP2 = NUMBER OF CODES TO READ FOR COLOR CODING OF FEATURES

NOTE: If IOP2=0, do not plot lines, just symbols and feature codes. If IOP2>0, plot color coded lines through
section intersects (lines can be omitted with IOP3=1.)

IOP3 = 0 & IOP2>0 DRAW LINES FOR MATCHING INTERSECTION ONLY

= 1 & IOP2>0 DO NOT PLOT LINES, JUST SYMBOLS & CODES

IOP9 = 0 USE ALL VBM FEATURES

= 1 READ FEATURE SPECIFICATION LINES

NOTE: If IOP9 and IOP2 are non-zero, then the program will use only the features from feature specificaton
lines, and assign colors according to color coding lines.

IOP10 = 0 READ VBM PLANES FROM THE RUN FILE

= 1 USE ALL VBM PLANES AND USE ORIENTATION DATA FROM THE VBM FILE

IOP39 = 0 DO NOT TRY TO FILL GAPS IN COLORS WHEN CONNECTING INTERSECTIONS

= 1 TAKE EXTRA EFFORT TO FILL GAPS IN COLORS

NOTE: IOP39=1 will slow the program.

PAR1 = MINIMUM X COORDINATE FOR PLOT (default=XMIN)

PAR2 = MAXIMUM X COORDINATE FOR PLOT (default=XMAX)

PAR3 = MINIMUM Y COORDINATE FOR PLOT (default=YMIN)

PAR4 = MAXIMUM Y COORDINATE FOR PLOT (default=YMAX)
PAR5 = PLOT SCALE IN USER UNITS PER PLOTTER UNITS (no default)
PAR6 = ANNOTATION SIZE (plotter units; default=0.07)

Revised: 6-August-97 Page 655-3

 MineSight®
M655V1-CALCULATE PLANE INTERSECTIONS FROM VBM DATA Proprietary Software: Mintec, inc.

PAR7 = ELEVATION FOR INTERSECTION CALCULATION (plane elevation, bench toe, midpoint, etc.)

NOTE: If 0.0, you will be prompted for value from the screen.

PAR8 = TOLERANCE FOR DISTINGUISHING INTERSECTIONS (default=0.1*(VBM XPLN Precision))

PAR9 = LENGTH OF TICK (default=6*PAR6)

END

4. FEATURE SPECIFICATION LINE (if IOP9=1)

left right
–2
where

left = Left side feature code or –1 for a wild card

right = Right side feature code or –1 for a wild card
–2 = end input of Feature Specification Lines

NOTE: Use one line for each set of feature codes, leaving a space between left and right

5. COLOR CODING FOR FEATURES (if IOP2>0)

right side feature codes (up to 50 codes in 132 columns are allowed on each line.)
pen numbers

NOTE: The very last feature code can be a wildcard -1. The corresponding pen# will be used for drawing all
the lines with codes for which pen number is not specified.

6. SECTION REQUEST LINES (blank line will produce error message—PLANE NOT FOUND=0)

plane# xorigin yorigin azm zorigin dip

where

plane# = Plane number of VBM plane

xorigin = X origin of plane
yorigin = Y origin of plane
azm = Azimuth of plane base line (0 for N-S section, 90 for E-W section)

zorigin = Z origin of plane

dip = Dip of the plane

X,Y,and Z origin coordinates of a VBM plane are the true Easting, Northing and Elevation of the lower left corner of the VBM plane
(the corner with coordinates XPLN minimum and YPLN minimum.)

Entering xorigin, yorigin, azm, zorigin and dip is optional. If they are not entered, the program will use orientation data from the
VBM file. However, if you enter orientation data after the plane# it will override the VBM data. To enter orientation parameters you
must enter AT LEAST xorigin, yorigin and azm. If zorigin and dip are not entered, the program will presume that the VBM plane is
vertical and will set dip to -90. For new VBMs the program will set zorigin to the corresponding value from the VBM file. For old
VBMs zorigin will be set to the minimum YPLN value.

NOTE: You cannot enter dip without entering zorigin.

Page 655-4 Revised: 6-August-97

MineSight®
Proprietary Software: Mintec, inc. M655V1-CALCULATE PLANE INTERSECTIONS FROM VBM DATA

M655V1 SAMPLE RUN FILE #1

MEDS-655V1 10=[Link] 25=[Link] 19=[Link];
MEDS-655V1 3=[Link]
EXTRACT VBM INTERSECTION SYMBOLS FOR ALL VBM FEATURES

USR = ABC

IOP1 = 3 / SYMBOL FOR INTERSECTION DISPLAY

IOP2 = 0 / # FEATURE CODES FOR COLOR CODING

PAR1 = 503000 506000 / XMIN, XMAX

PAR3 = 552500 555500 / YMIN, YMAX

PAR5 = 100 / SCALE

PAR6 = .07 / ANNOTATION SIZE

PAR7 = 1512.5 / ELEVATION OF HORIZONTAL PLANE FOR INTERSECTIONS

END
553000 502000 553000 90 Section Request Lines
553100 502000 553100 90
553200 502000 553200 90

M655V1 SAMPLE RUN FILE #2

MEDS-655V1 10=[Link] 25=[Link] 19=[Link];
MEDS-655V1 3=[Link]
EXTRACT VBM INTERSECTION SYMBOLS WITH SELECTED FEATURES

USR = ABC

IOP1 = 3 / SYMBOL FOR INTERSECTION DISPLAY

IOP2 = 0 / # FEATURE CODES FOR COLOR CODING
IOP9 = 1 / READ FEATURE SPECIFICATION LINES

PAR1 = 503000 506000 / XMIN, XMAX

PAR3 = 552500 555500 / YMIN, YMAX

PAR5 = 100 / SCALE

PAR6 = .07 / ANNOTATION SIZE

PAR7 = 1512.5 / ELEVATION OF HORIZONTAL PLANE FOR INTERSECTIONS

END
–1 301 Feature Specification Lines
–1 302
–2
553000 502000 553000 90 Section Request Lines
553100 502000 553100 90
553200 502000 553200 90

Revised: 6-August-97 Page 655-5

 MineSight®
M655V1-CALCULATE PLANE INTERSECTIONS FROM VBM DATA Proprietary Software: Mintec, inc.

M655V1 SAMPLE RUN FILE #3

MEDS-655V1 10=[Link] 25=[Link] 19=[Link];
MEDS-655V1 3=[Link]
EXTRACT VBM INTERSECTION SYMBOLS WITH FEATURE COLOR CODING

USR = ABC

IOP1 = 3 / SYMBOL FOR INTERSECTION DISPLAY

IOP2 = 6 / # FEATURE CODES FOR COLOR CODING

PAR1 = 503000 506000 / XMIN, XMAX

PAR3 = 552500 555500 / YMIN, YMAX

PAR5 = 100 / SCALE

PAR6 = .07 / ANNOTATION SIZE

PAR7 = 1512.5 / ELEVATION OF HORIZONTAL PLANE FOR INTERSECTIONS

END
301 302 303 304 305 306 Color Coding for Features
1 2 3 4 5 6

553000 502000 553000 90 Section Request Lines

553100 502000 553100 90
553200 502000 553200 90

HOW TO DEBUG AN M655V1 RUN

1. If the bench intersections do not plot at the correct location, check the X & Y origin values on the Section Request Line.
Also check that the azimuth of the section is correct. For sections that are not north-south or east-west the azimuth is
particularly critical.

2. Check the MineSight® error messages in the Appendix.

Page 655-6 Revised: 6-August-97

MineSight®
Proprietary Software: Mintec, inc. M655V2 - CALCULATE VBM SECTION INTERSECTIONS

M655V2 — CALCULATE SECTION INTERSECTIONS

FROM VBM DATA

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M655V2 extracts specified features from a series of specified M655V2 is used to extract section intersections from VBM files.
VBM planes and determines the section intersection points with The sections that are produced are used to interpret geology
a specified section. An M122 plot file for graphics or previewing that is usually digitized back into section VBM’s. Section
is output. intersections can be derived from bench VBM’s or other section
VBM’s. The X coordinates that are written to the M122 plot
PROGRAM FLOW DIAGRAM file are relative to the left edge of the section.

You can calculate any orientation section intersections from

digitized bench geology, north-south intersections from digitized
RUN FILE: data on east-west sections, east-west intersections from digitized
- Map limits
data on north-south sections and any orientation section
- Plot scale intersections from digitized data on section.
- Feature codes & plane
numbers PAR1-4 describe the section where the intersections are to be
calculated. If you are calculating intersections from sections that
are not N-S or E-W (IOP2≥3), then the true coordinates of these
sections must be specified after the END line (see Line 6—
Non-Orthogonal Section Request Lines). The true increment
between angled sections must also be specified (see Line 5—
INPUT: CALCS: Orthogonal Section Request Lines).
- PCF - Generate section
- File 25 intersections from When using IOP2≥3 you have to be careful when declaring your
digitized plans sections on Line 6. For the non-orthogonal case, the plane
- Generate an M122 plot number should be for the plane to be intersected. The X-origin
file of intersection points and y-origin need to be set to the true origin of the intersected
plane.

Oftentimes, a non-orthogonal VBM has a 0,0 origin that

represents a different coordinate in space (i.e. 7000,5000). It is
OUTPUT: this represented point that should be entered on Line 6. For
example, to run an intersection through plane 10000 of a VBM
- M122 plot file initialized with a 0,0 origin representing the point 7000,5000
- Printer Output File and having an azimuth of 45 degrees, enter the following for
Line 6.

10000 7000 5000 45

Revised: 30-November-95 Page 655-7

 MineSight®
M655V2 - CALCULATE SECTION INTERSECTIONS Proprietary Software: Mintec, inc.

Page 655-8 Revised: 30-November-95

MineSight®
Proprietary Software: Mintec, inc. M655V2-CALCULATE VBM SECTION INTERSECTIONS

M655V2 CALCULATE SECTION INTERSECTIONS FROM VBM DATA

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-655V2 10=filename 25=filename 19=filename;

MEDS-655V2 3=filename
where

MEDS-655V2 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
19 = the name of the M122 Plot File
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = SYMBOL NUMBER FOR PLOTTING (default=5)

IOP2 = IS THE CALCULATION TYPE CHOSEN FROM THE FOLLOWING TABLE:

Value of IOP2 as a function of VBM Geometry

Compute: Intersecting Plane: NS WE Non-orthogonal

From: VBM plane orientation

VBM default -1 -1 -1
Planar 0 0 0
NS none 2 7
WE 1 none 6
Non-orthogonal 4 3 5

Note that the intersecting plane is ALWAYS vertical (sectional) but its azimuth can be 0 (NS section), 90 (WE
section), or any other value (non-orthogonal). The most conceptually easy choice is IOP1=-1. Make sure a
default orientation is assigned to your VBM (See the VBM Technical Section) and define the intersecting plane
using PAR1-4.

IOP3 = 0 NO FEATURE SPECIFICATION LINES (Pen# 1 is used)

= 1 READ FEATURE SPECIFICATION LINES

IOP10 = 0 READ PLANES FROM THE RUN FILE

= 1 USE ALL PLANES FROM THE VBM FILE
(and use their orientation data from the VBM file)

PAR1 = X1 EASTING FOR BEGINNING POINT OF SECTION LINE

PAR2 = Y1 NORTHING FOR BEGINNING POINT OF SECTION LINE

Revised: 15-September-97 Page 655-9

 MineSight®
M655V2-CALCULATE VBM SECTION INTERSECTIONS Proprietary Software: Mintec, inc.

PAR3 = X2 EASTING FOR ENDING POINT OF SECTION LINE

PAR4 = Y2 NORTHING FOR ENDING POINT OF SECTION LINE

NOTE: For PAR1-4, there is no default. These are the coordinates of the section where intersections are to be
calculated.

PAR5 = PLOT SCALE IN USER UNITS PER PLOTTER UNIT (no default)

PAR6 = ANNOTATION SIZE (in plotter units) (default=0.07)

PAR9 = LENGTH OF TICK (default = 6*PAR6)

END

4. FEATURE SPECIFICATION LINES (if IOP3=1)

il ir ipen isy
where

il = Left side code (-1 = wild card)

ir = Right side code (-1 = wild card)
ipen = Pen #
isy = Symbol #

A maximum of 100 lines is allowed. Enter il = -2 to end input.

5. VBM PLANE NUMBERS REQUEST LINES (if IOP2<3, or IOP2>5)

plane#1 plane#2 inc

where

plane#1 = First plane to plot (inclusive)

plane#2 = Last plane to plot (inclusive)
inc = Increment between planes

A total of 2000 planes is allowed.

6. NON-ORTHOGONAL VBM PLANES REQUEST LINES (if IOP2=3, 4, or 5)

plane#1 xorigin yorigin azm

where

xorigin, yorigin, and zorigin are the true Easting, Northing, and Elevation of the lower-left corner of the VBM plane, azm is the
azimuth of the plane and dip is the dip of the VBM plane.

Orientation parameters xorigin, yorigin, azm, zorigin, and dip are optional.

If you enter only xorigin, yorigin, and azm the program will presume that the VBM plane is vertical and will set dip=-90. It will set
zorigin to its value from the VBM data for new VBMs. For old VBMs zorigin will be set to the minimum value of YPLN.

CAUTION: If you want to use orientation data from the VBM file (i.e., IOP2=-1, IOP10=1 or do not enter xorigin, yorigin, azm,
zorigin, and dip) be sure that you have a NEW VBM, or that all planes of interest have orientation data stored in the VBM file 25.

Page 655-10 Revised: 15-September-97

MineSight®
Proprietary Software: Mintec, inc. M655V2-CALCULATE VBM SECTION INTERSECTIONS

M655V2 SAMPLE RUN FILE #1

MEDS-655V2 10=[Link] 25=[Link] 19=[Link];
MEDS-655V2 3=[Link]
** EXTRACT S-N INTERSECTIONS FROM W-E SECTION GEOLOGY **

USR = ABC

IOP1 = 0 / SYMBOL NUMBER (default = 5)

IOP2 = 1 / 1=COMPUTE N-S INTERSECTIONS FROM E-W XSEC GEOLOGY

PAR1 = 12500 10000 / XBEG YBEG

PAR3 = 12500 15000 / XEND YEND
PAR5 = 1000 / SCALE
PAR6 = .05 / ANNOTATION SIZE

END
11750 13250 500 ORTHOGONAL SECTION REQUEST LINES

M655V2 SAMPLE RUN FILE #2

MEDS-655V2 10=[Link] 25=[Link] 19=[Link];
MEDS-655V2 3=[Link]
* EXTRACT W-E INTERSECTIONS FROM NON-ORTHOGONAL SECTIONS *

COM NOTE:IF [Link] VBM FILE NOT AVAILABLE, INITIALIZE

COM [Link] FIRST WITH 0-6500 X-LIMITS THEN, LOAD [Link]
COM INTO THIS VBM USING M649V1

USR = ABC

IOP1 = 0 / SYMBOL NUMBER (default = 5)

IOP2 = 3 / 3=COMPUTE W-E INTERSECTIONS FROM NON-ORTHOGONAL SECTIONS

PAR1 = 10000 13000 / XBEG YBEG

PAR3 = 15000 13000 / XEND YEND

PAR5 = 1000 / SCALE

PAR6 = .05 / ANNOTATION SIZE

COM NON-ORTHOGONAL SECTIONS FOLLOW ‘END’ LINE
COM PLANE#, XORIGIN, YORIGIN & AZIMUTH OF SECTION ARE REQ’D

END
2510000.10000.45. NON-ORTHOGONAL SECTION REQUEST LINES
5010000.10200.45.

Revised: 15-September-97 Page 655-11

 MineSight®
M655V2-CALCULATE VBM SECTION INTERSECTIONS Proprietary Software: Mintec, inc.

M655V2 SAMPLE RUN FILE #3

MEDS-655V2 10=[Link] 25=[Link] 19=[Link];
MEDS-655V2 3=[Link]
** EXTRACT W-E INTERSECTIONS FROM BENCH GEOLOGY **

USR = ABC

IOP1 = 0 / SYMBOL NUMBER (default = 5)

IOP2 = 0 / 0=COMPUTE INTERSECTIONS FROM BENCH GEOLOGY
IOP3 = 1/ 1 = READ FEATURE SPECIFICATION LINES (Pen # 1 is used)

PAR1 = 10000 12500 / XBEG YBEG

PAR3 = 15000 12500 / XEND YEND

PAR5 = 1000 / SCALE

PAR6 = .05 / ANNOTATION SIZE
END
-1 401 2 5 FEATURE SPECIFICATION LINES
-1 402 2 6
-2

HOW TO DEBUG AN M655V2 RUN

1. To check this routine, you should plot out the intersections. Check that the intersections appear at the correct location on
the section. If not, check that xorigin and yorigin have been set correctly.

2. If no intersections are calculated by this program, check that the sections are correctly oriented, and that IOP2 is
correctly specified.

3. Check the MineSight® error messages in the Appendix.

Page 655-12 Revised: 15-September-97

MineSight®
Proprietary Software: Mintec, inc. M657V1—EXTRACT VBM INTERSECTIONS WITH GRID

M657V1 EXTRACT INTERSECTIONS OF

VBM DATA WITH A GRID

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M657V1 is used to calculate the intersection elevation of M657V1 is used to compute intersections at row and/or column
specified grid lines with digitized VBM data (usually contours). midpoints of the mine grid from digitized data stored in File 25.
These intersections are written to an ASCII file for grid This is usually done as a first step in transforming data into a 2-
interpolation by other routines. -D grid of topography values. The ASCII file that is produced
should then be sorted by northings and subsorted by eastings
PROGRAM FLOW DIAGRAM with your system's sort routine.

There are two methods of producing a 2--D grid from the

intersection data:
RUN FILE:
Linearly interpolate between intersections with pro--gram
- Feature code M657V2. Only use east--west intersections from M657V1 with
- Number of rows & this method.
columns
- Minimum and maximum
nortfng and easting Interpolate the grid with inverse distance (M620V1) or with
kriging (M624V1). Use east-west and north-south intersections.

You must have stored digitized topo data in the VBM file prior
to running this program.

INPUT: CALCS: You can also specify the number of rows and columns for which
- PCF - Calculate intersection of intersections will be calculated.
- File 25 grid lines with VBM data
- Output file of intersections ASCII output can be used as input to M635V1 to create a DTM.

OUTPUT:
- ASCII output file of
intersections
- Printer Output File

Revised: 1-August-94 Page 657-1

 MineSight®
M657V1—EXTRACT VBM INTERSECTIONS WITH GRID Proprietary Software: Mintec, inc.

Page 657-2 Revised: 1-August-94

MineSight®
Proprietary Software: Mintec, inc. M657V1—EXTRACT INTERSECTIONS OF VBM DATA WITH A GRID

M657V1 EXTRACT INTERSECTIONS OF VBM DATA WITH A GRID

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-657V1 10=filename 25=filename 19=filename;

MEDS-657V1 3=filename
where

MEDS-657V1 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
19 = the name of the Output File to be Sorted
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = RIGHT SIDE FEATURE CODE

= –1 to make right side feature a wild card

IOP2 = # OF ROWS(Default=(PAR5–PAR4)/PAR6 + 0.5)

IOP3 = # OF COLUMNS(Default=(PAR2–PAR1)/PAR3 + 0.5)

IOP4 = 0 DO NOT COMPUTE E-W INTERSECTIONS

= 1 COMPUTE E-W INTERSECTIONS

IOP5 = 0 DO NOT COMPUTE N-S INTERSECTIONS

= 1 COMPUTE N-S INTERSECTIONS

NOTE: If you are planning to run M657V2 after the routine, do not calculate north-south intersections.

IOP6 = LEFT SIDE FEATURE CODE

= –1 to make left side feature a wild card

IOP7 = 0 OUTPUT ORIGINAL DATA FORMAT X, Y, Z TO FILE 19

= 1 OUTPUT STANDARD 3–D FORMAT X, Y, Z TO FILE 19
= 2 OUTPUT SURVEY DATA FORMAT TOPO X, Y, Z TO FILE 19

Revised: 30-September-92 Page 657-3

 MineSight®
M657V1—EXTRACT INTERSECTIONS OF VBM DATA WITH A GRID Proprietary Software: Mintec, inc.

PAR1 = MINIMUM X COORDINATE

PAR2 = MAXIMUM X COORDINATE
PAR3 = CHANGE IN X COORDINATE

PAR4 = MINIMUM Y COORDINATE

PAR5 = MAXIMUM Y COORDINATE
PAR6 = CHANGE IN Y COORDINATE

NOTE: PAR1-6 default to PCF values.

END

4. PLANE SPECIFICATION LINES

plane#1 plane#2 increment

where

plane#1 =First plane for which to calculate intersections

plane#2 =Last plane for which to calculate intersections
increment =Increment for the range of planes

NOTE: If increment is not specified, then all planes from plane#1 to plane#2 are used

Page 657-4 Revised: 30-September-92

MineSight®
Proprietary Software: Mintec, inc. M657V1—EXTRACT INTERSECTIONS OF VBM DATA WITH A GRID

M657V1 SAMPLE RUN FILE #1

MEDS-657V1 10=[Link] 25=[Link] 3=[Link];
MEDS-657V1 19=[Link]
* CALCULATE TOPO INTERSECTIONS *

USR = ABC

IOP1 = 901 / TOPO CODE

IOP2 = 5050 / # OF ROWS AND COLUMNS
IOP4 = 1 / CALCULATE E-W INTERSECTIONS

PAR1 = 1000015000100/ XMINXMAXDX

PAR4 = 1000015000100/ YMINYMAXDY

END
4000 5000 Plane specification line

M657V1 SAMPLE RUN FILE #2

MEDS-657V1 10=[Link] 25=[Link] 19=[Link];
MEDS-657V1 3=[Link]
CALCULATE TOPO INTERSECTIONS FOR INTERPOLATION WITH M620V1

USR = ABC

IOP1 = 901 / TOPO CODE

IOP2 = 50 / # OF ROWS - NY
IOP3 = 50 / # OF COLUMNS - NX
IOP4 = 1 / CALCULATE E-W INTERSECTIONS
IOP5 = 1 / CALCULATE N-S INTERSECTIONS

PAR1 = 1000015000100/ XMINXMAXDX

PAR4 = 1000015000100/ YMINYMAXDY

END
4000 5000

Revised: 30-September-92 Page 657-5

 MineSight®
M657V1—EXTRACT INTERSECTIONS OF VBM DATA WITH A GRID Proprietary Software: Mintec, inc.

HOW TO DEBUG AN M657V1 RUN

1. ERROR IN SECTION SPECIFICATION
will appear if there is a problem reading the VBM plane numbers from the end of the run file.

2. After running this routine, ensure that you sort the output file on northings (first field) and subsort on eastings (second field).

3. Check the MineSight® error messages in the Appendix.

Page 657-6 Revised: 30-September-92

MineSight®
Proprietary Software: Mintec, inc. M657V2—CREATE GRIDDED DATA FROM INTERSECTIONS

M657V2 CREATE GRIDDED DATA FROM INTERSECTIONS

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M657V2 takes the output from M657V1 (after it has been sorted This program is used to linearly interpolate intersections obtained
by northing and easting) and computes the grid elevations for from M657V1. These intersections can only be east-west as
topography. The grid elevation values can be input to the M657V2 only interpolates along rows. There is an option for
topography file (File 13) using M630V1. extending the last intersection on a row to the end of a row, or to
extrapolate from the last few intersections.
PROGRAM FLOW DIAGRAM
This routine is normally used in the conversion of digitized
topography data (stored in a VBM) into a 2-D grid of topography
RUN FILE: lines.
- Number of rows &
columns
You can also specify the number of rows and columns along
- with the minimum and maximum northings and eastings to
operate within.

INPUT: CALCS:

- PCF - Linearly interpolate

- ASCII file of intersections to 2-grid
intersections -Output file of grid
elevations

OUTPUT:
- Output ASCII file of grid
elevations
- Printer Output File

Revised: 31-May-91 Page 657-7

 MineSight®
M657V2—CREATE GRIDDED DATA FROM INTERSECTIONS Proprietary Software: Mintec, inc.

Page 657-8 Revised: 31-May-91

MineSight®
Proprietary Software: Mintec, inc. M657V2—CREATE GRIDDED DATA FROM INTERSECTIONS

M657V2 CREATE GRIDDED DATA FROM INTERSECTIONS

RUN FILE OPERATION
1. NAMES LINE (must be the first line entered)

MEDS-657V2 10=filename 19=filename 30=filename;

MEDS-657V2 3=filename
where

MEDS-657V2 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
19 = the name of the Input File
30 = the name of the Output File for M630V1
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = # OF COLUMNS
IOP2 = # OF ROWS

IOP3 = 0 EXTEND LAST VALUE TO ROW LIMIT

= 1 LINEARLY INTERPOLATE (EXTRAPOLATE) VALUE TO ROW
LIMIT BASED ON NEAREST Z INTERSECTIONS

IOP11 = STARTING COLUMN

IOP12 = ENDING COLUMN

IOP13 = STARTING ROW

IOP14 = ENDING ROW

PAR1 = MINIMUM X COORDINATE

PAR2 = MAXIMUM X COORDINATE
PAR3 = CHANGE IN X COORDINATE

PAR4 = MINIMUM Y COORDINATE

PAR5 = MAXIMUM Y COORDINATE
PAR6 = CHANGE IN Y COORDINATE
NOTE: PAR1-6 default to PCF values.

FMT1 = OUTPUT DATA FORMAT (Default = 3I3, 10F7.1)

NOTE: Format must be specified if your model is 1000 x 1000. An example format is (3I4,10F6.0).
Use the same format for M630V1.

END

Revised: 30-September-95 Page 657-9

 MineSight®
M657V2—CREATE GRIDDED DATA FROM INTERSECTIONS Proprietary Software: Mintec, inc.

M657V2 SAMPLE RUN FILE #1

MEDS-657V2 10=[Link] 30=[Link] 3=SAM657.LA2;
MEDS-657V2 19=SAM657.IA2
* CALCULATE TOPO MATRIX FROM INTERSECTION DATA *

USR = ABC

IOP1 = 50 50 / # OF COLUMNS AND ROWS

PAR1 = 10000 15000 100 / XMIN XMAX DX

PAR4 = 10000 15000 100 / YMIN YMAX DY

END

HOW TO DEBUG AN M657V2 RUN

1. Only use input data that was produced by M657V1 for east-west sections.

2. The input file created by M657V1 must be sorted on northing and subsorted on eastings. If this is not done, unpredictable results
will occur. Typically, the topography intersections file is called [Link] and the sorted intersections file [Link].
For IBM-PCs and compatibles, the following LSORT command will perform this sorting function:
C:\ >LSORT S C C [Link] [Link] V 1 12 N A 13 12 N A O Y Y

3. Check the MineSight® error messages in the Appendix.

Page 657-10 Revised: 30-September-95

MineSight®
Proprietary Software: Mintec, inc. M658V1—PLOT VBM CROSS-SECTIONS

M658V1 PLOT VBM CROSS--SECTIONS (M122)

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M658V1 takes contours stored in the VBM file and generates This program is used to cut cross--sections through a plan VBM
an M122 plot file containing the cross--section view at a specified file. An M122 plot file can be produced (IOP4=0) that contains
section line. It can also generate an ASCII file of sections in the intersection of a specified section with a particular feature
M649V1 input format. code from multiple planes. This routine is usually used for
generating a cross--section of topography to overlay on other
This program is useful for viewing pit designs and topography, cross--sections.
and for rationalizing seam structure between plan and section.
The section can be at any orientation. It is defined by the start
PROGRAM FLOW DIAGRAM and end easting and northing. There is also an option for
extending the section beyond the last intersection.

RUN FILE: The X origin of the section plot file is 0.0. All plot commands
are relative to this origin, not the VBM origin. Ensure that your
- Section specification
- Feature code
M122 run file is set up correctly to handle an origin of 0.0.

To generate an M649V1 input file, use IOP4>0, IOP5 and

PAR8–11.

Using IOP4=1 or 2 will create profiles for many sections in one

run. IOP4=3 creates a profile for one section only. IOP5 is used
to specify how the VBM feature code will be stored in the output
INPUT: CALCS: file.

- PCF - Cut cross-sections

- File 25 through a VBM feature
- Produce a M122 plot file

OUTPUT:
- M122 plot file
- ASCII file of points
- Printer Output File

Revised: 30-September-92 Page 658-1

 MineSight®
M658V1—PLOT VBM CROSS-SECTIONS Proprietary Software: Mintec, inc.

Page 658-2 Revised: 30-September-92

MineSight®
Proprietary Software: Mintec, inc. M658V1-PLOT VBM CROSS-SECTIONS

M658V1—PLOT VBM CROSS-SECTIONS (M122)

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-658V1 10=filename 25=filename 19=filename;

MEDS-658V1 3=filename
where

MEDS-658V1 (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
25= the name of the VBM FILE
19= the name of the M122 Plot File / Profile output file
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = VBM FEATURE CODE

IOP2 = FIRST INTEGER PLANE NUMBER

IOP3 = LAST INTEGER PLANE NUMBER

NOTE: Integer plane number is a plane number divided by plane precision.

IOP4 = 0 OUTPUT PLOT COMMANDS FOR ONE SECTION

= 1 OUTPUT PROFILES FOR MULTIPLE W-E SECTIONS (M649V1 input format)
= 2 OUTPUT PROFILES FOR MULTIPLE S-N SECTIONS (M649V1 input format)
= 3 OUTPUT PROFILES FOR ONE SECTION (with origin of 0; M649V1 input format)
(Use IOP4=3 for non-orthogonal sections or sections for dragline range diagrams)

IOP5 = FEATURE CODE FOR PROFILES(If IOP4>0)

PAR1 = X COORDINATE AT BEGINNING OF SECTION LINE

PAR2 = Y COORDINATE AT BEGINNING OF SECTION LINE
PAR3 = X COORDINATE AT END OF SECTION LINE
PAR4 = Y COORDINATE AT END OF SECTION LINE

PAR5 = FRACTION OF SECTION LENGTH TO EXTEND ON EITHER END FOR COMPUTING

INTERSECTIONS (1.0=100%; default=0.5)

PAR6 = FIRST PLANE (For real plane precision)

PAR7 = LAST PLANE (For real plane precision)

NOTE: If PAR6, PAR7, IOP2 and IOP3 are all equal to 0, then all planes will be used.

Revised: 01-August-97 Page 658-3

 MineSight®
M658V1-PLOT VBM CROSS-SECTIONS Proprietary Software: Mintec, inc.

PAR8–11 are used when IOP4>0.

PAR8 = X-OFFSET OF PROFILE DATA FOR VBM ENTRY

PAR9 = BEGINNING PLANE NUMBER FOR PROFILE GENERATION

(Smallest section northing if IOP4=1 or smallest section easting if IOP4=2)

PAR10 = ENDING PLANE NUMBER FOR PROFILE GENERATION

= (Largest section northing if IOP4=1 or largest section easting if IOP4=2)

PAR11 = INCREMENT BETWEEN PROFILE SECTIONS

END

M658V1 SAMPLE RUN FILE #1

MEDS-658V1 10=[Link] 25=[Link] 3=[Link];
MEDS-658V1 19=[Link]
** COMPUTE TOPO FOR PLOTTING @ 12250 EAST **

USR = ABC

IOP1 = 901 / TOPO CODE

PAR1 = 1225010500 /X1,Y1

PAR3 = 1225014500 /X2,Y2
PAR5 = 1

END

M122V1 SAMPLE RUN FILE #2

MEDS-122V1 10=[Link] 3=[Link]
* PLOT GEOLOGY & TOPO PROFILE; N-S SECT. LOOKING WEST @ 12250 E

USR = ABC
MAP = 0 5000 500 1500 5000 500
PLT = .07

END
USERF GRIDEW.122 / PLOT COMMANDS FOR STANDARD MAP
PEN# 2 / GREEN
USERF [Link] / TOPO PLOT COMMANDS FROM M658V1
SHIFT 1–105000 / GEOLOGY PLOT COMMANDS IN ACTUAL X-COORDS IDENT
MUST BE SHIFTED TO FIT INTO MAP (RELATIVE X-COORDS)
PEN# 3 / RED USERF
[Link] / GEOLOGY PLOT COMMANDS FROM M654V1
ENDOC

Page 658-4 Revised: 01-August-97

MineSight®
Proprietary Software: Mintec, inc. M658V1-PLOT VBM CROSS-SECTIONS

HOW TO DEBUG AN M658V1 RUN

1. When plotting the section with M122, remember that the cross-section data is relative to an origin of 0.0, not the VBM
or model origin. If overlaying this data on top of other cross-section data, you may have to shift the origin in M122 with
the SHIFT command. See the sample M122V1 file.

2. ?M658V1: IOP1 MUST be input in run file

The VBM feature code must be specified in the run file. There is no default.

3. ?M658V1: PAR’S 1–4 cannot all be ZERO

At least one of PAR1 through PAR4 must be non-zero in order to properly specify a section.

4. *** WARNING **No points were plotted!

The section you specified with PAR1 through PAR4 did not intersect any points in your VBM file. Make sure your
section corresponds to your VBM file.

5. Check the MineSight® error messages in the Appendix.

Revised: 01-August-97 Page 658-5

 MineSight®
M658V1-PLOT VBM CROSS-SECTIONS Proprietary Software: Mintec, inc.

Page 658-6 Revised: 01-August-97

MineSight®
Proprietary Software: Mintec, inc. M658V2—PLOT PIT CROSS-SECTIONS FROM VBM

M658V2 PLOT PIT CROSS-SECTIONS FROM VBM (M122 OR

VBM-READY ASCII)

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M658V2 is used to generate a cross-section through a pit stored This program is used to plot cross-sections through pits stored
in the VBM file. The topography can also be plotted at the same in a plan VBM file. The bench slope can be specified (as the
time. tangent of an angle) to produce a realistic pit section.

PROGRAM FLOW DIAGRAM The section can be at any orientation. It is defined by the start
and end easting and northing. There is also an option for
extending the section beyond the last intersection.

For M122 plot files, the X origin of the plot is 0.0. All plot
RUN FILE: commands are relative to this origin, not the VBM origin. Ensure
- Feature codes that your M122 run file is set up correctly to handle an origin of
- Pen numbers 0.0.
- Bench wall slope
For VBM-ready ASCII files the plane will be the starting y-
coordinate and the x-coordinate will correspond to the x-
coordinate of the VBM being used. The y-coordinate is the bench
or plane of the VBM being used.

INPUT: CALCS:

- PCF - Cut cross-sections

- File 25 through a VBM pit
Produce an M122 plot file
or
- VBM-ready ASCII file

OUTPUT:
- M122 plot file or VBM-
ready ASCII file
- Printer Output File

Revised: 10-September-96 Page 658-7

 MineSight®
M658V2—PLOT PIT CROSS-SECTIONS FROM VBM Proprietary Software: Mintec, inc.

Page 658-8 Revised: 10-September-96

MineSight®
Proprietary Software: Mintec, inc. M6582V2 —PLOT PIT CROSS-SECTION FROM VBM

M658V2 PLOT PIT CROSS-SECTIONS FROM VBM (M122or VBM-READY ASCII)

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-658V2 10=filename 25=filename 19=filename;

MEDS-685V2 3=filename
where

MEDS-658V2 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
19 = the name of the M122 Plot File or VBM ASCII File
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = VBM TOPOGRAPHY FEATURE CODE

IOP2 = 1ST PIT CODE

IOP3 = 2ND PIT CODE
. ... . ...

IOP10 = 9TH PIT CODE

IOP11 = 0 USE PCF BENCHES
> 0 USE INPUT BENCHES INSTEAD OF PCF BENCHES
(Enter the number of benches + 1)

NOTE: If IOP11>0, enter (after section specification line) the highest crest elevation followed by the
bench toe elevations from the top down at 10 per line.

OPTIONS FOR M122 PLOT FILES (IF IOP27 = 0)

IOP12 = PEN# FOR FIRST PIT CODE IOP2 (DEFAULT = IOP22)

IOP13 = PEN# FOR SECOND PIT CODE IOP3 (DEFAULT = IOP22)
. .... ...

IOP20 = PEN# FOR NINTH PIT CODE IOP10 (DEFAULT = IOP22)

IOP21 = PEN# FOR TOPO (DEFAULT=1)

IOP22 = PEN# FOR PITS (DEFAULT=1)

Revised: 10-September-96 Page 658-9

 MineSight®
M6582V2 —PLOT PIT CROSS-SECTION FROM VBM Proprietary Software: Mintec, inc.

OPTIONS FOR VBM ASCII FILE (IF IOP27 = 1)

IOP12 = FEATURE CODE FOR FIRST PIT (DEFAULT = IOP2)

IOP13 = FEATURE CODE FOR SECOND PIT (DEFAULT = IOP3)

. .... .... ...

IOP20 = FEATURE CODE FOR NINTH PIT CODE (DEFAULT = IOP10)

OPTIONS FOR M122 PLOT FILES OR VBM ASCII FILES

IOP23 = 0 DO NOT COMBINE FEATURES (i.e., use features in IOP2 through IOP10).
= # THE NUMBER OF FEATURE REQUEST LINES TO READ (after END line)

IOP24 = 0 PLOT TOPO IF SPECIFIED BY IOP1 AND TRUNCATE BY TOPO

= 1 TRUNCATE BY TOPO BUT DO NOT PLOT TOPO

IOP25 = 1 FOR DEBUG OUTPUT -INTERSECTIONS

IOP26 = 0 OPTION TO PLOT SYMBOL AT BENCH MIDPOINT
= 1 (DO NOT PLOT AT MIDPOINT)
(IF AND ONLY IF MORE THAN ONE PIT IS BEING PLOTTED)

IOP27 = 0 OUTPUT M122 PLOT FILE

= 1 OUTPUT VBM ASCII FILE
IOP28 = FEATURE CODE FOR TOPO (DEFAULT=IOP1)
PAR1 = FRACTION FOR EXTENDING SECTION LINE TO COMPUTE INTERSECTION
AT BEGINNING & END (1.0=100%) (DEFAULT=.5)

PAR2 = BENCH WALL SLOPE (TANGENT)

(DEFAULT=2.75; tangent of 70o)

PAR4 = MIN ELEVATION FOR SELECTING PLANES

PAR5 = MAX ELEVATION FOR SELECTING PLANES (DEFAULT = 99999.)

END

4. SECTION SPECIFICATION LINE

X1 Y1 X2 Y2
where

X1 = X COORDINATE AT BEGINNING OF SECTION LINE

Y1 = Y COORDINATE AT BEGINNING OF SECTION LINE -PLANE FOR VBM ASCII
X2 = X COORDINATE AT END OF SECTION LINE
Y2 = Y COORDINATE AT END OF SECTION LINE

5. BENCH SPECIFICATION LINE(s) (If IOP11>0)

Input IOP11 bench toe elevations at 10 per line from the top down. The first elevation will be the crest of the top bench.

Page 658-10 Revised: 10-September-96

MineSight®
Proprietary Software: Mintec, inc. M6582V2 —PLOT PIT CROSS-SECTION FROM VBM

6. FEATURE SPECIFICATION LINE(s) (If IOP23>0)

feature-code plane1 plane2 pen-code

The maximum number of features is 99. For each feature, only the planes between plane1 and plane2 will be used. All points are
then combined into a single feature. The default pen-code is IOP22.

M658V2 SAMPLE RUN FILE #1

MEDS-658V2 10=[Link] 25=[Link] 19=[Link];
MEDS-658V2 3=[Link]
** PLOT STRIPPER PIT IN SECTION @ 12300 N **

USR = ABC

IOP1 = 901 / TOPO CODE

IOP2 = 899 / 1ST PIT CODE

IOP21 = 2 / PEN # FOR TOPO

IOP22 = 3 / PEN # FOR PIT

PAR1 = 0.5 / EXTEND SECTION .5 AGAIN ON EITHER END FOR COMPUTING

COM END POINT INTERSECTIONS

PAR2 = 2.75 / BENCH WALL SLOPE TANGENT (70 DEG.)

END
10500 12300 14500 12300 Section Specification Line

M122V1 SAMPLE RUN FILE #1

MEDS-122V1 10=[Link] 3=[Link]
** PLOT STRIPPER PIT CROSS SECTION **

USR = ABC

MAP = 0 4000 500 3000 6000 500

END BORDR 1 0 4000 3000 6000 0
TICKS 10 3000 4000 3000 500 .1
TICKS 14000 3000 4000 6000 100 .1
TICKS 14000 6000 0 6000 500 .1
TICKS 10 6000 0 3000 100 .1
LABEL 1 50 4510 0 .08 10 /4500 ELEV
LINE 1 0 4500 4000 4500 0
LABEL 1 2010 5990 -90 .08 10 /12500 EAST
LINE 1 2000 6000 2000 3000 0
USERF [Link]
ENDOC

Revised: 10-September-96 Page 658-11

 MineSight®
M6582V2 —PLOT PIT CROSS-SECTION FROM VBM Proprietary Software: Mintec, inc.

HOW TO DEBUG AN M658V2 RUN

1. **** ERROR —- NO FEATURE xxx
will appear if you specify a feature code that is not in the VBM.

2. When plotting the section with M122, remember that the cross-section data is relative to an origin of 0.0, not the VBM or model
origin. If overlaying this data on top of other cross-section data, you may have to shift the origin in M122 with the SHIFT
command. See the sample M122V1 file.

3. Check the MineSight® error messages in the Appendix.

Page 658-12 Revised: 10-September-96

MineSight®
Proprietary Software: Mintec, inc. M658V3 - EXTRACT FEATURES FROM VBM

M658V3 EXTRACT FEATURES FROM

A PLAN/SECTION VBM

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M658V3 extracts points for specified features from a plan/section The features on the structure plan/section can be digitized at any
VBM along specified section/elevation lines. spacing and M658V3 will pick up all the intersection points.

The output from M658V3 is an intermediate file that requires

two steps before it can be loaded into another VBM file (either
PROGRAM FLOW DIAGRAM plan or section).

• the data must be sorted using LSORT

RUN FILE:

- Plane number • the data must be reformatted with M658V4

- Feature code
Output Format

The output from M658V3 is:

Plan to N/S sect – Feature code Easting Northing Elev.

Plan to W/E sect – Feature code Northing Easting Elev.
Plan to non-ortho sections -
INPUT: CALCS: Feature code Plane# X-Dist Elev.
- PCF - Extract feature points from
N/S sect to plan – Feature code Elev. Northing Easting
- File 25 File 25 W/E sect to plan – Feature code Elev. Easting Northing

Sorting for M658V4

The sorting must be done as follows:

Plan to N/S sec t– Easting Feature code Northing

Plan to W/E sect – Northing Feature code Easting
OUTPUT: Plan to non-ortho sections –
Plane# Feature code X-Dist
- ASCII output file of VBM
features
N/S sect to plan – Elev. Feature code Northing
- Printer Output File W/E sect to plan – Elev. Feature code Northing

Sample LSORT commands are included in the sample file

section of this documentation.

Revised: 13-February-12 Page 658-13

 MineSight®
M658V3 - EXTRACT FEATURES FROM VBM Proprietary Software: Mintec, inc.

Page 658-14 Revised: 13-February-12

MineSight®
Proprietary Software: Mintec, inc. M658V3 - EXTRACT FEATURES FROM VBM

M658V3 EXTRACT FEATURES FROM VBM

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-658V3 10=filename 25=filename 19=filename;

MEDS-658V3 3=filename
where

MEDS-658V3 (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
25= the name of the VBM FILE
19= the name of the ASCII Output File
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = START PLANE NUMBER (Elevation/Section; for integer planes only)

IOP2 = END PLANE NUMBER (Elevation/Section)
NOTE: IOP1-2 are for integer plane numbers only. Use PAR1-2 are for any plane numbers.

IOP3 = MINIMUM FEATURE CODE

IOP4 = MAXIMUM FEATURE CODE

IOP5 = START SECTION/ELEVATION NUMBER (i.e., slices to be taken)

IOP6 = END SECTION/ELEVATION NUMBER

IOP7 = SPACING BETWEEN SECTIONS/ELEVATIONS

IOP8 = MINIMUM EASTING (FOR E-W SECTIONS)

= MINIMUM NORTHING (FOR N-S SECTIONS)
IOP9 = MAXIMUM EASTING (FOR E-W SECTIONS)
= MAXIMUM NORTHING (FOR N-S SECTIONS)

IOP10 = 0 PLAN TO SECTION

= 1 SECTION TO PLAN

IOP11 = 0 W/E SECTION

= 1 N/S SECTION
= 2 NON-ORTHOGONAL SECTIONS (Read after END statement)

IOP12 = 0 FULL CODE SELECTION

= 1 LLL CODE SELECTION
= 2 RRR CODE SELECTION

Revised: 13-February-12 Page 658-15

 MineSight®
M658V3 - EXTRACT FEATURES FROM VBM Proprietary Software: Mintec, inc.

PAR1 = START PLANE NUMBER

PAR2 = END PLANE NUMBER

END
PLANE # AND SECTION ORIENTATION LINES (IF IOP11 = 2)
ONE SET PER LINE.

PLANE # X1 Y1 X2 Y2 (i.e., start and end points)

SAMPLE LSORT COMMANDS

To sort plan to section and N/S section to plan, use this command:

LSORT –H S C C infile outfile V 11 10 N A 1 10 N A 21 12 N A 0

To sort W/E section to plan, use this command:

LSORT –H S C C infile outfile V 11 10 N A 1 10 N A 33 12 N A 0

M658V3 SAMPLE RUN FILE #1

MEDS-658V3 10=[Link] 25=[Link] 3=[Link];
MEDS-658V3 19=[Link]
** EXTRACT SECTION DATA FROM PLAN VBM FOR TOPO

USR = ABC

IOP3 = 901 901 / MIN, MAX FEATURE CODES

IOP5 = 12200 12500 50 / START, END SECTION & INCR
IOP8 = 10000 15000 / START, END EASTING
IOP10 = 0 / 0=PLAN TO SECTION, 1=SECTION TO PLAN
IOP11 = 0 / 0=E-W SECTION, 1=N-S SECTION
IOP12 = 2 / 0=FULL CODE SELECTION, 1=LLL, 2=RRR

PAR1 = 2600 4600 / START, END PLANE

END

HOW TO DEBUG AN M658V3 RUN

1. Check the MineSight® error messages in the Appendix.

Page 658-16 Revised: 13-February-12

MineSight®
Proprietary Software: Mintec, inc. M658V4—REFORMAT M658V3 POINTS

M658V4 REFORMAT M658V3 POINTS

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M658V4 takes a sorted version of an M658V3 output file and This program allows for feature segment length checks and
converts it into standard format for loading to a plan or section maximum elevation change checks. It breaks features every user-
VBM. -specified distance. For example, if the distance between two
continuous points is greater than the specified maximum, two
PROGRAM FLOW DIAGRAM features are created, or if the elevation change between two
continuous points is greater than the specified maximum, two
features are created.

RUN FILE:
- Feature splitting
specifications

INPUT: CALCS:

- PCF - Reformat extracted points

- Sorted M658V3 for addition to a sectional
output file VBM

OUTPUT:
- ASCII output file in VBM
format
- Printer Output File

Revised: 30-September-92 Page 658-17

 MineSight®
M658V4—REFORMAT M658V3 POINTS Proprietary Software: Mintec, inc.

Page 658-18 Revised: 30-September-92

MineSight®
Proprietary Software: Mintec, inc. M658V4—REFORMAT M658V3 POINTS

M658V4 REFORMAT M658V3 POINTS

RUN FILE OPERATION
1. NAMES LINE (must be the first line entered)

MEDS--658V4 10=filename 19=filename 30=filename;

MEDS--658V4 3=filename
where

MEDS--658V4 (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
19= the name of ASCII Input File (Output from M658V3)
30= the name of the ASCII Output File (VBM format)
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free--field format)

USR = USER INITIALS (e.g. ABC)

PAR1 = MAXIMUM SEGMENT LENGTH BEFORE SPLITTING FEATURE

(DEFAULT=999999)

NOTE: If the X difference for consecutive points is greater than PAR1, then the feature is split into two
parts.

PAR2 = MAXIMUM ELEVATION INCREASE BEFORE SPLITTING FEATURE

(DEFAULT=999999)

NOTE: If the Z increase for consecutive points is greater than PAR2, then the feature is split into two
parts.

PAR3 = MAXIMUM ELEVATION DECREASE BEFORE SPLITTING FEATURE

(DEFAULT=999999)

NOTE: If the Z difference for consecutive points is less than PAR3, then the feature is split into two
parts.

END

Revised: 31-May-91 Page 658-21

 MineSight®
M658V4—REFORMAT M658V3 POINTS Proprietary Software: Mintec, inc.

Page 658-22 Revised: 31-May-91

MineSight®
Proprietary Software: Mintec, inc. M658V5—SLICE FEATURES FROM SECTION VBM

M658V5 SLICE FEATURES FROM SECTION VBM FOR

PLOTTING OR POSTING

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M658V5 is used to slice intersection points from a section VBM In M658V5, the features to slice can be selected based upon a
for posting to plan for plotting and/or contouring. The output range of feature codes or on individual feature codes. The
file is in M122 (USERF), survey, or 3--D format. intersection/slice points are generated by slicing vertical lines
from the top to bottom of the section at a user specified x distance
PROGRAM FLOW DIAGRAM apart. The intersection points can be either the highest or lowest
intersection. This enables M658V5 to post the top or bottom of
a closed feature (e.g., for seam hangingwall or footwall postings
for contouring).

M658V5 can also be used to post inflection and end points. An

inflection point is defined as a point that has a postive slope on
one side and a negative on the other. In certain cases, such as
RUN FILE: dragline range diagram posting, points that have a sharp angle
change but are not true inflection points may also be required
- Features to slice/post (e.g., the crest of a cut may have a very small down slope on
- Slicing/posting
parameters
one side and a steep down slope on the other). PAR12 can be
used to specify the maximum angle change on the other side of
a point before it is treated like a true inflection point.

The sections to slice can be at any orientation. If using E--W or

N--S sections, the sections can be specified using PAR8--10. If
using non--orthogonal sections, then the section plane number,
INPUT: CALCS: x--origin, y--origin, azimuth, and length must be specified after
the END statement, one section per line.
- PCF - Determine the
- VBM intersection/slice points
-Determine endpoints
and/or inflections points

OUTPUT:
- ASCII file in M122,
survey, or 3-D format (for
plotting or contouring)
- Printer Output File

Revised: 30-September-92 Page 658-23

 MineSight®
M658V5—SLICE FEATURES FROM SECTION VBM Proprietary Software: Mintec, inc.

Page 658-24 Revised: 30-September-92

MineSight®
Proprietary Software: Mintec, inc. M658V5-SLICE FEATURES FROM SECTION VBM

M658V5 SLICE FEATURES FROM SECTION VBM

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-658V5 10=filename 25=filename 19=filename;

MEDS-658V5 3=filename
where

MEDS-658V5 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM GEOMETRY FILE
19 = the name of the ASCII Output File
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP2 = 0 READ FEATURES AS A LIST AFTER END STATEMENT

= 1 READ FEATURES AS A RANGE FROM IOP3-IOP4

IOP3 = MINIMUM FEATURE CODE (if IOP2=1)

IOP4 = MAXIMUM FEATURE CODE (if IOP2=1)

IOP5 = 0 READ SECTION AND ORIENTATION INFO AFTER END STATEMENT

= 1 FOR W/E SECTION (use PAR8-10)
= 2 FOR N/S SECTION (use PAR8-10)

IOP6 = 0 FOR FULL CODE SELECTION

= 1 FOR LLL CODE SELECTION
= 2 FOR RRR CODE SELECTION

IOP7 = 0 OUTPUT FILE IN X,Y,Z, FEATURE CODE FORMAT

= 1 OUTPUT FILE IN SURVEY FORMAT (left side of feature code as point code)
= 2 OUTPUT FILE IN SURVEY FORMAT (right side of feature code as point code)
= 3 OUTPUT USERF OF POSTED POINTS

IOP8 = 0 DON’T OUTPUT INFLECTION POINTS OR ENDPOINTS

= 1 OUTPUT ENDPOINTS
= 2 OUTPUT INFLECTION POINTS
= 3 OUTPUT BOTH ENDPOINTS AND INFLECTION POINTS

NOTE: IOP8 endpoints are for open features only.

Revised: 05-January-00 Page 658-25

 MineSight®
M658V5-SLICE FEATURES FROM SECTION VBM Proprietary Software: Mintec, inc.

IOP9 = 0 OUTPUT LOWEST INTERSECTION POINT (i.e., footwall/bottom of feature)

= 1 OUTPUT HIGHEST INTERSECTION POINT (i.e., hangingwall/top of feature)
= 2 DON’T OUTPUT EITHER

IOP10 = PLOT SYMBOL NUMBER FOR POSTED POINTS (default=3)

IOP11 = PLOT SYMBOL NUMBER FOR INFLECTION POINTS (default=4)

IOP12 = PEN# FOR POSTED POINTS (default=1)

IOP13 = PEN# FOR INFLECTION POINTS (default=1)

PAR1 = MIN VBM X COORDINATE FOR PLOT/SELECTION (default=VBM limits)

PAR2 = MAX VBM X COORDINATE FOR PLOT/SELECTION (default=VBM limits)
PAR3 = MIN VBM Y COORDINATE FOR PLOT/SELECTION (default=VBM limits)
PAR4 = MAX VBM Y COORDINATE FOR PLOT/SELECTION (default=VBM limits)

NOTE: X is distance along section and Y is elevation.

PAR6 = ANNOTATION SIZE IN PLOTTER UNITS (default = 0.07)

PAR7 = SPACING BETWEEN VERTICAL SLICING LINES (default=10)

PAR8 = START PLANE # FOR E-W OR N-S SECTION

PAR9 = END PLANE # FOR E-W OR N-S SECTION
PAR10 = SPACING FOR E-W OR N-S SECTION

PAR12 = MAXIMUM ANGLE FOR POSTING “INFLECTION” POINTS (default=30)

NOTE: Points such as the crest of a DL cut may not be true inflection points but are useful for posting.

PAR13 = ANNOTATION ANGLE (default = 0)

END

4. SEAM CODE LINES (if IOP2=0)

List the allowable seam codes - Max 100, 1 per line; last code = –1

5. SECTION AND ORIENTATION LINES (if IOP5=0)

section vbm id, xorigin, yorigin, azim, distance

Page 658-26 Revised: 05-January-00

MineSight®
Proprietary Software: Mintec, inc. M658V5-SLICE FEATURES FROM SECTION VBM

M658V5 SAMPLE RUN FILE #1

MEDS-658V5 10=[Link] 25=[Link] 3=[Link] 19=[Link]
** EXTRACT VBM SECTION GEOLOGY FOR CONTOURING **

USR = ABC
IOP2 = 1 /0=READ FEATURES AFTER END, 1=USE IOP3-IOP4
IOP3 = 10 99 /MIN & MAX FEATURE CODE

IOP5 = 1 /0=READ SECTS AFTER END, 1=E-W, 2=N-S (see PAR8-10)

IOP6 = 0 /0=FULL CODE SELECTION, 1=LEFT SIDE, 2=RIGHT SIDE

IOP7 = 0 /0=OUTPUT 3-D FILE, 1=SURVEY WITH LEFT SIDE, 2=SURVEY, RIGHT
COM SIDE, 3=USERF OF POSTED POINTS
IOP8 = 0 /0=DON’T OUTPUT INFLECTION POINTS OR ENDPOINTS, 1=OUTPUT ENDPTS,
COM 2=INFLECTION PTS, 3=BOTH
IOP9 = 1 /0=OUTPUT LOWEST INTERSECTION(i.e., footwall), 1=HIGHEST,
COM 2=DON’T OUTPUT EITHER

IOP10 = 3 /PLOT SYMBOL NUMBER FOR POSTED POINTS (default=3)

IOP11 = 4 /PLOT SYMBOL NUMBER FOR INFLECTION POINTS (default=4)

IOP12 = 2 /PEN# FOR POST POINTS

IOP13 = 3 /PEN# FOR INFLECTION/END POINTS

PAR7 = 10 /SPACING BETWEEN VERTICAL SLICING LINES (default=10)

PAR8 = 36400 36600 /START,END, AND SPACING FOR E-W OR N-S SECTIONS

END

Revised: 05-January-00 Page 658-27

 MineSight®
M658V5-SLICE FEATURES FROM SECTION VBM Proprietary Software: Mintec, inc.

M658V5 SAMPLE RUN FILE #2

MEDS-658V5 10=[Link] 25=[Link] 3=RPT658.V5 19=[Link]
** EXTRACT RANGE DIAGRAM CUT 1 FOR POSTING **

USR = ABC

IOP2 = 1 /0=READ FEATURES AFTER END, 1=USE IOP3-IOP4

IOP3 = 1991 1991 /MIN & MAX FEATURE CODE

IOP5 = 0 /0=READ SECTS AFTER END, 1=E-W, 2=N-S (see PAR8-10)

IOP6 = 0 /0=FULL CODE SELECTION, 1=LEFT SIDE, 2=RIGHT SIDE

IOP7 = 3 /0=OUTPUT 3-D FILE, 1=SURVEY WITH LEFT SIDE, 2=SURVEY, RIGHT
COM SIDE, 3=USERF OF POSTED POINTS
IOP8 = 3 /0=DON’T OUTPUT INFLECTION POINTS OR ENDPOINTS, 1=OUTPUT ENDPTS,
COM 2=INFLECTION PTS ,3=BOTH
IOP9 = 2 /0=OUTPUT LOWEST INTERSECTION(i.e., footwall), 1=HIGHEST,
COM 2=DON’T OUTPUT EITHER

IOP10 = 3 /PLOT SYMBOL NUMBER FOR POSTED POINTS (default=3)

IOP11 = 4 /PLOT SYMBOL NUMBER FOR INFLECTION POINTS (default=4)

IOP12 = 2 /PEN# FOR POST POINTS

IOP13 = 3 /PEN# FOR INFLECTION/END POINTS

PAR7 = 500 /SPACING BETWEEN VERTICAL SLICING LINES (default=10)

PAR12 = 30 /ANGLE BETWEEN SEGMENTS FOR POSTING

END
10 3000.0 10000.0 90 20000
12 3000.0 12000.0 90 20000
14 3000.0 14000.0 90 20000

M658V5 SAMPLE RUN FILE #3

MEDS - 658V5 10=[Link] 25=[Link] 3=[Link] 19=[Link]
**EXTRACT VBM SECTION IN SURVEY FILE FORMAT**

USR = ABC

I-O=0

IOP2 = 1 /0=READ FEATURES AFTER END, 1=USE IOP3 - IOP4

IOP3 = 2991 2991 /MIN & MAX FEATURE CODE

IOP5 = 1 /0=READ SECTS AFTER END, 1=E-W, 2=N-S (see PAR8 - 10)
IOP6 = 0 /0=FULL CODE SELECTION, 1=LEFT SIDE, 2=RIGHT SIDE

IOP7 = 2. /0=OUTPUT 3D FILE, 1=SURVEY WITH LEFT SIDE, 2=SURVEY, RIGHT

COM SIDE, 3=USERF OF POSTED POINTS
IOP8 = 3 /0=DON’T OUTPUT INFLECTION POINTS OR ENDPOINTS, 1=OUTPUT ENDPTS,
2=INFLECTION PTS, 3=BOTH, WITH BREAK CODES.

Page 658-28 Revised: 05-January-00

MineSight®
Proprietary Software: Mintec, inc. M658V5-SLICE FEATURES FROM SECTION VBM

IOP9 = 2 /0=OUTPUT LOWEST INTERSECTION (IE: Footwall), 1=HIGHEST,

2=DON’T OUTPUT EITHER

IOP10 = 3 /PLOT SYMBOL NUMBER FOR POSTED POINTS (Default=3)

IOP11 = 4 /PLOT SYMBOL NUMBER FOR INFLECTION POINTS (Default=4)

IOP12 = 2 /PEN# FOR POST POINTS

IOP13 = 2 /PEN# FOR INFLECTION/END POINTS

PAR7 = 10. /SPACING BETWEEN VERTICAL SLICING LINES (DEFAULT=10)

PAR8 = 1700. 3200. 25. /START, END, AND SPACING FOR EW, NS

END

M658V5 SAMPLE RUN FILE #3 (attached)

HOW TO DEBUG AN M658V5 RUN

1. ERROR IN SECTION XXX

The run file contains a section that does not exist.

2. Check the MineSight® error messages in the Appendix.

Revised: 05-January-00 Page 658-29

 MineSight®
M658V5-SLICE FEATURES FROM SECTION VBM Proprietary Software: Mintec, inc.

Page 658-30 Revised: 05-January-00

MineSight®
Proprietary Software: Mintec, inc. M659V1—COMPUTE BLOCK PARTIALS FROM VBM FEATURES

M659V1 COMPUTE BLOCK PARTIALS

FROM VBM FEATURES

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M659V1 takes a feature from the VBM file and determine the This routine is used to calculate the percentage (partial) of a
percentage of each mine model block that is within the feature. mine model block that is within a VBM feature. The results are
This is a necessary step for generating reserves within a pit written to an ASCII partials file that is input into the reserves
design. routines.

The program can calculate partials for a single pit, the difference
PROGRAM FLOW SUMMARY between two pits, and the partials due to topography.

To calculate partials for a VBM feature and include topography,

the VBM feature must be closed. The topography option is not
generally required as topography is normally accounted for in
the reserves routine. Also, the topography option takes more
RUN FILE: CPU time to calculate.
- Plane numbers
- Pit & topo feature codes For a 3--D Block Model, the VBM plane numbers are normally
- Partials option matched against the PCF bench numbers to determine IZ, the
bench number that is written to the partials file. For a GSM
model, the VBM plane numbers are checked against the seam
numbers in the PCF. Optionally, for a GSM model, the VBM
plane number can be written to the partials file as IZ.

There is an option to compute partials from unclosed features.

INPUT: CALCS: However, the bottom bench must be closed and the features
- Calculate percentage of
calculated from the bottom up.
- PCF
- File 25 blocks that are within
VBM features

- Output a file of paritals

OUTPUT:
- ASCII file of partials
- Printer Output File

Revised: 30-September-93 Page 659-1

 MineSight®
M659V1—COMPUTE BLOCK PARTIALS FROM VBM FEATURES Proprietary Software: Mintec, inc.

Page 659-2 Revised: 30-September-93

MineSight® is a registered
trademark of Leica Geosystems AG. M659V1-COMPUTE BLOCK PARTIALS FROM VBM FEATURE

M659V1 COMPUTE BLOCK PARTIALS FROM VBM FEATURES

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS—659V1 10=filename 3=filename

where

MEDS-659V1 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
3 = the name of the PRINTER OUTPUT FILE

NOTE: The VBM and partials files are listed after the END line.

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free—field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = # OF INCREMENTS (PASSES) PER ROW FOR CALCULATION OF PARTIALS(DEFAULT=4)

IOP2 = FIRST ROW FOR PARTIALS (DEFAULT=1) IOP3=LAST ROW FOR PARTIALS (DEFAULT=NY)
IOP4 = 0 COMPUTES PARTIALS FROM CLOSED OUTLINES
= 1 COMPUTES PARTIALS FROM UNCLOSED OUTLINES
IOP5 = 0 FOR 3—D MODEL: MATCH VBM PLANE NUMBERS AGAINST THE PCF BENCH NUMBERS.
FOR GSM MODEL: MATCH AGAINST PCF SEAM NUMBERS
= 1 FOR GSM: USE VBM PLANE NUMBER AS IZ IN PARTIALS FILE

IOP6 = 0 USE TOPO ON SAME PLANE AS PIT=1USE TOPO AT BENCH MEDIAN

IOP7 = FIRST COLUMN FOR OUTPUT OF PARTIALS
IOP8 = LAST COLUMN FOR OUTPUT OF PARTIALS
IOP10 = NUMBER OF DECIMALS FOR PCT IN THE PARTIALS OUTPUT FILE (DEFAULT=0).
IOP11 = BENCH NUMBER FOR DEBUG
IOP12 = FIRST ROW FOR DEBUG (IF IOP11>0)
IOP13 = LAST ROW FOR DEBUG (IF IOP11>0)

IOP14 = 0 PLANES ENTERED AS VBM PLANE NUMBERS (DEFAULT)

= 1 PLANES ENTEREDAS MODEL BENCH ELEVATIONS

NOTE: IOP14 used for rotated models ONLY.

IOP21 = DEBUG — LIST INTERSECTIONS FROM PARTIALS CALCULATION

PAR1 = MINIMUM X—COORDINATE (DEFAULT = XMIN IN PCF)

PAR2 = MAXIMUM X—COORDINATE (DEFAULT = XMAX IN PCF)

END

Revised: 16-February-2017 Page 659-3

 MineSight® is a registered
M659V1-COMPUTE BLOCK PARTIALS FROM VBM FEATURE trademark of Leica Geosystems AG

4. PARTIAL SPECIFICATION LINES

filename output plane1 plane2 inc lab1 lab2 ltop

where

filename = VBM filename

output = Partials filename
plane1 = First plane to access
plane2 = Last plane to access
inc = Increment between planes
lab1 = Feature code # of larger pit
lab2 = Feature code # of smaller pit
ltop = Feature code # of topography

NOTE: Set lab2=0 if difference in partials is not required. Set ltop=0 if no topo is to be used. Set lab1=0
if partials for topo only required.

Page 659-4 Revised: 16-February-2017

MineSight® is a registered
trademark of Leica Geosystems AG. M659V1-COMPUTE BLOCK PARTIALS FROM VBM FEATURE

The following is the partials file for the feature trace and model blocks as shown in the image above. The partials file only lists those
blocks that are partially within the feature (polygon, solid). Those blocks that are completely contained within the feature (100%)
are not listed in the partials file.

BEN ROW COL PCT COL PCT BEN ELEV. VBM CODE
12 0 0 0 0 0 12 2300.0 804 - Header Line
12 1 1 1 2 30 12 2300.0 804 - Partials Lines
12 1 3 42 4 46 12 2300.0 804 :
12 1 5 46 6 31 12 2300.0 804 :
12 1 7 4 0 0 12 2300.0 804 :
12 2 1 35 7 28 12 2300.0 804 :
12 3 1 47 7 36 12 2300.0 804 :
12 4 1 51 7 38 12 2300.0 804 :
12 5 1 52 7 32 12 2300.0 804 :
12 6 1 36 7 22 12 2300.0 804 :
12 7 1 1 2 32 12 2300.0 804 :
12 7 3 36 4 27 12 2300.0 804 :
12 7 5 38 6 30 12 2300.0 804 :
12 7 7 1 0 0 12 2300.0 804 :
-1 0 0 0 0 0 12 2300.0 804 - Footer Line

M659V1 SAMPLE RUN FILE #1

MEDS—659V1 10=[Link] 3=[Link]
** COMPUTE PARTIALS FOR PIT 804 STORED IN VBM **

USR = ABC

IOP1 = 4 / # OF INCREMENTS PER ROW

IOP2 = 1 50 / 1ST AND LAST ROW

PAR1 = 10000 15000 / XMIN AND XMAX

COM NOTE THAT IOP2, IOP3, PAR1 AND PAR2 DEFAULT TO PCF VALUES
COM LAST LINE IS VBM FILE,PART. FILE,1ST BENCH,LAST BENCH,INC.
COM LARGER PIT CODE,SMALLER PIT CODE,TOPO CODE
END
[Link] [Link] 3500 4550 50 804 0 901

M659V1 SAMPLE RUN FILE #2

MEDS—659V1 10=[Link] 3=[Link]
** TEST PARTIALS FOR GSM **

USR = ABC

IOP1 = 4 / # OF INCREMENTS PER ROW IOP2=1 50 / 1ST AND LAST ROW

IOP4 = 0 / 0=CLOSED FEATURES, 1=UNCLOSED FEATURES
IOP5 = 1 / PCF MATCHING, 1=USE PLANE # AS IZ FOR GSM
PAR1 = 2000 32000 / XMIN AND XMAX
COM NOTE THAT IOP2, IOP3, PAR1 AND PAR2, DEFAULT TO PCF VALUES
COM LAST LINE IS VBM FILE,PART. FILE,1ST BENCH,LAST BENCH,INC.
COM LARGER PIT CODE,SMALLER PIT CODE,TOPO CODE
END
[Link] [Link] 101 104 1 777 0 0

Revised: 16-February-2017 Page 659-5

 MineSight® is a registered
M659V1-COMPUTE BLOCK PARTIALS FROM VBM FEATURE trademark of Leica Geosystems AG

HOW TO DEBUG AN M659V1 RUN

1. PLANE NOT IN VBM

will appear if you specify a plane number that is not in the VBM.

2. BENCH xxx OUTSIDE PCF RANGE OF ELEVATIONS

will occur if the VBM plane number is outside the elevation of the model.

3. SEAM xxx OUTSIDE PCF RANGE OF ELEVATIONS

will occur if the VBM plane number is outside the range of seam numbers in the PCF.

4. PIT NOT FOUND = xxx ON PLANE xxx

will occur if the specified pit feature code is not on a particular plane in the VBM.

5. TOPO NOT FOUND = xxx ON PLANE xxx

will occur if the topo feature code is not on a particular plane in the VBM.

6. Check the MineSight® error messages in the Appendix.

Page 659-6 Revised: 16-February-2017

MineSight®/
Proprietary Software: Mintec, inc. M659V2 CALCULATE WASTE DUMP VOLUMES FROM VBM DATA

M659V2 CALCULATE WASTE DUMP VOLUMES FROM

VBM DATA

REQUIREMENTS AND CONSIDERATIONS

PROGRAM SUMMARY
M659V2 is used to calculate the area, volume and tonnage of a
M659V2 uses topography and dump outlines stored in the VBM dump that is stored in the VBM. The procedure to run M659V2
file to compute dump area, volume and tonnage. is:

1. Draw and digitize the dump contours on the existing topo

map such that each dump contour overlaps the topo contour
PROGRAM FLOW DIAGRAM by exactly one point at the beginning and ending of the dump
contour.

2. Load the dump contours to the VBM, plot them out and
RUN FILE: correct as necessary.
- Plane numbers
- Feature codes
3. Combine the dump contours with the existing topo contours
- Weight conversion factor to create a new feature (M651V4).

4. Run M659V2 to compute area, volume and tonnage of the

dump.

The program computes the dump volume by calculating the

difference between the new feature and the existing topography.
INPUT: CALCS:
A weight conversion factor (tonnage factor for Imperial and
- PCF - Calculate the partials specific gravity for metric) is entered so that the tonnage of the
- File 25 between topo and dump
surface
dump can be calculated.
-Calculate the area, volume
and tonnage of the dump
- Output a file of paritals

OUTPUT:
- ASCII file of partials
- Printer Output File

Revised: 1-August-94 Page 659-7

 MineSight®/
M659V2 CALCULATE WASTE DUMP VOLUMES FROM VBM DATA Proprietary Software: Mintec, inc.

Page 659-8 Revised: 1-August-94

MineSight®
Proprietary Software: Mintec, inc. M659V2-CALCULATE WASTE DUMP VOLUMES FROM VBM

M659V2 CALCULATE WASTE DUMP VOLUMES FROM VBM DATA

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS—659V2 10=filename 3=filename

where

MEDS—659V2 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
3 = the name of the PRINTER OUTPUT FILE

NOTE: The VBM and partials files are listed after the END line.

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free—field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = # OF INCREMENTS (PASSES) PER ROW FOR CALCULATIONS(DEFAULT=4)

IOP2 = FIRST ROW TO USE FOR CALCULATIONS

IOP3 = LAST ROW TO USE FOR CALCULATIONS

IOP4 = 0 USE PLANE# AS DUMP LIFT HEIGHT

= 1 USE DEFAULT LIFT HEIGHT (PAR8) FOR VOLUME CALCULATIONS

IOP5 = 0 PLANE ENTERED AS VBM PLANE NUMBERS (DEFAULT)

= 1 PLANE ENTERED AS MODEL BENCH ELEVATIONS

NOTE: IOP5 used for rotated models ONLY.

IOP21 = DEBUG — LIST INTERSECTIONS

PAR1 = MINIMUM X COORDINATE (DEFAULT=XMIN IN PCF)

PAR2 = MAXIMUM X COORDINATE (DEFAULT=XMAX IN PCF)
PAR3 = COLUMN BLOCK SIZE (DX)
PAR4 = MINIMUM Y COORDINATE (DEFAULT=YMIN IN PCF)
PAR5 = MAXIMUM Y COORDINATE (DEFAULT=YMAX IN PCF)
PAR6 = ROW BLOCK SIZE (DY)
PAR7 = WEIGHT CONVERSION FACTOR

NOTE: Tonnage factor for Imperial units or specific gravity for metric units.

PAR8 = DEFAULT DUMP LIFT HEIGHT FOR VOLUME CALCULATIONS (DEFAULT=PCF BENCH HEIGHT)

END

Revised: 22-May-01 Page 659-9

 MineSight®
M659V2-CALCULATE WASTE DUMP VOLUMES FROM VBM Proprietary Software: Mintec, inc.

4. PARTIAL SPECIFICATION LINES

filename output plane1 plane2 inc lab1 lab2

where

filename= VBM filename

output = Partials output filename
plane1 = First plane to access
plane2 = Last plane to access
inc = Increment between planes (a negative increment is allowed)
lab1 = Feature code # of topo
lab2 = Feature code # of dump

M659V2 SAMPLE RUN FILE #1

MEDS—659V2 10=[Link] 3=[Link]
** COMPUTE DUMP VOLUMES **

USR = ABC
IOP2 = 01 40 / IY1, IY2

PAR1 = 7000 10000 100 / XMIN, XMAX, DX

PAR4 = 13000 17000 100 / YMIN, YMAX, DY

PAR7 = 12.5 / TONNAGE FACTOR

END
[Link] DAT659.0A 4270 4450 10 901 751

HOW TO DEBUG AN M659V2 RUN

1. PLANE NOT FOUND

will appear if you specify a plane that is not in the VBM.

2. %M659V2: WARNING. CODE XXX on plane XXX was not found.

will appear if a specified feature code (either topo or dump) is not found on a plane.

3. When splicing the dump with the topography (M651V4), make sure that the first and second point of the dump cuts the
topography and that the last and the last—1 point also cuts the topography.

4. Check the MineSight® error messages in the Appendix.

Page 659-10 Revised: 22-May-01

MineSight®
Proprietary Software: Mintec, inc. M661V1—INTERPOLATE INTERMEDIATE VBM PLANES

M661V1 - INTERPOLATE INTERMEDIATE VBM PLANES

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M661V1 is used to interpolate a linear feature onto a plane that
M661V1 will interpolate linear features into a new VBM plane is in between two other planes. The routine will not work for
between existing VBM planes. closed features unless they have a starting point that is coincident.
Also, the program will not handle multiple features with the
same left and right side codes (multiple sequence numbers).
The program works best for interpolating linear geological
PROGRAM FLOW DIAGRAM features on cross--section (i.e., digitized coal seams).

The program divides the features into equal lengths based on a

specified spacing between points and a maximum number of
points for the new feature.

RUN FILE: The new feature is calculated as a weighted function of the

features on either side. The weights are specified on the Feature
- Plane numbers
- Feature codes Specification Line. For a new plane that is halfway between
two planes, the weights are usually 0.5 and 0.5.

The features should be digitized in the same direction.

INPUT: CALCS:

- PCF - Interpolate a new feature

- File 25 onto a plane between
existig VBM planes

OUTPUT:
- Updated File 25
- Printer Output File

Revised: 31-May-91 Page 661-1

 MineSight®
M661V1—INTERPOLATE INTERMEDIATE VBM PLANES Proprietary Software: Mintec, inc.

Page 661-2 Revised: 31-May-91

MineSight®
Proprietary Software: Mintec, inc. M661V1—INTERPOLATE INTERMEDIATE VBM PLANES

M661V1—INTERPOLATE INTERMEDIATE VBM PLANES

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-661V1 10=filename 25=filename 3=filename

where

MEDS-661V1 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
3 = the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP20 = 1 DEBUG OPTION

END

4. FEATURE AND PLANE SPECIFICATION LINES

Left and right feature codes

0 0
plane1 plane2 planen npmax sizp wt1 wt2
0 0
where

plane1 = First plane

plane2 = Second plane
planen = New plane
npmax = Max number of points for new feature (must be ≤ 100,000)
sizp = Spacing between points for new feature
wt1 = Weight of first plane
wt2 = Weight of second plane

NOTE: 0 0 ends the input for feature code combinations and for plane specifications. –1 is wildcard
value. WT1 + WT2 must equal 1.00. SIZP is used to determine number of points required for new
feature up to NPMAX. There can be at most 1,000 feature code specification lines.

Revised: 22-September-98 Page 661-3

 MineSight®
M661V1—INTERPOLATE INTERMEDIATE VBM PLANES Proprietary Software: Mintec, inc.

M661V1 SAMPLE RUN FILE #1

MEDS-661V1 10=[Link] 25=[Link] 3=[Link]
** INTERPOLATE INTERMEDIATE VBM PLANES **

USR = ABC

END
333 444 Feature codes
0 0 End of input
12750 13250 13000 100 1 .5 .5 Plane specifications
0 0 End of input

HOW TO DEBUG AN M661V1 RUN

1. ERROR READING PLANE

will occur if there is no data in the VBM or if a plane that was specified does not exist.

2. Check the new feature by plotting it out. If the feature does not look reasonable, check that the original features are
digitized in the same direction.

3. Check the MineSight® error messages in the Appendix.

Page 661-4 Revised: 22-September-98

MineSight®
Proprietary Software: Mintec, inc. M662V1 - TRUNCATE MINING CUTS STORED IN VBM

M662V1 - TRUNCATE MINING CUTS STORED IN THE VBM

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M662V1 is used to exclude or include areas from mining cuts. M662V1 is used to truncate mining cuts by a feature stored in
The cuts to be truncated must be in separate planes in the VBM the VBM. The mining cuts must be closed features with points
file. oriented in a clockwise direction. The cuts must be stored on
successive features in the VBM and each cut must be on the
PROGRAM FLOW DIAGRAM same plane. M665V1 will generate mining cuts with these
criteria.

RUN FILE: The cuts may be either included or excluded depending on the
value of IOP4.
- Plane numbers
- Feature codes This truncation boundary must be a closed feature and must be
-
stored in the same VBM as the mining cuts. The truncated cuts
will automatically be written to the VBM (in the same plane as
the untruncated cuts).

To include cuts within a truncation boundary, set IOP4 to 0. To

exclude cuts within a truncation boundary, set IOP4 to 1. The
CALCS: program automatically reverses the direction of the digitized
INPUT:
boudary if it is currently incorrectly oriented. The new
- PCF - Truncate closed VBM orientation is used internally, so that the data on the VBM plane
- File 25 features with a closed is left unchanged. M650ED can also be used to check if an area
VBM boundary feature
has been digitized clockwise or counter-clockwise. A clockwise
boundary will have a positive area when you check a plane index
with M650ED.

OUTPUT:
- Updated PCF
- Printer Output File

Revised: 1-August-94 Page 662-1

 MineSight®
M662V1 - TRUNCATE MINING CUTS STORED IN VBM Proprietary Software: Mintec, inc.

Page 662-2 Revised: 1-August-94

MineSight®
Proprietary Software: Mintec, inc. M662V1—TRUNCATE MINING CUTS STORED IN VBM

M662V1 TRUNCATE MINING CUTS STORED IN THE VBM

RUN FILE OPERATION
1. NAMES LINE (must be the first line entered)

MEDS-662V1 10=filename 3=filename

where

MEDS-662V1 (must be the first line entered)

10= the name of the PROJECT CONTROL FILE
3= the name of the PRINTER OUTPUT FILE

Note: The VBM file is listed after the END line.

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text information that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = 0 DO NOT WRITE TO THE VBM FILE

= 1 WRITE TO THE VBM FILE

IOP2 = FEATURE CODE FOR FIRST TRUNCATED FEATURES (DEFAULT=777)

NOTE: The first truncated feature will be labeled IOP2. The second truncated feature will be labeled
IOP2 +1, etc. (777, 778, 779; if IOP2 default is used)

IOP3 = 0 STORE FEATURES IN THE VBM THAT ARE:

COMPLETELY INSIDE A CLOCKWISE EXCLUSION BOUNDARY
COMPLETELY OUTSIDE A COUNTER-CLOCKWISE BOUNDARY
= 1 DO NOT STORE FEATURES THAT FALL INTO THE ABOVE CATEGORIES

IOP4 = 0 TRUNCATE AREA OUTSIDE THE BOUNDARY

= 1 TRUNCATE AREA INSIDE THE BOUNDARY

IOP5 = OPTIONAL INCREMENT FOR NUMBERING NEW CUTS

END

4. PIT SPECIFICATION LINES

filename plane sectx ucode ncuts xcode

where

filename = Name of File 25

plane = First plane containing the untruncated features
sectx = Plane containing exclusion boundaries
ucode = Feature code of the first untruncated features
ncuts = Number of cuts to truncate
xcode = Feature code of the exclusion boundaries

Revised: 20-September-96 Page 662-3

 MineSight®
M662V1—TRUNCATE MINING CUTS STORED IN VBM Proprietary Software: Mintec, inc.

M662V1 SAMPLE RUN FILE #1

MEDS-662V1 10=[Link] 3=[Link]

* TRUNCATE SAMPLE DRAGLINE CUTS BY MINING AREA 1 BOUNDARY

COM WHERE:
COM [Link] = THE NAME OF THE MEDSYSTEM PROJECT CONTROL FILE
COM [Link] = THE NAME OF THE PRINTER OUTPUT FILE

USR = ABC

IOP2 = 777 / THE FEATURE CODE FOR TRUNCATED CUTS

IOP3 = 1 / DO NOT STORE CUTS WHICH ARE COMPLETELY OUTSIDE OF
COM THE MINING AREA BOUNDARY 1
END
[Link] 101 109 1 100 888 801

M662V1 SAMPLE RUN FILE #2

MEDS-662V1 10=[Link] [Link]
* TRUNCATE SAMPLE DRAGLINE CUTS BY MINING AREA 1 BOUNDARY

COM WHERE:
COM [Link] = THE NAME OF THE MEDSYSTEM PROJECT CONTROL FILE
COM [Link] = THE NAME OF THE PRINTER OUTPUT FILE

USR = ABC
IOP1 = 1 / STORE IN VBM
IOP2 = 555 / THE FEATURE CODE FOR TRUNCATED CUTS
IOP3 = 1 / 1=DO NOT STORE CUTS THAT ARE COMPLETELY OUTSIDE THE BOUNDARY
COM 0=STORE CUTS THAT ARE COMPLETELY OUTSIDE THE BOUNDARY
END
[Link] 100 110 1 99 888 802

HOW TO DEBUG AN M662V1 RUN

1. ERROR RETURN FROM VBMRGM

will occur if there is no data in the VBM or a specified plane number does not exist.

2. M662V1 works by finding the intersections of the exclusion boundary and the untruncated features. Once all of the intersec-
tions of the features are determined, the strings of points between the intersections are combined to form the truncated
features. This process is nearly foolproof, but occasionally certain geometric patterns cause problems with the algorithm. It is
recommended that all truncated features be plotted as a check. If problems exist, they can usually be corrected simply with
program M650ED.

3. Check the MineSight® error messages in the Appendix.

Page 622-4 Revised: 20-September-96

MineSight®
Proprietary Software: Mintec, inc. M663V1 - COMPUTE SEAM LENGTH FOR 3-D BLOCKS

M663V1 COMPUTE SEAM LENGTH FOR 3-D BLOCKS

FROM VBM DATA

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M663V1 computes the length of a VBM feature within each This program is used to calculate the length of up to two seams
block in a 3-D Block Model. at a time that are stored in a cross-sectional VBM. An output
file is produced that contains the feature code (left side code)
PROGRAM FLOW DIAGRAM and its length in a format suitable for input into the model with
M610V1.

The seams should be stored in the VBM such that the left side
code is the seam code and the right side code is a modifier, such
RUN FILE: as a fault block code. The seams should be digitized left to right
in the section and can either be on north-south sections or east-
- Plane numbers west sections. The features cannot be closed.
- Feature codes

Since the maximum length that can be written to the M610 input
file is 999 (3 integers), you may wish to change the precision of
the output. PAR11 can be used to divide the length before the
file is written. A PAR11 of 10 will allow you to write out a
maximum length of 9990.

INPUT: CALCS:

- PCF - Calculate length of up to

- File 25 two seams in a cross-
sectional VBM
- Output a file for M610V1
input

OUTPUT:
- ASCII output file of
lengths
- Printer Output File

Revised: 1-August-94 Page 663-1

 MineSight®
M663V1 - COMPUTE SEAM LENGTH FOR 3-D BLOCKS Proprietary Software: Mintec, inc.

Page 663-2 Revised: 1-August-94

MineSight®
Proprietary Software: Mintec, inc. M663V1—COMPUTE SEAM LENGTH FOR 3-D BLOCKS FROM VBM DATA

M663V1 COMPUTE SEAM LENGTH FOR 3-D BLOCKS FROM VBM DATA
RUN FILE OPERATION
1. NAMES LINE (must be the first line entered)

MEDS-663V1 10=filename 25=filename 19=filename;

MEDS-663V1 3=filename
where

MEDS-663V1 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
19 = the name of the Output File for M610V1
3 = the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = 0 FOR EAST-WEST SECTION

= 2 FOR NORTH-SOUTH SECTION

IOP2 = # OF ROWS (DEFAULT=PCF VALUE)

IOP3 = # OF COLUMNS (DEFAULT=PCF VALUE)

IOP20 = 1 DEBUG OPTION

PAR1 = MINIMUM X COORDINATE

PAR2 = MAXIMUM X COORDINATE
PAR3 = CHANGE IN X COORDINATE
PAR4 = MINIMUM Y COORDINATE
PAR5 = MAXIMUM Y COORDINATE
PAR6 = CHANGE IN Y COORDINATE

NOTE: If precision is 10, then lengths are divided by 10. PAR1-11 default to PCF values.

PAR11 = PRECISION FACTOR (DEFAULT=1)

END

Revised: 1-August-94 Page 663-3

 MineSight®
M663V1—COMPUTE SEAM LENGTH FOR 3-D BLOCKS FROM VBM DATA Proprietary Software: Mintec, inc.

4. FEATURE SPECIFICATION LINES (max=200)

LLL RRR
where

LLL = Left side feature code

RRR = Right side feature code

0 0 ends input. -1 is wildcard value

5. PLANE SPECIFICATION LINES

plane#1 plane#2
where
plane#1 = First plane to list
plane#2 = Last plane to list

M663V1 SAMPLE RUN FILE #1

MEDS-663V1 10=[Link] 25=[Link] 3=[Link];
MEDS-663V1 19=[Link]
COMPUTE SEAM LENGTH FOR 3-D BLOCKS FROM VBM

USR = ABC

IOP1 = 0 / 0 = E-W SECTION, 2 = N-S SECTION

PAR11 = 1 / PRECISION FACTOR
END
1 2 FEATURE SPEC. LINES
2 3
0 0 END FEATURE SPEC LINES
12750 12750 PLANE SPEC LINE

HOW TO DEBUG AN M663V1 RUN

1. If no output file or negative lengths are produced , verify the features are digitized left to right and do not close the feature.

2. If the lengths do not appear correct, check that PAR11 is set correctly.

3. Check the MineSight® error messages in the Appendix.

Page 663-4 Revised: 1-August-94

MineSight®
Proprietary Software: Mintec, inc. M664V1—COMPUTE OUTCROP INTERSECTIONS FOR VBM

M664V1 COMPUTE OUTCROP INTERSECTION FOR

VBM DATA

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M664V1 computes the intersection of two VBM features and M664V1 is used to calculate the intersections between two sets
creates an M122 plot file. of features stored in a VBM. An M122 plot file is produced that
shows the location of the intersection with a symbol and the
PROGRAM FLOW DIAGRAM plane number label. Specify the pen number, symbol type,
annotation size and angle along with the plane numbers and
feature codes to check for intersections.

RUN FILE: A further selection can be performed by specifying a rectangular

search window (PAR3-6). The VBM features do not have to be
- Plane numbers
digitized in the same direction for this routine to work.
- Feature codes
- Pen and symbol number

INPUT: CALCS:

- PCF - Calculate intersection of

- File 25 two VBM features
- Produce M122 plot file

OUTPUT:
- ASCII plot file
- Printer Output File

Revised: 1-August-94 Page 664-1

 MineSight®
M664V1—COMPUTE OUTCROP INTERSECTIONS FOR VBM Proprietary Software: Mintec, inc.

Page 664-2 Revised: 1-August-94

MineSight®
Proprietary Software: Mintec, inc. M664V1—COMPUTE OUTCROP INTERSECTIONS FOR VBM

M664V1 COMPUTE OUTCROP INTERSECTIONS FOR VBM DATA

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS-664V1 10=filename 25=filename 19=filename;

MEDS-664V1 3=filename
where

MEDS-664V1 (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
25= the name of the VBM FILE
19= the name of the M122 Plot File
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = SYMBOL # (DEFAULT=1)
IOP2 = PEN # (DEFAULT=1)
IOP3 = 0 MATCH ONLY RIGHT SIDE FEATURE CODE FOR THE PITS
= 1 MATCH 6 DIGIT FEATURE CODE FOR THE PITS
PAR1 = CHARACTER HEIGHT (DEFAULT=0.1)
PAR2 = ANNOTATION ANGLE (DEFAULT=0.0)
PAR3 = MINIMUM EASTING (DEFAULT=PCF(21))
PAR4 = MAXIMUM EASTING (DEFAULT=PCF(22))
PAR5 = MINIMUM NORTHING (DEFAULT=PCF(25))
PAR6 = MAXIMUM NORTHING (DEFAULT=PCF(26))

END

4. PIT SPECIFICATION LINES

plane#1 plane#2 inc ipit jpit

where
plane#1 = First plane
plane#2 = Last plane
inc = Increment between planes
ipit = First feature
jpit = Second feature

Revised: 19-July-96 Page 664-3

 MineSight®
M664V1—COMPUTE OUTCROP INTERSECTIONS FOR VBM Proprietary Software: Mintec, inc.

M664V1 SAMPLE RUN FILE #1

MEDS-664V1 10=[Link] 25=[Link] 19=[Link];
MEDS-664V1 3=[Link]
** COMPUTE FEATURE INTERSECTIONS & OUTPUT PLOT COMMANDS **

USR = ABC
IOP1 = 4 2 / SYMBOL # & PEN #
PAR1 = 0.12 45. / SYMBOL HEIGHT & ANGLE OF ANNOTATION
END
3500 4550 50 901 899 PIT SPECIFICATION LINES

HOW TO DEBUG AN M664V1 RUN

1. ERROR RETURN FROM VBMRGM
will occur if there is no data in the VBM file or the specified section does not exist.

2. The easiest way to check this routine is to plot out the intersections and compare them with an overlay of the original features.
If there are any discrepancies check that the plane numbers and feature codes are in the VBM and the run file correctly.

3. Check the MineSight® error messages in the Appendix.

Page 664-4 Revised: 19-July-96

MineSight®
Proprietary Software: Mintec, inc. M665V1 - VBM CUT GENERATOR

M665V1 - VBM CUT GENERATOR

PROGRAM SUMMARY Each cut will be projected parallel to the original cut shape at
the specified cut width distance (PAR1 in project units). The
M665V1 is used to generate a specified number of mining cuts cuts will show no signs of smoothing. The mining sequence
from a series of coordinate points which define some mining number of the first cut is specified by IOP3. The numbers for
limit. The cut geometry may be stored back into the VBM file. subsequent cuts will be automatically incremented by one per
cut. If the cuts are stored in the VBM file, each cut is stored in
the feature according to its mining sequence number. Each of
the cuts will be assigned the same plane number (IOP1).
PROGRAM FLOW DIAGRAM
The initial unclosed cut shape can be entered from the run file
or from an ASCII input file. The points that describe the initial
cut are entered so that as you look down the line from the start
point, the cuts will be generated to your right.
RUN FILE:
If A is the start point, cuts will be generated as shown.
- Number of cuts to
generate The incremental cut distance (PAR1) is the width of each
- Format to store cuts
(VBM/ASCII)
- Direction of mining B A

- Coordinate points along

the initial cut

e.g.

INPUT: CALCS: B
A

- PCF - Calculate the partials

- File 25 between topo and dump cut and should be entered in user units. The width will be applied
surface
-Calculate the area, volume
as a perpendicular distance. The new point can be created at the
and tonnage of the dump bisector between the previous and next cut, at the perpendicular
- Output a file of paritals to the previous segment or to the next segment. In normal cut
generation, the bisector is used. The other options are mainly
for flared cuts (i.e., variable width).

The following limitations apply to program M665V1:

OUTPUT:
- ASCII file of partials
• Initial cut shape cannot contain more than 250 points.
- Printer Output File
• No more than 300 cuts can be generated in a single
run.

• If the coordinate (0.0, 0.0) is encountered in the input

REQUIREMENTS AND CONSIDERATIONS data, it is used as an end of input idicator.
M665V1 is used to generate a series of closed shape mining • The VBM file name must be entered when storing the
cuts from an initial unclosed cut shape. (See Figure 1 of the
cuts to an ASCII output file, even though it is not used.
TECHGSM Section for a graphical explanation of the boundary
line conventions.)

Revised: 18-May-06 Page 665-1

 MineSight®
M665V1 - VBM CUT GENERATOR Proprietary Software: Mintec, inc.

Page 655-2 Revised: 18-May-06

MineSight®
Proprietary Software: Mintec, inc. M665V1 - VBM CUT GENERATOR

665V1 VBM CUT GENERATOR

RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)

MEDS—665V1 10=filename 25=filename 19=filename;

MEDS—665V1 30=filename 3=filename
where
MEDS—665V1 (must be the first 10 columns)
10= the name of the PROJECT CONTROL FILE
25= the name of the VBM FILE
19= the name of the Initial Cut Points File (optional)
30= the name of the Output File for M708SM
3= the name of the PRINTER OUTPUT FILE
2. RUN INFORMATION LINE (max. of 80 columns)

A single line of text that will be printed at the top of each page of printer output from the run.

3. RUN OPTIONS (in any order & free—field format)

USR = USER INITIALS (e.g. ABC)

IOP1 = VBM PLANE NUMBER (Integer plane numbers only, regardless of VBM plane precision.)
IOP2 = NUMBER OF CUTS TO BE GENERATED
IOP3 = FIRST MINING SEQUENCE NUMBER(or feature code)
IOP4 = 0 READ THE STARTING CUT LINE POINTS FROM RUN FILE
= 1 READ THE STARTING CUT LINE POINTS FROM FILE #19
IOP5 = 0 WRITE CUTS TO VBM FILE
= 1 WRITE CUTS TO ASCII FILE IN M708SM INPUT FORMAT
IOP7 = 0 FILE 19 IS IN X,Y FORMAT
= 1 FILE 19 HAS DIGED/M649V1 HEADER
PAR1 = INCREMENTAL CUT WIDTH(Default = 50)
PAR3 = VBM PLANE NUMBER (Real plane numbers, of any precision, only.)
NOTE: IOP1 cannot be used for real plane numbers such as 1.1 while PAR3 can be used for any plane number
END

Revised: 30-September-93 Page 665-3

 MineSight®
M665V1 - VBM CUT GENERATOR Proprietary Software: Mintec, inc.

4. BEGINNING CUT DEFINITION POINTS

X(I)Y(I)width(I)type(I)(one set of values per line)

where

X(I) = Easting of ith cut segment point

Y(I) = Northing of ith cut segment point

width(I)= an optional width at this point; defaults to PAR1; used for flared cuts

type(I) = method of generating cut

0=use bisector angle(default)

1=make perpendicular to previous segment

2=make perpendicular to next segment

M665V1 SAMPLE RUN FILE #1

MEDS—665V1 10=[Link] 25=[Link] 19=[Link];
MEDS—665V1 3=[Link]
*DRAGLINE CUT GENERATOR CHECK*

USR = ABC

IOP1 = 100 / PLANE # ON WHICH TO STORE CUTS

IOP2 = 10 / NUMBER OF CUTS TO BE GENERATED
IOP3 = 888 / FEATURE CODE OF FIRST CUT

IOP4 = 1 / INITIAL CUT POINTS ARE IN FILE #19

IOP5 = 0 / STORE CUTS IN VBM FILE

PAR1 = 250. / INCREMENTAL CUT LENGTH

END

Page 665-4 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M665V1 - VBM CUT GENERATOR

M665V1 SAMPLE RUN FILE #2

MEDS—665V1 10=[Link] 25=[Link] 3=[Link];
MEDS—665V1 30=[Link]
* CREATE SAMPLE DRAGLINE CUT SERIES #1 IN M708SM INPUT FORMAT

USR = ABC

IOP1 = 100 / PLANE # ON WHICH TO STORE DATA

IOP2 = 4 / NUMBER OF CUTS TO BE GENERATED
IOP3 = 101 / MINING SEQUENCE NUMBER OF FIRST CUT

IOP4 = 0 / INITIAL CUT POINTS ARE IN RUN FILE

IOP5 = 1 / STORE CUTS IN ASCII OUTPUT FILE

PAR1 = 250. / INCREMENTAL CUT WIDTH

END
4000. 8500. Beginning Cut Definition Points
6500. 12500.
5000. 17000.
9000. 19000.
11000. 23000.

M665V1 SAMPLE RUN FILE #3

MEDS—665V1 10=[Link] 25=[Link] 3=[Link];

* CREATE SAMPLE FLARED CUTS *

USR = ABC

IOP1 = 100 / PLANE # ON WHICH TO STORE CUTS

IOP2 = 10 / NUMBER OF CUTS TO BE GENERATED
IOP3 = 101 / INITIAL FEATURE CODE FOR NEW CUTS

IOP4 = 0 / INITIAL CUT POINTS ARE IN RUN FILE

IOP5 = 0 / STORE CUTS IN VBM FILE

PAR1 = 250. / INCREMENTAL CUT WIDTH

END
4000 8500 250 Beginning Cut Definition Pointswith width and type specified
4000 10000 250 1
3000 11000 300

Revised: 30-September-93 Page 665-5

 MineSight®
M665V1 - VBM CUT GENERATOR Proprietary Software: Mintec, inc.

M665V1 SAMPLE OUTPUT—CUT BOUNDARIES

0 1
1 4000.00 8500.00
2 6500.00 12500.00
3 5000.00 17000.00
4 9000.00 19000.00
5 11000.00 23000.00
6 11223.61 22888.20
7 9186.34 18813.66
8 5305.74 16873.36
9 6774.41 12467.35
10 4212.00 8367.50
11 4000.00 8500.00
-1
0 2
12 4212.00 8367.50
13 6774.41 12467.35
14 5305.74 16873.36
15 9186.34 18813.66
16 11223.61 22888.20
17 11447.21 22776.39
18 9372.68 18627.32
19 5611.47 16746.72
20 7048.81 12434.70
21 4424.00 8235.00
22 4212.00 8367.50
-1
0 3
23 4424.00 8235.00
24 7048.81 12434.70
25 5611.47 16746.72
26 9372.68 18627.32
27 11447.21 22776.39
28 11670.82 22664.59
29 9559.01 18440.98
30 5917.21 16620.08
31 7323.22 12402.05
32 4636.00 8102.50
33 4424.00 8235.00
-1
0 4
34 4636.00 8102.50
35 7323.22 12402.05
36 5917.21 16620.08
37 9559.01 18440.98
38 11670.82 22664.59
39 11894.43 22552.79
.
.
.

Page 665-6 Revised: 30-September-93

MineSight®
Proprietary Software: Mintec, inc. M665V1 - VBM CUT GENERATOR

HOW TO DEBUG A M665V1 RUN

1. CUT GENERATION WILL END AFTER CUT # nnn

RUN TERMINATED BEFORE DESIRED # OF CUTS BECAUSE OF CONCAVE ANGLE

Program M665V1 is able to generate up to 300 cuts, each with up to 200 points, in a single run. The initial cut points can have
any non—crossing geometry. However, if any concave angles exist between the points, the program will compute the number
of cuts required to fill the area inside the angle.

If this number is less than the number of requested cuts (IOP2), the above error messages will be displayed and the program
will only generate the number of cuts calculated.

2. The generated cuts should be checked by scanning the points or plotting. If any unexpected results occur, check the run file to
make sure that the initial cut points are input in the proper order and that the incremental cut distance is correct.

3. Check the MineSight® error messages in the Appendix.

Revised: 30-September-93 Page 665-7

 MineSight®
M665V1 - VBM CUT GENERATOR Proprietary Software: Mintec, inc.

Page 665-8 Revised: 30-September-93

MineSight® M667V1-COMPUTE MODEL CODES AND/OR PARTIALS
Proprietary Software: Mintec, inc. FROM VBM OUTLINES

M667V1 COMPUTE MODEL CODES AND/OR PARTIALS

FROM VBM OUTLINES

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M667V1 calculates block codes and/or block partials M667V1 computes block codes and block partials (percentages)
(percentages) using geology data from the VBM file. Codes from the VBM outlines.
can be assigned to a block either as codes at a center of a block
or as a majority code. The program can automatically read VBM orientation from the
VBM file (if you have a new VBM file). You can also specify
PROGRAM FLOW DIAGRAM VBM orientation with IOP1.

RUN FILE: By default the model is presumed to be the one defined in the
PCF. Actual bench elevations will be used to determine blocks
- Feature/Geology Codes
- VBM planes in the 3-D model. However, you can use a different model by
- Benches (Sections) setting NX, NY and NZ in IOP30-32 and XMIN, DX, YMIN,
DY, ZMIN, DZ in PAR21-26. In this case you must set IOP18=1
(constant bench height) as you would not want to use PCF
benches.

If you want to limit computations to a part of the model, you

can specify this part in PAR1-PAR6. You may enter the limiting
INPUT: CALCS: boundaries either in project coordinates (IOP17=0) or in block
- PCF - Calculate intersections of numbers (IOP17=1).
- VBM File 25 model rows (or columns
or benches) with VBM Feature codes and equivalent (geologic) codes are generally
features
- Match feature codes to
entered after the END line in the run file. However, you may
geologic codes choose to consider all 3-digit left and right codes (IOP11=–1).
- Find block % and codes By default (IOP11=0 and IOP12=0) codes should be entered in
a run file. If you choose IOP11=1 equivalent codes should also
be entered in a run file. You may equivalence several feature
codes to the same geologic code.
OUTPUT

- ASCII file of block codes You also have an option (IOP12=1) to consider 6-digit codes as
and/or % codes on the right of the feature. In this case you must enter
- M122xx plot file equivalent codes in the run file.
- Printer output file
If several features coincide, the program may not be able to
determine the proper codes from the left or from the right of the
IMPORTANT: Note about ASCII output files. features. In this case the code will be considered unresolved
M667V1 can create ASCII output in M610V1, M610V2, code of type 1 and will be assigned equivalent code of the value
M729V1 or M601V2 input formats.M610V1input format is of IOP25 (default=-1).
(4I5,20I4)M610V2 input formats are:
If there are inconsistencies in coding, i.e., features intersect and
codes do not match, and the proper code can not be determined,
(3I5,10(F6.1,F5.0)) to output both percentages and codes,
then such codes will be considered unresolved code of type 2
(3I5,10(F6.3,F5.0)) to output both partials and codes,
and will be assigned equivalent code of the value of IOP26
(3I5,20F6.0) to output only percentages and and do not
(default=-2). You have an option to equivalence feature codes
output codes,
before sorting intersections (IOP19=1) or after (IOP19=0).
(3I5,20F6.2) to output only partials and do not outputcodes,
M729V1 input format is (4I5)
M601V2 input format is (6I5)

Revised: 30-September-97 Page 667-1

M667V1-COMPUTE MODEL CODES AND/OR PARTIALS MineSight®
FROM VBM OUTLINES Proprietary Software: Mintec, inc.

While outputting majority codes or block partials (IOP2=0 or In the run file you can enter just bench/section locations
IOP2>0), the block is considered unresolved if the sum of partials (IOP16=1) or you can enter VBM plane numbers and
of both unresolved codes is greater than PAR12. corresponding benches (IOP16>1).

If you output majority codes (IOP2=0), a block is considered After bench/section is entered, the program finds the closest
undefined if the partial of the majority code is less than PAR11. VBM plane within the search distance (PAR14>0): the range of
Planes for the search is defined by inequalities
If you output partials (IOP2>0), a block is considered undefined
if the sum of all partials in the block is less than PAR11. -PAR14 + bench/sect. location #VBM plane level< bench/[Link] + PAR14

If you choose to output partials, you can do it in a majority If PAR14=0, then the search will be performed among all entered
owner order (default), or in the order the codes are entered VBM planes.
(IOP6>0).
If PAR14=-1, the search will be limited to the given bench/
By default the program will output partials as percentages. If section. For the bench, the toe will always be included and the
you want to output partials as fractions of 1, you have to set crest excluded from the search. Similarly, for sections, the west
IOP7 to 1. or south (left or bottom) edges will be included and east or north
(right or upper) edges excluded from the search.
You also have an option to combine codes (IOP8>0 or IOP8=-
1), and to output block partial outside the feature (IOP9=1). On each plane further computations are performed row by row
or column by column as given by IOP5. IOP5=0 (use horizontal
M667V1 treats VBM planes and model benches/sections lines) will perform computations along Xpln direction. IOP5=1
separately. Therefore, VBM planes and model benches(seams)/ will perform computations in direction along ypln. You might
sections are entered separately. choose IOP5=1 if your features are extended in Xpln direction.

To enter the set of VBM planes you may If you are computing partials (IOP2>=0), you have an option to
control precision. The value of IOP4 is the number of slices the
1) Set IOP15=0 to consider all planes from the VBM file within block is divided into while computing partials.
a range given by PAR7 and PAR8. You can also set an increment
in the plane numbers by setting PAR9. If you have chosen IOP16>0 (input benches/sections from a
run file) you may also create plot files for each section and view
2) Set IOP15=1 to enter VBM planes after the END line in a run them with one of the M122xx programs. You must specify plot
file. If plane number does not correspond to the actual plane filenames for each bench/section on the same line as bench/
location you must enter the actual location on the same line as a section location after the END line in a run file. By default only
plane number. PAR7 and PAR8 will be disregarded if IOP15=1. unresolved blocks will be plotted (IOP20=0).

3) Set IOP15=-1 and exclude the planes entered after the END If you choose IOP20=1 then all blocks (except undefined) will
line from the set of VBM planes within PAR7, PAR8 limits. be plotted. If you output the code at a center of a block, majority
code or partials in a majority owner order, then the majority
If actual plane location differs by a certain constant from the codes (or codes at the block centers) will be plotted.
one defined by the plane number for all planes, then you can
enter this number in PAR10, and this offset will be added To convert M656 run files to M667V1 run files you may use
automatically. If actual location is entered in the run file, then the program gn5667. Usage: gn5667 656runfile 667runfile.
PAR10 is disregarded.
For GSM models, only planar VBMs can be used with this
M667V1 does not allow input from the terminal. You must enter program.
your benches/sections from the run file (IOP16>0) or use all
benches/sections from the selected part of your model
(IOP16=0).

Page 667-2 Revised: 30-September-97

MineSight® M667V1-COMPUTE BLOCK CODES AND/OR PARTIALS
Proprietary Software: Mintec, inc. FROM VBM OUTLINES

M667V1 - COMPUTE BLOCK CODES AND/OR PARTIALS

FROM VBM OUTLINES
RUN FILE OPERATION
1. NAMES LINE (must be the first line entered)

MEDS-667V1 10=filename 25=filename 19= filename;

MEDS-667V1 3=filename
where

MEDS667V1 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
25 = the name of the VBM FILE
19 = the name of an ASCII OUTPUT FILE (REQUIRED if IOP3 is greater than or equal to 0)
3= the name of the PRINTER OUTPUT FILE

2. RUN INFORMATION LINE (maximum of 80 columns)

A single line of text that will be printed at the top of the printer output from the run.

3. RUN OPTIONS (in any order & free-field format)

USR = USER INITIALS (e.g., ABC)

IOP1 = 0 USE THE DEFAULT ORIENTATION FROM THE VBM

= 1 W-E
= 2 S-N
= 3 PLANAR

NOTE: 1) IOP1 must be > 0 if the VBM has no default [Link] entered value of IOP1 > 0 will
override the default orientation. M667V1 can not be used with non-orthogonal sections.

2) In the case of a rotated model, IOP1=1,2 or 3 must be specified. In this case, IOP1=1 is the
orientation of XZ-model sections, IOP1=2-orientation of YZ model sections and IOP1=3-
orientation of model benches.

IOP2 = -1 OUTPUT CODE AT THE BLOCK CENTER

= 0 OUTPUT THE MAJORITY CODE FOR A BLOCK (do not output % value)
= N OUTPUT FEATURE PERCENTAGE AND CODES FOR N FEATURES PER BLOCK

IOP3 = -1 DO NOT CREATE AN ASCII OUTPUT FILE

= 0 USE DEFAULT FORMAT: M610V1 INPUT FORMAT IF IOP2#0
M610V2 INPUT FORMAT IF IOP2>0
= 1 CREATE AN ASCII FILE IN M610V1 INPUT FORMAT (4I5,20I4)
= 2 CREATE AN ASCII FILE IN M610V2 INPUT FORMAT
If IOP6=0 or 2: (3I5,10(F6.0,F5.0)) FOR PERCENTAGES
(3I5,10(F6.2,F5.0)) FOR FRACTIONS OF 1
If IOP6=1 or 3: (3I5,20F6.0) FOR PERCENTAGES
(3I5,20F6.2) FOR FRACTIONS OF 1
= 3 CREATE AN ASCII FILE IN M729V1 INPUT FORMAT (4I5)
= 4 CREATE AN ASCII FILE IN M601V2 INPUT FORMAT (6I5)

NOTE: 1) If IOP2>0 output format will be set to M610V2 input format.

Revised: 24-September-02 Page 667-3

M667V1-COMPUTE BLOCK CODES AND/OR PARTALS MineSight®
FROM VBM OUTLINES Proprietary Software: Mintec, inc.

2) You can modify formats for longer than 3 digit codes using IOP37.

IOP4 = N NUMBER OF LINES TO PASS THROUGH A BLOCK FOR CALCULATION OF THE PARTIALS
(default=10)

NOTE: Used only if IOP2>0.

IOP5 = 0 DETERMINE CODES AND PARTIALS USING HORIZONTAL LINES

= 1 DETERMINE CODES AND PARTIALS USING VERTICAL LINES

IOP6 = 0 OUTPUT PERCENTAGES (PARTIALS) AND CODES IN MAJORITY OWNER ORDER

= 1 OUTPUT ONLY PERCENTAGES (PARTIALS) FOR THE FIRST IOP2 CODES
= 2 OUTPUT BOTH PERCENTAGES (PARTIALS) AND CODES FOR THE FIRST MAJOR IOP2
NONZERO PARTIALS IN THE SAME ORDER AS CODES ENTERED
= 3 OUTPUT HANGINGWALL, FOOTWALL AND/OR INTERBURDEN
= 4 OUTPUT WASTE PARTIALS BETWEEN ORE ZONES WORKING FROM MAX TO MIN COORD
= 5 OUTPUT WASTE PARTIALS BETWEEN ORE ZONES WORKING FROM MIN TO MAX COORD

NOTE: 1) IOP6 is used only if outputting partials (IOP2> 0.)

2) If codes are equivalenced (IOP10=1) the first IOP2 distinct equivalent codes will be used
if IOP6=1 or 2.

3) If you compute hw, fw and/or interburden IOP2 should be equal to 2 or 3.

IOP7 = 0 OUTPUT PARTIALS AS PERCENTAGE

= 1 OUTPUT PARTIALS AS FRACTIONS OF 1

NOTE: Used only if IOP2> 0.

IOP8 = -1 COMBINE THE REST OF PARTIALS INTO MAJORITY PARTIAL

= 0 DO NOT COMBINE PARTIALS
= M COMBINE PARTIALS INTO M-TH PARTIAL

NOTE: If you compute only hw and fw, set IOP2 =2, and then if you want to combine interburden to
hangingwall choose IOP8=1, if you want to combine interburden to footwall choose IOP8=2.

IOP9 = 0 OUTPUT BLOCK PERCENTAGE INSIDE THE FEATURE (on the right)
= 1 OUTPUT BLOCK % OUTSIDE THE FEATURE (100 - BLOCK %)

NOTE: IOP9 can only be used when IOP2 = 1 (computing partials for 1 code). If IOP2 is not equal to 1
or IOP6=3 then IOP9 will be ignored.

IOP11 = -1 USE ALL FEATURES (should be not more than 50 codes if computing partials)
= 0 DO NOT READ EQUIVALENT CODES
= 1 READ EQUIVALENT CODES FROM THE RUN FILE

IOP12 = 0 EQUIVALENCE 3-DIGIT CODE (right code if 6-digit codes are entered)
= 1 TREAT THE WHOLE 6 DIGIT CODE AS A RIGHT CODE
= 2 TREAT ALL LEFT CODES AS 0

NOTE: Equivalent codes must be an integer from 1 to 999. If IOP12=1 you must enter equivalent codes
in the run file (set IOP11=1).

IOP13 = 0 CHECK FEATURES AGAINST BOTH LEFT AND RIGHT CODES

= 1 CHECK AGAINST FULL CODE ONLY

Page 667-4 Revised: 24-September-02

MineSight® M667V1-COMPUTE BLOCK CODES AND/OR PARTIALS
Proprietary Software: Mintec, inc. FROM VBM OUTLINES

IOP14 = 0 DO NOT EXTEND CODES TO THE MODEL LIMITS

= 1 EXTEND CODES TO THE MODEL LIMITS

IOP15 = 0 VBM PLANES ARE SELECTED USING PAR7-PAR9

= 1 VBM PLANES ARE SPECIFIED AFTER THE END LINE
(PAR7-PAR9 are ignored in this case)
= -1 OMIT THE VBM PLANES SPECIFIED AFTER THE END LINE

IOP16 = 0 USE ALL BENCHES (SECTIONS) IN PAR1- PAR6 LIMITS

= 1 BENCHES/SECTIONS AND OPTIONAL PLOT FILES ARE SPECIFIED IN THE RUN FILE
= 2 VBM PLANES, BENCHES/SECTIONS AND OPTIONAL PLOT FILES ARE SPECIFIED
IN THE RUN FILE
= 3 VBM-PLANES, STARTING AND ENDING BENCH/SECTIONS, AND OPTIONAL
PLOT FILES ARE SPECIFIED IN THE RUN FILE

NOTE: If IOP16=1 then benches/sections elevations/coordinates are checked against PAR1-PAR6.

IOP17 = 0 PAR1-PAR6 ARE IN PROJECT COORDINATES

= 1 PAR1-PAR6 ARE IN BLOCK NUMBERS

IOP18 = 0 USE PCF BENCHES

= 1 USE CONSTANT DZ FOR BENCH CALCULATIONS

IOP19 = 0 EQUIVALENCE CODES AFTER SORTING INTERSECTIONS

= 1 EQUIVALENCE CODES BEFORE SORTING INTERSECTIONS

IOP20 = -1 DO NOT CREATE A PLOT FILE

= 0 PLOT ONLY UNRESOLVED BLOCKS
= 1 PLOT EVERYTHING

IOP21 = -1 OUTPUT ONLY UNRESOLVED BLOCKS

= 0 DO NOT OUTPUT UNDEFINED AND UNRESOLVED BLOCKS
= 1 OUTPUT ALL BLOCKS
= 2 DO NOT OUTPUT UNDEFINED BLOCKS

NOTE: If IOP2>0 you cannot use IOP21 = -1.

IOP22 = 0 USE VBM LIMITS TO LOOK FOR INTERSECTIONS

= 1 LIMIT INTERSECTIONS TO PAR1 - PAR6 LIMITS

IOP24 = -N UNDEFINED PARTIALS WILL BE ADDED TO THE EQUIVALENT CODE N FOR ALL BLOCKS
= 0 DO NOT ADD UNDEFINED PARTIALS TO ANY CODE
= N UNDEFINED PARTIALS WILL BE ADDED TO THE EQUIVALENT CODE N ONLY FOR THE
BLOCKS THAT HAVE SOME NON-ZERO PARTIALS

IOP25 = CODE TO ASSIGN TO UNRESOLVED BLOCKS OF THE FIRST TYPE (default=-1)

IOP26 = CODE TO ASSIGN TO UNRESOLVED BLOCKS OF THE SECOND TYPE (default=-2)

IOP27 = 0 BENCHES/SECTIONS ARE ENTERED IN PROJECT COORDINATES

= 1 BENCHES/SECTIONS ARE ENTERED IN BLOCK NUMBERS

NOTE: Used if IOP16>0.

IOP28 = 0 PLANES WITH NO REQUESTED CODES ARE NOT IGNORED

= 1 PLANES WITH NO REQUESTED CODES ARE IGNORED

Revised: 24-September-02 Page 667-5

M667V1-COMPUTE BLOCK CODES AND/OR PARTALS MineSight®
FROM VBM OUTLINES Proprietary Software: Mintec, inc.

IOP30 = NX (default=PCF value)

IOP31 = NY (default=PCF value)
IOP32 = NZ (default=PCF value)

IOP37 = NUMBER OF CHARACTERS RESERVED FOR ONE CODE OUTPUT

(default = 4 for M610V1 output, and 5 for M610V2 output)

IOP38 = 1 COMPUTE PARTIALS ONE FEATURE AT A TIME

NOTE: 1) If IOP38=1, all left codes will be treated as 0. If IOP12=0, then it will be forced to 2.

2) IOP6=3 (hangingwall, footwall, interburden) cannot be used.

IOP39 = 0 DO NOT TAKE ANY EXTRA EFFORT TO DETERMINE BLOCK CODES

= 1 TAKE EXTRA EFFORT TO DETERMINE BLOCK CODES (may be extremely time consuming)

PAR1 = WEST EDGE OF THE FIRST BLOCK TO USE (default = XMIN)

PAR2 = EAST EDGE OF THE LAST BLOCK TO USE (default = XMAX)

PAR3 = SOUTH EDGE OF THE FIRST BLOCK TO USE (default=YMIN)

PAR4 = NORTH EDGE OF THE LAST BLOCK TO USE (default=YMAX)

PAR5 = LOWEST TOE ELEVATION TO USE (default=ZMIN)

PAR6 = HIGHEST CREST ELEVATION TO USE (default=ZMAX)

NOTE: If IOP17=1, PARs 1-6 are in block numbers and defaults will change to 1, NX, 1, NY, 1, NZ
respectively.

PAR7 = STARTING VBM PLANE

PAR8 = ENDING VBM PLANE

NOTE: 1) PAR7 and PAR8 correspond to the range of plane numbers after applying offset (PAR10). The
defaults for PAR7 and PAR8 are determined by the VBM orientation and the values of the PARs 1-
6. For example, if the VBM orientation is planar, the default value for PAR7 is PAR6 (the minimum
elevation of the model limits).

2) ALWAYS enter PAR7 and PAR8 for non-orthogonal VBMs. The default values for minimum
and maximum plane for non-orthogonal planes (PAR7 and PAR8) are set based on a corresponding
model coordinate, which does not correspond to actual VBM plane numbers.

PAR9 = INCREMENT FOR SELECTING VBM PLANES FROM PAR7-PAR8 (default= (PAR9=0) USE ALL PLANES
WITHIN PAR7-PAR8 LIMITS)

PAR10 = OFFSET TO ADD TO PLANE NUMBERS

NOTE: PAR10 is used to convert the VBM plane number to an actual location. It will ALSO be applied to
the planes entered after the END line (IOP15=1) unless the plane has actual location explicitly
specified.

PAR11 = MINIMUM PERCENTAGE TO OUTPUT MAJORITY CODE (default=40)

PAR12 = MINIMUM PERCENTAGE OF UNRESOLVED CODES TO CONSIDER BLOCK UNRESOLVED (default=10)

Page 667-6 Revised: 18-May-06

MineSight® M667V1-COMPUTE BLOCK CODES AND/OR PARTIALS
Proprietary Software: Mintec, inc. FROM VBM OUTLINES

PAR13 = TOLERANCE FOR NORMALIZING FEATURES

NOTE: Default = 0.01 x (block size in the corresponding direction)

PAR14 = -1 SEARCH FOR VBM PLANES WITHIN A BENCH (can be used only for 3DBMs)
= 0 USE ALL ENTERED VBM PLANES TO SEARCH FOR THE CLOSEST SECTION/BENCH
> 0 USE VBM PLANES WITHIN PAR14 FROM THE BENCH (bench coordinate is taken at toe, section
coordinate is taken at the minimum side.)

PAR15 = SIZE OF PLOT CHARACTER (PLOTTER UNITS) (default=0.05)

PAR16 = MAP SCALE (PROJECT UNITS PER PLOTTER UNITS) (default=DX)

PAR21 = XMIN OF THE MODEL

PAR22 = DX
PAR23 = YMIN
PAR24 = DY
PAR25 = ZMIN
PAR26 = DZ

NOTE: PAR21-26 default to the PCF values

PAR27 = MINIMUM % OF UNDEFINED CODE TO DECLARE BOCK UNDEFINED (default=1–PAR11 if IOP2=0,

and 99.5 otherwise)

END

4. FEATURE CODES LINES (enter if IOP11 is greater or equal to 0)

ncode
fcode1 ... fcodeN
where

ncode = number of feature codes entered

fcodes - feature codes (up to 20 codes per line) maximum of 400 distinct values of feature codes is allowed

5. EQUIVALENT CODES LINES (enter if IOP11 > 0)

neqcode
eqcode1 ... eqcodeN
where

neqcode = number of equivalent codes entered

eqcodes -equivalent codes (up to 20 codes per line) maximum of 400 distinct values of equivalent codes is allowed

6. VBM PLANES LINES (enter if IOP15 is not 0)

nvbmplanes
vbmplane1 vbmloc1
...
vbmplaneN vbmlocN
where

nvbmplanes - number of VBM planes entered

vbmplanes - VBM plane numbers
vbmloc - VBM plane locations (optional)

Revised: 18-May-06 Page 667-7

M667V1-COMPUTE BLOCK CODES AND/OR PARTALS MineSight®
FROM VBM OUTLINES Proprietary Software: Mintec, inc.

NOTE: vbmloc is used to assign a plane location if the VBM plane number does not correspond to an
actual plane location. Offset (PAR10) will NOT be used if vbmloc is used.

7. BENCHES/SECTIONS DEFINITION LINES (enter if IOP16>0)

—-IF IOP16 = 1:

nlevels
level1 filename1
...
levelN filenanameN

—-IF IOP16 = 2:

nlevels
vbmplane1 level1 filename1
...
vbmplaneN levelN filenameN

—-IF IOP16 = 3:

nlevels
vbmplane1 levstart1 levend1 filename1
...
vbmplaneN levstartN levendN filenameN
where

nlevels - number of benches/sections to be used in the run

levels - benches/sections (in project coordinates if IOP27 = 0 and in block numbers if IOP27=1)
levsatrt,levend - starting and ending bench/section corresponding to a VBM plane (if IOP16=3)
(In project coordinates if IOP27=0 and in block numbers if IOP27=1)

Page 667-8 Revised: 18-May-06

MineSight® M667V1-COMPUTE BLOCK CODES AND/OR PARTIALS
Proprietary Software: Mintec, inc. FROM VBM OUTLINES

M667V1 SAMPLE RUN FILE #1

MEDS-667V1 10=[Link] 25=[Link] 3=[Link];
MEDS-667V1 19=dat610.i1
*Compute Block Codes from VBM Outlines*

USR = ABC /Wed Aug 28, 1996 4:16:37 PM MST

IOP1 = 0 /VBM ORIENTATION

IOP2 = 0 /0=MAJORITY CODE, -1=CODE AT THE BLOCK CENTER
IOP3 = 1 /ASCII OUTPUT TYPE
IOP5 = 0 /0=USE HORIZONTAL SLICES, 1=VERTICAL
IOP11 = 1 /TYPE OF FEATURE CODES ENTRY (-1-use all)
IOP12 = 0 /1=EQUIVALENCE THE WHOLE 6-DIGIT CODE
IOP13 = 0 /1=CHECK AGAINST FULL CODE ONLY
IOP14 = 0 /1=EXTEND CODES TO THE MODEL LIMITS
IOP16 = 0 /TYPE OF SECTIONS/BENCHES ENTRY
IOP17 = 0 /TYPE OF MODEL BOUNDS ENTRY (1=in block numbers)
IOP18 = 0 /0=USE PCF BENCHES, 1=USE CONSTANT DZ
IOP19 = 0 /1=EQUIVALENCE CODE BEFORE SORTING INTERSECTIONS
IOP20 = -1 /TYPE OF PLOT (1=plot everything, -1 = no plot)
IOP25 = /CODE FOR UNRESOLVED BLOCKS OF TYPE 1
IOP26 = /CODE FOR UNRESOLVED BLOCKS OF TYPE 1
IOP27 = 0 / 1=SECTIONS/BENCHES ARE ENTERED IN THE BLOCK NUMBERS
IOP30 = 0 /NX
IOP31 = 0 /NY
IOP32 = 0 /NZ
IOP39 = 0 / 1 = TAKE EXTRA EFFORT TO FILL GAPS IN CODES
PAR7 = 2600. 4600. /BOUNDS FOR VBM PLANES
PAR9 = 100. /OFFSET FOR VBM LOCATION
PAR11 = 30. /MINIMUM PARTIAL TO OUTPUT MAJORITY CODE
PAR13 = 1. /TOLERANCE FOR DEFINING COINCIDING INTERSECTIONS
PAR14 = 0. /SEARCH DISTANCE
PAR21 = 0. 0. /XMIN,DX (default=PCF values)
PAR23 = 0. 0. /YMIN,DY (default=PCF values)
PAR25 = 0. 0. /ZMIN,DZ (default=PCF values)
PAR27 = 0. /MINIMUM VALUE OF UNDEFINED PARTIAL TO DECLARE
COM BLOCK UNDEFINED (DEFAULT: 1-PAR11 if IOP2 = 0, AND
COM 99.5 OTHERWISE)
END
3501 502 503 31 2 1

Revised: 24-September-02 Page 667-9

M667V1-COMPUTE BLOCK CODES AND/OR PARTALS MineSight®
FROM VBM OUTLINES Proprietary Software: Mintec, inc.

M667V1 SAMPLE RUN FILE #2

MEDS-667V1 10=[Link] 25=[Link] 3=[Link];
MEDS-667V1 19=dat610.i2
*COMPUTE BLOCK PARTIALS FROM VBM OUTLINES*

USR = ABC /Wed Aug 28, 1996 4:20:53 PM MST

IOP1 = 2 /VBM ORIENTATION

IOP2 = 2 /NUMBER OF PARTIALS TO OUTPUT
IOP3 = 2 /ASCII OUTPUT TYPE
IOP4 = 15 /# OF PASSES (default = 10)
IOP5 = 0 /0=USE HORIZONTAL SLICES, 1=VERTICAL
IOP6 = 0 /0 =OUTPUT IN MAJORITY OWNER ORDER
COM 1=IN THE ORDER OF EQUIVALENT CODES ENTERED
IOP8 = 1 /0 =DO NOT COMBINE PARTIALS
COM 1=COMBINE PARTIALS INTO THE FIRST PARTIAl
COM -1= COMBINE PARTIALS INTO MAJORITY PARTIAL
IOP9 = 0 /1 = OUTPUT PARTIAL OUTSIDE FEATURES
IOP11 = 1 /TYPE OF FEATURE CODES ENTRY (-1 - use all)
IOP12 = 0 /1=EQUIVALENCE THE WHOLE 6-DIGIT CODE
IOP13 = 0 /1=CHECK AGAINST FULL CODE ONLY
IOP14 = /1=EXTEND CODES TO THE MODEL LIMITS
IOP16 = 1 /TYPE OF SECTIONS/BENCHES ENTRY
IOP17 = 0 /TYPE OF MODEL BOUNDS ENTRY (1=in block numbers)
IOP18 = 0 /0=USE PCF BENCHES, 1=USE CONSTANT DZ
IOP19 = 0 /1=EQUIVALENCE CODES BEFORE SORTING INTERSECTIONS
IOP20 = 0 /TYPE OF PLOT (0=plot unresolved blocks only)
IOP27 = 1 /1= SECTIONS/BENCHES ARE ENTERED IN BLOCK NUMBERS
IOP39 = 0 /1= TAKE EXTRA EFFORT TO FILL THE GAPS IN CODES

PAR11 = /MINIMUM PARTIAL TO OUTPUT MAJORITY CODE

PAR13 = 0.1 /TOLERANCE FOR DEFINING COINCIDING INTERSECTIONS
PAR14 = -1. /SEARCH DISTANCE

PAR15 = 0.07 500. /Size of plot characters and map scale

END
3
501 502 503
3
123
3
1 [Link]
2 [Link]
3 [Link]

Page 667-10 Revised: 24-September-02

MineSight® M667V1-COMPUTE BLOCK CODES AND/OR PARTIALS
Proprietary Software: Mintec, inc. FROM VBM OUTLINES

M667V1 SAMPLE RUN FILE #3

MEDS-667V1 10=[Link] 25=[Link] 3=[Link];
MEDS-667V1 19=dat610.i3
*COMPUTE BLOCK PARTIALS FROM VBM OUTLINES*

USR = ABC /Wed Aug 28, 1996 4:28:51 PM MST

IOP1 = 0 /VBM ORIENTATION

IOP2 = 3 /NUMBER OF PARTIALS TO OUTPUT
IOP3 = 2 /ASCII OUTPUT TYPE
IOP4 = 15 /# OF PASSES (default = 10)
IOP5 = 1 /0=USE HORIZONTAL SLICES, 1=VERTICAL
IOP6 = 3 /3=COMPUTE HW FW AND/OR INTERBURDEN
IOP8 = 1 /0 = DO NOT COMBINE PARTIALS
COM 1= COMBINE PARTIALS INTO THE FIRST PARTIAL
COM 2= COMBINE PARTIALS INTO SECONT PARTIAL
IOP11 = 0 /TYPE OF FEATURE CODES ENTRY (-1 - use all)
IOP12 = 2 /2 = IGNORE LEFT CODES
IOP13 = 0 /1=CHECK AGAINST FULL CODE ONLY
IOP14 = /1=EXTEND CODES TO THE MODEL LIMITS
IOP16 = 0 /TYPE OF SECTIONS/BENCHES ENTRY
IOP17 = 0 /TYPE OF MODEL BOUNDS ENTRY (1=in block numbers)
IOP18 = 0 /0=USE PCF BENCHES, 1=USE CONSTANT DZ
IOP19 = 0 /1=eQUIVALENCE CODES BEFORE SORTING INTERSECTIONS
IOP20 = -1 /TYPE OF A PLOT (-1=no plot)
IOP27 = 0 /1= SECTIONS ARE ENTERED IN BLOCK NUMBERS

PAR7 = 0. 0. /BOUNDS FOR VBM PLANES

PAR9 = 0. /OFFSET FOR VBM LOCATION
PAR11 = /MINIMUM PARTIAL TO OUTPUT MAJORITY CODE
PAR13 = 1. /TOLERANCE FOR DEFINING COINCIDING INTERSECTIONS
PAR14 = -1. /SEARCH DISTANCE

END
8
95701 95702 95703 95704 95705
96701 96702 96703

Revised: 24-September-02 Page 667-11

M667V1-COMPUTE BLOCK CODES AND/OR PARTALS MineSight®
FROM VBM OUTLINES Proprietary Software: Mintec, inc.

Page 667-12 Revised: 24-September-02

MineSight®
Proprietary Software: Mintec, inc. VBM - TECHNICAL SECTION

VBM Data

Point data in a VBM file is referenced by two descriptive data

In a VBM file, two coordinates are stored for each point in a
items: the plane reference number and the feature code. For
feature (X & Y). Normally, a coordinate pair will be packed
benches (horizontal planes), the plane reference number is the
into one word of storage. However, if the ((max -min)/precision)
bench toe elevation. For west-east sections, the north coordinate
for X and the ((max - min)/precision) for Y exceeds the number
is usually the plane reference number; for south-north sections
of bits in a word, two words of storage will be used.
the east coordinate is usually the plane reference number. For
planes with default non-orthogonal plane orientation, the plane For point data that is on a section, the X coordinate is either
number reflects the position of the plane (See VBM Orientation Northing, Easting or a distance along the section; the Y
Data topic on the next page.) coordinate is elevation. For point data on a plan, the X coordinate
is Easting and the Y coordinate is Northing.
On each plane, point data is stored as a string of points called
features. The feature code, which describes what type of data is Plane reference numbers are internally stored in the VBM file
stored in the VBM, is an eight digit integer number. This eight as integers. However, real plane numbers can be used in the
digit integer feature code represents material on each side of a VBM system if you specify a precision for the plane number. A
line according to the following convention: precision of 0.1 would allow you to store a plane with one
decimal place precision. A precision of 0.01 would allow you
LLLRRRnn
to store a plane with two decimal places.
where
VBM Limits
LLL = code for left side of line
The number of planes, features, and points in a VBM file is
RRR = code for right side of line 2000 planes per VBM, 2000 features per plane, and 20,000
points per plane. A VBM file created with the current version is
nn = sequence number for feature (not input by user; counted
known as an “expanded limit” VBM.
by program)
Prior to the 1994 release, the limits were 490 planes per VBM,
For a line segment, the feature code describes material on each
500 features per plane, and 8000 points per plane. VBMs created
side of the line as follows:
using programs piror to the 1994 release version with the above
limits are known as “original limit” VBMs.
LEFT SIDE = LLL
FROM > TO
RIGHT SIDE = RRR

The following limits apply to a VBM file:

• 2000 planes per VBM

• 2000 features per plane

• 20,000 points per plane

• 99 features with same code per plane

Normally, one type of data is stored in a single file, i.e., digitized

bench geology is stored in one file and digitized section geology
is stored in another file.

Revised: 22-August-01 Page TECVBM-1

 MineSight®
VBM - TECHNICAL SECTION Proprietary Software: Mintec, inc.

VBM Orientation

INDIVIDUAL ORIENTATION OF VBM SECTIONS Example 2.1 Non-vertical non-orthogonal VBM section with
Xmin = 0, Xmax = 5000, Ymin = 0, Ymax = 2000, reference
Throughout this section Xpln and Ypln will denote coordinates point X-ref = 10000, Y-ref = 12000, Z-ref = 2000, plane azimuth
on a VBM plane. = 111, plane dip = -60:

When you define the VBM file the first thing you do is set limits
of Xpln and Ypln. We denote the Xpln minimum by Xmin and
Ypln minimum by Ymin.

The point on the plane with coordinates Xmin and Ymin is the
lower-left corner of the map. We will call the actual position of
this lower-left corner the reference point of the VBM plane.

To finalize the position of the plane in space we use plane

azimuth and plane dip. The Xpln axis is always horizontal and
makes a “plane azimuth angle” with the Northing direction.

The “dip vector” goes 90 degrees clockwise from the Xpln vector
and makes a “plane dip angle” with the horizontal plane; the
Ypln axis is exactly opposite to the dip vector.

Example 1.1 Vertical VBM plane with Xmin = 0, Xmax = 5000,

Ymin = 2000, Ymax = 4000, reference point X-ref = 10000, Y-
ref = 12000, Z-ref = 2000, plane azimuth = 111, and plane dip =
-90:

RULES FOR SELECTION OF ORIENTATION

PARAMETERS

Starting in March 1996, we imposed certain restrictions on the

choices of orientation parameters.

a. Horizontal (or Planar) Planes.

Horizontal planes always have Xpln direction going along the

Easting direction and Ypln going along the Northing direction.
(they have azimuth = 90, and dip = 0). MineSight® expects any
plane with dip = 0 to be a standard horizontal plane. On a
standard horizontal plane the Xpln coordinate is an actual value
of Easting, and the Ypln coordinate is an actual value of
Northing. X(East) and Y(North) coordinates of the reference
point coincide with Xmin and Ymin values of the VBM.
Z(Elevation) coordinate of the reference point is given by a plane
number.

Page TECVBM-2 Revised: 22-August-01

MineSight®
Proprietary Software: Mintec, inc. VBM - TECHNICAL SECTION

b. South-North (S-N) Planes.

Default orthogonal orientations
S-N planes have Xpln direction going along the Northing
direction and Ypln direction going vertically upwards (they have You may specify your VBM as having one of the orthogonal
azimuth = 0.0 and dip = -90.0). MineSight® expects any plane orientations: W-E, S-N, or Planar.
with azimuth = 0 and dip = -90 to be a standard S-N plane. It
assumes that Xpln coordinate is an actual Northing coordinate, In this case to locate your plane properly the only information
Ypln is an actual elevation. Y(North) and Z(Elevation) reference that MineSight® needs is a plane number. For W-E planes the
coordinates are Xmin and Ymin. X(Easting) coordinate of the plane number should be an actual Northing on the plane, for S-
reference point is the plane number. N an actual Easting, and for Planar an actual Elevation.

c. West-East (W-E) Planes. Default non-orthogonal orientations

W-E planes have Xpln direction going along the Easting To set a default non-orthogonal orientation you must first specify
direction and Ypln direction going vertically upwards (they have the azimuth and dip of your planes (they will be the same for all
azimuth = 90.0 and dip = -90.0). MineSight® expects any plane planes with default orientation in the VBM file.)
with azimuth = 90 and dip = -90 to be a standard W-E plane. It
assumes that the Xpln coordinate is an actual Easting coordinate, Next you should choose the starting plane. The reference point
Ypln is an actual elevation. X(East) and Z(Elevation) reference of the default orientation (or the VBM reference point) is the
coordinates are Xmin and Ymin. Y(Northing) coordinate of the reference point of this starting plane.
reference point is the plane number.
The next step is to choose the Direction of Increasing
The three above cases are called orthogonal. Numbering (DIN). It should be orthogonal to the planes in the
VBM. There are two directions along the line perpendicular to
d. Vertical Non-orthogonal Sections. the plane. You may choose any of them. In the text below, DIN
will also mean the line going from the VBM reference point in
The special case (and the most often used one) of non-orthogonal this direction. All planes with default orientation are attached to
sections is the case of vertical sections. Ypln direction is going this line.
upwards (dip = -90), and Xpln direction makes a plane azimuth
angle with the Northing direction. MineSight® expects Ypln to Now we are ready to set the scale along the DIN. This scale is
be an actual elevation for any plane with dip=-90. Xmin for given by the plane number multiplier. Incrementing the plane
such planes should be 0. Z(Elevation) coordinate of the reference number by one will shift the reference point of the plane along
point is Ymin. X(Easting) and Y(Northing) coordinates of the the DIN by the distance equal to the plane number multiplier.
reference point define the position of this plane in space.
Example 3.1. Let us take a VBM with vertical planes with the
e. Non-vertical Non-orthogonal Sections. lowest elevation 2000.

For all other sections both Xmin and Ymin should be equal to For example take all the planes with the azimuth = 111 (See
zero. You must specify azimuth and dip for such a plane as well pictures).
as the position of the reference point.
Give the starting plane number 1.
DEFAULT ORIENTATION OF THE VBM FILE
The first plane has its reference point at
Default orientation of the VBM file automatically sets individual Xref = 10000, Yref = 12000 and Zref = Ymin = 2000.
plane orientations based on the plane number. Each VBM file
should have default orientation parameters set. Then any plane Choose DIN with azimuth 21, and plane number multiplier 200.
without individual orientation will be positioned in 3-D space
Then the plane number 5 will have reference point at:
based on the default orientation and the plane number.
X-ref = 10000 + (5-1) * 200 * sin (21) = 10286.7
Y-ref = 12000 + (5-1) * 200 * cos (21) = 12746.9
Z-ref = 2000.

Revised: 22-August-01 Page TECVBM-3

 MineSight®
VBM - TECHNICAL SECTION Proprietary Software: Mintec, inc.

The point on the VBM section number 5 with planar coordinates ENTERING INDIVIDUAL ORIENTATION DATA.
Xpln=500 and Ypln = 2500 will be located in 3-dimensional
space at the point: You should enter individual orientation data for planes while
entering VBM data from the VBM ready ASCII file.
X = 10286.7 + 500 * sin (111) = 10753.5
Y = 12746.9 + 500 * cos (111) = 12567.7 The orientation data in the VBM ready file should be organized
Z = 2500. in the following way: Each feature should be preceded by a
header line containing Plane number, Feature code, and optional
orientation data (X-ref, Y-ref, Z-ref, Azimuth and Dip) of the
plane. The header line is followed by a series of lines containing
the coordinates of the feature points, terminated by a line with a
pair of zeros.

Plane Feature
Number code X-ref Y-ref Z-ref Azimuth Dip
| | | | | | |
1.000 501 10000.00 12000.00 2000.00 111.00 -90.00
2204.30 2222.60
:
.
.00 .00

2.000 501 10071.67 12186.72 2000.00 111.00 -90.00

2492.60 2192.20
:
.
.00 .00
You will find general formulas in the Appendix at the end of 3.000 501 10143.35 12373.43 2000.00 111.00 -90.00
this section. :
.
NOTICE: RELATION BETWEEN INDIVIDUAL AND
DEFAULT ORIENTATION To enter data into a VBM file use the procedure [Link]:
Load VBM data. It is located in the VBM group with the Data
Individual orientation of a VBM section ALWAYS has Convert operations. You can also use an ASCII In function in
precedence over the default one. MineSight® has the ability to M650ED.
read VBM orientation automatically to some of the programs.
If you plan to use this feature please be sure that orientation CHECKING VBM ORIENTATION DATA
data is set correctly.
To check the default orientation of the VBM file use the Info -
INITIALIZING VBM FILE PCF File Editor in MS2 Compass.

To initialize a VBM file use the procedure [Link]: Initialize To check the individual orientations use the procedure
a VBM file 25. You will find it in the VBM group among the [Link]: Report VBM Index.
Initialize operations.
It is located in VBM group in Report operations. Choose to
CHANGING DEFAULT ORIENTATION. report orientation data and the orientation information will be
printed for each plane.
To set or reset the default orientation for an existing VBM file
use the procedure [Link]: Define Default Orientation. CREATING A VBM-READY FILE FROM A VBM FILE
You will find it in the VBM group with the Data Convert
operations. To get an ASCII dump of the VBM use the procedure
[Link]: Dump VBM to ASCII.
Important: If your new default orientation is vertical non-
orthogonal then Z-ref must be equal to Ymin. You should check You can find it in the VBM group among Data Convert
the Ymin value in your file using the Project File Editor in operations. You also can use the ASCII Out utility in M650ED.
MS2 Compass. If your VBM is not an orthogonal one do not forget to choose
the Dump Orientation option. MineSight® expects the VBM-

Page TECVBM-4 Revised: 22-August-01

MineSight®
Proprietary Software: Mintec, inc. VBM - TECHNICAL SECTION

ready file to have an extension .vbm. If you name an ASCII

output file according to this convention you will see this name
in the MineSight® file-chooser when importing VBMs.
However, you have an option to type any name you like.

APPENDIX

1. Given a VBM section with Xpln minimum equal to Xmin,

Ypln minimum equal to Ymin and individual orientation data
X-ref, Y-ref ,Z-ref, Azimuth = A, and Dip = D.

The position in 3-D space of the point with planar coordinates

Xpln and Ypln is determined by the formulas:

X = Xref + (Xpln -Xmin) * sin ( A ) - (Ypln - Ymin) * cos ( A ) * cos ( D )

Y = Y-ref + (Xpln - Xmin) * cos ( A ) + (Ypln - Ymin) * sin ( A ) * cos ( D )

Z = Z-ref - (Ypln - Ymin) * sin ( D

2. Given a VBM file with VBM reference point X0-ref, Y0-ref

and Z0-ref, starting plane number Nstart, Direction of Increasing
Numbering with Azimuth = Adin and Dip = Ddin, and a plane
number multiplier = P.

The reference point of a plane number N is determined by the

formulas:

X-ref = X0-ref + ( N - Nstart ) * P * sin ( Adin ) * cos ( Ddin )

Y-ref = Y0-ref + ( N - Nstart ) * P * cos ( Adin ) * cos ( Ddin )

Z-ref = Z0-ref + ( N - Nstart ) * P * sin ( Ddin )

Revised: 22-August-01 Page TECVBM-5

 MineSight®
VBM - TECHNICAL SECTION Proprietary Software: Mintec, inc.

VBM Data Entry

When digitizing data that is to be stored into a VBM file, several Without Coordinate Conversion
rules should be followed.
If the input data does not require coordinate conversion, the
Topography data should be in the following format:

The elevation of a contour line is the plane reference number Line 1 = Header line (integer free format)Plane
for the VBM. Topography is digitized so that uphill is to the NumberFeature Code (Optional Orientation)
right, air is to the left. Normally, the toe elevation of the
topography is digitized so that there can be interaction between Line 2 = Digitized coordinate data (1 point per line)East North
the digitized topography and a digitized or generated pit design. (real free format)

Pit Designs Line 3 = Trailer line (integer free format)0 0

The toe elevation of a bench is normally the plane reference One set of Lines 1-3 must be entered for each feature. The
number. Pits are digitized clockwise to enclose the mined area following is a sample of input:
to the right. The pits are digitized such that the pit number is the
VBM right side code. Pit designs must close. 4550 901
16293.20 13698.30
Underground Workings 15596.80 14105.50
15314.20 14326.70
Underground workings are digitized clockwise so that the mined 15045.20 14647.60
out area is enclosed to the right. 14947.00 14701.40
14632.00 14853.70
Naming Conventions 14417.00 15002.20
14233.40 15189.50
The following feature codes are recommended to describe certain 13567.30 15605.70
digitized features. 12825.90 15874.40
12517.40 15926.20
Code Features 12051.40 16054.20
001-499 Geologic features 11302.20 16383.30
501-599 Cutting features (faults) 10537.00 16542.70
601-799 Descriptive features 10090.30 16649.90
801-899 Mine designs 0 0
901-999 Topography 4500 901
16206.80 13230.60
15972.80 13409.90
Data Preparation 15453.90 13740.20
15066.30 14105.70
Each map to be digitized should be carefully prepared. The end 14762.70 14297.60
points of each feature should be marked and each feature labeled 14555.60 14385.70
with the correct code and the direction to digitize. 14350.90 14543.80
13840.20 14823.70
. .
. .

Page TECVBM-6 Revised: 22-August-01

MineSight®
Proprietary Software: Mintec, inc. VBM - TECHNICAL SECTION

With Coordinate Conversion

In this case, one set of Lines 4 through 6 must be entered for
If the input data requires coordinate conversion (i.e. points each feature.
digitized in inches should be converted to project limits), use
the following data lines: 0 0
10500 2600
Line 1 = Header line (integer free format) 10500 4600
14500 4600
0 0 14500 2600
4.0800 2.4700
Line 2 = Project coordinate lines (real free format; 4 required) 4.1500 12.4800
24.1500 12.4700
East North (lower left-hand corner point) 24.0800 2.4700
East North (upper left-hand corner point) 12750 001002
East North (upper right-hand corner point) 7.9300 2.4700
East North (lower right-hand corner point) 7.9600 3.0100
8.1200 3.8800
Line 3 = Digitized coordinate line (real free format; 4 required). 8.4100 4.9300
These are the digitized points corresponding with the points 8.6800 5.8300
entered on Line 2. 9.0700 7.0100
9.4400 8.0100
9.8700 8.9200
East North (lower left-hand corner point)
10.4000 9.5500
East North (upper left-hand corner point)
10.9200 9.8000
East North (upper right-hand corner point)
12.1100 10.1400
East North (lower right-hand corner point)
12.8200 10.3300
Line 4 = Header line (same as Line 1 under Without Conversion) 13.7400 10.5200
.
Line 5 = Digitized coordinate data (same as Line 2 under Without .
Conversion)
Handling data from two maps
Line 6 = Trailer line (same as Line 3 under Without Conversion)
If more than one set of converted data is required (i.e., data is
from two different maps or one oversized map), all of the data
from the first map should follow the initial set up lines (Lines
1-3). Then, following the trailer line (0 0) of the last feature, a
new set up must be entered (Lines 1-3). The data for the second
map must follow the second set up lines.

Revised: 22-August-01 Page TECVBM-7

 MineSight®
VBM - TECHNICAL SECTION Proprietary Software: Mintec, inc.

Rotated coordinates

To rotate VBM data, enter the first line as a map set-up flag (0
0). The first set of four lines are the four control points in rotated
values. The second four lines are the control points in real
coordinates. Follow the steps below:

1. Pick four control points on your map.

2. Calculate the rotated coordinate values of these same

points.

3. Edit the VBM file.

Enter the map set-up flag.

Enter the rotated coordinates of the four control points.
Enter the original coordinates of the four control points
in the same order as above.

4. Insert the rotation data at the beginning of the map data.

Line 1 = Map set-up flag

0 0

Line 2 - 5 = Rotated coordinates

ER1 NR1
ER2 NR2
ER3 NR3
ER4 NR4

Line 6 - 9 = Original coordinates

E1 N1
E2 N2
E3 N3
E4 N4

Line 10 = Plane number and feature code

1250 405406

Line 11 and on = Original digitized data

E1 N1
E2 N2
E3 N3
E4 N4
E5 N5
.
.

Page TECVBM-8 Revised: 22-August-01