M 600

MineSight
Proprietary Software: Mintec, inc. M600 - MINE MODEL OPERATIONS
MINE MODEL OPERATIONS
MineSight 600-Series Programs M602FS - Interactive Mine Model File Editing.
The MineSight 600-series programs allow you to create, update, M602FS allows interactive editing of the mine model data files
display and manipulate MineSight mine model files. Within (13, 14 or 15). Multiple items may be updated in a single run.
each model file, information required for reserve calculations
and mine design is stored on a block by block basis. Each block M603V1 - List Specified Data Items from the Mine Model File
may contain data such as grade, geology, ore type, percent below
topography, percent ore, grindability, etc. This program lists or dumps data items from a model file (File
13, 14 or 15). Output can be sent to a printer output file or an
The general features of the 600-series programs are: ASCII sequential file. The data can be output in integer format
(M610V1 format) or in real format (M610V2 format).
Store up to 500 items of information for each block,
such as rock codes, ownership codes, grades, etc. M606V1 - Plan Map (M122) of Mine Model Data
However, the individual programs can only access up
to 99 items. This program accesses the mine model files and prepares plot
commands for program M122V1. One or more values may be
plotted in a single run.
Allow up to 1000 columns by 1000 rows and up to 400
benches.
M607V1 - Contour Plot (M122) of Mine Model Data
Create or update the mine model with manually coded This program is used to create a contour map of a single item of
or digitized data. data from the mine model files. The program creates an M122
plot file.
Interpolate grades and/or surfaces in the model using
kriging or inverse distance weighting. M607V4 - Create Contour Data Using Triangulation
Represent geology or topographic features as 2-D This program is used to contour data and output either a plot
matrices. file or VBM input file.
Plot or print plan or section maps of the model. M608V1 - Classical Statistical Analysis of Model Data
This program summarizes mine model data using a frequency

Plot contour maps of data items in the model. distribution with the same format that is used in programs
M401V1 and M402V1 for drillhole and composite data.
Update topography as mining progresses.
M609V1 - Cross-Section (M122) of Mine Model Data
This program accesses the mine model files and prepares M122
Program Summaries plot commands for vertical cross-sections. Sections may be
oriented at any angle through the model.
M601V1 - Initialize a Mine Model File
M610V1 - Enter Data into a Mine Model File
This program is used to initialize the 3-D Block Model, Gridded
Seam Model and 2-D Surface Matrix Files prior to entry of This program is used to enter data into the mine model files
numerical values. M601V1 can also be used to reset existing to either create or update specified values. Only one value per
values in these files or copy levels within a 3-D or GSM model. block can be stored.
M601V2 - Create a Compressed Format Model File M610V2 - Enter Real Data into a Mine Model File
This program is used to create a compressed format model file This program is used to enter real data into the mine model files
(File 15 only). The compressed format is used when disk space either to create or update specified values. Several values for
is at a premium or when the regular model has large areas of each block can be stored in a single run.
no interest.
Revised: 09-December-10 Page 600-i

MineSight
M600 - MINE MODEL OPERATIONS Proprietary Software: Mintec, inc.
M612RP - Special Project Calculations for Mine Model Files M620V1 - Inverse Distance Weighting Interpolation (Standard
Version)
This program accesses a MineSight routine to perform
arithmetic calculations using RPN (Reverse Polish Notation) This program uses the sorted composites in File 8 to interpolate
logic specified in the run file. Calculated values may be stored values into the mine model using inverse distance weighting to
into File 13 or 15. the nth power. Geological zones are honored during interpolation.
M612SM - Surface Generation M620V2 - Inverse Distance Weighting Interpolation (Octant

Version)
This program will calculate and store elevations into a File 13
or 15 using one of several different methods. This program uses a similar interpolation scheme to M620V1.
However, it uses an octant selection method to limit the number
M612V1 - User Interface for Mine Model Files (Benches) of composites for interpolation. The n closest values in each
octant or quadrant around the block are used.
This program accesses a user-coded FORTRAN subroutine for
special calculations and reports from the mine model files. The M621V1 - Trend Plane Search Interpolation
model is accessed horizontally by bench. Calculated values may
be stored into the model. This program uses a similar interpolation scheme to M620V1.
However, the search is along the dip and strike of a trend plane
M612V2 - User Interface for Mine Model Files (Section) specified by a mine model code.
This program accesses a user-coded FORTRAN subroutine for M624IK - Multiple Indicator Kriging Technique
special calculations from the mine model files. The model is
accessed vertically by section. Calculated values may be stored This program is used to interpolate block grades using multiple
into the model. indicator kriging (MIK).
M615V1 - Compute Block Codes from Digitized Plan M624MIK - Multiple Indicator Kriging Technique with the
Boundaries GSLIB routine
This program computes and stores block codes in the mine model This program is a special version of M624IK to compute block
from digitized plan geology. grades using multiple indicator kriging, with the GSLIB routines.
M615V2 - Compute Block Codes from Digitized Section M624V1 - Kriging Interpolation Technique
Boundaries
This program is used to interpolate block grades using ordinary,
This program computes and stores block codes in the mine model lognormal or universal kriging. A single or nested variogram
from digitized E-W section geology. may be used to derive the interpolation weights.
M617V1 - Add Mine Model Codes to Composite Data M625V1 - Gradient Interpolation Technique
This program assigns mine model integer codes to the composite This program uses gradients to neighboring points for weighting
Data Files. the sorted composites during interpolation of mine model values.
M618V1 - Correlation Analysis of Model Data M630V1 - Load 2-D Surface File (File 13)
This program calculates siple bi-variate statistics and generates This program is used to load topography or other surface grid
scatter graphs and histograms of model data data into File 13. The program can also be used to update File 13.
M619V1 - Cumulative Distribution Analysis of Model Data M633V1 - Add Topography Percent to the Mine Model
This program is used to create an M122 plot file of the cumulative This program uses the 2-D Surface File (File 13) to determine
distribution versus grade from model data (cumulative the percentage of each block that is below the ground surface
probability plot). and stores this percent in the mine model.
Page 600-ii Revised: 09-December-10

MineSight
M635V1 - Create a Digital Terrain Model M600-Technical Section

This program will create a Digital Terrain Model from an ASCII Concepts of Geologic Items
file of input data points.
Model Rotations
M636V1 - Grid a Digital Terrain Model
Technical Considerations for Interpolation
This program will calculate the elevation at grid points that fall
within the limits of a DTM created by M635V1. Rotation Parameters for Modeling and Variograms
M637V1 - Cross Section Thru a DTM Sub-blocked Model Data Access
M637V1 will produce plot commands for a section line through Writing MineSight User Subroutines
a Digital Terrain Model (DTM). A DTM is a binary file that must
first be created using program M635V1. Useful COMMON BLOCK Variables
M639V1 - Generate Block Partials Between Two Surfaces
This program is used to generate block partials between two

surfaces in File 13.
Mine Models
A mine model is used to divide a deposit into units small enough
MSB2PR - Block Values from Sub-Block Data
to give an adequate representation of reality for mining purposes.
MSB2PR calculates full block values from sub-blocks and stores A matrix, or grid, is used to define the units of a mine model.
the result into the 3D block model. There are two basic mine models within MineSight:
MSCS - Conditional Simulation 3-D Block Model
MSCS computes conditionally simulated estimates for 3D grid Gridded Seam Model
points using composite or blasthole data information.
The 3-D Block Model (File 15) consists of a three-dimensional
MSPCS - Conditional Simulation Post Processing grid of blocks with all blocks having the same lateral dimensions
(typically 50 to 200 feet on a side). The vertical height of all
MSPCS performs statistical analysis of results from multiple blocks on a given bench is the same, although other benches
conditional simulation runs. may have different heights. The block height is usually specified
to conform to the proposed bench height. The lateral block
MSUC - Uniform Conditioning dimensions are often specified to be compatible with standard
map scales. However, these lateral dimensions must adequately
This program is used to compute recoverable reserves based represent the grade value distribution. Each 3-D block usually
on kriged estimates of the blocks or panels using a change of contains one type of material (i.e., ore or waste). The 3-D Block
support model. Model is used for large, disseminated deposits, such as base
metals, and for some uranium deposits.
ELLIPSE2MS - Ellipse to MineSight
The Gridded Seam Model (File 15) consists of a two-dimensional
This program is used to create a debug ellipsoid for viewing in
grid of blocks for each seam in the deposit with all blocks having
MineSight.
the same lateral dimensions. Each unit of data (grid point) of
a seam contains geometric and grade items with the minimum
being thickness and elevation. Other geometric parameters
that may be stored are: internal waste lengths, depth from
surface, overburden thickness, etc. The Gridded Seam Model
is frequently used for coal deposits, but can be used for other
deposits such as clays, mineral sands, tar sands, etc.
Revised: 26-Dec-13 Page 600-iii

MineSight
The minimum amount of data that should be stored in each block 2-D Surface File. The default item is the topography, but you
of a 3-D Block Model is: can also store the elevations of different subsurfaces.
At least one grade value Data can be stored in File 13 by several different methods.
The percent of the block below surface Convert digitized contours into grid values
A type code to classify material in reserve calculations Manually code grid values
Interpolate 2-D point data to a grid
The minimum amount of data that should be stored for a GSM is:
2-D topography data in File 13 can be loaded into the 3-D Block
Seam thickness Model as a percent topography code. File 13 data can also be
Seam elevation contoured and can be used to clip pits. The file is also important
in the moving cone pit design program.
There are several steps that must be performed to create a mine
model. The possible types of information that can be stored in a mine
model are geological, mineralogical, metallurgical, geometrical,
1. Formulate the model; define the problem geostatistical, production and financial.
Determine the exact results that are to be produced during The types of information that are stored in File 15 for metal,
the mine design, scheduling and financial portions of the coal and uranium include:
analysis. This will provide a reasonable guide to the detail
to be incorporated into the mine model. Geological, mineralogical & metallurgical information
Decide on the procedures to be used to handle the geologic Deposit structures (faults, formations, zones)
parameters and the interpolation of grades into the mine Lithology and alteration types
model. Ore types (sulfide, oxide, mixed, enriched)
2. Create the mine model file 3-D distribution of values
Set up the mine model descriptors in the PCF using M102TS. Base metal grades
Suggestions on items to be included are found in the M102TS Coal quality parameters
documentation. Radiometric values
Production grades or values
Initialize the mine model file using M601V1.
Geometrical and relative information
3. Store the geologic codes to be used during interpolation of
mine model grades using M610V1, M611V1, M612V1 or Elevations and thickness of seams
one of the other programs in the 610 subseries. Area, lease or property subdivisions
Interpolation rings and number of composites
Percent of block below surface topography
4. Establish a topographic surface
Create the 2-D surface topography file (File 13) with Physical deposit information
M630V1 and add topo percent to each block with M633V1.
Specific gravity
Internal waste thickness or percentage
5. Project grade values into unsampled areas True thickness of seams
Interpolate model grades using M620V1, M620V2, M621V1
or M624V1. Geostatistical information
Trend information
6. Verify the mine model Estimation errors
Calculate statistics with M608V1, plot cross-sections with Calculations for individual projects
M609V1, plot bench plans with M606V1, or plot contour
maps with M607V1. Equivalent grade
Relative in-situ value
Another file that is useful in the creation of the mine model is In-situ stripping ratio
the 2-D Surface File (File 13). Several items can be stored in the
Page 600-iv Revised: 26-Dec-13

MineSight
The following table shows an example of typical items to

beincluded for metal projects using a 3-D mine model.
ITEM LABEL MIN MAX PRECISION
1 ORTYP 0.00 5.0 1.000

2 TOPCT 0.00 100.0 1.000
3 ZONE 0.00 5.0 1.000
4 I-TCU 0.00 2.0 0.001
5 P-TCU 0.00 2.0 0.001
6 RCU-1 0.00 2.0 0.001
7 RCU-2 0.00 2.0 0.001
8 RINGS 0.00 625.0 25.000
9 #COMP 0.00 25.0 1.000
10 GEOL 0.00 5.0 1.000
11 EQUIV 0.00 4.0 0.001
12 MOS2 0.00 0.5 0.001
13 MINED 0.00 1.0 1.000
14 OVBD 0.00 100.0 10.000
15 EXTRA 0.00 250.0 1.000
where
ORTYP = ore type for reserve calculations (M711)

TOPCT = % below topo for reserve calculations (M711)
ZONE = geologic zone code
I-TCU = interpolated total copper grade
P-TCU = polygonal total copper grade
RCU-1 = simple interpolation for recoverable copper
RCU-2 = trend interpolation for recoverable copper
RINGS = relative distance, mid-block, closest composite
#COMP = number of composites used in interpolation
GEOL = geologic rock type
EQUIV = equivalent grade of block (RCU-1 & MOS2)
MOS2 = interpolated molybdenum grade
MINED = code to indicate whether or not block was mined
OVBD = relative % of block below overburden surface
EXTRA = extra item to fill up word #3
The following table shows an example of typical items to be

included for coal projects using a Gridded Seam Model.
ZTOP = top of seam

ZBOT = bottom of seam
THICK = seam thickness
BTU = BTU value of coal
SULF = sulfur content of coal
MOIST = moisture content of coal
ASH = ash content of coal
BLK% = percent within outcrop
PRTNG = seam parting
OVBD = seam overburden
EXTRA = extra item
Revised: 26-Dec-13 Page 600-v

MineSight
Page 600-vi Revised: 09-December-10

MineSight is a registered
trademark of Leica Geosystems AG. M601V1 - INITIALIZE A MINE MODEL FILE
M601V1 INITIALIZE A MINE MODEL FILE
PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M601V1 is used to initialize the model files prior to entry of
numerical values. M601V1 can also be used to reset existing Initialization
values in these files or to copy levels within a 3-D or GSM model.
Each data item of the mine model (File 14 or 15) or the 2D
Model files are the 3-D Block Model and Gridded Seam Model surface matrix (File 13) must be initialized before running any of
(File 15s), the GSM Summary File (File 14) and the 2-D Surface the 600-series. This initialization is a two or three step process.
Matrix File (File 13).
1. Set up the item descriptors with M102TS or M102V1.
2. Run M601V2 if you are creating a compressed file.
3. Use M601V1 to fill the file with default values.
PROGRAM FLOW DIAGRAM Each data item may be set to a specific value or left undefined.
RUN FILE: MineSight can determine when a value has never been entered
so that blocks with actual zero values can be distinguished from
blocks that have undefined values.
- PUT item labels
- Initial item values Some initial values for common model items are:
- File specifications
percent topography - initialize to 100%

rock types - initialize to the majority type
percent mined - initialize to zero
INPUT: CALCS: A model is initialized in terms of full benches/levels only.
Therefore, IOP4-11 are not used in initialization. Normally
- PCF - Create a new file IOP2 and IOP3 are not entered for File 15 mine models or File
- Mine Model File to -OR- 13 surface matrix files.
initialize (File 13, 14 - Reset existing items
or 15) -OR-
- Copy levels within a file Copy/Reinitialization
M601V1 can be used to copy levels within a model. New benches

are initialized as the copy is done. Set IOP2 and IOP3 to the
OUTPUT: new benches and use IOPs 4-7 to specify the copy commands.
- Updated Model File Reset

- Printer Output File
Specify RUN=RESET and PUTnn=label1 . . . labeln to reset
some existing values in a model or topo file without affecting the
others. Only the items listed in the PUTnn statement are reset.
Specify IOP4 and IOP5 for the benches to be reset; there are no
defaults for these IOPs. Use IOP8-11 to reset limited areas in a
model. IOP2 and IOP3 cannot be used for reset.
After the mine model file has been initialized, create geologic
and other descriptive codes to control the interpolation and
reserves calculations. Then run the 620-series to calculate grades
or quality parameters.
Revised: 12-August-14 Page 601-1

M601V1 - INITIALIZE A MINE MODEL FILE trademark of Leica Geosystems AG.
Page 601-2 Revised: 12-August-14

M601V1 - INITIALIZE A MINE MODEL FILE
RUN FILE OPERATION

1. NAMES LINE (must be the first line entered)
MEDS-601V1 10=filename 15 (or 14 or 13)=filename;

MEDS-601V1 3=filename
where
MEDS-601V1 (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
15 = the name of the MINE MODEL FILE -OR-
14 = the name of the GSM SUMMARY FILE -OR-
13 = the name of the 2-D SURFACE 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)
RUN = RESET(for resetting values only; do not use for initializing or copying)
NOTE: If you are using the RESET option, use IOPs 4-11 to define which part of the model will be reset.
IOP2 = M15 FIRST BENCH/LEVEL TO INITIALIZE (default=next bench/level after the last one initialized)
IOP3 = N15 LAST BENCH/LEVEL TO INITIALIZE (default = NZ for File 15 and 1 for Files 13 & 14)
NOTE: If you are running M601V1 to initialize a mine model file or to copy benches to new areas of the model,
use IOPs 2 and 3 to define which benches to initialize. These IOPs cannot be used for RESET.
You must initialize entire benches, not just a few rows in a bench. Also, if you want to initialize a certain
bench, all prior benches must be initialized, either previously or in the current run. For example, if you want to
initialize bench 33 and benches 1 through 21 have been initialized in a previous run, then benches 22 through 33
must be selected in the current run. IOP2 will default to 22 in this case.
IOP4 = STARTING BENCH TO BE COPIED FROM OR FIRST BENCH TO RESET (no default)
IOP5 = STARTING BENCH TO BE COPIED TO OR LAST BENCH TO RESET (no default)
NOTE: If RUN=RESET, these IOPs must be used to specify the first and last benches to be reset. Otherwise,
they are used as copy commands.
IOP6 = # BENCHES TO COPY (default=1)
IOP7 = OPTIONAL # TIMES TO REPEAT THE COPY
IOP8 = FIRST ROW TO RESET (default=1)

IOP9 = LAST ROW TO RESET (default=NY)

IOP10 = FIRST COLUMN TO RESET (default=1)

IOP11 = LAST COLUMN TO RESET (default=NX)
IOP12 = 1 PREVENT ACTUAL RESET

NOTE: Use for testing.
IOP13 = 0 DO NOT RESET VALUES OF UNSPECIFIED ITEMS (default)

= 1 RESET VALUES OF UNSPECIFIED ITEMS TO UNDEFINED
NOTE: IOP13=1 will reset all unlisted PUT15 items to undefined values. This option applies only if RESET =
RUN; otherwise IOP13 has no effect.
PUTnn = ITEMS TO BE INITIALIZED OR RESET (optional)

= label1 label2 ... labeln
NOTE: If no items are specified, no values will be assigned in this run. Values can be assigned at a later date
using the RUN=RESET command.
PAR1 = value1 value2 ... valuen

NOTE: Values are actual initial values to be assigned to label1, etc. If value = -2, item will be set to undefined.
I-O = 1 LIST INTERNAL FILE INFORMATION
END

M601V1 SAMPLE RUN FILE #1

MEDS-601V1 10=SAMP10.DAT 15=SAMP15.DAT 3=RPT601.LA
** INITIALIZE THE 3-D 100*100 BLOCK MODEL; SET DEFAULT VALUES FOR CODE AND TOPO
USR = ABC
I-O = 1
IOP2 = 00 / USE DEFAULTS; INITIALIZE COMPLETE MODEL
COM SAMP15.DAT ITEMS TO BE INITIALIZED:

PUT15 = CODE TOPO
PAR1 = 0. 100.
COM ALL BLOCKS WILL HAVE CODE = 0
COM ALL BLOCKS WILL HAVE TOPO = 100
%COM ALL OTHER ITEMS WILL BE UNDEFINED
END

MEDS-601V1 10=SAMP10.DAT 13=SAMP13.DAT 3=RPT601.LB
** INITIALIZE 2-D SURFACE TOPOGRAPHY ELEVATIONS MATRIX
USR = ABC
I-O = 1
IOP2 = 1 1
COM NOTE THAT FILE 13 ONLY HAS ONE 2-D SLICE.
COM NOTE THAT YOU DO NOT HAVE TO INITIALIZE ANY ITEMS

COM DURING AN M601V1 RUN. IN THIS CASE, ALL ELEVATIONS AND
COM OTHER ITEMS WILL BE UNDEFINED.
END


MEDS-601V1 10=SAMP10.DAT 15=SAMP15.DAT 3=RPT601.LC
** COPY EXISTING SAMP15.DAT BENCHES 20-21 TO 41-42
USR = ABC
I-O = 1
IOP4 = 20 / STARTING BENCH TO COPY FROM

IOP5 = 41 / STARTING BENCH TO COPY TO
IOP6 = 2 / # BENCHES TO COPY
IOP7 = 1 / # TIMES TO REPEAT THE COPY (1=default)
COM BENCH 20 WILL BE COPIED TO BENCH 41;

COM BENCH 21 WILL BE COPIED TO BENCH 42.
END

MEDS-601V1 10=SAMP10.DAT 15=SAMP15.DAT 3=RPT601.LD
** COPY EXISTING SAMP15.DAT BENCH 20 TO 41 & 42
USR = ABC
I-O = 1
IOP4 = 20 / STARTING BENCH TO COPY FROM

IOP5 = 41 / STARTING BENCH TO COPY TO
IOP6 = 1 / # BENCHES TO COPY
IOP7 = 2 / # TIMES TO REPEAT THE COPY (1=default)
COM BENCH 20 WILL BE COPIED TO BENCH 41;

COM BENCH 20 WILL BE COPIED TO BENCH 42.
END


MEDS-601V1 10=SAMP10.DAT 15=SAMP15.DAT 3=RPT601.LE
** RESET THE 3-D 100*100 BLOCK MODEL
RUN = RESET / READ SAMP15.DAT & ZERO VALUES FOR CODE

USR = ABC
I-O = 1
IOP4 = 1 40 / RESET ENTIRE MODEL
COM SAMP15.DAT ITEM TO BE RESET:

PUT15 = CODE
PAR1 = 0.
COM ALL BLOCKS WILL HAVE CODE = 0

COM ALL OTHER ITEMS WILL REMAIN AS IS
END

MEDS-601V1 10=SAMP10.DAT 15=SAMP15.DAT 3=RPT601.LF
** RESET A SUBSET OF THE 3-D BLOCK MODEL **
RUN = RESET / READ SAMP15.DAT & SET GEOL TO UNDEFINED FOR A CERTAIN AREA
USR = ABC
I-O = 1
IOP4 = 12 12 / BENCHES TO RESET
IOP8 = 21 30 21 30 / ROWS & COLS TO RESET
COM SAMP15.DAT ITEMS TO BE RESET:

PUT15 = GEOL
PAR1 = 2 / SPECIAL VALUE TO SET GEOLS = UNDEFINED
COM SPECIFIED BLOCKS WILL HAVE GEOL UNDEFINED

END


(Reset values instead of initializing)
MEDS-601V1 10=SAMP10.DAT 15=SAMP15.DAT 3=RPT601.LF

** RESET LITHO VALUE FOR ALL LEVELS ALL ROWS, AND ALL COLUMNS **
RUN = RESET / READ SAMP15.DAT & RESET LITHO TO UNDEFINED FOR A CERTAIN AREA
USR = ABC
I-O = 1
IOP4 = 1 40. / FIRST AND LAST BENCHES TO RESET
NOTE: IOP5 must have value, 0 (zero) is not a default.
COM SAMP15.DAT ITEMS TO BE RESET:

PUT15 = LITHO
PAR1 = -2 / SPECIAL VALUE TO SET LITHO (-2 = UNDEFINED)
COM SPECIFIED BLOCKS WILL HAVE LITHO UNDEFINED

END
HOW TO DEBUG AN M601V1 RUN
1. ?M601V1: ERROR. You have selected IOP2=xx. This exceeds

the total number of benches yy.
The first bench number you are trying to initialize exceeds the total number of benches in your project. Make sure that IOP2
and IOP3 specify bench numbers in the range of benches spanned by your PCF.
2. ?M601V1: ERROR. You have selected IOP2=0. This corresponds to

BENCH xx which exceeds the total number of
benches yy. This file might already be initialized.
You let IOP2 default so M601V1 computed the next bench to initialize based on information in the PCF. Since this computed
bench exceeds the total benches, its likely that this file is already initialized.
3. ?M601V1: ERROR. The first bench to initialize, xx, exceeds

the last bench to initialize, yy.
Check that IOP2 is no larger than IOP3. If you allowed one of these IOPs to default, try putting the actual values in them.
4. ?M601V1: ERROR. You have chosen to initialize BENCH xx.

According to the PCF, this file has been initialized thru
BENCH yy. These two values MUST correspond.
Since the file has been previously initialized through BENCH yy, then the next set of benches you initialize MUST begin with
BENCH yy+1. If you really need to re-initialize a lower BENCH xx, then use the RESET option.
If you get this message while trying to initialize a compressed File 15, remember that if, for example, bench 10 is defined and

initialized in your model and the next defined bench is 20, which is not initialized, then to initialize bench 20, you MUST set
IOP2=11.
5. %M601V1: WARNING. BENCH xx has already been partially

initialized. The ENTIRE bench is now being re-initialized.
It might happen that part, but not all, of a bench has been initialized. If this is the case, then the partially initialized bench will
be completely re-initialized.
6. ?M601V1: ERROR. You are attempting to COPY part of your model.

However, the IOPs you selected are NOT logically consistent.
For example, if IOP4=1, IOP5=22, IOP6=10, IOP7=3
First level from which to copy: 1

Last level from which to copy: 10
First level to which to copy: 22
Last level to which to copy: 51
Last level in the MODEL file: 40
Last level previously initialized: 20
Make sure the levels from which you are copying have already been initialized. In the above case, the model has been initialized
through bench 20 so copying benches 1 through 10 is okay.
If you are copying to an uninitialized bench, it must be the next bench after the last previously initialized one, because there
cannot be uninitialized benches existing between initialized ones. In the above example, level 21 needs to be initialized before
level 22 can be.
The last level copied to must be no greater than the last bench in the model file. Trying to perform the copy three times (IOP7)
would make bench 51 the last bench written and that is greater than the total number of benches in the model.
Make sure that the set of benches being copied from does not overlap the benches where they are supposed to be copied. For
example, you cannot copy benches 510 onto benches 49.
7. %M601V1: WARNING. Values outside the ITEM range are being limited.
# RESET values above maximum = xx
#RESET values below minimum = yy
Do you want to CONTINUE anyway? (Y or N)
You have tried to initialize some ITEMs to values outside of their range. If you continue, the initializing value will be limited
(either above or below) by the ITEM range.

8. ?M601V1: ERROR. Insufficient disk space

You are attempting to initialize a model of xxx bytes. The specified drive, C:, has yyy bytes total space of which zzz
bytes are free.
Possible solutions are:

1. Delete unnecessary files
2. Change the ACCT to another disk, (M104TS)
3. Reduce the number of items stored in the model.
4. Redefine PCF mins and maxs to reduce model blocks
If you are running on a PC, M601V1 will check the available disk space to make sure your model file will fit.
9. ?M601V1: ERROR. You are trying to initialize an undefined File 15.

For a compressed MODEL, you MUST run M601V2 to define your MODEL
limits before initializing with M601V1.
If you have a compressed File 15, as selected in M102TS/V1, you must define the blocks to be included in your model (M601V2)
before you can initialize them.
10. ?M601V1: ERROR. You are attempting to RESET an uninitialized part of the model
IOP4=xx IOP5=yy
Last Bench initialized = zz
Make sure the range of benches you want to RESET (in this case xx to yy) is in the range of previously initialized benches (1
to zz). You can only RESET benches that have already been initialized.
11. ?M601V1: ERROR. You have not selected any items to RESET.
To use the RESET option, you must specify a PUTnn item.
12. Also check the MINESIGHT error messages in the Appendix.

MineSight
Proprietary Software: Mintec, inc. M601V2 - CREATE A COMPRESSED FORMAT MODEL FILE
M601V2 CREATE A COMPRESSED FORMAT MODEL FILE

M601V2 is used to create a compressed format model file (File M601V2 is only used to limit your model to an area of interest.
15 only). The compressed format is used when disk space is at M601V1 must be run to initialize the model, then other 600-
a premium or when the regular model has large areas of no series programs can be used to load and interpret the data.
interest.
Be sure to include all areas of interest in the model for each run
of M601V2. Once a model has been created it can only be
overwritten by the next run. No levels or rows can be added
PROGRAM FLOW DIAGRAM after the first run.
Before running M601V2, set up the item descriptors for the file
with M102TS or M102V1. Be sure to specify the compressed
format option.
After your File 15 is created with M102TS or V1 and M601V2,

it must be initialized with M601V1 before the data can be used
by any other program.
RUN FILE
- File specifications
- Area specifications
INPUT: CALCS:
- PCF - Create a model file from

- File 15 area specifications
OUTPUT:
- Empty compressed
format model file
Revised: 6-June-01 Page 601-11

MineSight
M601V2 - CREATE A COMPRESSED FORMAT MODEL FILE Proprietary Software: Mintec, inc.
Page 601-12 Revised: 6-June-01

MineSight
Proprietary Software: Mintec, inc. M601V2 - CREATE A COMPRESSED FORMAT MODEL FILE
M601V2 - CREATE A COMPRESSED FORMAT MODEL FILE
RUN FILE OPERATION

MEDS-601V2 10=filename 15=filename 19=filename;

where

15 = the name of the MINE MODEL FILE
19 = the name of the AREA SPECIFICATION FILE (optional)
3= the name of the PRINTER OUTPUT FILE
END
4. AREA SPECIFICATION LINES (free-field format)
IZ1 IZ2 IR1 IR2 IC1 IC2

where
IZ1 = Starting level number

IZ2 = Ending level number
IR1 = First row in each level IZ1 to IZ2
IR2 = Last row in each level
IC1 = First column in each row IR1 to IR2
IC2 = Last column in each row
The above Area Specification Line can be repeated as often as necessary to define all areas of interest in the model. Area specifications
can overlap; however, once a level is completed, any defined row cannot be redefined. For example:
1 6 1 50 25 75
5 7 1 45 30 80
Overlap on levels 5 and 6. The result would be the largest definition for rows 1 to 45 where columns 25 to 80 would be defined.

MineSight
M601V2 - CREATE A COMPRESSED FORMAT MODEL FILE Proprietary Software: Mintec, inc.
If the following line were encountered:
1 1 8 10 25 90
an error would be generated since rows 1 to 50 were defined on the first Area Specification Line. Since the second line specifies level
5 to start, the program assumes that rows 1 to 50 are completely defined on levels 1 to 4. Rows 51 and up can be defined later if
desired; however, this would result in a less efficient, fragmented model. If 19= is used on the Names Line, then area specification
data is read from an external file, else the data is assumed to follow the END line.
NOTE: An Area Specification File, containing area specification lines in the proper format, can be created
using M667V1. However, data generated by M667V1 may need to be sorted by bench (top
downward) prior to using it in M601V2.
M601V2 SAMPLE RUN FILE

* CREATE A COMPRESSED MODEL
USR = ABC
END
1 6 1 50 25 75

1. Check the MINESIGHT error messages in the Appendix.

MineSight
Proprietary Software: Mintec, inc. M602FS - INTERACTIVE MINE MODEL FILE EDITING
M602FS INTERACTIVE MINE MODEL FILE EDITING

M602FS allows interactive editing of the mine model data files Before you start M602FS, make a backup of the file you intend
(13, 14 or 15). Multiple items may be updated in a single run. to edit. Once you have updated the file, there is no way to
restore the original.
M602FS can be used to update any of the mine model files (13,
PROGRAM FLOW DIAGRAM 14, or 15). The mine model file must be initialized with M102TS
and M601V1 before M602FS can be run. In order to have a
RUN FILE: basis for making changes, you should make a printer map of a
- Interactive keyboard small area containing the value(s) to be updated. Changes can
entry be marked on this map prior to execution of M602FS.
M602FS is also useful for displaying individual block values

for checking purposes.
If many changes need to be made, consider using M610V1.
M602FS modifies items in selected columns in a specific row

INPUT: CALCS: on one bench. M602FS can handle 20 items on the PC or 99
- PCF - Edit model files
items on a Sun computer.
- Mine model file (13, 14 or 15)
(13, 14 or 15) Always list the updated portions of the file to ensure that the
modified values have been properly stored.
OUTPUT:
- Updated mine model file

MineSight
M602FS - INTERACTIVE MINE MODEL FILE EDITING Proprietary Software: Mintec, inc.

MineSight
M602FS - INTERACTIVE MINE MODEL FILE EDITING
SELECT FILE AND ITEMS TO EDIT

At the system prompt, type MEDS M602FS to begin (on a PC, then press the <ENTER> key).
Enter the entire PCF name:

e.g. METL10.DAT
OR the first four letters:
e.g. METL
If the requested file is not found, a message is

displayed and you can choose again or exit.
Select the file type that you wish to edit.

MineSight
If there is more than one file with this reference

number, you must select one to edit from the list
of files that will appear. Confirm your selection
by pressing the <ENTER> key or enter the correct
filename.
All the items in the selected file are listed.
Select the ones that you wish to edit.
When selecting the items to edit, the selection order

is significant. At the time the actual data is being
edited, the items will be displayed in the order in
which they were selected.
INS-Tag
Position the cursor on the item that you wish to edit and press the INS key to select it.
DEL-Untag
Use this key to cancel a selected item.
F1-Continue
Proceed to choosing the bench, row and columns to edit.
This screen appears when you try to continue

without selecting items.

MineSight
CHOOSE THE BENCH, ROW AND COLUMNS TO EDIT
When selecting the bench/seam to edit, you can either

specify the bench/seam number or the bench elevation/
seam name. The corresponding value will be displayed.
Rows and columns work in a similar manner.
F1-Continue
Proceed to editing the file.
F2-Exit
Leave M602FS and return to the operating system.
F3-Reselect items
Return to the item selection panel to choose different items or to change the order of the items.
F4-Utilities
Go to the Utilities Menu where you will have these choices:
Display items from MineSight files
Change the MineSight screen colors

MineSight
EDIT THE FILE
Use the arrow keys and the Pg Up, Pg Down, Home

and End keys to move through the items.
F1-Continue
Go to the bench selection panel to choose a different bench, row or set of columns.
F2-Store
Store the changes made to the items.
F3-Missing
Mark an item as Missing. Formerly this value was displayed as a 1.
F4-Unset
Mark an item as Unset. Formerly this value was displayed as a 2.
Backspace Key
Toggle an information window at the top of the screen. The current items minimum and maximum values are displayed using the
appropriate number of decimal places (shown on the screen above).
If changes are made and not stored, this screen

appears in order to give you the opportunity to
store (save) your changes before continuing.

MineSight
HOW TO DEBUG AN M602FS RUN

Check the MineSight error messages in the Appendix.

MineSight

MineSight
Proprietary Software: Mintec, inc. M603V1 - LIST/DUMP SPECIFIED DATA ITEMSFROM MINE MODEL FILE
M603V1 LIST/DUMP SPECIFIED DATA ITEMS

FROM MINE MODEL FILE

M603V1 lists or dumps data items from a mine model file (File M603V1 is used to list or dump specified portions of a mine
13, 14 or 15). Output can be sent to a Printer Output File or an model file (File 13, 14 or 15). The data can be output to a Printer
ASCII sequential file. The data can be output in integer format Output File or an ASCII sequential file.
(M610V1 format) or in real format (M610V2 format).
The data can be output in two different formats. Integer format
(for M610V1 input) can only be dumped to an ASCII sequential
file*. Real format (for M610V2 input) can be dumped to an
PROGRAM FLOW DIAGRAM ASCII sequential file or listed in the Printer Output File.
RUN FILE: The data can be selected from the mine model file on the basis
of:
- Items to list
- Listing format
- Specified area to list Benches, rows and columns with an Area Specification
Line
Items with a GET line
Items can also be limited by the minimum and maximum values.

INPUT: CALCS: The output format will default for both integer and real output.
- PCF - Search mine model file However, you can specify an output format with an FMT1 line.
- Mine model file (File for area and items to list
13, 14 or 15) - List items in specified M603V1 is used most often to transfer information between
format computers using ASCII files or to transfer information between
MineSight files with different PCFs on the same computer.
* integer value = real value/precision
By default, block location is dumped by column/row/bench. You

OUTPUT: can also choose to dump by X/Y/Z or X/Y/Bench#. For File 13 or
GSM models, you can choose to dump the location by col/row, by
- ASCII file of data
X/Y, omitting the level #/Z value, or by X/Y/Seam#.
Revised: 27-July-09 Page 603-1

MineSight
M603V1 - LIST/DUMP SPECIFIED DATA ITEMSFROM MINE MODEL FILE Proprietary Software: Mintec, inc.
Page 603-2 Revised: 27-July-09

MineSight
Proprietary Software: Mintec, inc. M603V1 - LIST SPECIFIED DATA ITEMS FROM MINE MODEL FILE
M603V1 - LIST SPECIFIED DATA ITEMS FROM MINE MODEL FILE
RUN FILE OPERATION

MEDS-603V1 10=filename 15 (or 14 or 13)=filename 30= filename;

MEDS-603V1 19=filename 3=filename
where

30 = the name of the CROSS REFERENCE FILE (if IOP8=1)
19 = the name of the OPTIONAL OUTPUT FILE (required if IOP2=0)
USR = USER INITIALS (e.g., ABC)
IOP2 = -2 OUTPUT ONE GSF (FILE 13) ITEM IN M610V1 FORMAT

= -1 OUTPUT ONE GSF (FILE 13) ITEM IN M630V1 INPUT FORMAT
= 0 OUTPUT INTEGER DATA IN M610V1 FORMAT
= 1 OUTPUT REAL DATA IN M610V2 FORMAT (only if the first GETn item in the block has a value)
= 2 OUTPUT REAL DATA IN M610V2 FORMAT (if any GETn item in the block has a value)
= 3 OUTPUT REAL DATA SYSTEM FORMAT USING X/Y/Z COORDINATES (see IOP20)
NOTE: If IOP2 is less than or equal to 0, you must specify an output file on the Names Line as 19=.If
IOP2=1, 2 or 3, the output file is optional. If File 19 is not specified, output will go to the Printer
Output File. The output to the printer Printer Output file is always in M610V2 format.
IOP5 = DUMP X-OFFSET CONSTANT; ADD TO COL# (INTEGER)

IOP6 = DUMP Y-OFFSET CONSTANT; ADD TO ROW# (INTEGER)
IOP7 = DUMP Z-OFFSET CONSTANT; ADD TO BENCH# (INTEGER)
NOTE: For example, if IOP5=10, the column item in the output will be increased by 10 (i.e., column 1
will become column 11).
IOP8 = 1 OUTOUT AN IGP CROSS REFERENCE FILE FOR N-S SECTIONS
IOP10 = 0 DUMP ONLY ITEMS PROVIDED IN THE GET ITEM LIST

1 DUMP ALL ITEMS (may use GET item list for ordering first few items)
IOP11 = TOTAL # OF COLUMNS OCCUPIED BY GET ITEMS(default=8 * # items, Max=64)
NOTE: If IOP2=0, IOP11 can be used in conjunction with FMT1 to reduce the size of the output file. For
example, if you want to list two items in I5 format, then IOP11=10.
Revised: 25-February-11 Page 603-3

MineSight
M603V1 - LIST SPECIFIED DATA ITEMS FROM MINE MODEL FILE Proprietary Software: Mintec, inc.
NOTE: If IOP2=0, IOP11 can be used in conjunction with FMT1 to reduce the size of the output file. For
example, if you want to list two items in I5 format, then IOP11=10.
If FMT1 is not specified, then IOP11 will be computed to match the default format
If IOP2=-1, IOP11 is number of columns for output values. (default=10)
IOP12 = 0 DUMP LEVEL #/Z-VALUE (Default)

= 1 DO NOT DUMP LEVEL #/Z-VALUE (Only applicable if IOP2>0)
IOP13 = 0 NO BOUNDARY APPLIED

= 1 APPLY BOUNDARY USING:
CMD = INCL LOCPT FILE (To include point location file.)
Note: When using with 3D-rotated GSM file 15, or 3D-rotated files 13 and 14, you MUST specify
Z-coordinate model item by command:
CMD = ZCRD label-nn
IOP14 = 0 DO NOT OUTPUT ANY HEADER RECORDS (Default)

1 OUTPUT A SINGLE HEADER RECORD OF ITEM NAMES
2 OUTPUT FULL HEADER RECORDS (PATH, MODEL, ETC)
3 OUTPUT HEADER IN CSV FORMAT
NOTE: IOP14 is used only with IOP2 > 0
IOP15 = 0 DO NOT OUTPUT FILE IN CSV FORMAT (Default)

1 OUTPUT FILE IN CSV FORMAT
NOTE: 1) IOP15 is used only with IOP2 > 0.

2) Format statement is ignored when IOP15 = 1.
IOP20 = 0 IF IOP2=3, DUMP IN OCS FORMAT WITH TOE ELEVATION OF BLOCK

= 1 IF IOP2=3, DUMP IN X,Y,Z NON-OCS FORMAT AT MIDPOINT OF BLOCK
= 2 IF IOP2=3, DUMP IN X,Y, BLOCK# (or SEAM#) AT MIDPOINT OF BLOCK
IOP21 = 0 If IOP2 = 3, Dump project coordinates

= 1 If IOP2 = 3, Dump model coordinates
Note: To use IOP3 = 2, IOP21 = 0 combination for 3D-rotated GSM file 15, enter Z coordinate item
with CMD = ZCRD label-nn. (see also Note for IOP13)
PAR1 = MINIMUM VALUE OF CONTROLLING ITEM (first GET item; default=0.0)
PAR2 = MAXIMUM VALUE OF CONTROLLING ITEM (default = 999999.)
GETn = LIST OF ITEMS TO DUMP/LIST (maximum of 99 items)

For example: GET15 = T-CU MOLY ROCK or GET13 = TOPOG
Page 603-4 Revised: 8-December-11

MineSight
FMT1 = FORMAT FOR DATA OUTPUT (optional)
IF IOP2=-2 Default Format: (4I5,20F4.0)

IF IOP2=-1 Default Format: (3I6,10F8.1)
IF IOP2= 0 Default Format: (3I6,500F10.1)
IF IOP2= 3 Default Format: (I7,2F10.1,F8.1,500F10.3) unless the following also applies:
IF IOP12 > 0 Default Format: (2F10.2,500F10.3)
IF IOP12 < 1 and IOP20 = 1 Default Format: (3F12.2,500F10.3)
IF IOP12 < 1 and IOP20 = 2 Default Format: (2F12.2,I5,500F10.3)
When you are using IOP11, the repeat specification for the items format must be greater than or equal to the integer
quotient of 64/IOP11. For example, if IOP11=10, the repeat specification must be 6 or greater (64/10=6) and your
format statement would read:FMT1=(4I5,6(2I5)).
Optional data selection by RANGE, OMIT or TABLE

ITMn = label-nn RANGE min-value max-value
ITMn = label-nn OMIT min-value max-value
ITMn = label-nn TABLE IOPm IOPn
Optional Z coordinate item (for 3D-rotated GSM models or files 13 and 14)
CMD = ZCRD label-nn
END
4. AREA SPECIFICATION LINES
IZ1 IZ2
IX1 IX2 IY1 IY2
where
IZ1 = First bench (no default)

IZ2 = Last bench (default=Last Bench Initialized)
IX1 = First column (no default)

IX2 = Last column (default=NX)
IY1 = First row (no default)

IY2 = Last row (default=NY)
Revised: 8-December-11 Page 603-5

MineSight

MEDS-603V1 10=SAMP10.DAT 15=SAMP15.DAT 3=RPT603.LA;
MEDS-603V1 19=DAT603.OA
** DUMP SPECIFIED ITEMS FROM FILE 15 IN INTEGER FORMAT **
USR = ABC
IOP2 = 0 / 0=INTEGER OUTPUT. 1=REAL OUTPUT
IOP5 = 0 0 0 / X,Y,Z OFFSET CONSTANTS
COM* IF IOP2=0, SPECIFY IOP11 IF USING FORMAT TO SAVE SPACE
IOP11 = 16 / TOTAL # OF DIGITS OCCUPIED BY GET ITEMS FOR OUTPUT
PAR1 = .10 1.0 / MIN AND MAX VALUE OF CONTROLLING ITEM
GET15 = TCU-1 MO-1 DIST CODE
COM OUTPUT FORMAT IS OPTIONAL, BUT RECOMMENDED TO SAVE SPACE

FMT1 = (4I4,4(I5,I5,I4,I2))
I-O = 2
END
20 20 1 0 1 0 Benches, columns, rows
21 21 1 0 1 0
M603V1 SAMPLE OUTPUT FILE #1(For integer format, IOP2=0)
bench row col a col b Data for col a Data for col a+1 Data for col a+2
20
20 40 16 19 32 16 73 1 32 16 71 1 32 16 70...
20 40 20 23 32 16 73 1 42 21 73 1 42 21 71...
20 40 24 27 42 21 71 1 42 21 73 1 42 21 73...
20 40 28 31 42 21 70 2 42 21 71 2 42 21 73...
20 40 32 35 32 16 71 2 32 16 70 2 32 16 71...
20 39 14 17 16 8 61 1 18 9 63 1 19 9 63...
20 39 18 21 32 16 60 1 37 18 61 1 37 19 63...
20 39 22 25 38 19 61 1 42 21 60 1 42 21 61...
20 39 26 29 42 21 63 2 42 21 61 2 42 21 60...
20 39 30 33 37 19 63 2 37 19 63 2 36 18 61...
20 39 34 37 32 16 61 2 32 16 63 2 32 16 67...
20 38 13 16 14 7 50 1 14 7 51 1 17 8 54...
20 38 17 20 22 11 51 1 28 14 50 1 36 18 51...
20 38 21 24 38 19 54 1 39 19 51 1 40 20 50...
20 38 25 28 42 21 54 1 42 21 54 2 42 21 51...
. . . .
. . . .
If output is in integer format, values for several blocks will be written to each line of output. The number of blocks on each line is
dependent on the number of items and the format requested.
Page 603-6 Revised: 25-February-11

MineSight

MEDS-603V1 10=SAMP10.DAT 15=SAMP15.DAT 3=RPT603.LB;
MEDS-603V1 19=DAT603.OB
** DUMP SPECIFIED ITEMS FROM FILE 15 IN REAL FORMAT**
USR = ABC
IOP2 = 1 / 0=INTEGER DUMP, 1=REAL DUMP
GET15 = TCU-1MO-1DISTCODE
ITM1 = TCU-1RANGE0.11.0
COM* FOR IOP2=1, DEFAULT FORMAT IS (3I4,8F8.1)
FMT1 = (3I4,F8.2,F8.3,2F8.0)
I-O = 2
END
21 21 1 0 1 0
M603V1 SAMPLE OUTPUT FILE #2 (For real format, IOP2=1)

col row bench < Data for this block >
21 12 20 0.10 0.005 220. 1.

25 12 20 0.11 0.006 220. 1.
26 12 20 0.11 0.006 220. 1.
30 12 20 0.10 0.005 220. 1.
20 13 20 0.10 0.005 200. 1.
21 13 20 0.10 0.005 200. 1.
25 13 20 0.12 0.006 200. 1.
26 13 20 0.12 0.006 200. 1.
30 13 20 0.11 0.006 200. 1.
31 13 20 0.10 0.005 200. 1.
20 14 20 0.12 0.006 220. 1.
21 14 20 0.13 0.007 220. 1.
22 14 20 0.12 0.006 140. 1.
23 14 20 0.10 0.005 100. 1.
24 14 20 0.12 0.006 140. 1.
25 14 20 0.14 0.007 220. 1.
26 14 20 0.15 0.007 220. 1.
27 14 20 0.12 0.006 140. 1.
28 14 20 0.10 0.005 100. 1.
29 14 20 0.12 0.006 140. 1.
30 14 20 0.13 0.007 220. 1.
31 14 20 0.12 0.006 220. 1.
If output is in real format, values for one block per line are written to the output file.

MineSight

MEDS-603V1 10=F31610.DAT 15=F31615.DAT 3=RPT603.LC 19=IGPNS.DAT;
MEDS-603V1 30=IGPNS.PAR
** SETUP ASCII DATA FOR IGP SLICES **
USR = ABC
I-O = 0
IOP2 = 1 / 1=M610V2 FORMAT
IOP8 = 1 / 0=OUTPUT IGP N-S PARAMETER FILE
IOP9 = / 0=OUTPUT M650IP SLICES, 1=M830V1
GET15 = ORE% REM% NSR LENS DEN AU AG CU

GET15 = PB BA FE ZN
FMT1 = (3I4,20F10.3)
PAR1 = 1 / MIN VALUE FOR 1ST ITEM

PAR2 = 100 / MAX VALUE FOR 1ST ITEM
END
1. 45. 20. 22. 1. 48.
M603V1 SAMPLE OUTPUT FILE #2 (For real format, IOP2=1)

1
F31610.DAT 3-D N-S IGPNS.
1 48 1 45
3520.00 5.00 2880.00 4.00 2942.50 3725.50 5.00 12 45
ORE% REM% NSR LENS DEN AU AG CU PB BA FE ZN
0.000 0.000 0.000 0.000 2.600 0.000 1.000 0.000
1023 127 511 7 31 10923 1048575 4095
0.100 1.000 1.000 1.000 0.100 0.100 0.001 0.10
20 3040.00 5.00 N/A
21 3045.00 5.00 N/A
22 3050.00 5.00 N/A

MineSight

MEDS-603V1 10=SAMP10.DAT 13=SAMP13.DAT 3=RPT603.LD;
MEDS-603V1 19=DAT603.OC
** DUMP TOPOGRAPHY FROM FILE 13 IN INTEGER FORMAT FOR M610V1 **
USR = ABC
IOP11 = 6 / TOTAL # OF DIGITS OCCUPIED BY GET ITEMS FOR OUTPUT
PAR1 = .10 99999/ MIN AND MAX VALUE OF CONTROLLING ITEM
GET13 = TOPOG
COM* OUTPUT FORMAT IS OPTIONAL, BUT RECOMMENDED TO SAVE SPACE

COM* DEFAULT FORMAT FOR IOP2 = 0 IS: (4I4,8I8)
FMT1 = (4I4,20(I6))
I-O = 2
END

MEDS-603V1 10=SAMP10.DAT 13=SAMP13.DAT 3=RPT603.LE
** LIST TOPOGRAPHY ITEMS FROM FILE 13 TO REPORT FILE **
USR = ABC
GET13 = TOPOG
COM* DEFAULT FORMAT FOR IOP2 = 1 IS: (3I4,8F8.1)

COM* NO FILE 19 SPECIFIED, SO OUTPUT TO REPORT FILE
I-O = 2
END
1 1 1 1 40 30 30
1 1 1 1 40 40 40

MineSight
1. ?M603V1: ERROR. Your file 15 is empty.

You MUST initialize your file with M601V1 before proceeding
Your model file must be initialized using M601V1 before any other MineSight program can access it.
2. ?M603V1: ERROR. No file 19 specified.
You have selected IOP2=0 but have not specified a File 19 on the NAMES line of your run file.
3. ?M603V1: ERROR. Your ROW/COLUMN/BENCH specifications are inconsistent.

First COLUMN = 10 Last COLUMN = 2 Maximum COLUMN = 70
First ROW = 0 Last ROW = 30 Maximum ROW = 50
First BENCH = 1 Last BENCH = 45 Maximum BENCH = 20
Something is wrong with one of your Area Specification Lines. Make sure the first Row/Column/Bench is not larger than the
last Row/Column/Bench. Note the following:
1) There is no default for the First Row/Column/Bench. If you enter zero, thats what youll get.
2) The Maximum bench is the last bench initialized with M601V1; NOT the last bench in the PCF.
4. ?M603V1: ERROR. You have requested xx items which exceeds the maximum 10.
You can dump at most 10 items from your model file.
5. If your output wraps around to the next line, check your IOP11 and FMT1 statements. IOP11 must equal the number of columns
of output specified in the format statement for the items. The repeat specification for the items must be greater than or equal to
the integer quotient of 64/IOP11.
For example, if you are dumping four items with six columns each (4I6), set IOP11=24 (4 items x 6 columns/item) and
FMT1=(4I4,2(4I6)) because 64/24=2. If you are dumping four items with five, five, four and two colums (I5,I5,I4,I2), set
IOP11=16 and FMT1=(4I4,4(I5,I5,I4,I2)).
6. Check the MineSight error messages in the Appendix.

MineSight
Proprietary Software: Mintec, inc. M606V1 - PLAN MAP (M122) OFMINE MODEL DATA
M606V1 PLAN MAP (M122) OFMINE MODEL DATA

M606V1 accesses the mine model files and prepares plot M606V1 is used to plot up to four data items from Files 13, 14,
commands for program M122V1. One or more values may be or 15 on a plan map. The plot commands are written out to an
plotted in a single run. M122V1 plot file in either ASCII or binary format. A binary
format plot file is more efficient for plotting, but you cannot
modify its contents.
PROGRAM FLOW DIAGRAM The first four ITM commands in the run file select the data items
to be plotted. You can also restrict plotting to blocks with a topo
RUN FILE: percent greater than a certain value. The outline of each
- Model areas to display individual block in the model can also be plotted. You can also
- Model items to display select data to be plotted using the Range, Omit or Table
- Plot specifications commands.
The horizontal and vertical spacing of the items to be plotted

can be specified, along with the size of the annotation. Block
values can be plotted in different colors on the basis of grade
cutoffs.
INPUT: CALCS: Data can also be selected by row and column. Ranges and scales
- PCF - Extract model area for in both easting and northing can be specified.
- Mine Model File display
(File 13, 14 or 15) - Extract items for display
- Create M122 plot
commands
OUTPUT:
- M122 Plot File (binary or
ASCII)

MineSight
M606V1 - PLAN MAP (M122) OFMINE MODEL DATA Proprietary Software: Mintec, inc.

MineSight
Proprietary Software: Mintec, inc. M606V1 - PLAN MAP (M122) OF MINE MODEL DATA
M606V1 - PLAN MAP (M122) OF MINE MODEL DATA
RUN FILE OPERATION

MEDS-606V1 10=filename 15(or 14 or 13)=filename;

where

19 = the name of the M122 OUTPUT FILE
IOP3 = 0 PLOT IN MODEL COORDINATES

= 1 PLOT IN EAST-NORTH PROJECTION
= 2 PLOT IN EAST-ELEVATION PROJECTION
= 3 PLOT IN NORTH-ELEVATION PROJECTION
= 4 PLOT IN PROJECTION ON THE CLOSEST COORDINATE PLANE IN PROJECT COORDINATES
IOP5 = IX1 FIRST MODEL COLUMN TO ACCESS (default=1)

IOP6 = IX2 LAST MODEL COLUMN TO ACCESS (default=NX)
IOP7 = IY1 FIRST MODEL ROW TO ACCESS (default=1)

IOP8 = IY2 LAST MODEL ROW TO ACCESS (default=NY)
IOP11 = 1 PLOT BLOCK OUTLINE (optional)

= 2 FILL BLOCK
NOTE: Or use ITMn = PLOT BLOCK OUTLINE
IOP12 = 0 ASCII 122 OUTPUT (default)

= 1 BINARY 122 OUTPUT
IOP13 = -1 COLOR OUTLINE/VALUES BASED ON FIRST VALUE, BUT DO NOT PLOT FIRST VALUE
= 0 PLOT GRADES
= 1 DO NOT PLOT GRADES. USE GRADE TO SELECT PEN # FOR PLOT
IOP14 = 0 ANNOTATION ANGLE (PAR7) IS COUNTED FROM MODEL X COORDINATES

= 1 ANNOTATION ANGLE IS COUNTED FROM HORIZONTAL
Revised: 16-May-01 Page 606-3

MineSight
M606V1 - PLAN MAP (M122) OF MINE MODEL DATA Proprietary Software: Mintec, inc.
IOP15 = 0 USE BENCH TOE FOR ELEVATION

= 1 USE MID-BENCH FOR ELEVATION
Note: Used for 3D-rotated block models when IOP3 > 0
PAR1 = X-SCALE OF M122 MAP IN USER COORDINATES

(default = 2.0 * DX from PCF)
PAR2 = Y-SCALE OF M122 MAP IN USER COORDINATES

(default = PAR1)
PAR3 = HEIGHT OF VALUE ANNOTATIONS IN INCHES

(default = 0.10)
NOTE: Values above 0.5 are set to 0.1.
PAR4 = VERTICAL SEPARATION OF MULTIPLE VALUES IN INCHES

(default = 0.05)
PAR5 = HORIZONTAL SPACING FROM LEFT SIDE OF BLOCK TO START OF VALUE ANNOTATION, IN INCHES
(default = 0.0)
PAR6 = PLOT BLOCK OUTLINE OFFSET IN PLOTTER UNITS
Note: Offset is counted along the model X direction
PAR7 = ANGLE OF ANNOTATIONS
PAR8 = ELEVATION TO PLACE SEAM ON, IF IOP3 > 0 FOR A 3D-ROTATED GSM FILE 15 OR FILES 13 & 14
NORTH
PAR12 = PERCENT SHADING (default = 100.0 for 100%)
PLT = CUTOFF VALUES TO CONTROL COLORING (For use with a 4 pen plotter):
vmax1 vmax2 vmax3 vmax4 p1 p2 p3 p4

where
Page 606-4 Revised: 16-May-01

MineSight
Value Color
0.0 # x < vmax1 p1

vmax1 # x < vmax2 p2
x > vmax4 p1 Set vmax4 to 999 (or higher than any grade) to avoid reverting to pen 1
NOTE: P1, p2, p3 and p4 are optional pen numbers. Default is 1, 2, 3, 4. Cutoffs are applied to ITM1
item and should be stated in the same precision as the data.
For increased pen numbers:
CMD = PLOT CUT V1 V2 V3 ... V15 (for cutoffs)

CMD = PLOT PEN V1 V2 V3 ... V16 (for pen numbers)
NOTE: Always list one more pen number than you have cutoffs. The additional pen is for any material
greater than the last cutoff.
ITM1 = label-nn Fw.d min-value1 (required)

.
.
ITMn = label-nn Fw.d (optional)
Label-nn is the item to plot. Fw.d is the output format for plotting. Min-value is the minimum value to be plotted. Enter
even if 0.0. If the required ITMn value for a block is less than the minimum value, then no block values are plotted.
ITMn = topo-label TOPO value (optional)
Topo-label is the File 15 TOPO% item. TOPO is a keyword for the program. Value is the least TOPO% value of a
block to be plotted. Blocks with TOPO% less than value will not be plotted. (default=50%)
ITMn = PLOT BLOCK OUTLINE
The block outline will be plotted with the same pen as the grade label.
ITMn = label-nn RANGE min-value max-value

ITMn = label-nn OMIT min-value max-value
ITMn = label-nn TABLE IOPm IOPn
END
4. BENCH REQUEST LINES
Each bench request line contains up to 10 bench reference numbers (integers) in free-field format. If a line contains fewer than 10
bench reference numbers, input will terminate with the last bench referenced on that line. So, for example, given the following bench
request lines:
1 2 3 4 5 6
7 8 9 10 11 12
the last bench processed would be 6.
If you are using File 13, set the bench reference number to 1.

MineSight

MEDS-606V1 10=SAMP10.DAT 15=SAMP15.DAT 19=PLT606.PAA;
MEDS-606V1 3=RPT606.LA
* EXTRACT TCU-1 BLOCK VALUES FROM FILE 15-BENCH 20-ELEV 3600 *
USR = ABC
IOP5 = 11 40 / COLUMNS TO PLOT

IOP7 = 11 40 / ROWS TO PLOT
PAR1 = 500 500 / X AND Y SCALE

PAR3 = .04 .04 .02 / ANNOT SIZE, VERT AND HORIZ SPACING
ITM1 = TCU-1 F5.2 .01 /PLOT TOTAL COPPER

ITM2 = TOPO TOPO 50 /LIMIT BY 50% TOPO
PLT = .19 .49 .99 999 1 2 3 4 / PEN COLOR CONTROL FOR GRADES
COM = THIS WILL PLOT MATERIAL LESS THAN .2 WITH PEN 1, LESS THAN .5 WITH PEN 2, LESS THAN 1 WITH PEN 3 AND
GREATER THAN OR EQUAL TO 1 WITH PEN 4.
END
20

MEDS-122V1 10=SAMP10.DAT 3=RPT122.LA
PLOT OF 3-D T-CU BLOCK VALUES ON BENCH 20-SCALE 1" = 500
USR = ABC
MAP = 10000 15000 500 10000 15000 500
END
BORDR 1 1000 14000 11000 14000 0
BORDR 1 11007.5 13992.5 11000 13992.5 0
GRID 1 11000 14000 11000 14000 1000
TICKS 1 11000 11000 11000 14000 1000 .08
TICKS 1 11000 14000 14000 14000 1000 .08
COORD 1 10850 11015 10850 14015 1000 .05 0 0 11000 1000
COORD 1 10985 14015 13985 14015 1000 .05 90 0 11000 1000
BORDR 1 11000 14000 10750 11000 0
BORDR 1 11007.5 13992.5 10757.5 10992.5 0
LINE 1 13250 10750 13250 11000 0
LINE 1 13250 10900 14000 10900 0
LINE 1 14000 10800 13250 10800 0
LABEL 1 13455 10940 0 .04 17/WIDGET MINING CO.
LABEL 1 13455 10770 0 .04 17/SCALE 1" = 500
LABEL 1 13455 10860 0 .04 17/T-CU BLOCK VALUES
LABEL 1 13545 10820 0 .04 8/BENCH 20
USERF PLT606.PAA
ENDOC

MineSight

MEDS-606V1 10=SAMP10.DAT 15=SAMP15.DAT 19=PLT606.PAB;
MEDS-606V1 3=RPT606.LB
* EXTRACT TCU-1 BLOCK VALUES ABOVE 0.3; USE FIVE PENS *
USR = ABC
IOP5 = 11 40 / COLUMNS TO PLOT

IOP7 = 11 40 / ROWS TO PLOT
PAR1 = 500 500 / X AND Y SCALE

PAR3 = .04 .04 .02 / ANNOT SIZE, VERT AND HORIZ SPACING
ITM1 = TCU-1 F5.2 .01 / PLOT TOTAL COPPER

ITM2 = TOPO TOPO 50 / PLOT BLOCKS WITH GT 50% TOPO
ITM3 = TCU-1 RANGE 0.3 99.9 /PLOT COPPER ABOVE 0.3
ITM4 = PLOT BLOCK OUTLINE
CMD = PLOT CUT .19 .49 .99 1.49

CMD = PLOT PEN 1 2 3 4 5
END
20

MineSight
1. ?M606V1: ERROR. No File 15, 14 or 13 specified on the NAMES line.
You have not specified a model file on the NAMES line in your run file.
2. ?M606V1: ERROR. Your MODEL file is empty.

You MUST initialize your file with M601V1 before proceeding.
3. %M606V1: WARNING. Skipping bench xx.

The last initialized bench is yy.
You have only initialized through bench yy (M601V1) and are attempting to plot data for bench xx, which has never been
initialized.
4. ?M606A1: ERROR. No items for plotting are specified.
You are required to specify at least one item to plot. For example, ITM1=ASH F5.2 0.
5. If no plot file is created, check that you have interpolated or loaded block values into the area of the model that you are plotting.
6. If no data is plotted, but data exists in the model, check the TOPO% item. It must be above the minimum value if ITMn = topo-
label TOPO value is used.

MineSight
Proprietary Software: Mintec, inc. M607V1 - CONTOUR PLOT (M122) OFMINE MODEL DATA
M607V1 - CONTOUR PLOT (M122) OFMINE MODEL DATA

M607V1 is used to create a contour map of a single item of data M607V1 is used to create a contour map of a single item in a
from the mine model files. The program creates an M122 mine model file. The maps can be bench plans, south to north
USERF/DATAF file. sections, or west to east sections.
This program can generate:
PROGRAM FLOW DIAGRAM A M122 plot file of contours

RUN FILE:
An ASCII trace file of contours in VBM format
- Mine model area and
items The trace file of contours can be loaded into a VBM file and
- Contour/trace file specs
- Plot specs plotted using the VBM plot routines. This option will generate
extra topography contours for use in later parts of the system.
Only one contour map or trace file can be produced per run. the
area to be plotted can be selected on the basis of row and column
ranges (IOP4 - IOP7), or with a series of boundary points.
INPUT: CALCS:
(selected by IOP13).
- PCF - Extract area and items Contour lines can be smoothed by specifying IOP9>0. This
- Mine model file from mine model
should be done if DX and DY are relatively large in relation to
(File 13, 14 or 15) - Create contours, trace
file (opt.) and plot the map scale (1/2" or more). However, computer run time will
commands increase if IOP9 is used.
OUTPUT:
- M122 USERF or DATAF
File
- Optional Trace File

MineSight
M607V1 - CONTOUR PLOT (M122) OFMINE MODEL DATA Proprietary Software: Mintec, inc.

MineSight
Proprietary Software: Mintec, inc. M607V1 - CONTOUR PLOT (M122) OF MINE MODEL DATA
M607V1 - CONTOUR PLOT (M122) OF MINE MODEL DATA
RUN FILE OPERATION


MEDS-607V1 30=filename 31=filename 3=filename
where

15 = the name of the 3-D MINE MODEL FILE
14 = the name of the GSM SUMMARY FILE
30 = the name of the CONTOUR FILE (see IOP2)
31 = the name of the TRACE FILE (see IOP3)
NOTE: Many of the following program setup features are dependent on IOP2 & IOP3.
IOP2 = -1 DO NOT PRODUCE A PLOT FILE

= 0 PRODUCE A PLOT FILE FOR M122 (default)
IOP3 = 0 DO NOT PRODUCE A TRACE FILE (default)

= 1 PRODUCE A TRACE FILE IN VBM FORMAT (use PAR10 & 11)
IOP4 = FIRST MODEL COLUMN TO ACCESS (default=1)

IOP5 = LAST MODEL COLUMN TO ACCESS (default=NX)
IOP6 = FIRST MODEL ROW TO ACCESS (default=1)

IOP7 = LAST MODEL ROW TO ACCESS (default=NY)
IOP8 = THE MODEL BENCH OR SEAM TO BE REFERENCED (default=1)
NOTE: Rows, columns and benches are relative to the axis of the map. In either case, the last bench you
can access is the last bench that was initialized using M601V1.
For N-S section For E-W section

Column numbers refer to rows Column numbers refer to columns
Row numbers refer to benches Row numbers refer to benches
Bench numbers refer to columns Bench numbers refer to rows
IOP9 = THE NUMBER OF INTERIOR LINEAR INTERPOLATIONS FOR EACH GRID CELL IN THE X & Y
DIRECTIONS (default=0)

MineSight
M607V1 - CONTOUR PLOT (M122) OF MINE MODEL DATA Proprietary Software: Mintec, inc.
NOTE: Maximum of 7. This option is used primarily for large cells to increase the smoothness of contour
lines or to increase the density of points in the trace file. If IOP9>0 and contour=cell value, it is possible
for disjointed trace lines to occur.
IOP10 = THE TYPE OF VIEW TO GENERATE

= -1 S-N SECTION LOOKING WEST
= 0 PLAN VIEW (default)
= 1 W-E SECTION LOOKING NORTH
IOP11 = FEATURE CODE FOR THE TRACE FILE IF ONE IS TO BE PRODUCED (default=901)
IOP13 = 0 USE ROWS & COLUMNS TO DEFINE THE GRID BOUNDARY

= 1 INPUT A BOUNDARY POINT POLYGON TO LIMIT GRID POINTS
NOTE: If IOP13=1, the specified boundaries can be in a separate file. Use the following command line:
CMD=INCL LOCPT FILE filename
IOP14 = 0 CREATE ASCII PLOT FILE (default)

= 1 CREATE BINARY PLOT FILE
IOP15 = NUMBER OF DECIMAL PLACES IN PLOT LABEL (default = 0, max = 3)

IOP16 = PEN # FOR INDEX CONTOURS (default = 2)
IOP18 = 0 PLOT IN MODEL COORDINATES

= 1 PLOT PROJECT COORDINATES IN EAST-NORTH PROJECTION
= 2 PLOT PROJECT COORDINATES IN EAST-ELEVATION PROJECTION
= 3 PLOT PROJECT COORDINATES IN NORTH-ELEVATION PROJECTION
IOP19 = 0 TRACE IN MODEL COORDINATES

= 1 TRACE PROJECT COORDINATES IN EAST-NORTH PROJECTION
= 2 TRACE PROJECT COORDINATES IN EAST-ELEVATION PROJECTION
= 3 TRACE PROJECT COORDINATES IN NORTH-ELEVATION
GETnn = LABEL OF THE SINGLE ITEM TO PLOT
NOTE: nn is the file reference number of the model file on the Names Line. This must be the first GET
item.
ITMn = UN value
ITMn = GT old new
ITMn = LT old new
NOTE: The keyword UN specifies that any undefined cell values are to be reset to value. The keywords
GT and LT specify that cell values greater than or less than old are to be reset to new, respectively.
GETnn = LABEL OF THE SINGLE LIMITING ITEM
NOTE: nn must be the same file reference number as the GET plot item. This must be the second GET
item. In addition, the following ITM command must be used to invoke limiting:
ITMn = label RANGE min-value max-value
NOTE: You may limit on another variable in the file.
FMT1 = FORMAT OF THE TRACE FILE COORDINATE PAIR OUTPUT (default = (2F10.1))

MineSight
FMT2 = FORMAT OF THE TRACE FILE CONTOUR HEADERS, CONTOUR LEVEL & FEATURE CODE
(default = (F10.1,I8))
PAR1 = MINIMUM CONTOUR LEVEL (required)

PAR2 = 1ST CONTOUR INCREMENT (required)
PAR3 = MINIMUM VALUE OF THE 2ND CONTOUR INTERVAL (optional)

PAR4 = 2ND CONTOUR INCREMENT (optional)
PAR5 = MINIMUM VALUE OF THE 3RD CONTOUR INTERVAL (optional)

PAR6 = 3RD CONTOUR INCREMENT (optional)
PAR7 = MINIMUM VALUE OF THE 4TH CONTOUR INTERVAL (optional)

PAR8 = 4TH CONTOUR INCREMENT (optional)
PAR9 = MAXIMUM CONTOUR LEVEL (required)
NOTE: Intervals must be in ascending order & are terminated by a zero increment or by a full complement
of intervals.
PAR10 = THE LOWEST CONTOUR LEVEL TO OUTPUT TO THE TRACE FILE

PAR11 = THE HIGHEST CONTOUR LEVEL
NOTE: PAR10 & 11 need only be specified if IOP3>0.
PAR12 = 0 OUTPUT STANDARD LINE SEGMENTS

= >0 OUTPUT DASHED LINE SEGMENTS OF PAR12 LENGTH
= <0 OUTPUT SMOOTHED LINE SEGMENTS
PAR13 = ANNOTATION FREQUENCY IN INCHES (default = 10)
PAR14 = ANNOTATION SIZE (default = 0.1)
PAR15 = PLOT SCALE IN USER COORDINATES (no default)
PAR16 = INTERVAL BETWEEN INDEX CONTOURS
PAR17 = Z MODEL VALUE (FOR GSM MODEL ONLY)
Note: Used when IOP18 > 0 or IOP19 > 0.
END
4. BOUNDARY POINT LINES (If IOP13=1)
If the specified boundaries are to be added at the end of the run file, then use the following format:
Easting Northing (in free-field format)
where 0 0 ends the input or input end of end-of-file. Boundary points must close. The maximum number of boundary points
allowed is 2000.

MineSight

MEDS-607V1 30=PLT607.PAA
** CONTOUR PLOT OF FILE 13 ITEM TOPOG **
USR = ABC
IOP2 = 0 / PRODUCE PLOT FILE

IOP3 = 0 / NO TRACE FILE
IOP4 = 1 50 / 1ST AND LAST COLUMN
IOP6 = 1 50 / 1ST AND LAST ROW
IOP8 = 1 / REFERENCE BENCH #
IOP9 = 0 / # OF INTERIOR LINEAR INTERPOLATIONS
IOP14 = 0 / 0=ASCII PLOT FILE, 1=BINARY PLOT FILE
IOP15 = 11 / NUMBER OF DECIMAL PLACES ON LABEL
PAR1 = 4200 / ZMIN=MINIMUM CONTOUR LEVEL

PAR2 = 50 / CONTOUR INCREMENT
PAR9 = 4550 / ZMAX=MAXIMUM CONTOUR LEVEL
PAR12 = 0 / OUTPUT STANDARD LINE SEGMENTS

PAR13 = 10 / DISTANCE BETWEEN LABELS ON PLOT
PAR14 = .1 / ANNOTATION SIZE
PAR15 = 500 / PLOT SCALE
MAP = 0 0 1000 0 0 1000 /XMIN, XMAX, XSCALE, YMIN, YMAX, YSCALE
GET13 = TOPOG/ PLOT TOPOGRAPHY

END

* PLOT OF FILE 13 TOPOGRAPHY *
USR = ABC
MAP = 9000 16000 500 9000 16000 500

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 9850 10025 9850 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 13850 9680 0 .07 20/CONTOURED TOPOGRAPHY
LABEL 1 13910 9540 0 .07 17/SCALE: 1" = 500
PEN# 2
USERF PLT607.PAA
ENDOC

MineSight

MEDS- 607V1 30=PLT607.PAB 31=DAT607.OB
** CONTOUR OF TCU-1 FROM FILE 15 **
USR = ABC
IOP2 = 0 / -1=NO CONT, 0=CONTOUR
IOP3 = 1 / 0=NO TRACE, 1=TRACE FILE

IOP4 = 1 50 / 1ST AND LAST COLUMN
IOP6 = 1 50 / 1ST AND LAST ROW
IOP8 = 20 / REFERENCE BENCH #
IOP9 = 0 / # OF INTERIOR LINEAR INTERPOLATIONS
IOP11 = 201 / FEATURE CODE FOR TRACE FILE
IOP14 = 0 / 0=ASCII PLOT FILE, 1=BINARY PLOT FILE
IOP15 = 2 / NUMBER OF DECIMAL PLACES ON LABEL
PAR1 = 0.0 / ZMIN=MINIMUM CONTOUR LEVEL

PAR2 = 0.1 / CONTOUR INCREMENT
PAR9 = 2.0 / ZMAX=MAXIMUM CONTOUR LEVEL
PAR10 = 0.0 / ZMIN FOR TRACE FILE
PAR11 = 2.0 / ZMAX FOR TRACE FILE
PAR12 = 0 / OUTPUT STANDARD LINE SEGMENTS
PAR13 = 10 / DISTANCE BETWEEN LABELS ON PLOT
PAR15 = 500 / PLOT SCALE
GET15 = TCU-1 / PLOT COPPER

END
MEDS-122V1 10=SAMP10.DAT 3=RPT122.LB
* PLOT OF BENCH 20 CONTOURED COPPER 1"=500 *
USR = ABC

MineSight
MAP = 9000 16000 500 9000 16000 500

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 9850 10025 9850 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 0BORDR 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 13850 9680 0 .07 20/CONTOURED COPPER
LABEL 1 13910 9540 0 .07 17/SCALE: 1" = 500
PEN# 2
USERF PLT607.PAB
ENDOC
1. ?M607V1: ERROR. No file 15, 14, or 13 specified on the Names Line
You have not specified a model file on the Names Line in your run file.

MineSight
2. ?M607V1: ERROR. Cannot do a section through File 13.
Since File 13 is essentially two-dimensional, contour plots are only allowed in plan view.
3. ?M607V1: ERROR. Your File 13 is empty.

4. ?M607V1: ERROR Your ROW/COLUMN/BENCH selection is inconsistent.

X, Y, and Z values are relative to the PLOT coordinates.
First X= 220 Last X= 100 Maximum X= 300

First Y= 1 Last Y= 49 Maximum Y= 40
Z= 17 Maximum Z= 66
Something is inconsistent in the way you selected the ROW/COLUMN/BENCH to plot (IOP4-IOP8). Note the X, Y, and
Z are relative to the PLOT coordinates. For example, if IOP10=1 (so youre plotting a WE section looking North) then X
would refer to model columns, Y would refer to model benches, and Z would refer to model rows. Note also that the
benches are always limited by the last bench initialized using M601V1. This limit might be less than the total number of
benches in your model.
5. ?M607V1 FILE filename IS NOT AVAILABLE
will appear if a contour file does not exist and you choose to do a preview plot.
6. ?M607V1: ERROR. Invalid contour LEVEL specification (PAR1-9)
Something is inconsistent in the way you specified your minimum and maximum contour levels or your contour intervals.
7. ?M607V1: ERROR. Invalid trace LIMIT (PAR10-11)
Something is inconsistent in the way you specified the range of contour levels output to the trace file.
8. Be careful when using IOP9 as computer time will increase as IOP9 is increased.
9. If no contour map is produced, check that you have interpolated or loaded the item into the model.

MineSight

MineSight
Proprietary Software: Mintec, inc. M607V4 - CREATE CONTOUR DATA USING TRIANGULATION
M607V4 CREATE CONTOUR DATA

USING TRIANGULATION

M607V4 is used to contour data and output either a plot file or M607V4 uses a triangular mesh, sometimes referred to as a
VBM input file. Digital Terrain Model or DTM, to contour the z value of the
input data points. In a triangular mesh, each point is connected
to two other points to form a triangle. The z value of each of the
points in a triangle gives the triangle an orientation in 3-D space.
PROGRAM FLOW DIAGRAM The z value used for contouring is frequently an elevation, but
may be a grade, thickness or any other value you would like to
RUN FILE: contour.
- Input type
- Output type The number of points that can be used in a triangular mesh are
- Boundary limited to 300,000. If this point limitation is a problem, the
- Contour values program can be run multiple times using run file options to
restrict the input by either area or range of contour values.
The program flow is:
Create a triangular mesh if input is ASCII points file.

INPUT: CALCS:
- PCF - Calculate triangular math Calculate contour segments from triangular mesh and
- ASCII input file -OR- - Create contours write to binary file TMP032.TMP. A contour segment
DTM is the line formed across a triangular plane having a
constant z value. It is defined by its endpoints, the
intersections with 2 sides of a triangle.
Produce contour output as a plot file or ASCII file in

VBM format.
OUTPUT:
The type of output is specified with IOP4. The default (IOP4=0)
- M122 Plot File -OR- is to produce a file of plot commands for contouring (File 30).
ASCII Input File (649 To display the contours, File 30 must be accessed with the
format)
- Printer Output File USERF/DATAF command in a M122V1 run file. If IOP4=1,
the output will be an ASCII file that is in a form ready to load
into a VBM. If IOP4=2, the output is in a survey file format.
For all output types the MAP command mst be used which
specifies two SCALES. The XSCALE directly affects the result,
as it is used in the computations. Be aware that changing the
XSCALE can produce more or fewer points on the contours
and also affect the joining of contour segments.
Four types of input are acceptable and are specified with IOP20.
The default input (IOP20=0) is to read an ASCII file of points
and create a triangular mesh. Points will be read as x-coordinate,
y-coordinate, contour value, unless a different order is specified
by the ALF1 command. The data may be read free format or
with a specified format using a FMT1 statement. If IOP20=1,

MineSight
M607V4 - CREATE CONTOUR DATA USING TRIANGULATION Proprietary Software: Mintec, inc.
the program will read the file TMP032.TMP and contour the Contours are produced over a specified range with a regular
data. This option can only be used when the program has been interval specified as PAR5 and are referred to as base contours.
run before with IOP20 set to 0 or 2. If IOP20=2, the program The base contours are output to File 30. The program will
will read in a binary Digital Terrain Model file that has been optionally produce a second set of contours, referred to as index
created by the program M635V1. If IOP20=-1, a MineSight contours, if an interval is specified in PAR6. This option is
Shell File will be read in. intended to provide contours that can be plotted with a heavier
pen or a different color pen. The index contours are output to
Note that if IOP20=0, the triangular mesh will be unconstrained. the same File 30, but with the pen color specified by IOP9. It
The triangulation algorithm will attempt to make all triangles as may be necessary to run this program more than once if the
nearly equilateral as possible. If IOP20=2, the triangular mesh desired index contours cannot be generated at a regular interval
will have been constrained so that sides of a triangle do not with the range used by the base contours.
cross certain boundaries. This method should be used if you
are trying to contour pit data that includes toe and crest points.
For example, when trying to model a pit surface with a DTM, it
is important that the triangles form along the toes and crests of
the benches rather than across a toe or crest boundary.
Output can be limited by placing constraints on the processing

of input data. The constraints that can be applied to input are:
Limit the maximum length of a triangle side by

specifying maximum length in PAR1.
Limit the data used by a polygonal boundary. Boundary

must be clockwise and closed.
Limit the data used by a rectangular area.
Limit the contours produced by a range for the contour

values.

MineSight
M607V4 - CREATE CONTOUR DATA USING TRIANGULATION
RUN FILE OPERATION

1. NAMES LINE (must be first line entered)

where

19 = the name of the INPUT DATA FILE (see IOP20)
30 = the name of the PLOT FILE OF BASE CONTOURS -OR- THE ASCII VBM INPUT FILE
IOP1 = 0 NO BOUNDARY FILE IS REQUIRED

= 1 USE A BOUNDARY TO RESTRICT INPUT COORDINATES
NOTE: If IOP1=1, the specified boundaries can be in a separate file. Use one of the following command lines:
CMD = INCL LOCPT FILE filename (to include input data within the boundary) OR
CMD = EXCL LOCPT FILE filename (to exclude input data within the boundary)
Contour output will NOT be excluded by the boundary file. The constraint is only applied against the input data
points.
IOP3 = 0 FREE FORMAT INPUT

= 1 USE FMT1 FOR INPUT
NOTE: Input is in the format: Easting, Northing, and Contour Value.
IOP4 = 0 OUTPUT FILE (#30) IS FOR PLOTTING

= 1 OUTPUT FILE (#30) IS FOR VBM INPUT
= 2 SURVEY FILE OUTPUT
IOP5 = FEATURE CODE (if IOP4=1)

NOTE: Use IOP5 to define feature code.
IOP6 = 0 OUTPUT ASCII PLOT FILES (if IOP4 = 0)

= 1 OUTPUT BINARY PLOT FILES (if IOP4 = 0)
IOP7 = NUMBER OF DECIMAL PLACES IN PLOT LABEL (default = 0, max = 3)
IOP8 = PEN # FOR CONTOUR (default = 2)
IOP9 = PEN # FOR INDEX CONTOURS (default = 3)

MineSight
IOP20 = -1 READ SHELL FILE FORMAT

= 0 INPUT FILE (#19) IS AN ASCII POINTS FILE
= 1 BYPASS INPUT FILE (#19) AND READ EXISTING TMP032.TMP FILE
= 2 INPUT FILE (#19) IS A BINARY DIGITAL TERRAIN MODEL
(DTM) FROM M635V1
NOTE: Program creates this binary contour segments file when IOP20 is set to 0 or 2.
PAR1 = MAXIMUM TRIANGLE SIDE LENGTH (default = no limit)

NOTE: If two points are more than PAR1 apart, they will not be included in the same triangle. Set PAR1 if you
want to influence contours for widely distributed points.
PAR5 = BASE CONTOUR INTERVAL

NOTE: Contour output is in File 30.
PAR6 = INDEX CONTOUR INTERVAL

NOTE: Contour output is in File 30; must be a multiple of 2 or more of the base contour interval.
PAR7 = LOWER LIMIT OF CONTOUR ELEVATION

PAR8 = UPPER LIMIT OF CONTOUR ELEVATION
PAR9 = SMOOTHING FACTOR (default = 9)

NOTE: Range is 1 through 9, with 9 producing the smoothest contours.
PAR10 = CONSTANT TO BE ADDED TO X COORDINATE

PAR11 = CONSTANT TO BE ADDED TO Y COORDINATE
PAR12 = MINIMUM VALUE OF INPUT DATA TO ACCEPT FOR CONTOURING
PAR14 = ANNOTATION FREQUENCY IN INCHES (default = 10)

PAR15 = ANNOTATION SIZE (default = 0.1)
MAP = XMIN XMAX XSCALE YMIN YMAX YSCALE
FMT1 = FORMAT OF INPUT DATA IN FILE 19

NOTE: Use only if IOP3=1.
ALF1 = yval xval value

where:
yval indicates relative position of input y-coordinate
xval indicates relative position of input x-coordinate
value indicates relative position of input contour value
NOTE: Keywords specify order of input data from File 19. ALF1 is only needed for data that is NOT in the
order xval yval value.
END
4. BOUNDARY POINT LINES (if IOP1=1)
If the specified boundaries are to be added at the end of the run file rather than a separate file, then use the following format:
Easting Northing OR x-coordinate y-coordinate (in free-field format)
where 0 0 ends the input or input ends on end-of-file. Boundary points must close. The maximum number of boundary points
allowed is 2000.

MineSight

MEDS-607V4 10=SAMP10.DAT 19=DAT607.IA 3=RPT607.LA;
MEDS-607V4 30=PLT607.PB1
** CONTOUR DATA USING TRIANGULATION - ASCII FILE INPUT **
COM OUTPUT FILE 30 WILL BE IN CONTF FORMAT
USR = ABC
IOP1 = 0 / 0=NO BOUNDARY FILE, 1=USE A BOUNDARY FILE
IOP3 = 0 / 0=FREE FORMAT INPUT
IOP4 = 0 / 0=OUTPUT IS PLOT FORMAT
IOP6 = 0 / 0=ASCII PLOT FILE

IOP7 = 2 / NUMBER OF DECIMAL PLACES
IOP20 = 0 / 0=INPUT IS ASCII POINT DATA
PAR1 = 40 / MAXIMUM TRIANGLE SIDE SIZE
PAR5 = 2.0 / CONTOUR INTERVAL

PAR6 = 10.0 / INDEX CONTOUR INTERVAL
COM AN INDEX CONTOUR WILL BE OUTPUT TO FILE 31 FOR EVERY 5TH CONTOUR
PAR7 = 168. / LOWER LIMIT OF CONTOUR OUTPUT

PAR8 = 236. / UPPER LIMIT OF CONTOUR OUTPUT
PAR9 = 0 / SMOOTHING FACTOR FOR CONTOURS (range = 1 to 9; default= 9)
PAR10 = -430000 / CONSTANT TO BE ADDED TO X COORDINATE

PAR11 = -760000 / CONSTANT TO BE ADDED TO Y COORDINATE
PAR12 = 166. / MINIMUM INPUT VALUE TO ACCEPT FOR CONTOURING
PAR14 = 100 / ANNOTATION FREQUENCY

MAP = 3400. 4500. 20. 2500. 3600. 20. / MAP LIMITS AND SCALE
I-O = 0
END

MineSight

MEDS-607V4 -10=TEMP 19=SURF1.DTM. 30=PLT607.PBB 3=RPT607.LB
** CONTOUR DATA USING TRIANGULATION - INPUT IS A DTM **
COM FILE 30 IS A 122 CONTF FILE
USR = ABC
IOP1 = 0 / 0=NO BOUNDARY FILE, 1=USE BOUNDARY FILE
IOP3 = 1 / 0=FREE FORMAT READ, 1=USE FMT1

IOP4 = 0 / 0=OUTPUT IS PLOT FILE, 1=OUTPUT IS VBM DATA
IOP5 = 901 / IF IOP4=1, FEATURE CODE FOR VBM DATA
IOP6 = 1 / BINARY PLOT FILE
IOP20 = 2 / INPUT IS DTM FILE FROM M635V1
PAR1 = 0.0 / MAXIMUM TRIANGLE SIZE
PAR5 = 10 / BASE CONTOUR INTERVAL

PAR7 = 1500 / LOWER LIMIT OF CONTOUR VALUE

PAR8 = 1900 / UPPER LIMIT OF CONTOUR VALUE
PAR9 = 7 / SMOOTHING FACTOR FOR CONTOURS
PAR10 = 0. / CONSTANT TO BE ADDED TO X COORDINATE

PAR11 = 0. / CONSTANT TO BE ADDED TO Y COORDINATE
PAR12 = 0. / MINIMUM VALUE TO ACCEPT FOR CONTOURING

MAP = 5300 6100 100 3300 4200 100 / XMIN,XMAX,SCALE, YMIN,YMAX,SCALE
COM DATA IS IN THE FORMAT: XCOORD, YCOORD, CONTOURING VALUE
FMT1 = (12X,3F12.3)
I-O = 0 / IOLEV
END

MineSight

MEDS-607V4 10=SAMP10.DAT 19=DAT607.IB 3=RPT607.LC;
MEDS-607V4 30=DAT607.OC1
** CONTOUR DATA USING TRIANGULATION - ASCII FILE INPUT, VBM OUTPUT **
COM OUTPUT FILE 30 WILL BE IN M649V1 INPUT (VBM) FORMAT
USR = ABC
IOP1 = 0 / NO BOUNDARY FILE
IOP3 = 1 / USE FMT1 FOR INPUT DATA FORMAT

COM INPUT IS IN THE FORM: EAST, NORTH, CONTOUR VALUE
IOP4 = 1 / OUTPUT IS IN VBM FORMAT (specify feature code in IOP5)

IOP5 = 901 / FEATURE CODE FOR OUTPUT CONTOURS IN VBM FORMAT (if IOP4=1).
IOP20 = 0 / INPUT IS ASCII FILE
PAR5 = 1.0 / BASE CONTOUR INTERVAL

PAR9 = 9 / SMOOTHING FACTOR FOR CONTOURS (range = 1 to 9; default= 9)
MAP = 9400. 10200. 100 9600. 10100. 100 / MAP LIMITS AND SCALE
FMT1 = (2F8.1, F8.2)

I-O = 0
END

MineSight

MEDS-607V4 10=SAMP10.DAT 19=DAT607.IB 3=RPT607.LD;
MEDS-607V4 30=PLT607.PB1
** CONTOUR DATA USING TRIANGULATION - ASCII FILE INPUT **
COM OUTPUT FILE 30 WILL BE IN PLOT FORMAT

COM A BOUNDARY FILE WILL BE USED TO LIMIT THE CONTOURS
USR = ABC
IOP1 = 1 / USE A BOUNDARY FILE
IOP3 = 0 / FREE FORMAT INPUT

IOP4 = 0 / OUTPUT IS PLOT FORMAT
IOP6 = 1 / BINARY PLOT FILE
IOP20 = 0 / INPUT IS ASCII POINT DAT
PAR5 = 1.0 / BASE CONTOUR INTERVAL

PAR9 = 9 / SMOOTHING FACTOR FOR CONTOURS

CMD = INCL LOCPT FILE BOUND.DAT
MAP = 9400. 10200. 20. 9600. 10100. 20. / MAP LIMITS AND SCALE
I-O = 0
END

MineSight
1. OPEN error error # on data points file filename.

Contour aborted in M607C4.
Will occur if there is an error opening the ASCII input data file (file 19). Check to see file exists and is available.
2. NEWFFR error error # on data points file filename at record number line #.
Will occur if there is an error reading the ASCII input data. Check the data file at the indicated line number.
3. Number of points in data file filename exceeded xxx.

Will occur if the input has more points than allowed (4000 for PCs or 80000 for other machines). Edit the run file to restrict the
area or input minimum.
4. NEWOCI error on temporary segments files tmp032.tmp.

Contour aborted in M607J4 because of error on file tmp032.tmp.
Will occur if the contour segments file cannot be opened. Check system configuration.
5. More than 500 intercepts on a triangle side.

Will occur if there are more than 500 contour values found on a single triangle side. Either increase the contour interval (PAR5)
or decrease the contour limits (PAR7 and PAR8) and use multiple passes to get all of the desired contours.
6. MSWRBR error in writing a record to tmp032.tmp.

Will occur if there is an error writing contour segment to tmp032.tmp. Check to make sure there is disk space and that you have
write privileges if applicable.
7. NEWOCI error in closing temporary file tmp032.tmp.

Will occur if there is an error closing tmp032.tmp. Check system configuration.
8. M607J4: No contour segments accepted from file tmp032.tmp.

Will occur if there are no contour segments found within the specified area and range. Check run file input and make sure it is
compatible with input data.
9. OPEN error = xxx on temporary segments file tmp032.tmp.

Will occur if the contour segments file cannot be reopened for sorting. Check system configuration and test file integrity.
10. File MSRDBR error = xxx

Will occur if there is an error reading tmp032.tmp. Check your machine setup and test file for corruption.

MineSight
11. File open error = xxx on segment File tmp033.tmp.

Contour aborted in M607N4.
Will occur if the sorted contour segments file cannot be opened. Check for disk space and file existence. Delete if it exists and
try again.
12. MSRDBR error = xxx on segment file tmp033.tmp.

Will occur if there is an error reading tmp033.tmp. Check your machine setup and test file for corruption.
13. M607Q4 error = xxx on strings file tmp033.tmp.

Will occur if there is an error writing contour segment to tmp033.tmp. Check to make sure there is disk space and that you have
write privileges if applicable.
14. OPEN error = xxx on strings file filename.

Contour aborted in M607O4.
Will occur if the contour strings file (File 30) cannot be opened. Check for disk space and file existence.
15. MSRDBR error = xxx on strings file filename.

Will occur if there is an error writing a contour string to File 30. Check to make sure there is disk space and that you have write
privileges.
16. Points in contour string exceed array limits= 10000.

Will occur if the number of points in a single contour exceeded limit of 10000. Limit the area being contoured with the run file
and use multiple passes to get all desired contours.
17. AN ERROR HAS OCCURRED READING DTM INPUT FILE

Will occur if a DTM file (File 19) cannot be read. Check to make sure the file is a DTM created by CREDTM and that the file
is not corrupted.
18. M60704: WARNING Index Contour Interval is less than or equal to BaseContour Interval.
No Index Contours will be generated.
Plot commands will still be written to File 30 but only for the base contours. The index contour interval, PAR6, should be a
multiple of 2 or more of the base contour interval, PAR5.

MineSight
Proprietary Software: Mintec, inc. M608V1 - CLASSICAL STATISTICALANALYSIS OF MODEL DATA
M608V1 CLASSICAL STATISTICAL

ANALYSIS OF MODEL DATA

M608V1 summarizes mine model data using the classical M608V1 is used to compute the statistics of model items at
frequency distribution with the same format used in programs different cutoff grades. The program outputs the number of
M401V1 and M402V1 for drillhole and composite data. blocks or the weight, percent above cutoff, average grade,
and standard deviation at each cutoff grade. It also outputs a
histogram with a cumulative frequency distribution of the grades.
PROGRAM FLOW DIAGRAM
M608V1 can calculate statistics on up to 99 items in a single run.
RUN FILE: However, the cutoff grade statistics and the histogram are based
- Mine model area on the first model item specified in the ITM1 line.
- Item to access
- Type of frequency The program allows the statistics of negative values for
distribution untransformed data. However, when log option is used, the
- Plot specifications
negative values are ignored. On the other hand, the program
does not ignore zero values.
Any zero interval is first assigned a very small value (0.000001)

before it is transformed to logs (-13.815). Therefore, if the user
INPUT: CALCS: wants to include the zeros in the statistics, he or she should set
PAR7= -14 or less.
- PCF - Extract area and items
- Mine Model File (File - Calculate frequency
13, 14, or 15) distribution Two weighting factors can be used to weight the statistics (i.e.
- Create histogram and tonnage or specific gravity weighting).
table of grade intervals
The statistics based on the natural logarithm of the model grades
can be obtained by setting IOP13=1. The log means can be
transformed to normal by setting IOP13=2.
OUTPUT: Data can be selected on the basis of Range, Omit or Table

commands.
- M122 Plot File
- Summary output for Two different types of M122 plot files can be generated:
MHISTO
With IOP9=1 or 2 and 19=filename, M608V1 will
generate a plot file with data only for either frequency
distribution or bench statistics. Titles, labels and
borders must be added with the M122 run file (see
sample).
With IOP9=0 and 30=filename, an input file for the

post-processor program, MHISTO, is generated.
Running MHISTO will create both printer and plotter
files for the frequency distribution, complete with titles,
labels and borders. Bench statistics cannot be plotted
with this option. When M608V1 is run through the
menus, this option is used.
The program can output statistical data in a spreadsheet format

to the filename specified by 31= in the run file.
Revised: 19-September-01 Page 608-1

MineSight
M608V1 - CLASSICAL STATISTICALANALYSIS OF MODEL DATA Proprietary Software: Mintec, inc.
Page 608-2 Revised: 19-September-01

MineSight
Proprietary Software: Mintec, inc. M608V1 - CLASSICAL STATISTICAL ANALYSIS OF MODEL DATA
M608V1 - CLASSICAL STATISTICAL ANALYSIS OF MODEL DATA
RUN FILE OPERATION


MEDS-608V1 19=filename 30=filename 3=filename 31=filename 32=filename
where

19 = the name of the OUTPUT FILE FOR M122 (if IOP9=1 or 2)
30 = the name of the SUMMARY TABLE FILE (optional; input for MHIST)
31 = the name of the OUTPUT FILE IN SPREADSHEET FORMAT
32 = the name of the OUTPUT FILE FOR BENCH ANALYSIS IN SPREADSHEET FORMAT
IOP2 = 1 OMIT FREQUENCY INTERVAL ACCUMULATION

IOP3 = 1 DO NOT REPORT 1ST ITEM
NOTE: When this option is ON, the sums within the frequency intervals will not be accumulated.
IOP4 = 0 NO BOUNDARY
= 1 USE BOUNDARY
NOTE: If IOP4=1, the specified boundaries can be in a separate file. Use one of the following command
lines:
CMD = INCL LOCPT FILE filename (to include points within the boundary) OR
CMD = EXCL LOCPT FILE filename (to exclude points within the boundary)
IOP5 = FIRST COLUMN OF MINE MODEL TO ACCESS (default=1)

IOP6 = LAST COLUMN OF MINE MODEL TO ACCESS (default=NX)
IOP7 = FIRST ROW OF MINE MODEL TO ACCESS (default=1)
IOP8 = LAST ROW OF MINE MODEL TO ACCESS (default=NY)
IOP9 = 0 DO NOT GENERATE PLOT COMMANDS
= 1 GENERATE PLOT COMMANDS FOR BENCH STATISTICS
= 2 GENERATE PLOT COMMANDS FOR FREQUENCY DISTRIBUTION
NOTE: If IOP9>0, plot commands are written to File 19 which must be specified on the Names Line.
The bench statistics plot is limited to 10 inches vertically.

MineSight
M608V1 - CLASSICAL STATISTICAL ANALYSIS OF MODEL DATA Proprietary Software: Mintec, inc.
IOP10 = 0 PROGRAM COMPUTES THE LOG INCREMENT BASED ON PAR8 AND IOP12
= 1 LOG INCREMENT IS THE SAME AS PAR8
NOTE: IOP10 is used only if IOP13 > 0
IOP11 = # OF ITEMS FOR STATISTICS (used only with GET15)
IOP12 = # OF INTERVALS FOR HISTOGRAM (default=20, max=100)
IOP13 = 0 NO TRANSFORMATION OF DATA

= 1 LOGTRANSFORMATION OF DATA (log means are printed)
= 2 LOGTRANSFORMATION OF DATA (log means are transformed to normal)
IOP14 = 0 MULTIPLY WEIGHTS

= 1 CHOOSE MINIMUM WEIGHT
NOTE: IOP14 is used only if two weighting items are entered.
IOP15 = 0 DONT INVERT WEIGHTING ITEMS

= 1 INVERT FIRST WEIGHTING ITEM
= 2 INVERT SECOND WEIGHTING ITEM
= 3 INVERT BOTH WEIGHTING ITEMS
NOTE: If IOP14 =1, then if IOP15 = 1, 2 or 3, program will use the maximum value only.
Optional integer values for TABLE command
IOP16-25 = INTEGER VALUE OF ITM ITEM
Frequency table parameters
PAR7 = VALUE OF FIRST FREQUENCY INTERVAL (default=0 if IOP13=0; default=-8 if IOP13>0)

PAR8 = SIZE OF FREQUENCY INTERVALS (default=0.1)
PAR9 = MINIMUM VALUE OF FIRST MODEL ITEM
NOTE: If the CONTROLLING ITEM (ITM1) is less than PAR9, that block will not be used. PAR9 should
be in untransformed units regardless of the IOP13 value.
The following parameters can be used with the weighting items:

PAR10 = optional multiplier for 1st weight
PAR11 = optional multiplier for 2nd weight
PAR12 = optional multiplier for block values
PAR13-36 = optional frequency intervals
Limiting items to control the run
ITMn = label-15 GRADE (controlling item for run)

. .
. .
ITMn = label-15 GRADE
NOTE: The keyword GRADE can be replaced with the keywords VALUE or Q.P. A maximum of 10
items are allowed for a table. Up to 99 items can be used with keyword GRADE. EXTRA is not
a keyword, but if EXTRA is used, that item will be skipped.
ITMn = label-15 WT#1 <default value> (optional weighting item #1)

ITMn = label-15 WT#2 <default value> (optional weighting item #2)

MineSight
NOTES: 1. If <default value> is specified, it will be used for blocks where weighting item is undefined.
If it is not entered, blocks with undefined weight will not be included in calculations.
2. You can use DUMMY for item name to specify a constant weight value.
Optional weighting by block volume
To use block volume as additional weight multiplier specify:
For 3DBMs:
CMD = BLOCK VOL WT
For GSMs:
CMD = BLOCK VOL WT label-15
Where label-15 is the label of the thickness item.
This option is not available for GSFs.
Optional data selection with RANGE, OMIT or TABLE
ITMn = label-15 RANGE min-value max-value

ITMn = label-15 OMIT min-value max-value
ITMn = label-15 TABLE IOPm IOPn
Optional Z coordinate item (for 3D rotated GSM models)
CMD = ZCRD label-15
END
4. BOUNDARY POINT LINE (if IOP4=1)
Where 0 0 ends the input or input ends on end-of-file. Boundary point must close. The maximum number of boundary points allowed
is 2000.
If using a 3D-rotated GSM file 15 or 3D-rotated files 13 & 14, you must specify the Z coordinate model item by using:
CMD = ZCRD label-15.
5. BENCH REQUEST LINES (free-field format)
REF#1 REF#2
where
REF#1 = FIRST MINE MODEL BENCH (default = 1)

REF#2 = LAST MINE MODEL BENCH (default = Last bench initialized using M601V1)
All benches between REF#1 and REF#2 will be used. Several Request Lines may be entered sequentially to select particular benches,
seams, etc.

MineSight

MEDS-608V1 19=PLT608.PAA
* 3-D BLOCK MODEL STATISTICS-TCU-1 AND MO-1 VALUES *
COM* SAMPLE RUN FOR BENCH # 20 (ELEV 3600)
USR = ABC
IOP9 = 2 / 1=PLOT BENCH STATS, 2=PLOT FREQ DIST

IOP12 = 20 / 20 INTERVALS
PAR7 = .0 .02 .0001 / BEGIN FIRST INT, INCR, MIN VALUE
ITM1 = TCU-1 GRADE/ FIRST GRADE ITEM

ITM2 = MO-1 GRADE/ SECOND GRADE ITEM
END
20
M122V1 SAMPLE RUN FILE #1 - (for plotting files generated when IOP9>0)
** FREQUENCY DISTRIBUTION OF MODEL **
USR = ABC
MAP = 0 9 1 0 11 1
PLT = .07 0 0 0 0 .6
END
BORDR 0 0 9 0 11
BORDR 0 .9 7.9 .9 10.9
COORD 0 1.8 . 7 8. .7 1. .1 0 2 .40 . 40 /
LABEL 0 3.5 .4 0. .1 20 COPPER GRADE
LABEL 0 .5 3.5 90 .1 20 PERCENT FREQUENCY
COORD 0 .6 1.9 .6 11. 1. .1 0. 0 10 10 /
SHIFT 0 .9 .9
TICKS 0 7 0 0 0 .25 .05
TICKS 0 0 0 0 10 1. .1
PEN# 2
USERF PLT608.PAA
ENDOC
NOTE: The default plot size for M608V1 is 8 1/2 x 11 in. If you are plotting on a metric device, insert
the following command in your M122 run file: FACTR 0 2.54 or use the factor option in the PLT
command line.

MineSight

MEDS-608V1 30=DAT608.0B
* 3-D BLOCK MODEL STATS - TCU-1 & MO-1 VALUES - USE MHISTO TO CREATE PLOT FILE *
COM* SAMPLE RUN FOR BENCH # 15-20
USR = ABC
IOP9 = 0 / 0=OMIT M122 OUTPUT, 1=PLOT BENCH STATS, 2=PLOT FREQ DIST
IOP12 = 20 / 20 INTERVALS IOP16
= 1 2 / ROCK CODE LIMITS (SEE ITM3)
PAR7 = .0 .02 .0001 / BEGIN FIRST INT, INCR, MIN VALUE
ITM1 = TCU-1 GRADE/ FIRST GRADE ITEM

ITM2 = MO-1 GRADE/ SECOND GRADE ITEM
ITM3 = CODE TABLE 16 17/ LIMIT BY ROCK CODE
END
15 20
M122V1 SAMPLE RUN FILE #2 - (for plotting files created with MHISTO)
MEDS-122V1 10=SAMP10.DAT 3=RPT122.LB
** COMPOSITE BENCH DISTRIBUTION PLOT - T-CU **
USR = ABC
MAP = 0. 30. 1. 0. 25. 1.

PLT = .07 0 0 0 0 .6
END
USERF HISTO.PLT
ENDOC

MineSight

MEDS-608V1 10=TEST10.DAT 15=TEST15.DAT 3=RPT608.LB;
* 3-D BLOCK MODEL STATS IDS METHOD - NEW ALTR CODES *
USR = ABC
IOP2 = 1 / 1=OMIT FREQ ACCUMULATION

IOP3 = 1 / 1 =OMIT REPORTING 1ST ITEM.
IOP5 = 1 2 / ROCK CODE LIMITS (SEE ITM3)
IOP9 = 51 60 66 75 / ROWS AND COLUMNS
IOP12 = 20 / 20 INTERVALS
PAR7 = .0 1.0 .0 / BEGIN FIRST INT, INCR, MIN VALUE
ITM01 = ALTR GRADE / FIRST GRADE ITEM

ITM02 = CUIDS GRADE / SECOND GRADE ITEM
ITM03 = AUIDS GRADE / LIMIT BY ROCK CODE
I-O = 1
END / BENCHES
01 40

MineSight
1. ?M608V1: ERROR. Your model file is empty. You MUST initialize your file with M601V1 before proceeding.
2. ?M608V1: ERROR. You have not specified any ITEMs

You must specify an ITEM on which to perform the statistics.
3. ?M608V1: ERROR. Bench xx specified on BENCH REQUEST LINE exceeds the last bench initialized yy
Your model has only been initialized through bench yy and you are trying to access bench xx. If you really want to access bench
xx, you must re-run M601V1 to initialize your model down to that bench.
4. M608V1: ERROR. No LEVELs were specified.

You have not specified the benches on which to perform the statistical analysis. Select the benches using the Bench Request Lines.
5. ?M608V1: ERROR. No file 15, 14, or 13 specified on the Names Line.

6. ?M608V1: ERROR. Your ROW and COLUMN selections are not logically consistent.
First COLLast COLMax COLFirst ROWLast ROWMax ROW3524022160
Something is wrong with the way you selected the ROWs and COLUMNs to use in the statistical analysis (IOP5IOP8). In the
above example, the last column to access (52) exceeds the maximum number of columns in the model (40). Also the last row
to access (1) precedes the first row to access (22).
7. When calculating log stats, the function of PAR8 is based on IOP10. If IOP10 is 0, the program will compute a log increment
based on PAR8 and the number of increments used. If IOP10=1, then PAR8 becomes the actual interval used.

MineSight

MineSight
Proprietary Software: Mintec, inc. M609V1- CROSS-SECTION (M122)OF MINE MODEL DATA
M609V1 CROSS-SECTION (M122) OF MINE MODEL DATA

M609V1 accesses the mine model files and prepares M122 plot M609V1 is used to generate vertical cross-sections through the
files for vertical cross-sections. Sections may be oriented at any 3-D Block Model (File 15) or the GSM (File 15). Sections can
angle through the model. also be cut through the 2-D Surface File (File 13). A section
through File 15 can also be limited by topography from File 15
or from File 13.
PROGRAM FLOW DIAGRAM Up to four items can be plotted in section and the location of the
plotted label, the character height of the label, and the pen
RUN FILE: number can all be changed. You may choose which seams or
- Type of cross-section benches to plot as well as the starting and ending points of the
- Model items to display section line. Multiple sections can be generated in a single run.
- Format for output data
M609V1 is used to set up the primary plot commands used to
plot a mine model in cross-section. Other data such as geologic
outlines, topography profiles, etc. may be added to the M609V1
plot commands. M609V1 does not output any border or plot
annotations other than the seam label.
INPUT: CALCS: The M122 plot file that is created can be an ASCII file or a
- PCF - Retrieve a row of data
binary file. For an ASCII file, use a USERF command in the
- Mine Model File (File - Select data ranges M122 run file. For a binary file, use a DATAF command in the
13 or 15) - Remove blocks above M122 run file.
topo
- Calculate annotation
coordinates
OUTPUT:
- M122 Plot File (ASCII or

binary)

MineSight
M609V1 - CROSS-SECTION (M122)OF MINE MODEL DATA Proprietary Software: Mintec, inc.

MineSight
Proprietary Software: Mintec, inc. M609V1-CROSS SECTION OF (M122) OF MINE MODEL DATA
M609V1 - CROSS-SECTION (M122) OF MINE MODEL DATA
RUN FILE OPERATION

MEDS-609V1 10=filename 15(or 13)=filename;

where

15 = the name of the MINE MODEL FILE (GSM or 3-D)
NOTE: The PLOT filename is specified on the CROSS-SECTION REQUEST LINES.
IOP3 = TYPE OF LINE THROUGH SURFACES

= -1 STAIR-STEP DISPLAY THROUGH EACH BLOCK
= 0 STRAIGHT LINE SEGMENTS JOINING MIDPOINTS
= 1 SMOOTH CURVE JOINING MIDPOINTS (SEE FLINE IN M122V1 DOCUMENTATION)
= 2 USE M122V1 COMMAND DASHL (1 SIZE PATTERN, SEE M122V1 DOCUMENTATION)
IOP7 = IZ1 FIRST BENCH REF# TO ACCESS (DEFAULT=1)

IOP8 = IZ2 LAST BENCH REF# TO ACCESS (DEFAULT=NZ)
IOP9 = 0 USE BENCHES SPECIFIED BY IOP7 & IOP8

= 1 READ BENCHES TO BE USED AT END OF RUN FILE
NOTE: If IOP9=1, add lines containing bench reference numbers after END (see Section 4). These Bench
Request Lines precede the Cross-Section Lines.
IOP10 = M122V1 COMMAND DASHL PATTERN NUMBER

(IF IOP3=2, SEE M122V1 DOCUMENTATION FOR PATTERN NUMBERS)
IOP11 = 1 PLOT BLOCK OUTLINE (OR ITMN=PLOT BLOCK OUTLINE)

= 2 FILL BLOCK
IOP12 = 0 M122 ASCII OUTPUT TO PLOT FILE

= 1 M122 BINARY OUTPUT TO PLOT FILE
IOP13 = -1 OMIT GSM END-OF-SEAM LABELS
= 0 USE GSM END-OF-SEAM LABELS
> 0 PLOT GSM BLOCK VALUES
NOTE: Assumes item to plot is ITM1, ZTOP=ITM2, and ZBOT=ITM3.

MineSight
M609V1-CROSS SECTION (M122) OF MINE MODEL DATA Proprietary Software: Mintec, inc.
IOP14 = 0 NORMAL COORDINATE OUTPUT

= 1 FLIP X AND Z COORDINATES ON OUTPUT (FOR VERTICAL GSM)
NOTE: If IOP18 = 0 (section in project coordinates) and PCF is a 3D-rotated PCF, then IOP14 will be
ignored.
IOP15 = -1 COLOR OUTLINE/VALUES BASED ON FIRST VALUE, BUT DO NOT PLOT FIRST VALUE
= 0 PLOT GRADES
= 1 DO NOT PLOT GRADES. USE GRADE TO SELECT PEN # FOR BOX
IOP16 = MAXIMUM PEN NUMBER TO USE FOR COLORING GSM LEVELS BY THEIR NUMBER
NOTE: If IOP16=8, then levels 1-7 will be plotted with pens 2-8 respectively, levels 8-14 will use pens 2-
8 as well, etc.
IOP17 = 0 PAR7 ANGLE IS COUNTED FROM HORIZONTAL

= 1 PAR7 ANGLE IS COUNTED FROM MODEL BENCH
NOTE: Used for 3D-rotated models ONLY.
IOP18 = 0 SECTION IS ENTERED IN PROJECT COORDINATES

= 1 SECTION IS ENTERED IN MODEL COORDINATES
NOTE: If IOP18 = 0, the section MUST be parallel to the model Z direction.
IOP19 = 0 IF IOP18 = 1, PLOT IN MODEL COORDINATES

= 1 IF IOP18 = 1, PLOT IN PROJECT COORDINATES
: IOP19 is ignored if IOP18 = 0.
IOP19 = 1 can be used ONLY if the model Z direction is parallel to one of the project coordinate
axes.
If IOP19 = 0, then direction along the section is horizontal, unless IOP14 = 1.
ITMN = LABEL-15 FW.D MIN-VALUE

ITMN = LABEL-15 FW.D (OPTIONAL 2ND ITEM) (REQUIRED ZTOP FOR GSM IF IOP13 > 0)
ITMN = LABEL-15 FW.D (OPTIONAL 3RD ITEM) (REQUIRED ZBOT FOR GSM IF IOP13 > 0)
ITMN = LABEL-15 FW.D (OPTIONAL 4TH ITEM)
ITMN = LABEL-13 TOPO VALUE (OPTIONAL)
NOTE: The first, (up to 4), items must be the plot items with TOPO and RANGE/OMIT/TABLE items
following.
Label-15 is the item to plot from the mine model. Fw.d is the display format for the item. Min-
value is the minimum value to plot. No block will be plotted if its value is less than the min-value.
If specified, a value should be entered to indicate the least topo percentage value of a block to be
plotted. Blocks with a TOPO% less than value will be omitted. File 13 can be used along with
File 15 for topo truncation on a GSM plot. In this case, specify File 13 on the Names Line and an
ITMn=label-13 TOPO line, instead of label-15 TOPO above.
ITMN = PLOT BLOCK OUTLINE (OR IOP11=1)
PAR1 = HORIZONTAL MAP SCALE FOR M122V1 RUN (DEFAULT = 2*DX)

MineSight
PAR2 = VERTICAL MAP SCALE FOR M122V1 RUN (DEFAULT = PAR1)
NOTE: When plotting a 3D-rotated model in project coordinates, use PAR2 = PAR1.
PAR3 = CHARACTER HEIGHT FOR ANNOTATION (DEFAULT = 0.10 INCH)
NOTE: Values above 0.5 are set to 0.1. (For GSM if PAR3 would cause value to be larger than seam on
plot, it doesnt plot it.)
PAR4 = VERTICAL SPACING FOR MULTIPLE VALUES (DEFAULT = 0.05 INCHES)
PAR5 = HORIZONTAL SPACING FROM LEFT SIDE OF BLOCK (DEFAULT = 0.05 INCHES)
PAR6 = VERTICAL SPACING FOR TOP VALUE (DEFAULT = 0.05 INCHES)
PAR7 = ANGLE AT WHICH TO PLOT BLOCK LABEL (DEFAULT=0)
NOTE: Use 0.01 to override seam angle labeling in GSM block plot.
PAR8 = PLOT BLOCK OUTLINE OFFSET IN PLOTTER UNITS
PAR10 = M122V1 COMMAND DASHL LENGTH (DEFAULT = 0.1)
NOTE: Use if IOP3=2.
PAR12 = PERCENT SHADING (DEFAULT=100.0 FOR 100%)
PLT = CUTOFF VALUES TO CONTROL COLORING (FOR USE WITH A 4 PEN PLOTTER):
VMAX1 VMAX2 VMAX3 VMAX4 P1 P2 P3 P4

WHERE
VALUE COLOR
0.0 X VMAX1 P1
VMAX1 X VMAX2 P2
VMAX2 X VMAX3 P3
VMAX3 X VMAX4 P4
X VMAX4 P1 SET VMAX4 TO 999 (OR HIGHER THAN ANY GRADE) TO AVOID
REVERTING TO PEN 1.
NOTE: P1, p2, p3 and p4 are optional pen numbers. default is 1, 2, 3, 4. Cutoffs are applied to ITMn item.
If vmaxn=0, then a default of 99999. is used as a cutoff. If you want to specify a cutoff of 0.0,
specify a small number (i.e. 0.001). Cutoffs should be stated in the same precision as the data.
For increased pen numbers:
CMD = PLOT CUT V1 V2 V3 ... V15 (FOR CUTOFFS)

CMD = PLOT PEN V1 V2 V3 ... V16 (FOR PEN NUMBERS)
NOTE: Always list one more pen number than you have cutoffs. The additional pen is for any material
greater than the last cutoff.

MineSight
ITMN = LABEL-15 RANGE MIN-VALUE MAX-VALUE

ITMN = LABEL-15 OMIT MIN-VALUE MAX-VALUE
ITMN = LABEL-15 TABLE IOPM IOPN
END
4. BENCH REQUEST LINES (If IOP9=1)
Each Bench Request Line contains up to 10 bench numbers in free-field format. A blank line ends input.
5. CROSS-SECTION REQUEST LINES
X1 Y1 X2 Y2 FILENAME
WHERE
X1 & Y1 = Beginning point of section line

X2 & Y2 = Ending point of section line
filename = Output M122 plot file
There should be at least one blank column preceding the M122 plot filename.

MineSight

* EXTRACT T-CU VALUES FROM A SECTION OF 3-D BLOCK MODEL *
COM* ROW #23 (12250 NORTH)
USR = ABC
IOP7 = 1 39 / 1ST BENCH, LAST BENCH TO ACCESS

IOP12 = 0 / 0=ASCII PLOT FILE,1=BINARY PLOT FILE
ITM1 = TCU-1F5.2 .01/ PLOT TOTAL COPPER

ITM2 = TOPOTOPO50/ EXCLUDE AIR BLOCKS
PLT = .19 .49 .99 999 1 2 3 4/ CUTOFFS FOR PEN CHANGE
PAR1 = 500 500 / HORIZ AND VERT SCALE

PAR4 = .02 / VERT SPACING FOR MULT VALUES (default=.05")
PAR5 = .02 / HORIZ SPACING FROM LEFT EDGE OF BLOCK (default=.05")
PAR6 = .02 / VERT SPACING FROM TOP EDGE (default=.05")
END
10500 12250 14500 12250 PLT609.PAA

* PLOT BLOCK T-CU, E-W SECTION @ 12300 AN *
USR = ABC
MAP = 0 5000 500 1500 5000 500

PLT = .07
END
USERF PLT609.PAA
ENDOC

** TOPO FOR X-SECTION 12500 **
USR = ABC
IOP3 = 1 / SMOOTH POINTS

ITM1 = TOPOG F4.0 1 / ITEM TO PLOT
PAR1 = 200 200 / SCALES
END
10000 12500 15000 12500 PLT609.PAB

MineSight
1. ?M609V1: ERROR. Your model file is empty.

YOU MUST INITIALIZE YOUR FILE WITH M601V1 BEFORE PROCEEDING.
3. ?M609V1: ERROR. No plot ITEMs are specified
You must specify at least one ITEM to plot. For example, ITM1=ASHF5.20
4. %M609V1: WARNING. First BENCH to plot, xx, exceeds last bench initialized.
First BENCH being set to yy.
You have specified IOP7=xx, but your model file has only been initialized through bench yy. Therefore, the only benches
you can access are 1 through yy.
5. %M609V1: WARNING. Last BENCH to plot, xx, exceeds last bench initialized.
Last BENCH being set to yy.
You have specified IOP8=xx, but your model file has only been initialized through bench yy. Therefore, the only benches
you can access are 1 through yy.
6. %M609V1: WARNING. Last BENCH to plot, xx, is less than first BENCH.
Last BENCH being set to yy.
The last bench to plot as specified by IOP8 is less than the first bench to plot specified by IOP7.
7. %M609V1: WARNING. Skipping bench xx

The last initialized bench is yy
You have only initialized through bench yy (M601V1) and are attempting to plot data for bench xx which has never been
initialized. If you get this message, you probably used the Bench Request Lines to select your benches.
8. If no items are plotted when you plot GSM blocks (IOP13=1), check the vertical scale. If there is not enough room, the label
will not be plotted. Specify the item to be plotted as ITM1 with ZTOP and ZBOT as ITM2 and 3.
9. If no data is plotted, check these things:

- There must be at least one Cross-Section Request Line.
- You must have interpolated or loaded the data into the mine model.
- Any Bench Request Lines specified must end with a blank line.
10. To plot the model columns for GSM plots or block outlines for 3-D models, set IOP11=1 or use ITMn=PLOT BLOCK
OUTLINE.

MineSight
Proprietary Software: Mintec, inc. M610V1 - ENTER DATA INTO A MINE MODEL FILE
M610V1 ENTER DATA INTO A MINE MODEL FILE

M610V1 is used to enter either integer or real data into the mine Grade data, geological codes and ownership codes are examples
model files. Only one item can be updated at a time. of items that can be entered with this program. M610V1 can
also be used to print symbol maps of existing data in Files 13,
14 or 15.
PROGRAM FLOW DIAGRAM Coding can be done manually or M656V1 or V2 can produce
the input file from the VBM data file.
RUN FILE:
- Format of data
- Area/item selection
- Symbol map specification SUGGESTIONS FOR MANUALLY CODING DATA
1. Pick a standard format for the coding.
If IOP11=0 and File 14 or 15 is being used
INPUT: CALCS: Variable Columns Description

- PCF - Read input file
- Mine Model File (13, - Load model with values LCHK 1-5 Ref. # of bench
14 or 15) - Plot symbol map IROW 6-10 Row # within the bench
- Optional input file
IX1 11-15 First column of codes
IX2 16-20 Last column of codes
IN1 21-23 Integer value for IX1
IN2 24-26 Integer value for IX1 + 1
.
.
OUTPUT: IN20 78-80 Integer value for IX20
- Printer Output File The format statement for the above input data is:
FMT1 = (4I5,20I3)
For this option, LCHK, IROW, IX1 and IX2 must be

entered on each and every data line input to M610V1.
Revised:6-June-01 Page 610-1

MineSight
M610V1 - ENTER DATA INTO A MINE MODEL FILE Proprietary Software: Mintec, inc.
If IOP11=0 and File 13 is being used or if IOP11=2 3. Overlay the grid on the map to be manually coded and
read off a code for each block (or series of blocks) and
Do not use a bench reference number. record on a coding form such as that suggested in Step 1
above.
Variable Columns
IROW 1-5 4. It is easier and faster to use two people to manually code
IX1 6-10 a map: one person to visually code and the other to
IX2 11-15 record the data on the coding form. The use of two
IN1 16-18 people in this way is less error prone than one person
IN2 19-21 working alone and is usually much faster.
etc. to IN20
The format statement for the above input data is:

FMT1 = (3I5,20I3) PROCEDURE TO TEST INPUT DATA
If real numbers are being loaded, as with IOP11=2, a

sample format might be: 1. Test each data line for the end of the bench. The end of
FMT1 = (3I5, 10F6.3) each bench is specified by a blank line (IROW=0 and
IX1=0).
If IOP11=1
2. Test the input columns IX1 and IX2 against IOP5 and
If STRIPPER pit partials data is being loaded (output from IOP6 for a valid range.
M659V1), the format must be a mixture of integers and
real data. Use the F6.2 format so that the partial from 3. Test for a string of like codes between columns IX1 and
M659V1 is recognized as a percent, not a whole number. IX2 by checking for a -1 in code IN2. When a -1 is
For example, if the partial for a block is 65, the F6.2 format encountered in IN2, all blocks specified will be assigned
causes that number to be read as .65. the value of code IN1. The number of blocks between
columns IX1 and IX2 may be larger than the maximum
Variable Columns
number of block codes per line (IOP2). For example, if
LCHK 1-3 (I3)
the suggested format is used with a maximum of 20
IROW 4-7 (I4)
codes per line, there may be cases where 40 blocks will
IX1 8-11 (I4)
have the same code. Then set IX1=1, IX2=40, IN1=value
PX1 12-17 (F6.2)
and IN2=-1 on the input line to store all 40 codes.
IX2 18-24 (I6)
P2 25-30 (F6.2)
4. When IOP3=0, the code stored for each block between
If IOP11=3 IX1 and IX2 will be exactly as input, including those
specified as zero.
If DIPPER pit partials data is being loaded (output from
M728V1) the format must be a mixture of integers and real 5. When IOP3=1, a code will be stored only if the value is
data. non-zero. This allows you to update selected blocks in
the range of IX1 to IX2 without entering codes for blocks
Variable Columns that will stay the same.
LCHK 1-3 (I3)
IROW 4-7 (I4) NOTE: If there are any errors on an input line, the entire set of
IX1 8-11 (I4) codes for that line will be ignored. The print file will contain
PX1 12-19 (F8.4) messages informing you of any input data that was omitted due
IX2 20-23 (I4) to errors. Check the print file for any errors.
PX2 24-31 (F8.4)
2. Construct an overlay, preferably on mylar, with blocks at
the scale of the map to be coded. M122V1 can be used to
produce such an overlay. Size blocks according to the
parameters DX and DY in the PCF.

MineSight
Proprietary Software: Mintec, inc. M610V1 - ENTER DATA IN MINE MODEL FILE
M610V1 - ENTER DATA INTO A MINE MODEL FILE
RUN FILE OPERATION


where

19 = the name of the OPTIONAL INPUT FILE (see IOP9)
I-O = 1 PRINT A LIST OF ALL INPUT DATA
IOP2 = MAXIMUM # OF BLOCK CODES PER LINE (default=20; GSM=24)
IOP3 = 0 STORE ALL VALUES, EXACTLY AS INPUT

= 1 STORE VALUES IF NOT ZERO
IOP4 = 0 NORMAL RUN, INPUT & STORE DATA

= 1 PRINT SYMBOL MAP OF EXISTING MODEL DATA (do not store any new data)
NOTE: For IOP4=1, list the benches you want printed after the END line, one bench per line.
IOP5 = FIRST MODEL COLUMN TO STORE DATA (default=1)

IOP6 = LAST MODEL COLUMN TO STORE DATA (default=NX)
IOP7 = FIRST MODEL ROW TO STORE DATA (default=1)

IOP8 = LAST MODEL ROW TO STORE DATA (default=NY)
IOP9 = 0 INPUT DATA IS IN RUN FILE

= 1 INPUT DATA IS IN A SEPARATE FILE
IOP10 = 0 OMIT THE SYMBOL MAP

= 1 PRINT THE SYMBOL MAP

MineSight
M610V1 - ENTER DATA IN MINE MODEL FILE Proprietary Software: Mintec, inc.
IOP11 = 0 BLOCK INTEGER CODES (File 15 format)

= 1 M659V1 STRIPER PIT BLOCK PARTIALS
= 2 REAL CODES (If using File 15, see IOP15)
= 4 M728V1 DIPPER PIT BLOCK PARTIALS
IOP12 = COLUMN OFFSET FOR COLUMN TO BE STORED

IOP13 = ROW OFFSET FOR ROW TO BE STORED
IOP14 = LEVEL OFFSET FOR LEVEL TO BE STORED
NOTE: For example, if the bench number in the input data lines is 17 and IOP14=3, the data would be stored in
bench 20.
IOP15 = LEVEL NUMBER WHEN IOP11=2 AND FILE 14 OR 15 IS BEING USED
IOP16 > 0 INDICATES CODE TO ASSIGN TO MODEL ITEM WHEN|

1) IOP11=1 AND PARTIAL % IS GREATER THAN OR EQUAL TO PAR3 (Sample Run File #3),
2) IOP11=3 (Sample Run File #4)
IOP17 = NUMBER OF FILE 19 HEADER LINES TO SKIP
ITMn = label-nn (Model item to receive input data)
FMT1 = FORMAT FOR INPUT DATA
bench# row# col1 col2 values IOP11=0 and Files 14 and 15

bench# row# col1 part1 col2 part2 IOP11=1 (Partials)
row# col1 col2 values IOP11=0 and File 13 or IOP11=2
NOTE: For partials -
1) Part1 and part2 must be read as fractions between 0.0 and 1.0 (See the introduction and Sample Run File#2
for examples of a format statement for M659V1 output)
2) Blocks between col1 and col2 have a 100% partial
3) The item to store the block partial may be either a fraction item (0.0 - 1.0, precision=0.01) or a percent item
(0 - 100, precision=1)
Default format: IOP11=0: (3I5,20I4)
IOP11=1: (I3,2I4,F6.2,I6,F6.2)
IOP11=2: (3I4,10F8.1)
IOP11=3: (I3,I4,2(I4,F8.4))
PAR1 = MINIMUM VALUE TO BE DISPLAYED ON SYMBOL MAPS

(default = 1 for integer codes)
PAR2 = VALUE INCREMENT BETWEEN SUCCESSIVE SYMBOLS ON MAP

(default = 1 for integer codes)
(default = 10 * precision for non-integer items)
NOTE: The maximum number of map symbols is 36 (0-9 and A-Z), so use care in choosing PAR1 & PAR2 for
grade and other such items.
PAR3 = MINIMUM VALUE (IN PERCENT) FOR A BLOCK PARTIAL IN ORDER TO ASSIGN CODE IOP16 TO THE
BLOCK (used when IOP16>0 and IOP11=1)
NOTE: The combination of IOP11=1, IOP16>0, and PAR3 allows the user to assign a code item to a block
based upon a minimum partials cutoff.
If IOP11=3, leave PAR3=0.
END

MineSight
4. INPUT DATA LINES (free-field format)
If IOP11=0 and Files 14 or 15 are being used

bench#
bench# row# col1 col2 values
If IOP11=1
bench#
bench# row# col1 part1 col2 part2
If IOP11=0 and File 13 is used OR if IOP11=2

row# col1 col2 values
Bench# on bench line & data lines must match. If IOP4=1, list only the bench#s for which you want symbol maps. End bench data
input with a blank line or zero in bench#, row#, & col1.

MEDS-610V1 19=DAT610.IA
* LOAD DIGITIZED GEOLOGY CODES INTO MINE MODEL *
USR = ABC
IOP2 = 20 / NUMBER OF BLOCK CODES PER LINE

IOP3 = 0 / 0= STORE ALL VALUES AS INPUT; 1=STORE NONE 0 VALUES
IOP4 = 0 / 0=INPUT & STORE DATA; 1=SYMBOL MAP ONLY
IOP5 = 1 50 / COLUMNS
IOP7 = 1 50 / ROWS
IOP9 = 1 / 0=INPUT IN THIS RUN FILE, 1=INPUT IN UNIT 19 FILE
IOP10 = 1 / 0=OMIT SYMBOL MAP; 1= PRINT SYMBOL MAP
IOP11 = 0 / INPUT BLOCK INTEGER CODES
ITM1 = GEOL
FMT1 = (4I5,20I3)
I-O = 0 / 1= PRINT LIST OF INPUT DATA

END
M610V1 SAMPLE INPUT FOR RUN FILE #1 - BLOCK CODES FROM DAT610.IA
32 Bench line
32 14 21 40 0 2 2 2 2 2 2 2 0 0 0 ... Bench, row, first col, last col, col values
32 15 1 20 0 0 0 0 0 0 0 0 0 0 0 ...
32 15 21 40 2 2 2 2 2 2 2 2 2 2 0 ...
32 16 1 20 0 0 0 0 0 0 0 0 0 0 0 ...
32 16 21 40 2 2 2 2 2 2 2 2 2 2 2 ...
32 17 1 20 0 0 0 0 0 0 0 0 0 0 0 ...
32 17 21 40 2 2 2 2 2 2 2 2 2 2 2 ...

MineSight

MEDS-610V1 10=METL10.DAT 15=METL15.DAT 19=PRT801.ASC 3=RPT610.LB
** LOAD M659V1 PARTIALS TO MODEL FILE **
USR = ABC
IOP4 = 0 / 0=NORMAL RUN; 1=PRINT SYMBOL MAP ONLY
IOP5 = 0 0 / 1ST & LAST MODEL COLUMNS
IOP7 = 0 0 / 1ST & LAST MODEL ROWS
IOP9 = 1 / 1=DATA IN FILE 19
IOP10 = 1 / 1=PRINT SYMBOL MAP
IOP11 = 1 / 1=LOAD M659V1 PARTIALS
FMT1 = (I3, 2I4, F6.2, I6, F6.2)
PAR1 = 20 / MINIMUM VALUE TO DISPLAY (default=1 for integer item)

PAR2 = 5 / VALUE INCREMENT FOR SYMBOL CHANGE
ITM1 = TOPO / FILE 15 ITEM
END
M610V1 SAMPLE INPUT FOR RUN FILE #2 - PARTIALS FROM M659V1

20 0 0 0 0 0 20 3600.0 801 Bench, row, col1, part1, col2, part2,
20 19 24 8 25 45 20 3600.0 801 bench, elev, feature code
20 19 26 80 27 98 20 3600.0 801
20 19 28 100 30 99 20 3600.0 801
20 19 31 69 32 4 20 3600.0 801
20 20 19 8 20 62 20 3600.0 801
20 20 21 98 32 48 20 3600.0 801

MineSight

MEDS-610V1 10=CSMP10.DAT 15=CSMP15.DAT 19=PRT.DAT 3=RPT610.LC
** ASSIGN ROCK CODE 3 TO BLOCKS WHERE PARTIAL IS >= 50% **
USR = ABC
IOP3 = 1 / STORE ONLY NON-ZERO VALUES

IOP11 = 1 / 1=PARTIALS INPUT
IOP16 = 3 / CODE TO ASSIGN TO ITEM RTYP
FMT1 = (I3, 2I4, F6.2, I6, F6.2)
PAR3 = 50 / BLOCK MUST HAVE PARTIALS OF AT LEAST HALF
ITM1 = RTYP / FILE 15 ITEM

END

MineSight

MEDS-610V1 10=SAMP10.DAT 15=SAMP15.DAT 19=DIPPER.PRT 3=RPT610.LA
** LOAD DIPPER PARTIAL TO THE BLOCK MODEL SAMP15.DAT **
USR = ABC
COM ----------------------------------------------------------------------------------------
COM LOAD 3-D GEOLOGIC CODES
COM ---------------------------------------------------------------------------------------
IOP2 = 0 /MAXIMUM # OF BLOCK CODES PER INPUT LINE

IOP3 = 0 / 0=STORE ALL VALUES AS INPUT; 1=STORE IF >0
IOP5 = 0 0 / 1ST AND LAST MODEL COLUMNS
IOP7 = 0 0 / 1ST AND LAST MODEL ROWS
IOP9 = 1 / 1=INPUT DATA IS IN FILE 19=PIT1.PRT
IOP11 = 3 / OPTION FOR TYPE OF INTEGER DATA
COM 0 = INTEGER BLOCK CODES
COM 1 = M659V1 STRIPPER PARTIALS
COM 2 = FILE 13 REAL PARTIALS
COM 3 = M728V1 DIPPER PARTIALS
IOP16 = 5 / OPTIONAL CODE FOR PIT PARTIALS
ITM1 = DPIT / FILE 15 ITEM
COM ** THE FOLLOWING FORMAT IS FOR LOADING THE ASCII DATA

FMT1 = ( I3, I4, 2 (I4,F8.4)) /USER INPUT DIPPER PARTIAL FORMATS
END

MineSight

MEDS-610V1 10=METL10.DAT 15=METL15.DAT 19=DAT610.ID 3=RPT610.LD
** LOAD REAL NUMBERS TO FILE 15 **
USR = ABC
IOP2 = 10 / # VALUES PER RECORD (default=20)

IOP5 = 0 0 / 1ST & LAST MODEL COLUMNS
IOP7 = 25 25 / 1ST & LAST MODEL ROWS

IOP11 = 2 / 2=LOAD REAL #S TO MODEL
IOP15 = 20 / LEVEL#, IF IOP11=2 + FILE 15
FMT1 = (3I4, 10F6.3)
PAR1 = .01 / MINIMUM VALUE TO DISPLAY (default=1 for integer item)

PAR2 = .2 / VALUE INCREMENT FOR SYMBOL CHANGE
ITM1 = TOTCU/ FILE 15 ITEM

END
M610V1 SAMPLE INPUT FOR RUN FILE #5 - LOAD GRADES TO BLOCK MODEL
Row, col1, col2, col values
25 7 16 0.162 0.162 0.163 0.165 0.157 0.194 0.231 0.252 0.275 0.325
25 17 26 0.413 0.464 0.579 0.629 0.712 0.857 0.979 1.084 1.121 1.085
25 27 36 0.994 0.901 0.801 0.736 0.670 0.517 0.452 0.375 0.329 0.266
25 37 45 0.168 0.124 0.107 0.088 0.095 0.059 0.059 0.059 0.058

MineSight

1. ?M610V1: ERROR. Your model file is empty.
Your model file MUST be initialized using M601V1 before any other MineSight program can access it.
2. %M610V1: WARNING Skipping INPUT DATA LINE for BENCH xxx

You are attempting to access an uninitialized bench.
Input BENCH xxx Output BENCH yyy Last BENCH xxx
You are attempting to store data in bench yyy, a higher bench number than xxx, through which your model has been initialized.
Since the input bench is not the same as the output bench, a level offset must have been specified with IOP14. Both the input
and output benches MUST have been initialized with M601V1 before M610V1 can access them.
3. %M610V1: WARNING Skipping INPUT DATA LINE for INPUT bench xx and OUTPUT bench xx.
This INPUT bench might not match the bench number on the header line.
In the File 14 and 15 input data lines, there is a bench header line (i.e., a line with only a bench number on it) followed by the
data line(s). The bench number on the header line MUST be the same as the bench number(s) on the data line(s).
4. %M610V1: WARNING Skipping INPUT DATA LINE for INPUT bench xx and OUTPUT bench xx. The ROW/COL-
UMNs are badly specified.
ROW=10 Minimun ROW=6 Maximum ROW=9

COLUMN=730 Minimum COLUMN=1 Maximum COLUMN=40
You are trying to store data in row 10 but have limited the rows in which to store data to rows 6-9 (IOP7-IOP8). Row 10 is the
row number AFTER the row offset (IOP13) has been added. The same is true for the columns.
5. %M610V1: WARNING Skipping INPUT DATA LINE for INPUT bench xx and OUTPUT bench xx.
The number of COLUMNs specified (e.g. 101-130) exceeds the maximum, e.g. 20 (IOP2).
For bench xx, you are trying to enter values for 30 columns (columns 101-130) on a single data input line. However, the maximum
number of values per line, as specified with IOP2, is 20. In this case, you can have at most 20 values entered on a single line.
6. ?M610V1: ERROR. No File 15, 14, or 13 specified on the NAMES line.
You have not specified a model file on the Names Line in your run file, e.g., SAMP15.DAT.
7. ?M610V1: ERROR. You have not specified any ITEM.
You MUST select an ITEM in your model file in which to store your code.
8. Check the Printer Output File for any error messages after the run. Check the symbol map for incorrect data.
9. If no symbol map is printed, check that IOP10=1. A symbol map of existing data can be printed if IOP10=1 and IOP4=1. You
must also specify a bench header line for each bench for which you want a map.
If too many symbol maps appear, check that you are not running the program with IOP10=1, IOP4=1 and a file of coded data.
Use only a bench header line.

MineSight
Proprietary Software: Mintec, inc. M610V2-ENTER REAL DATA IN MINE MODEL FILE
M610V2 ENTER REAL DATA INTO A MINE MODEL FILE

M610V2 is used to enter real data into the mine model files to M610V2 is used to enter real (non-integer) data into mine model
either create or update specified values. Values of several items files. Program M603V1 can be used to create the input file if
for each block can be stored in a single run. the intent is to load data from one MineSight Data File into
another. M610V2 functions similarly to M610V1, but is able to
PROGRAM FLOW DIAGRAM load several items into each block in one run.
RUN FILE: M610V2 only accepts one type of input coding. The order of
- Area specification the input data must be as follows:
- Item to store & # items
per block
- Input format 1. Column number of the block (integer format)
2. Row number of the block (integer format)
3. Bench number of the block (integer format)
INPUT: CALCS:
4. Matrix data for this block (99 items max.).
- PCF - Read ASCII input matrix
- Mine Model File (13, data Alternatively, block location can be specified by the X,Y,Z
14, or 15) - Store data in mine model location of the midpoint of the block or the X, Y, Bench# 9 (or
- Optional input file file Seam#) of the midpoint of the block.
- Print symbol map
When a format statement is used, the column, row and bench

numbers must be given integer format, and the matrix data must
be given real format. For CSV input files, use free-field format.
OUTPUT:
- Printer output file

MineSight
M610V2-ENTER REAL DATA IN MINE MODEL FILE Proprietary Software: Mintec, inc.

MineSight
Proprietary Software: Mintec, inc. M610V2-ENTER REAL DATA INTO A MINE MODEL FILE
M610V2 - ENTER REAL DATA INTO A MINE MODEL FILE
RUN FILE OPERATION


where

15 = the name of the MINE MODEL FILE - OR -
14 = the name of the GSM SUMMARY FILE - OR -
19 = the name of the OPTIONAL INPUT FILE (see IOP9)
IOP2 = NUMBER OF HEADER LINES TO SKIP
IOP3 = FIRST BENCH TO ACCESS (DEFAULT=1)

IOP4 = LAST BENCH TO ACCESS (DEFAULT=LAST BENCH INITIALIZED WITH M601V1)
IOP5 = FIRST MODEL COLUMN TO ACCESS (DEFAULT=1)

IOP6 = LAST MODEL COLUMN TO ACCESS (DEFAULT=NX)
IOP7 = FIRST MODEL ROW TO ACCESS (DEFAULT=1)

IOP8 = LAST MODEL ROW TO ACCESS (DEFAULT=NY)
IOP9 = INPUT DATA LOCATION OPTION

= 0 INPUT DATA IN RUN FILE
= 1 INPUT DATA IN A SEPARATE FILE
IOP10 = OFFSET TO BE ADDED TO INPUT BENCH NUMBER (Default=0)

IOP11 = OFFSET TO BE ADDED TO INPUT COLUMN NUMBER (Default=0)
IOP12 = OFFSET TO BE ADDED TO INPUT ROW NUMBER (Default=0)
IOP13 = LEVEL MULTIPLIER (Default=1)
IOP14 = COLUMN MULTIPLIER (Default=1)
IOP15 = ROW MULTIPLIER (Default=1)
NOTE: Offsets and multipliers will be applied before limiting bench, column and row.
IOP20 = 0 READ STANDARD COLUMN#, ROW#, BENCH# INPUT

= 1 READ X, Y, Z LOCATION INPUT
= 2 READ X, Y, BENCH/SEAM# LOCATION INPUT

MineSight
IOP21 = 1 ROTATE INPUT DATA IN X,Y PLANE IF IOP20=1.
NOTE: 1) Rotation is defined by PARs 30-34.

2) If IOP26=1 the result of the above rotation is expected to be in model coordinates.
3) Cant have an I-O statement.
IOP22 = 1 COORDINATE INPUT ORDER IS SPECIFIED IN IOPs 23-25
IOP23 = X (COLUMN #) POSITION

IOP24 = Y (ROW #) POSITION
IOP25 = Z (BENCH #) POSITION
NOTE: IOP23-25 ARE USED ONLY IF IOP22=1
IOP26 = 0 INPUT X,Y,Z DATA IS IN PROJECT COORDINATES

= 1 INPUT X,Y,Z DATA IS IN MODEL COORDINATES
NOTE: IOP26 is used only when IOP20=1.
IOP27 = 0 APPLY OFFSETS TO COMPUTED BLOCKS LOWER LEFT CORNERS

= 1 APPLY OFFSETS TO MODEL COORDINATES BEFORE COMPUTING BLOCK
= 2 APPLY OFFSETS TO PROJECT COORDINATES IN CASE OF ROTATED MODELS
NOTE: IOP27 is used only when IOP20=1.
PAR1 = MULTIPLIER FOR FIRST GET ITEM (DEFAULT=1.0)

PAR2 = MULTIPLIER FOR SECOND GET ITEM (DEFAULT=1.0)
. .
. .
. .
PAR20 = MULTIPLIER FOR TWENTIETH GET ITEM (DEFAULT=1.0)
NOTE: Multipliers are provided for the first 20 items only.
PAR30 = ORIGINAL X COORD REFERENCE POINT

PAR31 = ORIGINAL Y COORD REFERENCE POINT
PAR32 = NEW X COORD REFERENCE POINT
PAR33 = NEW Y COORD REFERENCE POINT
PAR34 = ANGLE OF ROTATION
PAR35 = OFFSET TO BE ADDED TO INPUT LEVEL VALUE (DEFAULT=0)
NOTE: PAR35 has affect only if IOP27>0.
PAR36 = OFFSET TO BE ADDED TO INPUT COLUMN VALUE (DEFAULT=0)

PAR37 = OFFSET TO BE ADDED TO INPUT ROW VALUE (DEFAULT=0)
NOTE: 1) If IOP20=1, PAR35-37 will override IOP10-12 if they are set.

2) PAR35 has affect only if IOP27 > 0
PAR38 = DX BLOCK SIZE IF NOT PCF DX

PAR39 = DY BLOCK SIZE IF NOT PCF DY
PAR40 = DZ BLOCK SIZE IF NOT PCF DZ

MineSight
PUT15 = LABELS OF ITEMS TO BE LOADED WITH THIS RUN
NOTE: For a 2-D Surface File, use PUT13. For an auxiliary model file, use PUT14. Up to 99 items can
be loaded. Line length for free-format input is limited to 1024 characters.
FMT1 = OPTIONAL FORMAT FOR INPUT DATA
NOTE: If no format is supplied, the program will use free-field format. The input width is limited to 5000
columns, but a user supplied format can read multiple lines. Free-field format should be used for CSV
files. Input data must have the following general format:
column# row# bench# values
END
4. INPUT MATRIX DATA LINES (Read with FMT1 above)
col# row# bench# values (1 to n)
Input ends with a blank line or the end of file.

* * LOAD BLOCK DATA FROM ASCII DATA FILE INTO TO 3-D MODEL
USR = ABC
IOP3 = 0 0 / PLACE NO RESTRICTION ON BENCH NUMBER

IOP5 = 0 0 / PLACE NO RESTRICTION ON COLUMN NUMBER
IOP7 = 0 0 / PLACE NO RESTRICTION ON ROW NUMBER
IOP9 = 1 / INPUT DATA RESIDES IN A SEPARATE FILE

IOP10 = 0 0 0 / APPLY NO BENCH, COLUMN, OR ROW OFFSETS
PUT15 = TCU-1 MO-1 DIST CODE / ITEM-LABELS FOR ITEMS TO BE LOADED
FMT1 = (3I4,F8.2,F8.3,2F8.2) / OPTIONAL FORMAT FOR INPUT DATA

COM INPUT DATA MUST HAVE THE FOLLOWING GENERAL FORMAT:
COM COLUMN#, ROW#, BENCH#, INPUT DATA VALUES
END

MineSight
M610V2 SAMPLE INPUT FOR RUN FILE #1DAT610.IA

1 1 1 0.00 0. 0. 100.00 Col Row Bench TCU-1 MO-1 DIST CODE
2 1 1 0.00 0. 0. 100.00
3 1 1 0.00 0. 0. 100.00
4 1 1 0.00 0. 0. 100.00
5 1 1 0.00 0. 0. 100.00
6 1 1 0.00 0. 0. 100.00
7 1 1 0.00 0. 0. 100.00
8 1 1 0.00 0. 0. 100.00
9 1 1 0.00 0. 0. 100.00
10 1 1 0.00 0. 0. 100.00
. . . . . . .
. . . . . . .

1. ?M610V2: ERROR. You have not specified any PUT ITEMS.
You must specify from 1 to 99 PUT items to be stored in your mine model.
3. ?M610V2: ERROR. Your MODEL file is emptyYou MUST initialize your file with M601V1 before proceeding.
4. ?M610V2: ERROR. Theres an inconsistency with your MINIMUM/MAXIMUM BENCH/COLUMN/ROW

specifications. (IOP3IOP9)
Minimum Bench 17 Maximum Bench 1

Minimum Column 1 Maximum Column 150
Minimum Row 1 Maximum Row 200
The limits on the benches/rows/columns that were specified using IOP3 through IOP9 are not correct. Make sure that the
minimum values are indeed less than or equal to the maximum. Note also that the maximum values are limited by the
model limits. Additionally, the maximum bench is limited by the last bench initialized with M601V1.
5. %M610V2: WARNING. Skipping BLOCK with indicies outside limits.
Row = 22 Minimum Row = 1 Maximum Row = 120

Col = 13 Minimum Col = 1 Maximum Col = 140
Bench = 71 Minimum Bench = 1 Maximum Bench = 60
This indicated BLOCK is outside the limits selected by IOP3 through IOP9. Note that the maximum values are limited
by the model limits. Additionally, the maximum bench in limited by the last bench initialized with M601V1.
6. ?M610V2: ERROR. You are trying to LOAD more than 99 items using a free-field FORMAT.
You can load at most 99 items with M610V2 (free format or not).

MineSight
7. RUN # nn. has over 99 items.
You can load at most 99 items with M610V2 (free format or not).
8. ?M610V2: ERROR reading LINE xx of your INPUT MATRIX DATA LINES.
There was an error trying to read the indicated line of your input matrix data. Check your FMT1 line and make sure the
data on the indicated line matches the format in the FMT1 line.

MineSight

MineSight
Proprietary Software: Mintec, inc. M612RP - SPECIAL PROJECT CALCULATIONS FOR MINE MODEL FILES
M612RP SPECIAL PROJECT CALCULATIONS FOR MINE

MODEL FILES

M612RP accesses a MineSight routine to perform arithmetic To run M612RP, specify each calculation as an arithmetic
calculations using RPN (Reverse Polish Notation) logic specified expression in the run file. The calculations can access existing
in the run file. Calculated values may be stored into a model items in a model file and can also modify block values stored in
file. a model file. An example use for M612RP would be to compute
an equivalent grade. Any of the model files may be accessed
simultaneously, but only one file may be updated.
PROGRAM FLOW DIAGRAM M612RP is an executable module that is provided by Mintec. It

is not linkable like M612V1.
If any values are to be stored in any model file, make a backup
copy of the file before running M612RP. Arithmetic expressions are written as standard algebraic
statements. For example, in the statement A=B + C, item A will
RUN FILE: be calculated as the sum of items B & C , where B & C must be
- Options and parameters retrieved from File 15 or calculated in a previous expression.
- Selecion criteria Each expression must be contained within 80 columns, and each
- Arithmetic expressions
may contain a combined maximum of 25 item names, real
numeric constants, arithmetic operators (+, -, *, **, /) and the
following functions:
ABS ( ... ) : the absolute value

AINT( ... ) : the integer value
SQRT( ... ) : the square root
INPUT: CALCS:
- PCF - Decode user equations ALOG( ... ) : the natural logarithm (base e)
- Mine Model File (File - Select model file data EXP ( ... ) : the exponential (the power of e)
13, 14 or 15) - Perform calculations
- Optionally store data
SIN ( ... ) : the sine function, radian argument
COS ( ... ) : the cosine function, radian argument
TAN ( ... ) : the tangent function, radian argument
SIND( ... ) : the sine function, degree argument

COSD( ... ) : the cosine function, degree argument
OUTPUT: TAND( ... ) : the tangent function, degree argument
- Updated Mine Model File
- Printer Output File ATAN( ... ) : the arctangent function
DEG ( ... ) : convert radians to degrees
MIN(... , ...): the minimum of the given arguments.

MAX(... , ...): the maximum of the given arguments
where ( ... ) indicates an argument as a constant, a variable or an

expression.
Manually check the values reported by M612RP or run M603V1
to list the values. CHECK THE RESULTS CAREFULLY. To evaluate log to base 10, use the ratio: ALOG(x) / ALOG(10).
Data may be selected through the use of standard Range, Omit

or Table command lines.
Revised: 14-Nov-07 Page 612-1

MineSight
M612RP - SPECIAL PROJECT CALCULATIONS FOR MINE MODEL FILES Proprietary Software: Mintec, inc.
PROCEDURE SUMMARY FOR USE OF

M612RP
1. Define the arithmetic expression(s) with reference to the

item labels of the model files.
2. Prepare the run file, including I-O=2 for a listing of all

items to be used in the run. Use the OUT keyword to
select items for printing.
3. Make a copy of the model file before testing M612RP if

data will be stored from the run.
4. Make a test run with program M612RP, using options

IOP5 to IOP8 to specify a small portion of the model file.
Check the results.
5. When M612RP provides satisfactory results, make a full

production run setting IOP5 to IOP8 as appropriate and I-
O=0.
6. Check the updated model items.
IMPORTANT NOTE: If the M612RP run replaces existing

values in the model file, there is no way to restore the original
file. Save a copy of the file (on disk or tape) before you begin
your M612RP run.
Page 612-2 Revised: 14-Nov-07

MineSight
M612RP - SPECIAL PROJECT CALCULATIONS FOR MINE MODEL FILES
RUN FILE OPERATION

MEDS-612RP 10=filename 15 (or 14 or 13)=filename;
MEDS-612RP 3=filename
where
MEDS-612RP (must be the first 10 columns)

10= the name of the PROJECT CONTROL FILE
15= the name of the MINE MODEL FILE -OR-
14= the name of the GSM SUMMARY FILE -OR-
13= the name of the 2-D SURFACE FILE
USR = USER INITIALS (E.G., ABC)
IOP2 = OPTION FOR TEST RUN ONLY

= 0 FOR A FULL RUN (FILE READING & STORING)
= 1 FOR A TEST RUN (DO NOT STORE INTO FILE)
IOP3 = 0 USE ALL BLOCKS SPECIFIED BY IOP5, IOP6, IOP7, IOP8, IOP11, IOP12 AND/OR CMD = USE Z
= 1 RESTRICT THE BLOCKS USED BY A SPECIFIED BOUNDARY
lines:
CMD = INCL LOCPT FILE filename (to include points within the boundary) - OR -
See Section 4. Boundary Points for formatting details.
IOP5 = FIRST MODEL COLUMN TO ACCESS (DEFAULT=1)

IOP6 = LAST MODEL COLUMN TO ACCESS (DEFAULT=NX)
IOP7 = FIRST MODEL ROW TO ACCESS (DEFAULT=1)

IOP8 = LAST MODEL ROW TO ACCESS (DEFAULT=NY)
IOP11 = FIRST BENCH TO ACCESS (DEFAULT=1)

IOP12 = LAST BENCH TO ACCESS (DEFAULT=LAST BENCH INITIALIZED IN THE MODEL)
NOTE: Optional CMD lines may be used in place of and override IOP11 and IOP12.CMD = USE Z
bench1 bench2 ... bench15

MineSight
IOP14 = 0 PERFORM UNDEF SUBSTITUTION BEFORE RANGE CHECKING

= 1 PERFORM UNDEF SUBSTITUTION AFTER RANGE CHECKING
GETNN = LABELS OF ITEMS TO BE RETRIEVED FROM MODEL FILE

UPDNN = LABELS OF ITEMS TO BE RETRIEVED AND STORED
PUTNN = LABELS OF ITEMS TO BE STORED AFTER M612RP CALCULATIONS
NOTE: UPD and PUT labels must reference only one model file.
OUTNN = LABELS OF ITEMS TO BE LISTED AFTER CALCULATIONS
NOTE: OUT labels must match a GET, UPD, or PUT item.
NOTE: A maximum of 99 items can be specified by GETnn, UPDnn PUTnn and OUTnn
ITMN = LABEL-NN RANGE MIN-VALUE MAX-VALUE

ITMN = LABEL-NN OMIT MIN-VALUE MAX-VALUE
ITMN = LABEL-NN TABLE IOPM IOPN
Optional block limiting by level
CMD = USE Z LEVEL #1 LEVEL #2 . . . LEVEL#15
NOTE: Multiple CMD = USE Z lines are allowed.

The levels may be entered in any order, e.g., CMD = USE Z7213 will restrict calculations to
levels 2, 7 and 13. This command overrides the levels specified by IOP11 and IOP12.
Optional lines for label substitution (see note in Section 5)
CMD = LABEL-NN ALIAS IS RUN-LABEL
Example: CMD = T-CU ALIAS IS TOTCU
Optional Z coordinate item (for 3D-rotated GSM models)
CMD = ZCRD label-nn
Optional lines for value substitution
ITMN = LABEL-NN UNDEF VALUE
NOTE: Value substitution for undefined retrieved values occurs before RPN calculations and after RPN
calculations for stored items. The result of an expression containing an undefined value is an
undefined value.

MineSight
END
4. BOUNDARY POINTS (If IOP3 = 1)
Boundary points define a polygon. A block whose center is within the polygon will be included.
NOTE: The format for specifying boundary points either after the END line or in a separate file is as
follows:
1) Easting 1 Northing 1
Easting 2 Northing 2
. .
. . Free-field format
. .
Easting n Northing n
0 0
2) The boundary points must close, i.e., Easting 1 = Easting nNorthing 1 = Northing n
3) 00 must be entered at the end of the boundary points
4) The maximum number of boundary points is 2000.
If using a 3D-rotated GSM file 15 or 3D-rotated files 13 & 14, you must specify the Z coordinate mode item by using:
CMD = ZCRD LABEL-NN.
5. ARITHMETIC EXPRESSION LINES (max = 40 expressions)
Example: EQUIV = TOTCU + MOLY * 5.0
NOTE: An item label may not contain a hyphen () since it will be read as a minus sign. For item labels
containing embedded hyphens, such as TCU, substitute an alternative name using the ALIAS
command line.

MineSight
M612RP SAMPLE RUN FILE #1

MEDS-612RP 10=SAMP10.DAT 15=SAMP15.DAT 3=RPT612.LA
** CALCULATE EQUIVALENT COPPER FOR 3-D BLOCK MODEL **
USR = ABC
IOP2 = 0 / 0=NORMAL RUN, 1=TEST RUN ONLY
IOP5 = 1 0 / MIN AND MAX COLS

IOP7 = 1 0 / MIN AND MAX ROWS
IOP11 = 1 0 / MIN AND MAX BENCHES
GET15 = TOTCU MOLY / GET ITEMS FROM MODEL

PUT15 = EQCU / PUT ITEMS IN MODEL
END
EQCU = TOTCU + 5.0 * MOLY

COAL-612RP 10=COAL10.DAT 15=COAL15.DAT 3=RPT612.LA
** CALCULATE ZBOT AND BTU FOR COAL SAMPLE **
USR = ABC

CMD = USEZ 1 1
GET15 = ZTOP THICK BTU / ITEMS TO GET FROM MODEL

PUT15 = ZBOT DIST / ITEMS TO STORE IN MODEL
I-O = 1
END
ZBOT = ZTOP THICK
DIST = BTU * THICK * 0.005

MineSight

MEDS-612RP 10=CRUZ10.DAT 13=CRUZ13.DAT 3=RPT612.LA
** SPECIAL BLOCK MODEL CALCULATIONS ON CRUZ13.DAT **
USR = ABC

IOP3 = 0 / 0=NO BOUNDARY CHECK, 1=WITHIN SPECIFIED BOUNDARY

IOP11 = 1 1 /MIN AND MAX BENCHES
COM MODEL ITEMS ORDER WITHIN INPUT DATA

UPD13 = STOP1 THIK1 CODE1
ITM01 = CODE1 UNDEF 0
ITM02 = CODE1 RANGE 0 0
END
STOP1 = 0
THIK1 = 0
HOW TO DEBUG AN M612RP RUN
1. If I-O=2 is specified in the run file, MineSight routines will print a list of all the items in the Mine Model File followed by the
items to be used, in the form
**MEDITM: FILE SAMP15.DAT PCF DESCRIPTORS ### ###
**MEDITM: ### REF #
**MEDITM: ### FROM items in File 9
**MEDITM: GET ITEM = 1 TOTCU (for the first example above)
**MEDITM: GET ITEM = 2 MOLY
**MEDITM: PUT ITEM = 3 EQCU
The MEDITM information (I-O=2) allows you to check the items of information that will be retrieved (GET items) from File
15. Check if all desired items are listed.
2. If you make a mistake in entering the variable names in the Arithmetic Expression Lines, the calculations will be in error. If
results are not correct, check the equations and labels specified in the run file.
3. ?M612RP: ERROR. Your File 15 is empty.

4. ?M612RP: ERROR. Cannot find a file name for reference number nn.
You have a PUTnn, GETnn, or UPDnn item but have not specified a File nn on the Names Line of your run file.

MineSight
5. ?M612RP: ERROR. Only ONE model file can have PUT and UPD items.
You have selected PUT and UPD items from more than one model file. For example, having a PUT13=TOPOG and UPD15=ROCK
would be illegal since you can PUT/UPDATE items from only one model file at a time.
6. ?M612RP: ERROR. No valid GET, PUT, or UPD items were found.

You have not selected any items to access with M612RP.
7. ?M612RP: ERROR. You have selected xx GET/PUT/UPD/OUT items which exceeds the maximum of 99.
You can select at most 99 items total with GET/PUT/UPD/OUT commands.
8. ?M612RP: ERROR. Level xx is out of range. Last initialized bench is yy.

On one of your CMD=USE Z lines, you selected bench xx. However, your model has only been initialized through bench yy. You
need to run M601V1 to initialize your model through bench xx.
9. ?M612RP: ERROR. IOP12=xx exceeds the last initialized bench yy.

You have selected benches up to bench xx by using IOP12. However, your model has only been initialized through bench yy. You
need to run M601V1 to initialize your model through bench xx.
10. ?M612RP: ERROR. IOP11 exceeds IOP12.

The initial bench to access cannot exceed the final bench to access.
The initial column to access cannot exceed the final column to access.

The initial row to access cannot exceed the final row to access.
13. ?M612RP: ERROR. No match for 2 substitute ITEMS.

You have used two ITMn=label-n UNDEF value commands but the labels you have specified are not any of the GET/PUT/OUT
items.
14. ?M612RP: ERROR. GET item MOLY cannot be on LEFT side of RPN expression.
You have used a GET command to access item MOLY, but you are assigning MOLY a value by placing it in the left side of an
RPN expression. If you really want to reassign a value for MOLY, you need to access it using either a PUT or UPD command.
15. A test run should always be performed on a small portion of the drillhole data before actually storing any calculations.

MineSight
Proprietary Software: Mintec, inc. M612SM - SURFACE GENERATION
M612SM SURFACE GENERATION

This program will calculate and store elevations in File 13 or in M612SM can be used to calculate and store elevations in the
File 15 using one of several different methods. 2-D Surface File (File 13) or the GSM Model File (File 15). The
available methods are:
The use of this program is described in two parts. If the
results are to be stored in File 13, see File 13 operations SURF = TOPOG - constant
below. If the results are to be stored in File 15, see the File SURF = ZTOP + constant
15 Operations Section on page 612-39. SURF = ELEV constant (fixed elevation)
SURF = PLANE Ax + By + C

File 13 Operations
RUN FILE:
- Options and parameters

If you want to store elevations in File 13, you must specify
- Selection criteria RUN=TOPO in the run file. Several surfaces may be calculated
- Arithmetic expressions and stored in a single run by selecting items from File 13 with
the command
UPD13 = TOPOG label2 label3 ... labeln
A topography item (TOPOG) or another item is required for

each run. The calculated surfaces will be constrained by this
INPUT: CALCS: topography item. At least one other item must also be specified.
- PCF - Decode user equations
- Mine Model File (File 13, - Select model file data The second item on the UPD13 line will be calculated from the
14 or 15) - Perform calculations first SURFace command. The third item on the UPD13 line will
- Optionally store data be calculated from the second SURFace command, etc.
Calculated surfaces can also be constrained by a single item that

is retrieved from File 15 or 14. Use GET15 or 14 to retrieve the
constraining item. This item is usually a seam top and SURF is
found to be above it.
OUTPUT:
NOTE: M612SM is a complete program that is executed directly

by the user. Do not to link a USR612 subroutine.
Revised: 26-January-12 Page 612-9

MineSight
M612SM - SURFACE GENERATION Proprietary Software: Mintec, inc.
Page 612-10 Revised: 26-January-12

MineSight
M612SM - SURFACE GENERATION
MEDS-612SM 10=filename 15 (or 14)=filename 13=filename;

MEDS-612SM 3=filename
where
MEDS-612SM (must be the first 10 columns)

15 = the name of the GSM MINE MODEL FILE -OR-
14 = the name of the GSM SUMMARY FILE
RUN = TOPO FOR UPDATING FILE 13

= GSM FOR UPDATING FILE 15

IOP11 = FIRST SEAM FROM GSM FOR CONSTRAINT (default=first seam)

IOP12 = LAST SEAM FROM GSM FOR CONSTRAINT (default = last initialized seam)
IOP13 = 0 USE IOP11 AND IOP12 FOR SEAMS
= 1 READ SEAM REF# FROM END OF RUN FILE
IOP14 = 0 USE IOP5-IOP8 FOR ROW AND COLUMNS
= 1 READ ROWS AND COLUMNS FROM END OF RUN FILE
IOP15 = row# PRINT CALCULATION DETAILS (optional)
IOP20 = 1 OMIT ZTOP ELEVATION CONSTRAINT
NOTE: By default surfaces computed by the CMD = SURF command are constrained below by the value of the
item specified in the GET15 command (if any).
IOP21 = 0 SET MISSING SURFACE VALUES TO MISSING

= 1 SET MISSING SURFACE VALUES TO TOPOG
= 2 LEAVE AS IS
NOTE: IOP20 and IOP21 are only applicable to RUN = TOPO.

MineSight
GET15 = label-15 (item to retrieve from GSM)

NOTE: GET15 is optional. If used, calculated surfaces will be constrained to have elevations that are greater
than or equal to label-15 (usually ZTOP).
GET13 = label1 label2 ... (items to retrieve from File 13)

or
UPD13 = label1 label2 ... (items to retrieve & store back)
NOTE: Usually UPD13 should be used to store surfaces. GET13 would be used mainly to test calculations.
Calculated surfaces will be constrained to lie below the surface label1 (usually TOPOG).
Special use of File 14:
The GSM Summary File (File 14) created by M706SM may be used instead of the GSM File 15 by:
GET14 = label-14 (item to take the place of label-15 above)

NOTE: The calculated elevations would then be limited by label-14 (usually ZPIT).
UPD13 = label1 label2 ...
Specifying surface calculations
CMD lines format as follows:
CMD = SURF = TOPOG - constant

To create a surface that is a constant below topography.
CMD = SURF = ZTOP + constant

To create a surface that is a constant above a seam top.
CMD = SURF = ELEV constant

To set a constant elevation for a plane constrained by topography and seam top.
CMD = SURF = PLANE A-constant B-constant C-constant

(elevation = A*x + B*y + C)
To create a surface that has an equation as indicated above.
NOTE: If you select a File 15 item with a GET15 command, the computed surface will be constrained below by
the value of the File 15 Item unless IOP20 = 1.
END
4. SEAM REFERENCE NUMBERS LINE (If IOP13=1)
10 reference numbers per line
5. ROWS AND COLUMNS LINES (If IOP14=1)
mrow nrow mcol ncol
Multiple lines allowed. End with 0 0 or end of file.

MineSight
M612SM SAMPLE RUN FILE #1

COAL-612SM 10=COAL10.DAT 13=COAL13.DAT 15=COAL15.DAT;
COAL-612SM 3=RPT612.LA
** CALCULATE ARBITRARY SURFACE AT 950 ELEVATION **
RUN = TOPO
USR = ABC
IOP5 = 01 00 / MIN AND MAX COLUMNS

IOP11 = 1 1 / FIRST AND LAST SEAM FOR ZTOP CHECK
GET15 = ZTOP / GET TOP OF SEAM FOR CONSTRAINT

UPD13 = TOPOG MINEZ / ITEMS TO GET FROM FILE 13
CMD = SURF = ELEV 950
END
NOTE: A surface with a constant elevation of 950 will be generated. However, if TOPOG is less than the
constant of 950, the new surface elevation will be set equal to TOPOG. If the ZTOP of the first seam is
greater than the constant elevation, the new surface elevation will be ZTOP. In other words, the new surface is
constrained by TOPOG on top and ZTOP of seam 1 below.

COAL-612SM 3=RPT612.LB
** CALCULATE SURFACE AT ZTOP + CONSTRAINTS**
RUN = TOPO
USR = ABC

CMD = SURF = ZTOP + 100
END
NOTE: A new surface that is 100 feet above ZTOP will be created. If the new elevation is greater than TOPOG,
the elevation will be set to TOPOG.

MineSight

COAL-612SM 3=RPT612.LC
** CALCULATE NEW SURFACE WITH CONSTANT 2% SLOPE **
RUN = TOPO
USR = ABC


CMD = SURF = PLANE 0.01732 0.0100 1813.4

COM ELEV = 0.01732*X + 0.0100*Y + 1813.4
END
NOTE: A surface with a slope of 2% will be calculated. The equation for the plane can be obtained from
M404V1. The surface will be constrained by TOPOG on top and ZTOP of seam 1 below.

MineSight
Proprietary Software: Mintec, inc. M612V1 - USER INTERFACE FOR MINE MODEL FILES (BENCHES)
M612V1 USER INTERFACE FOR MINE MODEL FILES

(BENCHES)

Program M612V1 is used to read/modify your model files. M612V1 is used to access, modify and update data in one of the
M612V1 provides read-write access to your model files, allowing mine model files (File 13, 14 or 15). Data is accessed by bench.
you to manipulate the values via a FORTRAN subroutine. You do not need to know the structure of the Data File nor the
The program acts as an interface between your file and your details of how data is stored and retrieved. However, you should
subroutine. The model is accessed horizontally by bench. be able to write a simple FORTRAN program that will perform
Calculated values may be stored into the model. the desired calculations. An example of a user-coded subroutine
is provided in this section.
Mintec provides M612V1 object modules which need to be

PROGRAM FLOW DIAGRAM linked with your compiled subroutine to produce an executable
program. These are the M612V1 object modules capable of
RUN FILE: accessing different numbers of items:
- Area selection m612d1.obj object module can access up to 99 items and links
- Item selection with the user subroutine USR612D.
- Symbol map option
m612db1.obj object module can access up to 500 items and links
with the same user subroutine name USR612D.
You may specify the area of the model to be accessed by row,

column and bench number. Data can be read in from an external
INPUT: CALCS: ASCII file or can be written to an external ASCII file. A symbol
map may be printed that will provide a check on the calculations
- PCF - Select data from model that were performed.
- Mine Model File (File - Apply user calculation/
13, 14 or 15) report The user subroutine is called by the main routine a number of
- Update model
times. A call is always made for initialization. If IOP3=0, the
subroutine is called for each row in the selected range. If IOP3=1,
the subroutine is called for each row and after each bench. If
IOP3=2, the subroutine is called for each row, after each bench
and at the end of the run.
OUTPUT:
A number of arguments are passed from the main routine
- Update mine model file (M612V1) to the user-coded subroutine.
NTRY = -1 Initialization (always done)
NTRY = 0 Process row data (If IOP3=0,1,2)
NTRY = 1 End of bench (If IOP3=1,2)
NTRY = 2 End of run (If IOP3=2)
IZ = Bench number
ZMID = Elev. of bench midpoint or seam number
IROW = Row number

YROW = Northing of row midpoint
MCOL = First column to process

NCOL = Last column to process

MineSight
M612V1 - USER INTERFACE FOR MINE MODEL FILES (BENCHES) Proprietary Software: Mintec, inc.
MAP = Array of integer values to write back to file The MAP array is an integer one-dimensional array (sized to
(dimension to MXCOL columns) MXCOL) that contains an integer result from a user-calculation
for each block in a row (up to MXCOL blocks). The value in
RMX = Array of real values to read from and write the MAP array corresponds to the item specified in the ITM1
back to file command in the run file.
MXCOL= Maximum number of columns to process (used To write real values to a MineSight Data File, use the UPD
for array dimensioning such as RMX & MAP) command in the run file. To write one integer value back to
a MineSight Data File, use the GET command and the ITM
MXROW= Maximum number of rows to precess (used command.
for array dimensioning)
WARNING: If you are updating your model, make a backup
MAXITM= Maximum number of items to process (used copy of the model file before running M612V1.
for array dimensioning such as RMX)
IMPORTANT NOTE: Common blocks used for item and
The dimension of RMX is MXCOL columns multiplied by system information are different for the object modules (they
MAXITM (the maximum number of items). If you use the 99 are named differently as well).
item maximum, your subroutine should be linked with module
m612d1.obj. For the 500 item maximum, your subroutine must Please refer to the Technical 600 section for more information
be linked with module m612db1.obj. The RMX array should about how to write MineSight user subroutines.
be dimensioned to RMX(MXCOL,MAXITM).
The RMX array in the subroutine is a real two-dimensional array

that contains the selected data items for each block in a row (up
to MXCOL). The order of the data items corresponds to the
order of items on the GET or UPD in the run file. For example,
if the GET command was
GET15 = TCU-1 MO-1 ROCK
the RMX array would have
TCU-1 in RMX(NX,1) - NX=column number

MO-1 in RMX(NX,2)
ROCK in RMX(NX,3)

MineSight
M612V1- USER INTERFACE FOR MINE MODEL FILES (BENCHES)
RUN FILE OPERATION

where

19 = the name of the OPTIONAL INPUT/OUTPUT FILE (See IOP9)
IOP2 = RETRIEVE DATA FROM FILE BEFORE CALLING USR612D FOR EACH ROW
= 0 OMIT RETRIEVING DATA FROM THE FILE
= 1 RETRIEVE DATA SPECIFIED ON GETn or UPDn LINE
NOTE: If IOP2=0, then GETn and UPDn items are not allowed
IOP3 = GOVERN CALLING ROUTINE USR612D

= 0 CALL SUBROUTINE FOR EACH ROW ONLY
= 1 CALL SUBROUTINE BY ROW & AFTER EACH BENCH
= 2 CALL SUBROUTINE BY ROW, BENCH & END-OF-RUN
IOP4 = TYPE OF RUN

= -1 ACCESS SUBROUTINE BUT DO NOT STORE ANY DATA (For Testing)
= 0 ACCESS SUBROUTINE AND STORE RESULTS IN FILE


IOP9 = USE A SEQUENTIAL INPUT/OUTPUT FILE

= 0 OMIT ANY USE OF THIS EXTRA FILE
= 1 SET UP A FILE TO BE OUTPUT BY USR612D
= 2 SET UP A FILE TO BE INPUT BY USR612D

MineSight

= 1 PRINT THE SYMBOL MAP OF USR612D GENERATED VALUES
NOTE: You can only plot values that are calculated and stored in the MAP array in the user subroutine.
IOP11-40 are available for user integer constants.

PAR1-40 are available for user real constants.
To write one integer value to file use:
ITMn = item-label (for storing integer value)

NOTE: Corresponds to the MAP array in the subroutine. A symbol map may be printed for this item.
To retrieve multiple real values from file use:
GETn = label1 label2 ... labeln (for retrieving real data)

NOTE: The order of the GET line is the same as the RMX array in the user subroutine. IOP2 must be 1 to read
the data.
To write multiple real values to file use:
UPDn = label1 label2 ... labeln (for retrieving and storing real data)
NOTE: Matches variables in RMX array in the subroutine. The ITM command is not used. IOP2 must be 1 to
use UPDn. At most 10 total GETn, UPDn items may be used.
END
4. BENCH HEADER LINES (free-field format)

Multiple bench header lines may be used to select a range of benches or a single bench. For example:
END
10 20
25
33 34
50
The above lines would select:
Benches 10 through 20
Bench 25
Benches 33 through 34 and
Bench 50

MineSight

MEDS-612V1 10=SAMP10.DAT 15=SAMP15.DAT 3=SAM612.LA
** ADD OWNER CODE TO MODEL **
COM USER SUBROUTINE OWN612 LINKED WITH M612V1
USR = ABC
IOP2 = 0 / 0 = OMIT DATA RETRIEVAL FROM FILE 15

IOP3 = 2 / CALL USR612D BY ROW, BENCH & END-OF-RUN
IOP4 = 0 / 0 = ACCESS USR612D AND STORE
IOP10 = 1 / 1 = PRINTER MAP
ITM1 = CODE / STORE RESULTS IN CODE ITEM
END
20
M612V1 SAMPLE SUBROUTINE #1

The following is a sample user subroutine for use with M612V1 that unites a single integer value to File 15. Note that the item
specified by the ITM command should have a precision of 1 and a minimum value of 0.
C OWN612.FOR
C
SUBROUTINE USR612D(NTRY, IZ,ZMID, IROW,YROW, MCOL,NCOL, MAP,RMX,
& MXCOL, MXROW, MAXITM)
C
C -
C SAMPLE USER SUBROUTINE FOR MINE MODEL CALCULATIONS
C
C COMPUTE OWNER CODES FOR COPPER EXAMPLE (50 X 50 MATRIX)
C
C
DIMENSION RMX(MXCOL,MAXITM), MAP(MXCOL)
C
COMMON
& /M612/ KGEO, IOU
& /SYS/ DUM1(100), IOP(40), PAR(40), DUM2(104),
& ICR, IPR, LCR, LPR, DUM3(5), IOLEV, DUM4(89)
& /F15/ DUM6(61),
& XMIN,XMAX, DX , NX ,
& YMIN,YMAX, DY , NY , DUM7(5),
& ZMIN,ZMAX, DZ , NZ , DUM8(8)
& /F10/ DUM9(50),TOES(200), DUMA(414)
C
C COMMON BLOCK DEFINITIONS
C -
C I-O UNITS: IOU = OPTIONAL UNIT# FOR USER INPUT/OUTPUT
C SEE IOP9 IN RUN DOCUMENTATION
C ICR = INPUT RUN FILE
C IPR = PRINT FILE
C LCR = TERMINAL READ
C LPR = TERMINAL WRITE
C

MineSight
C RUN OPTIONS: IOP(1-10) FROM RUN FILE IOP1-10 ARE RESERVED

C FOR PROGRAM USE. DO NOT MODIFY.
C IOP(11-40) ARE AVAILABLE FOR USE. IOP(11) = IOP11
C FROM RUN FILE, ETC.
C
C RUN PARAMETERS: PAR(1-40) AVAILABLE FOR USE
C
C MODEL LIMITS: X-COORDINATE XMIN,XMAX,DX,NX
C Y-COORDINATE YMIN,YMAX,DY,NY
C ELEVATION ZMIN,ZMAX,DZ,NZ
C
C BENCHES: TOES(I-200) ARE TOE ELEVATIONS OF BENCHES
C (3D) 1 TO 200. TOES(1) = TOE ELEVATION OF TOP BENCH
C
C IOLEV = DEBUG OPTION SET IN RUN FILE AS I-O = N
C FOR N GREATER THAN 0, ADDITIONAL DETAIL IS
C USUALLY PRINTED.
C
C KGEO AND ARRAYS DUM1-8 ARE RESERVED FOR USE BY M612V1
C
C -
IF ( NTRY ) 100, 200, 1000
C
C 77-
C NTRY = -1 : INITIALIZE USR612D, AS NEEDED
C
100 WRITE (LPR,110)
C
C SET UP PRINTER PAGE USING MineSight SUBROUTINE NEWPAG
C WHICH PRINTS STANDARD HEADER
C
CALL NEWPAG ( 0 )
WRITE (IPR,110)
RETURN
C
110 FORMAT (/ ** OWN612 INITIALIZATION **/)
C
C 77-
C NTRY = 0 : PROCESS MODEL DATA
C
200 CONTINUE
C
C ** CALCULATE FOR BLOCKS FROM COLUMN MCOL TO NCOL OWNER
C CODE AND STORE IN ARRAY MAP
C
DO 180 ICOL = MCOL, NCOL
ICODE = 1
IF (IROW .GT. 25 .AND. ICOL .GT. 25) ICODE = 2
MAP(ICOL) = ICODE
IF(IOLEV.EQ.2) WRITE(IPR,170) IZ, IROW, ICOL, ICODE
180 CONTINUE
RETURN
170 FORMAT( IZ,IY,IX = ,3I4, CODE = ,I5)
C
C 77-
1000 IF (NTRY .GT. 1) GO TO 1500

MineSight
C
C NTRY = 1 : PROCESS OR SUMMARIZE AT END OF BENCH:
C
WRITE (LPR,1510) IZ
IF(IOLEV.GT.0) WRITE (IPR,1510) IZ
RETURN
C
C 77-
C NTRY = 2 : PROCESS OR SUMMARIZE AT END OF ENTIRE RUN
C
1500 CONTINUE
CALL NEWPAG (0)
WRITE (LPR,1520)
IF(IOLEV.GT.0) WRITE (IPR,1520)
RETURN
C
1510 FORMAT ( ** OWN612 END BENCH,I4/)
1520 FORMAT ( ** OWN612 END-OF-RUN//)
END

MEDS-612V1 10=SAMP10.DAT 15=SAMP15.DAT 3=SAM612.LB
** COMPUTE EQUIVALENT COPPER GRADE **
COM USER SUBROUTINE EQU612 LINKED WITH M612V1

USR = ABC
IOP2 = 1 / 0 = OMIT, 1=RETRIEVE DATA FROM FILE 15
IOP3 = 2 / 2 =CALL USR612D BY ROW, BENCH & END-OF-RUN
IOP4 = 0 / 0 =ACCESS USR612D & STORE RESULTS
IOP7 = 1 0 / ROWS
PAR1 = 5.0 / FACTOR TO COVERT MO-1 TO EQ-CU
UPD15 = MO-1 TCU-1 EQ-CU / READ GRADES AND STORE
I-O = 0 / 0=MINIMUM PRINTER OUTPUT, 2= PRINT BLOCK CALCULATIONS
END 21

The following is a sample user subroutine for use with M612V1 that allows the user to access items in File 15, perform calculations
and store the items back in File 15.
C EQU612
C
C
C
C COMPUTE EQUIV COPPER TO COPPER EXAMPLE (50 X 50 MATRIX)
C
C
C

MineSight
COMMON
& /M612 / KGEO , IOU
& /SYS/ DUM1(100) ,IOP(40) , PAR(40), DUM2(104),
& ICR, IPR, LCR, LPR, DUM3(5) , IOLEV , DUM4(89)
& /F15/ DUM6(61),
& /F10/ DUM9(50),TOES(200), DUMA(414)
C
C ICR = INPUT RUNFILE
C IPR = PRINT FILE
C
C
C
C
C
C USUALLY PRINTED.
C
C
IF ( NTRY ) 100, 200, 1000
C
C
100 WRITE (LPR,110)
C
C
CALL NEWPAG ( 0 )
WRITE (IPR,110)
FACT = PAR(1)
WRITE (LPR,120) FACT
WRITE (IPR,120) FACT
120 FORMAT(/ EQUIVALENT GRADE FACTOR = ,F10.3)
RETURN
C
110 FORMAT (/ ** USR612D INITIALIZATION **/)

MineSight
C
C
200 CONTINUE
C
C ** CALCULATE FOR BLOCKS FROM COLUMN MCOL TO NCOL
C ARRAY RMX(ICOL,I) CONTAINS DATA FROM FILE 15 FOR ROW IROW
C ICOL = COLUMN NUMBER
C I = 1 FIRST ITEM IN UPD15 COMMAND MO-1
C I = 2 SECOND ITEM IN UPD15 COMMAND TCU-1
C I = 3 THIRD ITEM IN UPD15 COMMAND EQ-CU
C
C NOTE: VALUES IN RMX ARRAY MUST BE RETRIEVED AS BELOW AND TESTED FOR
C A LARGE NEGATIVE NUMBER. THE RMX ARRAY CONTAINS A NEGATIVE VALUE
C FOR ITEMS NOT SET (LARGE NUMBER) OR MISSING (-1.0). AN ERROR
C WILL RESULT IN PERFORMING MATH OPERATIONS ON THE RMX ARRAY BEFORE
C TESTING FOR THE LARGE NEGATIVE NUMBERS. ALL VALUES IN THE RMX
C ARE WRITTEN BACK TO THE MODEL SO THE USER SHOULD ONLY CHANGE
C RMX VALUES THAT ARE TO BE UPDATED.
C
C RETRIEVE MOLY GRADE
RMOLY = RMX(ICOL,1)
IF (RMOLY .LT. 0.) RMOLY = 0.
C RETRIEVE COPPER GRADE
TCU = RMX(ICOL,2)
IF (TCU .LT. 0.) TCU = 0.
C CALCULATE AND STORE EQUIVALENT GRADE
EQCU = FACT * RMOLY + TCU
RMX(ICOL,3) = EQCU
C
IF(IOLEV.EQ.2) WRITE(IPR,170) IZ, IROW, ICOL, RMOLY,TCU,EQCU
180 CONTINUE
RETURN
170 FORMAT( IZ,IY,IX = ,3I4, MOLY =,F7.3, TCU =,F7.3,
& EQCU =,F7.3)
C
1000 IF (NTRY .GT. 1) GO TO 1500
C
C
WRITE (LPR,1510) IZ
RETURN
C
C
1500 CONTINUE
CALL NEWPAG (0)
WRITE (LPR,1520)
RETURN
C
1510 FORMAT ( ** USR612D END BENCH,I4/)
1520 FORMAT ( ** USR612D END-OF-RUN//)
END

MineSight

MEDS-612V1 10=SAMP10.DAT 13=SAMP13.DAT 3=SAM612.LC
** COMPUTE SOILZ ELEVATION **
COM USER SUBROUTINE TOP612 LINKED WITH M612V1
USR = ABC

IOP4 = 0 / 0 =ACCESS USR612D & STORE RESULTS
IOP7 = 1 0 / ROWS
UPD13 = TOPOG SOILZ / STORE SOILZ
I-O = 0 / 2= PRINT EACH BLOCK CALCULATION
PAR1 = 150. / OVERBURDEN THICKNESS
END
1

The following is a sample user subroutine for use with M612V1 that reads from and writes to File 13.
C TOP612
C
C
C SAMPLE USER SUBROUTINE FOR FILE 13 CALCULATIONS
C
C COMPUTE SOILZ FROM TOPOG - PAR1
C
C
C
COMMON
& /M612 /KGEO , IOU
& /F15/ DUM6(61),
& /F10/ DUM9(50),TOES(200), DUMA(414)
C
C IPR = PRINT FILE
C

MineSight

C
C
C
C
C USUALLY PRINTED.
C
C
IF ( NTRY ) 100, 200, 1000
C
C
100 WRITE (LPR,110)
C
C
CALL NEWPAG ( 0 )
WRITE (IPR,110)
DP = PAR(1)
WRITE (LPR,120) DP
WRITE (IPR,120) DP
120 FORMAT(/ OVERBURDEN THICKNESS = ,F10.3)
RETURN
C
110 FORMAT (/ ** TOP612 INITIALIZATION **/)
C
C
200 CONTINUE
C
C ** CALCULATE FOR BLOCKS FROM COLUMN MCOL TO NCOL
C I = 1 FIRST ITEM IN UPD13 COMMAND -TOPOG
C I = 2 SECOND ITEM IN UPD13 COMMAND -SOILZ
C

MineSight
C
C RETRIEVE TOPOG
TOPO = RMX(ICOL,1)
IF (TOPO .LT. 0.) TOPO = 0.
RMX(ICOL,2) = TOPO - DP
300 CONTINUE
RETURN
C
1000 IF (NTRY .GT. 1) GO TO 1500
C
C
WRITE (LPR,1510) IZ
RETURN
C
C
1500 CONTINUE
CALL NEWPAG (0)
WRITE (LPR,1520)
RETURN
C
1510 FORMAT ( ** TOP612 END BENCH,I4/)
1520 FORMAT ( ** TOP612 END-OF-RUN//)
END

MEDS-612V1 10=SAMP10.DAT 15=SAMP15.DAT 3=SAM612.LD;
MEDS-612V1 19=SAM612.OD
** WRITE GRADES TO OUTPUT FILE **
COM USER SUBROUTINE WRT612 LINKED WITH M612V1
USR = ABC

IOP4 = -1 / -1 = DO NOT WRITE TO FILE 15, 1 = WRITE
IOP7 = 1 0 / ROWS
IOP9 = 1 / 1= OUTPUT TO FILE #19, 2 = INPUT FROM FILE #19
GET15 = TCU-1 MO-1 EQ-CU / READ GRADES
PAR1 = .5 .9 / MIN AND MAX VALUES FOR EQCU
I-O = 0 / 0=MINIMUM PRINTER OUTPUT,2= PRINT BLOCK CALCULATIONS
END
21

MineSight

The following is a sample user subroutine for use with M612V1 that reads items from File 15 and writes them to an ASCII file. This
ASCII file can be used to transfer data to non-MineSight programs or between computers.
C WRT612
C
C
C
C OUTPUT SELECTED ITEMS FROM MINE MODEL TO ASCII FILE C
C
C
COMMON
& /M612 / KGEO , IOU
& /F15/ DUM6(61),
& /F10/ DUM9(50),TOES(200), DUMA(414)
C
C IPR = PRINT FILE
C
C
C
C
C
C USUALLY PRINTED.
C
C
IF ( NTRY ) 100, 200, 1000
C

MineSight

C
100 WRITE (LPR,110)
C
C
CALL NEWPAG ( 0 )
WRITE (IPR,110)
GMIN=PAR(1)
GMAX=PAR(2)
WRITE (LPR,120) GMIN,GMAX
WRITE (IPR,120) GMIN,GMAX
120 FORMAT(/ MINIMUM AND MAXIMUM GRADE = ,2F10.3)
RETURN
C
110 FORMAT (/ ** USR612D INITIALIZATION **/)
C
C NTRY =0 : PROCESS MODEL DATA
C
200 CONTINUE
C
C ** CALCULATE FORBLOCKS FROM COLUMN MCOL TO NCOL
C I = 1 FIRST ITEM IN GET15 COMMAND -TCU-1
C I = 2 SECOND ITEM IN GET15 COMMAND -MO-1
C I = 3 THIRD ITEM IN GET15 COMMAND -EQ-CU
C
C
C RETRIEVE MOLY GRADE
RMOLY = RMX(ICOL,2)
IF (RMOLY .LT. 0.) RMOLY = 0.
C RETRIEVE COPPER GRADE
TCU = RMX(ICOL,1)
IF (TCU .LT. 0.) TCU = 0.
C RETRIEVE EQUIVALENT COPPER GRADE
EQCU = RMX(ICOL,3)
IF (EQCU.LT. 0.) EQCU = 0.
C
IF (EQCU.GE. GMIN .AND. EQCU.LE.GMAX) THEN
XX = XMIN + ICOL * DX -DX *.5
WRITE(IOU,220) XX,YROW,ZMID,TCU,RMOLY,EQCU
ENDIF
IF(IOLEV.EQ.2) THEN
WRITE(IPR,270) IZ, IROW, ICOL,TCU,RMOLY,EQCU
ENDIF

MineSight
300 CONTINUE
RETURN
220 FORMAT(1X,3F10.1,3F8.3)
270 FORMAT( IZ,IY,IX = ,3I4, TCU =,F7.3, MOLY =,F7.3,
& EQCU =,F7.3)
C
1000 IF (NTRY .GT. 1) GO TO 1500
C
C
WRITE (LPR,1510) IZ
RETURN
C
C
1500 CONTINUE
CALL NEWPAG (0)
WRITE (LPR,1520)
RETURN
C
1510 FORMAT ( ** USR612D END BENCH,I4/)
1520 FORMAT ( ** USR612D END-OF-RUN//)
END
CONVERTING OLD M612V1 USER SUBS TO NEW USER SUBS
If you have written user subs for m612v1 prior to the 2011 Update CD, you may notice changes in the way newer object modules
(namely m612d1.obj and m612db1.obj) are being called versus the manner older object modules were being called (what was
once distributed as m612v1.obj, m612b1.obj, and m612e1.obj). The process to convert an older user sub to the newer standard
first involves identifying whether /ITM/ & /SYS/ or /ITMB/ & /SYSB/ common blocks will be used. If you need to access more
than 99 items, you will need to use /ITMB/ & /SYSB/ common blocks. Thus use the following conversion for replacing object
modules:
Replace m612v1.obj (for 10-item m612v1) with m612d1.obj (which uses /ITM/ & /SYS/)
Replace m612b1.obj (for 99-item m612v1) with m612d1.obj (which uses /ITM/ & /SYS/)
Replace m612e1.obj (for 500-item m612v1) with m612db1.obj (which uses /ITMB/ & /SYSB/)
There is a subroutine name change - all m612* objects now are named USR612D. All newer subroutines will have MXCOL,
MXROW, MAXITM added to the argument list.
Thus convert the old m612* argument list from this:
SUBROUTINE USR612 (NTRY, IZ, ZMID, IROW, YROW, MCOL, NCOL, MAP, RMX)
... to this:
SUBROUTINE USR612D(NTRY, IZ, ZMID, IROW, YROW, MCOL, NCOL, MAP, RMX, MXCOL, MXROW,
MAXITM)
Since MAXITM is now passed as an argument, the various older subroutine names of USE612, U99612, U25612, USR612 are no
longer neccessary and all may now be renamed to USR612D. Remember to add MXCOL, MXROW, MAXITM to the argument
list.

MineSight
Thus, as done with USR612 above, also convert USE612 from this:
SUBROUTINE USE612 (NTRY, IZ,ZMID, IROW,YROW, MCOL,NCOL, MAP, RMX)
... to this:
SUBROUTINE USR612D(NTRY, IZ,ZMID, IROW,YROW, MCOL,NCOL, MAP, RMX, MXCOL, MXROW, MAXITM)
And convert U99612 from this:
SUBROUTINE U99612 (NTRY, IZ,ZMID, IROW,YROW, MCOL,NCOL, MAP, RMX)
... to this:
... to this:
Arrays passed in the argument list (namely MAP, RMX) need to be dimensioned accordingly. Thus, redimension these arrays as
such using the MXCOL,MAXITM parameters passed in the subroutine argument list:
DIMENSION MAP(MXCOL)
DIMENSION RMX(MXCOL,MAXITM)

2. ?M612V1: ERROR. Stopping at BENCH HEADER LINE with benches xxx to yyy.
The last initialized bench is zzz (and is less than yyy).
Either 1) you are trying to access benches that have not yet been initialized with M601V1 (as in the above example) or 2) your
starting bench number is greater than your ending bench number.

4. ?M612V1: ERROR. You have requested xx ITEMs in this run. M612V1 currently has a limit of 10 ITEMs.
M610V1 has a limit of 10 items (or 99 if you are linking with M612B1) that can be accessed during a single run. The total
number of ITM, GET, PUT, and UPD items in your run file exceeds this number.

MineSight
5. ?M612V1: ERROR. You are running with the STORE option (IOP4=0), but you have not selected an ITEM to store using
the ITM, UPD or PUT command.
If you wish to store data, you must select the item to be used with an ITM, UPD or PUT command.
6. ?M612V1: ERROR. No ITEMs have been selected.

Regardless of the IOP4 setting, you need to select an ITEM to access. Do so by using an ITM, GET, UPD or PUT command.
7. Check the results of your calculation by plotting out the bench(es) with M606V1. If you have reason to doubt the results, check
The UPD or GET lines. Your subroutine should be using the correct items.
The program logic.

MineSight

MineSight
Proprietary Software: Mintec, inc. M612V2 - USER INTERFACE FOR MINE MODEL FILES (SECTIONS)
M612V2 USER INTERFACE FOR MINE MODEL FILES

(SECTIONS)

Program M612V2 is used to read/modify your model files. M612V2 is used to access, modify and update data in one of the
M612V2 provides read-write access to your model files, mine model files (File 13, 14 or 15). Data is accessed by section.
allowing you to manipulate the values via a FORTRAN You do not need to know the structure of the Data File nor the
subroutine. The program acts as an interface between your file details of how data is stored and retrieved. However, you should
and your subroutine. The model is accessed vertically by section. be able to write a simple Fortran program that will perform the
Calculated values may be stored into the model. desired calculations. Examples of user-coded subroutines are
provided in the sample file section. M612V2 is used to perform
the following types of operations which cannot be done using
M612V1.
Modify File 15 items using surface read from File 13
RUN FILE:
- Area selection Calculate summary parameters by column from data in Files

- Item selection 15 and 13 and store the calculated values in File 13
- Symbol map option
Calculate benches or seams from data in File 13 and 15 and

output the results in M610V2 format
You may specify the area of the model to be accessed by row,

column and bench number. Data can be read in from an external
INPUT: CALCS: ASCII file or can be written to an external ASCII file. A symbol
map can be printed that will provide a check on the calculations
- PCF - Select data from model that were performed.
- Mine Model File (File - Apply user calculation/
13, 14, or 15) report
- Update model Mintec provides M612V2 object modules which need to be
linked with your compiled subroutine to produce an executable
program. These are the M612V2 object modules capable of
accessing different numbers of items:
m612d2.obj object module can access at most 99 items and links

OUTPUT: with the user subroutine USR612D.
- Updated mine model file m612db2.obj object module can access up to 500 items and links
- Printer Output File with the same user subroutine name, USR612D.
The user subroutine is called by the main routine a number of

times. A call is always made for initialization. If IOP3=0, the
subroutine is called for each bench in the selected range. If
IOP3=1, the subroutine is called for each bench and after each
row. If IOP3=2, the subroutine is called for each bench, after
each row and at the end of the run.

MineSight
M612V2 - USER INTERFACE FOR MINE MODEL FILES (SECTIONS) Proprietary Software: Mintec, inc.
A number of arguments are passed from the main routine The RMX array in the subroutine is a real two-dimensional array
(M612V2) to the user coded subroutine. that contains the selected data items for each block in a row (up
to MXCOL blocks). The order of the data items corresponds
NTRY = -1 Initialization (always done) to the order of items on the GET or UPD in the run file. For
NTRY = 0 Process bench data (If IOP3=0, 1, 2) example, if the GET command was
NTRY = End of row (If IOP3=1,2)
NTRY = 2 End of run (If IOP3=2) GET15 = TCU-1 MO-1 ROCK
IZ = Bench number the RMX array would have

ZMID = Elev. of bench midpoint or seam number
TCU-1 in RMX(NX,1) NX=column number
IROW = Row number MO-1 in RMX(NX,2)
YROW = Northing of row midpoint ROCK in RMX(NX,3)
MCOL = First column to process If you specify a GET13 line and/or a GET14 line, the items will
NCOL = Last column to process be sequentially put into the RMX array after the GET15 items.
MAP = Array of integer values to write back to file The MAP array is an integer one-dimensional array (sized to
(dimension to MXCOL columns) MXCOL) that contains an integer result from a user-calculation
for each block in a row (up to MXCOL blocks). The value in
RMX = Array of real values to read from and write the MAP array corresponds to the item specified in the ITM1
back to file command in the run file.
MXCOL = Maximum number of columns to process To write values to a MineSight Data File, use the UPD
(used for array dimensioning such as RMX command in the run file.
& MAP)
To process levels in inverse order (from bottom to top), add
MXROW = Maximum number of rows to process (used CMD = LEVS UP to your run file.
for array dimensioning)
WARNING: If you are updating your model, make a backup
MAXITM = Maximum number of items to process (used copy of the model file before running M612V2.
for array dimensioning such as RMX)
IMPORTANT NOTE: Common blocks used for item and
The dimension of RMX is MXCOL columns multiplied by system information are different for the object modules (they
MAXITM (the maximum number of items). If you use the 99 are named differently as well).
item maximum, your subroutine should be linked with module
m612d2.obj. For the 500 item maximum, your subroutine must Please refer to the Technical 600 section for more information
be linked with module m612db2.obj. The RMX array should about how to write MineSight user subroutines.
be dimensioned to RMX(MXCOL,MAXITM).

MineSight
M612V2 - USER INTERFACE FOR MINE MODEL FILES (SECTIONS)
RUN FILE OPERATION

MEDS-612V2 10=filename 15=filename 14 (or13)= filename;

where

19 = the name of the OPTIONAL INPUT/OUTPUT FILE (See IOP9)
IOP2 = OPTION TO ACCESS DATA FROM FILE BEFORE CALLING USR612D FOR EACH BENCH
= 0 OMIT ACCESSING DATA FROM THE FILE
= 1 ACCESS DATA SPECIFIED ON PUTn, GETn OR UPDn LINE
NOTE: If IOP2=0, then PUTn, GETn and UPDn items are not allowed
IOP3 = OPTION TO GOVERN CALLING ROUTINE USR612D

= 0 CALL SUBROUTINE FOR EACH BENCH
= 1 CALL SUBROUTINE BY BENCH & AFTER EACH ROW
= 2 CALL SUBROUTINE BY BENCH, ROW & END-OF-RUN
IOP4 = OPTION FOR TYPE OF RUN

= -1 ACCESS SUBROUTINE BUT DO NOT STORE ANY DATA
= 0 ACCESS SUBROUTINE AND STORE RESULTS IN FILE
= 1 PRINT SYMBOL MAP ONLY


IOP9 = USE A SEQUENTIAL INPUT/OUTPUT FILE

= 0 OMIT ANY USE OF THIS EXTRA FILE
= 1 SET UP A FILE TO BE OUTPUT BY USR612D
= 2 SET UP A FILE TO BE INPUT BY USR612D

MineSight

= 1 PRINT THE SYMBOL MAP OF USR612D GENERATED VALUES
NOTE: You can only plot values that are calculated and stored in the MAP array in the user subroutine.
IOP11 = FIRST BENCH TO ACCESS (default=1)

IOP12 = LAST BENCH TO ACCESS (default=last bench initialized in the model file)
IOP13 = 0 USE IOP11-12

= 1 READ BENCH NUMBERS TO USE IN RUN
IOP14 = 1 READ ROWS & COLUMNS TO MANIPULATE

NOTE: Overrides IOP5-8.
IOP16 = GSM REF# TO STORE UPD ITEMS AFTER ALL SLICES HAVE BEEN PROCESSED FOR EACH SECTION
IOP20-40 are available for user integer constants.
PAR1-40 are available for user real constants.
To retrieve multiple real values from file use:
GETn = label1 label2 ... labeln (for retrieving real data)
NOTE: Matches variables in RMX array in the subroutine. IOP2 must be 1. If you want to retrieve a value from
File 13 or 14 as well as File 15, you may specify
GET13 = label13 -or- GET14 = label14
The items will be stored in the RMX array after the GET15 items.
To write values to file use:
PUTn = label1 label2 ... labeln (for storing real data)

-OR-
UPDn = label1 label2 ... labeln (for retrieving and storing real data)
NOTE: Matches variables in RMX array in the subroutine. At most 10 total GETn, PUTn, UPDn items may be
used.
END

MineSight
There may be one or more lines specifying benches. Up to 10 benches per line in free-field format.
The bench request lines terminate when a zero is entered for the first bench. For example:
1 17 22 4
16 33
0
The last line terminates the bench request lines.
5. ROW/COLUMN LINES (If IOP14=1)
There may be one or more lines specifying rows and columns as:
row1 row2 col1 col2

MEDS-612V2 10=SAMP10.DAT 13=SAMP13.DAT 15=SAMP15.DAT 3=RPT612.LA2
USR = ABC
IOP2 = 1 / Read UPD data

IOP3 = 2 / Call user routine at end-of-bench & run
IOP10 = 1 / Print symbol map
PUT15 = EXTRA / File 15 item to compute

GET13 = TOPOI TOPOD / File 13 items use in the computation
END

MineSight

The following is a sample user subroutine for use with M612V2 that reads from File 15 and writes to File 13. The purpose of this
subroutine is to determine the top of ore (first occurrence of a grade above cutoff) for each column and store its elevation in File 13.
The surface generated in File 13 can be contoured for use in other programs.

C=======================================================================
C
C Compute a relative elevation for file 15 item EXTRA.
C
C Use file 13 items TOPOI and TOPOD
C
C=======================================================================
DIMENSION RMX(MXCOL,MAXITM), MAP(MXCOL), PCF(512)
C
COMMON /SYS/ XDUM1(100), IOP(40), PAR(40), XDUM2(104),
& ICR, IPR, LCR, LPR, XDUM3(5), IOLEV, XDUM4(89)
COMMON /F10/ IPCF(512), XDUMD(142)
C
EQUIVALENCE ( IPCF(1), PCF(1) )
C
C Limit R2 by R1 below and R3 above
RLIMIT( R1, R2, R3 ) = AMIN1( AMAX1( R1, R2 ), R3 )
C
C=======================================================================
IF ( NTRY ) 100, 400, 600
C..................................................... INITIALIZE
C
100 CONTINUE
OMIT = PCF(490)
C
WRITE ( LPR,110 )
WRITE ( IPR,110 )
110 FORMAT( /, 10X, Computing Relative Elevations, // )
GOTO 900
C
C..................................................... PROCESS SECTION
400 CONTINUE
C
DO 410 IC = MCOL, NCOL
ZONTOP = RMX(IC,2)
ZONBOT = RMX(IC,3)
IF ( ZONTOP.EQ.OMIT .OR. ZONBOT.EQ.OMIT ) THEN
C this block is not well-defined
EXTRA = 0.
ELSE IF ( ZONBOT.LE.ZMID .AND. ZMID.LE.ZONTOP ) THEN
C the center of this block is inside the zone
EXTRA = ( ZMID-ZONBOT ) / ( ZONTOP-ZONBOT )
EXTRA = RLIMIT( 0., EXTRA, 1. )
ELSE

MineSight
C the center of the block is outside the zone

EXTRA = 0.
ENDIF
RMX(IC,1) = EXTRA
MAP(IC) = INT( 26.*EXTRA )
410 CONTINUE
GOTO 900
C
C..................................................... LAST BENCH IN ROW
600 CONTINUE
IF ( NTRY .EQ. 2 ) GOTO 800
C
WRITE ( IPR, 1410 ) , IROW, YROW
WRITE ( LPR, 1410 ) +, IROW, YROW
1410 FORMAT( A1, 5X, Finished with row:, I5, 2X, F10.2 )
GOTO 900
C
C..................................................... END OF RUN
800 CONTINUE
WRITE ( LPR, 810 )
810 FORMAT( /, 10X, Successful Program Completion )
C
C..................................................... EXIT
900 CONTINUE
RETURN
END

MineSight
Sample Symbol Map: This is in the report file.
RUN# 519. PAGE 51 METL 612V2 DATE 02-16-93 TIME 13:39:58

_________________________________________________________
* SAMPLE METAL PROJECT - INITIALIZE P.C.F. PARAMETERS *
Symbol Plot: Row 49 Northing= 14850.
1020 30 40 50
Z +....+....+....+....+....+....+....+....+....+....+
1 !..................................................
2 !..................................................
3 !..................................................
4 !..................................................
5 !..................................................
6 !..................................................
7 !..................................................
8 !...P......................P.........P.............
9 !...M..N........O.ONKP.OO.MLL..P...O.KP.OO........O
10 !...J.KG.......OG.KFDJ.JLHJHG..JMN.J.FK.KKOLLM.N.ML
11 !INMG.E9ON...NOJ9PH85ENEH8GECH.CJBCD.AG.GGKHGI.H.HH
12 !9EDCJ82FJJMMHGE2KD..8I9E.DA7..6F..8G6BMDCHCBENAJCD
13 !.459.2.6FBHGB8A.F9..3D4A.A62...B..2516D99D77AH3C7A
14 !...6....A4CB4.5.A6...9.7.72....7.....14559227B.426
15 !...3....6.75..1.62...4.3.3.....3.......115..35...3
16 !........2.2.....1........................1........
17 !..................................................
18 !..................................................
19 !..................................................
20 !..................................................
21 !..................................................
22 !..................................................
23 !..................................................
24 !..................................................
25 !..................................................
26 !..................................................
27 !..................................................
28 !..................................................
29 !..................................................
30 !..................................................
31 !..................................................
32 !..................................................
33 !..................................................
34 !..................................................
35 !..................................................
36 !..................................................
37 !..................................................
38 !..................................................
39 !..................................................
40 !..................................................
Z +....+....+....+....+....+....+....+....+....+....+
10 20 30 40 50
Finished with row: 49 14850.00

MineSight
CONVERTING OLD M612V2 USER SUBS TO NEW USER SUBS

If you have written user subs for m612v2 prior to the 2011 Update CD, you may notice changes in the way newer object modules
(namely m612d2.obj and m612db2.obj) are being called versus the manner older object modules were being called (what was
once distributed as m612v2.obj, m612b2.obj, and m612e2.obj). The process to convert an older user sub to the newer standard
first involves identifying whether /ITM/ & /SYS/ or /ITMB/ & /SYSB/ common blocks will be used. If you need to access more
than 99 items, you will need to use /ITMB/ & /SYSB/ common blocks. Thus use the following conversion for replacing object
modules:
There is a subroutine name change - all m612* objects now are named USR612D. All newer subroutines will have MXCOL,
MXROW, MAXITM added to the argument list.
SUBROUTINE USR612 ( NTRY, IZ, ZMID, IROW, YROW, MCOL, NCOL, MAP, RMX )
... to this:
SUBROUTINE USR612D( NTRY, IZ, ZMID, IROW, YROW, MCOL, NCOL, MAP, RMX, MXCOL, MXROW,
MAXITM )
Since MAXITM is now passed as an argument, the various older subroutine names of USE612, U99612, U25612, USR612 are no
longer neccessary and all may now be renamed to USR612D. Remember to add MXCOL, MXROW, MAXITM to the argument
list.
Thus, as done with USR612 above, also convert USE612 from this:
SUBROUTINE USE612 (NTRY, IZ,ZMID, IROW,YROW, MCOL,NCOL, MAP, RMX)
... to this:
... to this:
... to this:
Arrays passed in the argument list (namely MAP, RMX) need to be dimensioned accordingly. Thus, redimension these arrays as
such using the MXCOL,MAXITM parameters passed in the subroutine argument list:

MineSight

1. ?M612V2: ERROR. Your File 15 is empty.
You MUST initialize your file with M601V1 before proceeding

The ROWs/COLUMNs/BENCHes that you selected using IOP5 through IOP8, IOP11 and IOP12 are badlin defined. Either
the first index is greater than the last index (as in the columns above) or the last index exceeds the maximum (as in the benches
above). Note that when IOP2=1, the last bench you can access is determined by the last bench initialized with M601V1. This
might not be the same as the last bench in the model.
3. ?M612V2: ERROR. You have selected IOP13=1 but have not entered any BENCH REQUEST LINES.
By selecting IOP13=1, M612V2 expects to read Bench Request Lines after the END in the run file.
4. ?M612V2: ERROR. You have selected xx items.

M612V2 currently has a limit of 10 items.
You must limit the number of items accessed using the GET, PUT, and UPD commands to 10.
6. ?M612V2: ERROR. Bench xx on BENCH REQUEST LINE exceeds the last bench initialized yy.
The bench number specified on a Bench Request Line is greater than the last bench initialized using M601V1. You can only
access benches that have been previously initialized.
7. Check the results of your calculations by plotting the model section(s) with M606V1. If you have reason to doubt the results,
check
the UPD or GET lines. Your subroutine should be using the correct items
the program logic.


MineSight
Proprietary Software: Mintec, inc. M615V1 - COMPUTE BLOCK CODES FROM DIGITIZEDPLAN BOUNDARIES
M615V1 COMPUTE BLOCK CODES FROM DIGITIZEDPLAN

BOUNDARIES
M615V1 computes and stores block codes in the mine model M615V1 is used to update integer block codes in a mine model
from digitized plan geology. file. These block codes should have a precision of 1 for the
program to work as documented. The block codes are determined
from digitized outlines that are read from the end of the run file
or from an external ASCII file. Updating is on a bench basis.
PROGRAM FLOW DIAGRAM The mine model may be either a regular 3-D Block Model or a
Gridded Seam Model.
RUN FILE:
- Area selection STORING INTEGER CODES:
- Item selection
Each outline is input and then converted into block partials that
correspond to the limits of the model. If you enter the command
ITMn=label, M615V1 will store the integer block code for blocks
with a partial greater than PAR1. Blocks with a partial less than
PAR1 are not altered.
STORING BLOCK PERCENTAGE:

INPUT: CALCS:
- PCF - Read input data for new If you enter the command ITM1=label BLK%, M615V1 will
- Mine model file (File codes store the percent of the block, with PAR1 not being used.
13, 14 or 15) - Update model item
- Optional input file
If there are several geologic outlines that must interact with each
other, then the outlines should be ordered from the largest or
outermost outline to the smallest innermost outline. This will
insure that codes will be stored in the correct blocks of the model.
The input data for each geologic outline consists of a single line
OUTPUT: specifying the bench and the numeric code to be inserted,
- Updated Model File followed by a series of (X,Y) points around the outline. To end
- Printer Output File an outline, close the digitized data with 0 0. The next outline
will have the same bench range and code. To change the bench
number and/or the code, end the digitized data with -1 -1. Then
specify a new Bench Request Line. For example,
Bench Request Line - new bench & code

X Y points
00
X Y points
00
X Y points
-1 -1
Bench Request Line - new bench & code
X Y points
. .
. .
The terminator lines (0 0 or -1 -1) should be in the same format

as the X,Y points. The Bench Request Line is read with free
format.

MineSight
M615V1 - COMPUTE BLOCK CODES FROM DIGITIZEDPLAN BOUNDARIES Proprietary Software: Mintec, inc.

MineSight
Proprietary Software: Mintec, inc. M615V1 - COMPUTE BLOCK CODES FROM PLAN BOUNDARIES
M615V1 - COMPUTE BLOCK CODES FROM PLAN BOUNDARIES
RUN FILE OPERATION


where

15 = the name of the 3-D MINE MODEL FILE -OR-
19 = the name of the OPTIONAL INPUT FILE (See IOP9)
IOP2 = NUMBER OF X,Y POINTS PER INPUT LINE (default=1) (MAX=10 points or 20 values)
IOP4 = NUMBER INCREMENTS PER RUN FOR PARTIAL CALCULATION (default=20)


IOP9 = 0 INPUT OUTLINES IN RUN FILE

= 1 INPUT OUTLINES IN A SEPARATE FILE
IOP10 = 0 OMIT SYMBOL MAP

= 1 PRINT SYMBOL MAP
IOP11 = 0 PARTIALS ARE IN DECIMAL FORMAT (i.e., from 0 to 1.00)

= 1 PARTIALS ARE IN INTEGER FORMAT (i.e., from 0 to 100)
ITMn = label-nn RECEIVE CODE FROM OUTLINE CALCULATIONS

ITMn = label-nn BLK% (alternate)
NOTE: If BLK% is used, the program will store block% instead of an integer code.

MineSight
M615V1 - COMPUTE BLOCK CODES FROM PLAN BOUNDARIES Proprietary Software: Mintec, inc.
FMT1 = FORMAT FOR POINT OUTLINES
NOTE: If FMT1 is omitted or FMT1 = (*), free-field format is assumed. Otherwise, FMT1 = (Fortran
format).
PAR1 = MINIMUM BLOCK PARTIAL VALUE TO ADD CODES
NOTE: 1) IOP11 controls if PAR1 will be decimal (0 to 1.00) or integer (0 to 100)
2) PAR1 is not effective when loading block % (option BLK% in ITMn)
END
first code last

where
first = the bench reference number

code = the integer code stored for blocks inside the geologic outline.
last = the last bench reference number (default=first) (optional)
NOTE: One outline can be used and put into several benches.
5. POINTS FOR GEOLOGIC OUTLINE
Easting Northing
Multiple pairs of points in free format on a single line are allowed as long as IOP2 is specified. 0 0 closes an outline. -1 -1 ends a
bench.

MineSight
Proprietary Software: Mintec, inc. M615V1 - COMPUTE BLOCK CODES FROM PLAN BOUNDARIES

MEDS-615V1 10=SAMP10.DAT 15=SAMP15.DAT 3=SAM615.LA
* REDUCE OUTLINES TO MINE MODEL CODES *
COM* SAMPLE RUN FOR BENCH # 1
USR = ABC
IOP2 = 1 / # OF X,Y POINTS PER INPUT LINE

IOP7 = 20 40 / ROWS
IOP9 = 0 / INPUT RESIDES IN THIS RUN FILE
IOP10 = 1 / 1= PRINT SYMBOL MAP, 0= OMIT
ITM1 = CODE
FMT1 = (2F10.0)
I-O = 1
END
11 BENCH REQUEST LINE
13000. 13800.
14600. 13000.
13800. 12400.
12400. 12400.
11400. 13000. POINTS FOR GEOLOGIC OUTLINE
13000. 13800.
0. 0. CLOSE OUTLINE
13000. 13500.
14000. 13000.
13000. 12500.
12500. 13000.
13000. 13500.
-1. -1. END BENCH
21 BENCH REQUEST LINE
11600. 13800.
12800. 13800.
12800. 13600.
12400. 13400. POINTS
11800. 13000.
11200. 13600.
0. 0. END BENCH

MineSight
M615V1 - COMPUTE BLOCK CODES FROM PLAN BOUNDARIES Proprietary Software: Mintec, inc.

1. M615V1: THERE ARE NOT ENOUGH POINTS FOR AN OUTLINE.
You must have at least 3 points to define your geologic outline. (you must have 4 or more)
2. * M615A1: IOP1 NOT 13, 14 OR 15 **
will appear if you try to access a file that is not a mine model file.
3. ** M615A1: NO ITM1 WAS SPECIFIED **
will appear if you do not have an ITM1 line in the run file.
4. ** M615A1: IOP2 CAN NOT EXCEED 10 **
There can be, at most, 10 X, Y points per input line.
5. If your symbol map does not look like the digitized outline check that
The input format matches the data
Separate zones are closed by a 0 0 line (if same bench and code)
New benches or codes are preceded by a -1 -1 line and a Bench Request Line
6. ?M615V1: ERROR. Level XX exceeds the last model, YY
Your model has only YY levels and you are trying to access a level number exceeding YY (level XX).
7. ?M615V1: WARNING. THE MINIMUM VALUE FOR YOUR BLOCK CODE IS 0. THIS WILL CORRESPOND
TO ZERO ON YOUR SYMBOL MAP. ALL OTHER CODES WILL BE SCALED ACCORDINGLY.
If you have selected the Symbol Map option (IOP10=1) and your block code ITEM has a minimum value other than zero, then
the values printed in your symbol map have been scaled so that zero (on the symbol map) corresponds to the minimum block
code value. For example, if the block code minimum value is -3, then -3 will be printed as 0 on the symbol map.

MineSight
Proprietary Software: Mintec, inc. M615V2 - COMPUTE CODES FROM DIGITIZED SECTION BOUNDARIES
M615V2 COMPUTE BLOCK CODES FROM DIGITIZED

SECTION BOUNDARIES
M615V2 computes and stores block codes in the mine model M615V2 is used to update integer block codes in a mine model
from digitized E-W section geology. file. The block codes are determined from digitized outlines
that are read from the end of the run file or from an external
ASCII file. Updating is on a section basis. The mine model may
be either a regular 3-D Block Model or a Gridded Seam Model.
STORING INTEGER CODES:
RUN FILE:
- Area selection Each outline is input and then converted into block partials that
- Item selection correspond to the limits of the model. If you enter the command
ITMn=label, M615V2 will store the integer block code for blocks
with a partial greater than PAR1. Blocks with a partial less than
PAR1 are not altered.
STORING BLOCK PERCENTAGE:
If you enter the command ITM1=label BLK%, M615V2 will

INPUT: CALCS: store the percent of the block, with PAR1 not being used.
- PCF - Read input data for new
- Mind model file (File codes If there are several geologic outlines that must interact with each
13, 14 or 15(- - Update model item other, then the outlines should be ordered from the largest or
Optional output file
outermost outline to the smallest innermost outline. This will
insure that codes will be stored in the correct blocks of the model.
The input data for each geologic outline consists of a single line
specifying the section and the numeric code to be inserted,
followed by a series of (X,Y) points around the outline. To end
OUTPUT: an outline, close the digitized data with 0 0. The next outline
- Updated Model File will have the same section range and code. To change the section
- Printer Output File number and/or the code, end the digitized data with -1 -1. Then
specify a new Row Request Line. For example,
Row Request Line - new row & code

X Y points
00
X Y points
00
X Y points
-1 -1
Row Request Line - new row & code
X Y points
. .
. .
The terminator lines (0 0 or -1 -1) should be in the same format

as the X,Y points. The Row Request Line is read with free
format.

MineSight
M615V2 - COMPUTE CODES FROM DIGITIZED SECTION BOUNDARIES Proprietary Software: Mintec, inc.

MineSight
Proprietary Software: Mintec, inc. M615V2 - COMPUTE BLOCK CODES FROM SECTION BOUNDARIES
M615V2 - COMPUTE BLOCK CODES FROM SECTION BOUNDARIES
RUN FILE OPERATION


where

15= the name of the 3-D MINE MODEL FILE -OR
13= the name of the 2-D SURFACE FILE -OR-
19= the name of the OPTIONAL INPUT FILE (See IOP9)
IOP2 = NUMBER OF X,Y POINTS PER INPUT LINE (default=1, MAX = 10 points or 20 values)
IOP4 = NUMBER INCREMENTS PER ROW FOR PARTIAL CALCULATION (default=20)
IOP5 = COL1: 1ST MATRIX COLUMN TO PRINT (default=1)

IOP6 = COL2: LAST MATRIX COLUMN TO PRINT (default=NX)
IOP7 = LEV1: 1ST MATRIX LEVEL TO PRINT (default=1)

IOP8 = LEV2: LAST MATRIX LEVEL TO PRINT (default=NY)
IOP9 = 0 IF INPUT DATA RESIDES IN RUN INPUT FILE

= 1 IF INPUT DATA RESIDES IN A SEPARATE FILE
IOP10 = 0 OMIT SYMBOL MAP

= 1 PRINT SYMBOL MAP
ITMn = label-nn RECEIVE CODE FROM OUTLINE CALCULATIONS

ITMn = label-nn BLK% (alternate)
NOTE: If BLK% is used, the program will store block% instead of an integer code.

MineSight
M615V2 - COMPUTE BLOCK CODES FROM SECTION BOUNDARIES Proprietary Software: Mintec, inc.
FMT1 = OPTIONAL INPUT FORMAT FOR POINT OUTLINES
PAR1 = MINIMUM BLOCK PARTIAL VALUE TO ADD CODES
END
4. ROW REQUEST LINES (If IOP9=0)
first code last

where
first = the model row reference number

code = the integer code stored for blocks inside the geologic outline
last = the last row reference number (default=first, optional)
NOTE: One outline can be used and put into several sections.
5. POINTS FOR GEOLOGIC OUTLINE
Easting Northing
Multiple pairs of points in free format on a single line are allowed as long as IOP2 is specified. 0 0 closes an outline. -1 -1 ends a
section.

MineSight
Proprietary Software: Mintec, inc. M615V2 - COMPUTE BLOCK CODES FROM SECTION BOUNDARIES

MEDS-615V2 10=SAMP10.DAT 15=SAMP15.DAT 3=RPT615.LA2
* REDUCE OUTLINES TO MINE MODEL CODES *
COM* SAMPLE RUN FOR SECTION # 1
USR = ABC
IOP2 = 1 / # OF X,Y POINTS PER INPUT LINE

IOP7 = 20 40 / ROWS
IOP9 = 0 / INPUT RESIDES IN THIS RUN FILE
IOP10 = 1 / 1= PRINT SYMBOL MAP, 0= OMIT
ITM1 = CODE
FMT1 = (2F10.0)
I-O = 1
END
11
13000. 13800.
14600. 13000.
13800. 12400.
12400. 12400.
11400. 13000.
13000. 13800.
0. 0.
13000. 13500.
14000. 13000.
13000. 12500.
12500. 13000.
13000. 13500.
-1. -1.
21
11600. 13800.
12800. 13800.
12800. 13600.
12400. 13400.
11800. 13000.
11200. 13600.
0. 0.

MineSight
M615V2 - COMPUTE BLOCK CODES FROM SECTION BOUNDARIES Proprietary Software: Mintec, inc.

1. M615V2: #PTS= xx NOT ENOUGH FOR AN OUTLINE
You must have at least 3 points to define a zone boundary.
2. * M615A1: IOP1 NOT 13, 14 OR 15 **
will appear if you try to access a file that is not a mine model file.
3. ** M615A1: NO ITM1 WAS SPECIFIED **
will appear if you do not have an ITM1 line in the run file.
4. ** M615A1: IOP2 GREATER THAN 10 **
will appear if you specify more than 10 pairs of digitized data points per line.
5. If your symbol map does not look like the digitized outline check that
the input format matches the data
separate zones are closed by a 0 0 line (if same section and code)
new sections or codes are preceded by a -1 -1 line and a Row Request Line

MineSight
Proprietary Software: Mintec, inc. M617V1 - ADD MINE MODEL CODES TO COMPOSITE DATA
M617V1 ADD MINE MODEL CODES TO COMPOSITE DATA

M617V1 assigns mine model codes to composite data files (files M617V1 is used to add mine model codes from File 15 to the
9/8) or to an MSTorque database. drillhole composites. The program takes each composite and
finds the mine model block which contains it. The code of the
block is then assigned to that composite. The program can access
either the composites in File 9, the sorted composites in File 8
PROGRAM FLOW DIAGRAM or an MSTorque database. Assigning composite codes in this
manner guarantees an accurate match between a composite and
RUN FILE: the block that contains it. This is important if you want to match
- Composite data unit block geology with composite geology when interpolating model
- Item selection grades. You can also run statistics on composites and block
- Area selection values based on rock types.
The following notes may help in deciding about updating File

8 or File 9 or an MSTorque database.
Add codes to File 9 or an MSTorque database when:
INPUT: CALCS:
You have not yet sorted the composites to produce
- PCF - Access composite and File8.
- File 15 find corresponding mine
- File 8 or 9
or
model block
- Assign mine model code
You have a File 8 but are going to re-composite and
- MSTorque database to composite file then produce another File 8. (If you add codes to File
8, but not File 9, re-sorting will over-write them.)
Add codes to File 8 when:
OUTPUT: Your composites are in final form and you are going
directly to interpolating. (This saves the step of re-
- Updated File 8 or 9 sorting File 9.)
or
- Updated MSTorque
database
- Printer Ourput File

MineSight
M617V1 - ADD MINE MODEL CODES TO COMPOSITE DATA Proprietary Software: Mintec, inc.

MineSight
M617V1 - ADD MINE MODEL CODES TO COMPOSITE DATA
RUN FILE OPERATION

MEDS-617V1 10=filename 15=filename 9 (or 8)=filename;

where

9 = the name of the COMPOSITE FILE OR TORQ for input from MSTorque
8 = the name of the SORTED COMPOSITE FILE
20 = MSTorque information file (mstorq.inf), if 9=TORQ is used
NOTE: To access the MSTorque database, use 9=TORQ and include an MSTorque info file (20=mstorq.inf). For information
about the MSTorque info file, please refer to the M600-Technical Section, Technical Considerations for Interpolation.
IOP1 = FIRST COMPOSITE DATA UNIT TO ACCESS

IOP2 = LAST COMPOSITE DATA UNIT TO ACCESS
IOP3 = 0 LIST DHS WITHIN PROJECT LIMITS

= 1 LIST DHS WITHIN SPECIFIED BOUNDARY
lines:
CMD = INCL LOCPT FILE filename (to include points within the boundary) - OR -
IOP4 = 0 ACCESS DH COMPOSITES IN FILE 9 OR MSTORQUE

= 1 ACCESS SORTED COMPOSITES IN FILE 8
IOP5 = 0 NO COMPOSITE LISTING

= 1 LIST COMPOSITES AND MODEL VALUE

MineSight
ITMn = CODE label-15 label-09(08)

where
CODE = Keyword for the program

label-15 = Label of the code item in the model
label-09(08) = Label of the code item in the composite file
NOTE: Codes may be integers or real numbers.
ITMn = LEVEL label-nn

where
LEVEL = Keyword for the program

label-nn = Controlling Z item for a 3-D model (default = ELEV.)
NOTE: Use this ITM if you have stored the composites at an elevation other than the bench toe, for
example, ZMID.
ITMn = SEAM label-nn

where
SEAM = Keyword for the program

label-nn = Controlling Z item to match the PCF seam code table, usually an item called SEAM
NOTE: The SEAM keyword can only be used with GSM models and is mutually exclusive with the
LEVEL keyword.
If using a 3D-rotated GSM file 15, specify the item for composite elevation:
CMD = ZCRD label-nn

where
label-09 = composite elevation item (e.g., ZTOP)
END
4. BOUNDARY POINT LINES (If IOP3=1)
where 0 0 ends the input or input ends on end-of-file. Boundary point MUST close. The maximum number of boundary points
allowed is 2000.

MineSight

MEDS-617V1 10=SAMP10.DAT 9=SAMP09.DAT 15=SAMP15.DAT;
* ADD ROCK CODES TO DH COMPOSITES FROM 3-D MODEL *
USR = ABC
IOP1 = 1 0 / FIRST AND LAST DATA UNITS IN FILE 9

IOP3 = 0 /-1=NO BOUNDARY, 0=PCF BOUNDARY, 1= USER SPEC. BOUNDARY
IOP4 = 0 /0 =ACCESS FILE 9, 1=ACCESS FILE 8
ITM1 = CODE GEOL ROCK

END

1. %M617V1: WARNING. You have only initialized 52 of the 130 benches in your File 15.
Only the first 52 benches of your File 15 have been initialized using M601V1. Any composite in benches 53 through 130 will
not have mine model codes assigned to it since File 15 has no data for those benches.
2. ?M617V1: ERROR. Your file 15 is emptyYou MUST initialize your file with M601V1 before proceeding.
You must initialize File 15 with M601V1 before any MineSight program can access it.
3. ?M617V1: ERROR. Seam Z-ITEM control can ony be used with GSM
You have an ITMn=SEAM labeln line in your run file which indicates you are using a controlling Z-item from a GSM. However,
your model file is a standard 3-D block model and not a GSM. To access a 3-D block model, use an ITMn=LEVEL labeln line.
4. ?M617V1: ERROR. No CODE item was entered.
You must enter an ITMn=CODE label15 label9 line in your run file. This command tells which File 15 item gets mapped to
which File 9 item.

MineSight

MineSight
Proprietary Software: Mintec, inc. M618V1 - CORRELATION ANALYSIS OF MODEL DATA
M618V1 CORRELATION ANALYSIS

OF MODEL DATA
M618V1 calculates simple bi-variate statistics and generates M618V1 is used to calculate simple statistics, histograms, and
scatter graphs and histograms of model data. scatter graph plots between data items in model files.
Both histograms and scatter graph generation are optional. The

user specifies the labels of the items for correlation analysis in a
PROGRAM FLOW DIAGRAM GET line. Minimum and maximum values for both items can
also be specified.
RUN FILE:
- Mine model area If IOP9 = 1, M618V1 will generate a plot file for a scatter graph
- Items to access complete with X and Y-axis labels and borders. This file is then
- Plot specifications plotted with a USERF in a run file to program M122.
INPUT: CALCS:
- PCF - Averages
- Mine Model File (File - Standard deviations
13, 14 or 15) - Correlation coefficient
- Histogram
- Scatter graph
OUTPUT:
- Optional Scatter Plot File

MineSight
M618V1 - CORRELATION ANALYSIS OF MODEL DATA Proprietary Software: Mintec, inc.

MineSight
Proprietary Software: Mintec, inc. M618V1 - CORRELATION STATISTICAL ANALYSIS OF MODEL DATA
M618V1 - CORRELATION STATISTICAL ANALYSIS OF MODEL DATA
RUN FILE OPERATION

MEDS-618V1 10=filename 15(or 14 or 13)=filename 19=filename 3=filename

where

19 = the name of the OUTPUT FILE FOR SCATTER GRAPH (If IOP9=1)
IOP5 = FIRST COLUMN OF MODEL TO ACCESS (default=1)

IOP6 = LAST COLUMN OF MODEL TO ACCESS (default=NX)
IOP7 = FIRST ROW OF MODEL TO ACCESS (default=1)

IOP8 = LAST ROW OF MODEL TO ACCESS (default=NY)
IOP9 = 0 DO NOT GENERATE SCATTER PLOT COMMANDS

= 1 GENERATE SCATTER PLOT OUTPUT FILE (POINTS ARE MAPPED WITHIN A FINE GRID)
NOTE: If IOP9 = 1, plot commands are written to File 19 which must be specified on the Names Line.
IOP11 = NO. OF FREQUENCY INTERVALS FOR THE HISTOGRAM AND/OR SCATTER GRAPH (MULTIPLES OF
10; MAX=50, DEFAULT=30)
IOP12 = 0 PLOT LIMITS FOR THE AXES ALSO APPLIES TO DATA
= 1 PLOT LIMITS DO NOT APPLY TO DATA
IOP13 = N PEN NUMBER FOR SYMBOLS (default = 3)
IOP14 = N SYMBOL TYPE (default = 1)
PAR1 = MIN VALUE FOR ITEM#1 (Y-AXIS)

PAR2 = MAX VALUE FOR ITEM#1 (Y-AXIS)
PAR3 = MIN VALUE FOR ITEM#2 (X-AXIS)

PAR4 = MAX VALUE FOR ITEM#2 (X-AXIS)
PAR5 = SYMBOL SIZE (default = 0.05)

MineSight
M618V1 - CORRELATION STATISTICAL ANALYSIS OF MODEL DATA Proprietary Software: Mintec, inc.
Items to control the run
GETn = LIST OF ITEMS TO BE USED IN THE RUN (Maximum of 10 items)

For example : GET15 = T-CU MOLY ROCK
NOTE: The program expects first two GET items to be Y-AXIS and X-AXIS variables respectively.

ITMn = label-15 OMIT min-value max-value
ITMn = label-15 TABLE IOPm IOPn
END
4. BENCH REQUEST LINES (free-field format)
REF#1 REF#2
where
REF#1 = FIRST MINE MODEL BENCH (default = 1)

REF#2 = LAST MINE MODEL BENCH (default = Last bench initialized using M601V1)
All benches between REF#1 and REF#2 will be used. Several Request Lines may be entered sequentially to select particular benches,
seams, etc.

MineSight
Proprietary Software: Mintec, inc. M618V1 - CORRELATION STATISTICAL ANALYSIS OF MODEL DATA

MEDS-618V1 10=GEOS10.DAT 15=GEOS15.DAT 19=PLT618.A;
MEDS-618V1 3=RPT618.A
** BIVARIATE ANALYSIS OF AUI VS AUKDOC AUI VS AUK
USR = AA / 02-22-95 10:50:00
IOP9 = 1 / 0=NO PLOT, 1=SCATTER PLOT
IOP11 = 40 / NO. OF FREQ. INTERVALS FOR HISTOGRAM (DEFAULT=30)
IOP12 = 0 / 1=LIMITS DO NOT APPLY TO DATA
IOP13 = 5 / PEN TYPE (DEFAULT = 3)
IOP14 = 1 / SYMBOL TYPE (DEFAULT=1)
PAR1 = 0. 1. / MIN AND MAX VALUES FOR Y-AXIS
PAR3 = 0. 1. / MIN AND MAX VALUES FOR X-AXIS
PAR5 = .08 / SYMBOL SIZE (DEFAULT=0.05)
GET15 = AUI AUK
END
27 27

MineSight
M618V1 - CORRELATION STATISTICAL ANALYSIS OF MODEL DATA Proprietary Software: Mintec, inc.

MineSight
Proprietary Software: Mintec, inc. M619V1 - CUMULATIVE DISTRIBUTION ANALYSIS OF MODEL DATA
M619V1 - CUMULATIVE DISTRIBUTION

ANALYSIS OF MODEL DATA

M619V1 is used to create an M122 plot file of the cumulative M619V1 generates a cumulative probability plot. On such a
distribution versus grade from model data (cumulative plot, a normal distribution will plot as a straight line. Plot
probability plot). commands are generated for further processing by M122. Basic
statistics are output as well.
Data can be obtained from Files 15, 13 or 14.

Data can be limited by geology if desired and a log transform of
RUN FILE: the input data can be performed before a plot is generated.
- Data ranges
- Geology codes There is no limit to the number of samples, since the program
- Type of plot divides the data up into bins between specified limits. A
maximum of 5000 bins is allowed.
M619V1 only generates one plot per run.
To generate a 3 parameter lognormal distribution, set IOP19=1

and specify the constant value on PAR4.
INPUT: CALCS:
- PCF - Cumulative distribution
- File 13 probability vs. grade
OR - Statistics
File 14
OR
File 15
OUTPUT:
- M122 Plot File

MineSight
M619V1 - CUMULATIVE DISTRIBUTION ANALYSIS OF MODEL DATA Proprietary Software: Mintec, inc.

MineSight
M619V1 CUMULATIVE DISTRIBUTION ANALYSIS OF MODEL DATA
RUN FILE OPERATION


where

15 = the name of the MODEL FILE
19 = the name of the OUTPUT FILE FOR PROBABILITY PLOT

IOP6 = LAST MODEL COLUMN TO ACCESS (default=all)
IOP8 = LAST MODEL ROW TO ACCESS (default=all)
IOP9 = 0 OUTPUT EVERYTHING

= 1 OUTPUT ONLY CUMULATIVE PROBABILITY CURVE (used for future overlays)
IOP13 = PEN COLOR FOR THE HORIZONTAL LINES IN PLOT (default=2)

IOP14 = PEN COLOR FOR THE VERTICAL LINES IN PLOT (default=3)
IOP15 = SYMBOL COLOR (default=1)

IOP16 = SYMBOL TYPE (default=3)
PAR16 = SYMBOL SIZE (default=0.05)
IOP17 = LINE TYPE FOR HORIZONTAL LINES (default=0)

IOP18 = LINE TYPE FOR VERTICAL LINES (default=0)
NOTE: 0=solid; 1=dash; -1=none.
IOP19 = 0 UNTRANSFORMED DATA

= 1 LOG TRANSFORMED DATA

MineSight
PAR1 = MINIMUM GRADE FOR PLOT (default=0)

PAR2 = MAXIMUM GRADE FOR PLOT (no default)
PAR3 = BIN SIZE (default=(PAR2 - PAR1)/1000)
PAR4 = LOG CONSTANT (if IOP19=1)
NOTE: If IOP19=1, PAR1 and PAR2 should be in untransformed units; PAR3 should be transformed.
GETnn = label1 label2 ... labeln
where label1 is the model item and is required; label2 to labeln are the optional limiting items.
4. BENCH HEADER LINES (free field format)
Multiple bench header lines may be used to select a range of benches or a single bench.

MineSight

MEDS-619V1 10=msop10.dat 15=msop15.dat 19=plt619.paa;
MEDS-619V1 3=rpt619.la
** Cumulative Probability Plot of EQCU **
USR = abc /
IOP9 = 0/1 Output only cum prob curve
IOP13 = 4 / Pen# for horizontal lines (default=2)

IOP14 = 5 / Pen# for vertical lines (default=3)
IOP15 = 4 / Symbol color to use (default=1)
IOP16 = 1 / Symbol type to use (default=3)
IOP17 = 1 / Line type for horizontal (default=0,solid)
IOP19 = 0/1 0 / 0=Untransformed; 1=Log
PAR1 = 0. 10. 0.1 / min, max, bin size

PAR16 = 0.1 / Symbol size to use (default=0.05)
GET15 = EQCU ROCK
ITM1= ROCK RANGE 1. 1.

END
31 35

MineSight
SAMPLE M122 FILE

** CUMULATIVE PROBABILITY PLOT **
USR = ABC
MAP = -1 9 1 -1 12 1
END
PEN# 1
USERF PLT619.PAA
ENDOC
1. Common problems are associated with setting the parameter values for PAR1, PAR2 and PAR3. PAR2 must be set as a value.
If PAR3 is not set, it is computed by the program as PAR3=(PAR2 - PAR1)/1000).
2. The program computes the number of bins using the equation N=(PAR2-PAR1)/PAR3. If PAR3 is too small or PAR2 is too
large, this may result in a number that is not accepted by the program. The current limit for the number of bins is 5000.
3. If I-O is set to 2 or greater, the program will list all the values retrieved from the model in the report file.

trademark of Leica Geosystems AG. M620V1 - INVERSE DISTANCE WEIGHTING INTERPOLATION (Std. Version)
M620V1 INVERSE DISTANCE WEIGHTING INTERPOLATION

(Std. Version)

M620V1 uses the sorted composites in File 8 to interpolate The standard interpolation method used for initial extension of
(extend) values into the mine model using inverse distance grades and other values makes use of the principle of gradual
weighting to the nth power. Geological zones are honored during changes for calculating block values. This technique of gradual
interpolation. changes uses a weighting function calculated from the inverse
distance between each composite and the block midpoint.
The program works with sub-blocked models and is enabled
to perform individual calculations for each zone of the sub- M620V1 uses inverse distance weighting to calculate block
divided block. values. The equation to calculate the value of a block with this
method is given below
G= /D1n + V2/D2n + ... + Vk/Dkn

V1
1
/D1n + 1/D2n + ... + 1/Dkn
RUN FILE:
- Interpolation parameters where

- Search distances or
ranges G = estimated value of block
- Controlling and limiting
item labels
V = value of sample
D = distance of sample to center of block
n = power (or exponent ) of D (distance)
k = # of samples
INPUT: CALCS:
POLYGONAL VS INVERSE DISTANCE WEIGHTING
- PCF - Locate composites within (IDW)
- Mine model file (File 13, search window
14 or 15) - Match block/geology The weight assigned to each sample will be affected by the
- File 9 or File 8 or codes
MSTorque composite set - Apply limiting factors exponent used for the distance. More weight can be assigned to
- Geology codes - Determine nearest the nearest sample by increasing this exponent. The larger the
composites exponent, the more polygonal the estimate.
- Compute weights
- Calculate and store
grades
ANISOTROPIC SEARCH DISTANCES
M620-series programs assume that data is weighted the same

in all directions unless anisotropic search distances are entered
using the CMD=SEARCH line. In this case, the program will
OUTPUT: compute an adjusted distance based on the anisotropy ratios in
horizontal and vertical directions.

M620V1 - INVERSE DISTANCE WEIGHTING INTERPOLATION (Std. Version) trademark of Leica Geosystems AG.
COORDINATE PARAMETERS HANDLING OF BLOCKS
PAR1-3 control the primary coordinate selection of data from The default is to set uninterpolated blocks to PCF minimum for
File 9 (or File 8) composites, the ASCII composite file or the that item, however we may set the interpolated item(s) to 0.0,
MSTorque composite set. These parameters may come from or ignore them.
geostatistical analysis, preliminary interpolation runs or from
deposit experience.
The composites selected for the entire row are kept in program GEOLOGIC LIMITATIONS
memory while interpolating the blocks in that row.
You should have geologic codes in the model and composite
STORAGE OF INTERPOLATED VALUES data to limit values used in the calculations.
Interpolated values can be stored in three ways.

USE OF BOUNDARY FILE
1) Normally, interpolated values are stored back into the
model file. The Names Line contains a 15(or13or 14)=file- A digitized boundary of a production area (shot) or any special
name entry. area may be used to define the blocks that will be interpolated.
The boundary will be used to determine a minimum and
2) For testing, when data from the model file is needed, as maximum column to be interpolated in each row. The boundary
in BLOCK LIMIT or MATCH MODEL, the model file must be contained in its own file.
can be read but the values stored into an ASCII file. The
Names Line contains 15(or13or14)=filename and 20=file-
name entries.
3) ASCII output.

trademark of Leica Geosystems AG. M620V1-IDW INTERPOLATION (STD. VERSION)
M620V1INVERSE DISTANCE WEIGHTING INTERPOLATION (Standard)
RUN FILE OPERATION

MEDS-620V1 10=filename 15(or 14 or 13)=filename 9 (or 8)=filename;

MEDS-620V1 19=filename 3=filename 20=filename 31=filename
where

15 = the name of the MINE MODEL FILE OR 15=ASCII -OR-
8 = the name of the SORTED COMPOSITE FILE (obsoleted) - OR - CARD for ASCII input -OR- TORQ for input
from MSTorque
9 = the name of the COMPOSITE FILE (gets sorted on-the-fly)
19 = the name of the Input File with Composites (if 8=CARD is used) -OR- MSTorque info file (mstorq.inf) (if
8=TORQ is used)
20 = the name of the ASCII Output File (optional)
31 = the name of the ID WEIGHTS FILE (optional, see IOP11)
NOTE: If 9 = filename is specified on the names line, then composite data will be retrieved from this file
9. To request an ASCII input DO NOT enter 9 = on the names line and specify 8 = CARD. To
access the MSTorque database, use 8=TORQ and include an MSTorque info file (mstorq.inf). For
information about the MSTorque info file, please refer to the M600-Technical Section, Technical
Considerations for Interpolation.
IOP3 = BASIC SEARCH OPTION FOR COMPOSITES

= 0 2-D CIRCULAR SEARCH (Uses PAR4 after PAR1 & PAR2)
= 1 3-D SPHERICAL SEARCH (Uses PAR4 after PAR1, PAR2 & PAR3)
(Superceded by CMD=SEARCH)
IOP4 = MATCH BLOCK VS. COMPOSITE GEOLOGY

= 0 NO GEOLOGIC MATCHING
= 1 MATCH 1 ITEM AFTER A BLOCK IS SELECTED
= 2 MATCH 2 ITEMS AFTER A BLOCK IS SELECTED
= -1 MATCH 1 ITEM BEFORE A BLOCK IS SELECTED
= -2 MATCH 2 ITEMS BEFORE A BLOCK IS SELECTED
NOTE: Only selection by PAR7 is affected by before/after choice

M620V1-IDW INTERPOLATION (STD VERSION) trademark of Leica Geosystems AG.
IOP5 = MINIMUM GRADE CRITERION

= 0 OMIT MINIMUM GRADE CRITERION
= 1 USE PAR9 AS MINIMUM GRADE ON THE FIRST GRADE TO BE INTERPOLATED
NOTE: See the HOW TO DEBUG AN M620V1 RUN section.
IOP6 = 0 USE TRUE DISTANCES

= 1 USE ADJUSTED DISTANCES BASED ON ANISOTROPY
NOTE: This option is used with CMD = SEARCH ...
IOP7 = MINIMUM NUMBER OF COMPOSITES FOR INTERPOLATION
IOP11 = ROW NUMBER FOR EXTENDED OUTPUT FROM CALCULATION (debug)
NOTE: If File 31 is entered on the names line, setting IOP11>0 will output a file of ID Weight spikes (that can be
viewed in MineSight 3-D.
IOP13 = -1 READ PAIRS OF CROSS REFERENCE CODES TO ALIAS BLOCK CODES

= 0 STANDARD GEOLOGIC CODES
= n READ n CROSS REFERENCE CODES TO ALIAS BLOCK CODES AT 10 VALUES PER LINE
(see Section 4, following)
NOTE: If IOP13= 1-10, one cross reference line is read. If IOP13= 11-20, two cross reference lines are
read.
IOP14 = 0 ALIAS BOTH COMPOSITES AND MODEL CODES (default = 0)

= 1 ALIAS ONLY COMPOSITE CODES
= 2 ALIAS ONLY 3-D MODEL CODES
IOP16 = MAXIMUM NUMBER OF COMPOSITES TO INTERPOLATE A BLOCK

(default =25, max = 100)
IOP18 = 0 STORE LOCAL ERROR AS VARIANCE

= 1 STORE LOCAL ERROR AS STANDARD DEVIATION
IOP19 = MAXIMUM NUMBER OF COMPOSITES TO BE USED FROM ANY INDIVIDUAL HOLE

(default = 0; no limit)
IOP21 = 0 OMIT ALL CHECKS

= 1 CHECK SEQUENTIAL COMPOSITES FOR DUPLICATE X,Y,Z COORDINATES;
DUPLICATES ARE DELETED
NOTE: IOP21 is applicable to blasthole projects only.
IOP22 = # OF DECIMAL PLACES TO OUTPUT FOR INTERPOLATED VALUES IN FILE 20

(default=3; max=4)
IOP25 = 0 APPLY WEIGHTING FACTOR BEFORE TAKING POWER OF DISTANCE (default).

= 1 APPLY WEIGHTING FACTOR AFTER TAKING POWER OF DISTANCE.
IOP27 = OPTION TO STORE THE CLOSEST COMPOSITE GRADE VALUE (for polygonal method only)
= 0 STORE THE VALUE OF THE OUTLIER CUTOFF (PAR31) AS THE CLOSEST COMPOSITE GRADE
IF THE CLOSEST COMPOSITE IS GREATER THAN PAR31 IN VALUE AND IT IS AT A DISTANCE
GREATER THAN ABS(PAR32). OTHERWISE, STORE THE TRUE GRADE VALUE OF THE
CLOSEST COMPOSITE. (default=0).

= 1 STORE TRUE GRADE VALUE OF THE CLOSEST COMPOSITE INDEPENDENTLY OF PAR31 AND
ABS(PAR32) VALUES.
NOTE: IOP27 is valid if PAR31 (outlier cutoff) is used and PAR32 is negative.
IOP31 = 0 NO DYNAMIC UNFOLDING (default)

= 1 USE DYNAMIC UNFOLDING WITH EXISTING FMR FILE (requires CMD=FMR FILE
command line)
= 2 RUN FAST MARCHING, CREATE NEW FMR FILE AND USE DYNAMIC UNFOLDING
(requires CMD=FMR FILE, CMD=RSI FILE, and CMD=FMR PAR command lines).
= 3 RETRIEVE PARAMETERS FROM EXISTING FMR FILE, RE-CREATE FMR FILE AND USE
DYNAMIC UNFOLDING (requires CMD=FMR FILE command line).
PAR1 = X-SEARCH DISTANCE (no default, must enter a value)

PAR2 = Y-SEARCH DISTANCE (no default, must enter a value)
PAR3 = Z-SEARCH DISTANCE (default = .1)
NOTE: PAR3 not used for SCAN1-D or SCAN2-D.
PAR4 = MAXIMUM 3-D DISTANCE FROM BLOCK CENTROID TO ACCEPT DATA

(default=SQRT((PAR1)2 + (PAR2)2 + (PAR3)2))
PAR5 > 0 INVERSE POWER TO BE USED FOR COMPOSITE WEIGHTS

(Default=2; PAR5 must be greater than or equal to 0.1 )
= -1 USE AVERAGE OF COMPOSITES INSTEAD OF INVERSE DISTANCE WEIGHT
PAR6 = CONSTANT TO BE INCLUDED IN CALCULATION OF WEIGHTS BETWEEN BLOCK

MIDPOINTS & EACH SELECTED COMPOSITE AS WEIGHT = 1.0 / (DISTANCE + PAR6) ** PAR5
PAR7 = MAXIMUM DISTANCE TO CLOSEST POINT FOR INTERPOLATION (default = PAR4)
PAR8 = MAXIMUM DISTANCE TO THE CLOSEST COMPOSITE (default = PAR7)
NOTE: Use this parameter when the number of composites within the search equal IOP7. The difference
between PAR7 and PAR8 is that PAR7 is tested at all cases whereas PAR8 is tested only when the
number of composites within the search volume is equal to IOP7 (IOP7 is the minimum number
of composites to use).
PAR9 = MINIMUM GRADE VALUE (if IOP5=1)
PAR10 = MINIMUM DISTANCE FOR WEIGHTING (default = 0.01)
NOTE: If the distance from the composite to the block is less than the Min Distance, the Min Distance
value is used in the Inverse Distance Weight calculation.
PAR20 = OPTIONAL SEARCH DISTANCE FOR THE ELEVATION RANGE (DEFAULT = PAR3)
PAR31 = CUTOFF GRADE FOR CHANGING THE 3-D SEARCH DISTANCE

PAR32 = THE 3-D SEARCH DISTANCE AT THE SPECIFIED CUTOFF
PAR33 = LOW GRADE CUTOFF FOR CHANGING THE 3-D SEARCH DISTANCE
PAR34 = THE 3-D SEARCH DISTANCE AT THE SPECIFIED CUTOFF FOR LOW GRADES
CMD = SEARCH RY RX RZ ROTN DIPN DIPE

CMD = ELEV ZMID
CMD = BLOCK LIMIT CODES V1 V2 V3 ... Vn

ITMn = label-15 BLOCK LIMIT

CMD = ELEV IS label-08 label-15
CMD = CALC MINn value
CMD = INCL LOCPT FILE [filename]
CMD = label-08 FACTR
CMD = FMR FILE [filename.fmr] (required for IOP31 = 1 - 3)
CMD = RSI FILE [filename.rsi] (required for IOP31 = 2)
CMD = FRM PAR F1 F2 F3 F4 F5 [F6 F7 F8] (required for IOP31 = 2)
Types of Calculations:
CALC INVWT / Inverse Distance Squared method

CALC POLYG / Polygonal method - nearest neighbor
ALOG INVWT / use the natural logarithm of the composite
CALC ZCRD INVWT / (or POLYG) is used to interpolate the model Z coordinate
Additional Values which may be stored:
BLOCK CALC #COMP NCOM / number of composites used to interpolate each block
BLOCK CALC #COMP NDHO / number of drillholes used per block
BLOCK CALC RINGS DMIN / distance to the closest composite used
BLOCK CALC RINGS DAVG / average distance to the block
BLOCK CALC RINGS DMAX / distance to the farthest composite used
LOCAL ERROR / store local area
BLOCK DILN% / dilution/smoothing measure
Limit on Calculations:
There is a limit of 30 ITMs for calculations including CALC, BLOCK ERROR, FACTR and/or ALOG.
Including / Excluding Composite Items:
An alternative method of limiting composites, in an interpolation run would be to use the RANGE, OMIT, and TABLE options
for the composite item. For example if you are compositing GOLD you could limit only use GOLD item between 0.001 to 0.025.

There are several options and methods for running M620V1. The following table lists the primary options and the page on which
you may learn about the IOPs and PARs which control these options.
Sample 13,
Customizing Run Files 14, Page
Option Description File 8 15 Number
I Primary 3D search parameters defining a box around a block 1 X 620-8
II* Optional full 3D (ellipsoidal) coordinate search definition 2, 11, 12 X 620-9
III Optional interpolation parameters X X 620-10
IV Optional 3D search distance at specified cutoff 620-10
V SCAN 2D: 2D (X and Y) coordinate search X 620-11
VI SCAN 1D: Interpolating the seacms that branch 16 X 620-11
VII Search from mid-point of the bench - ZMID 8 X 620-11
VIII Handling of blocks that are not interpolated RUN = X 620-12
IX* Matching composite vs block geology codes 3, 5, 6, X X 620-12
10
X* Assigning and matching geology codes 4 X X 620-13
XI* Interpolate selected geology types 5, 10 X 620-13
XII* Using alias geology codes 10 X X 620-14
XIII* Relative elevation specification 7 X X 620-14
XIV* Use of special weighting factor 9 X 620-15
XV ITM lines for values to be computed & stored ALL X X 620-15
XVI To limit the number of composites used to interpolate a block 10, 11, X 620-16
12, 14
XVII To limit the number of composites from an individual hole 11 X 620-16
XVIII The selection of the composites used in interpolation 7, 9 X 620-16
XIX Input from an ASCII file 6, 12 620-16
XX Use of a boundary file X 620-17
XXI Option to override coordinate items X 620-18
XXII Option to override/enter controlling seam item X 620-18
XXIII* Dynamic Unfolding Option X 620-18
* Pre-requisited required. NOTE: The above options have major effects on interpolation and should be carefully considered.
Considerations
GSM Two dimensional, No PAR3, always use SCAN 2-D, SCAN 1-D is used for branching seams. Ellipsoidal search can be
used but only apply to 2-D plane. (see Sample Run Files 14-16)
Interpolating - PAR3 is small (e.g., 1)
Topography - No ellipsoidal search

- PAR7 may be very largel,
- Input data normally comes from an ASCII file
- For an example run file see Sample Run File #13

I. Primary 3-D search parameters defining a cube around a block:
1. The primary coordinate selection (in section)is usually based upon the range of ZTOE - PAR3 to ZTOE + PAR3, where
ZTOE is the toe elevation of the bench to be used.
If topographic or other 2-D data is to be interpolated, this selection is not used.
2. The secondary coordinate selection (in plan)is always based upon the range of
YMID - PAR2 to YMID + PAR2,
where YMID is the midpoint northing of the row to be used.
Eastings are in the range X1 - PAR1 to X2 + PAR1.
where: X1 and X2 are the beginning and ending columns.
Figure 1. Definition of Primary Coordinate Search Parameters (PAR1, PAR2, and PAR3)
PAR1 = X-SEARCH DISTANCE (no default, must enter a value)

PAR2 = Y-SEARCH DISTANCE (no default, must enter a value)
PAR3 = Z-SEARCH DISTANCE (default = .1)
NOTE: PAR3 not used for SCAN1-D or SCAN2-D.

(default=SQRT((PAR1)2 + (PAR2)2 + (PAR3)2))
All of the composites within this rectangular box are checked against the maximum 3-D search distance (PAR4). The composites
that are less than or equal to this distance from the center of the box are retained for further screening, such as geologic matching.
If there are more than IOP16 number of composites for a given block after all the tests, then the composites are sorted by increasing
distance. Only the closest IOP16 are retained for calculating the weights. Based on these weights, the grade of the block is computed
and stored.
IMPORTANT NOTE: To interpolate GSM or 2-D surface data, the coordinate selection must be based on X and Y coordinates
only. If this is the case, then use one of the following command lines in your run file, depending on which source is appropriate:
ITMn = CARD DATA INPUT SCAN2-D (ASCII Input Data) or

ITMn = FILE DATA INPUT SCAN2-D (Composite File 8)

II. Optional ellipsoidal coordinate search and anisotrophy definition:
Prerequisite: You must have defined your 3-D search parameters, PAR1-3, and they must define an area equal to or larger than the
ellipsoidal search pattern.
To add a search within the primary search explained above include the following command in your run file:

or
CMD = SEARCH GSLIB RY RX RZ ROT1 ROT2 ROT3
or
CMD = SEARCH COORD filename file RY RX RZ
where
SEARCH = Keyword for the program indicating an ellipsoidal search
The following parameters define the anisotrophy

RY = Search distance (range) in the new north (major-axis) direction
RX = Search distance (range) in the new east direction
RZ = Search distance (range) in the new up direction
ROTN = Rotation from the old north axis to the new north axis(clockwise is a positive rotation)
DIPN = Dip of the new north axis measured horizontally(negative dip is plunging down)
DIPE = Dip easterly from the new north axis
(the horizonal component of this vector is 90 degrees clockwise from the horizontal component of the new north
axis. The dip is measured as in DIPN)
GSLIB = Keyword to specify GSLIB rotation entry
ROT1 = Horizontal rotation of north axis
ROT2 = Rotation of the north axis from horizontal
ROT3 = Final rotation around the new north axis
COORD = Keyword to specify rotation with three points
filename = name of the ASCII file with coordinates of these points
file = Keyword following the filename
For a detailed description of rotation parameters, see the 600-series Technical Section.
Figures 2, 3, 4, and Sample Run File #2 show the relationships of the various parameters for ellipsoidal search.
Figure 2. Definition of ROTN, RY and RX used in Figure 3. Definition of DIPN, RY and RZ used in Figure 4. Definition of DIPE, RX and RZ in 3D
3D Ellipsoidal Coordinate Search. 3D Ellipsoidal Search. Ellipsoidal Search.

This search forms an ellipsoid around the center of the block based on the search ranges and angles used. The composites within
this ellipsoid are retained for calculations. The 3D distances (RX, RY, RZ) between the block center and the composites are adjusted
distances based on anisotropy ratios between the ranges. Therefore, if the full 3-D search is used, the value of the maximum 3-D
search distance (PAR4) must be the same as the major axis of the ellipsoid. This option may supersede the IOP3 setting. If this option
is used for the GSM mine model or File 13 interpolation, then the ellipsoidal search is applied in 2-D, (i.e. the vertical axis is ignored).
By default, search rotation angles presumed entered with respect to model coordinates. To specify rotation angles with respect to
project coordinates, add command:
CMD = SEARCH PROJECT
III. Optional interpolation parameters
PAR5 = INVERSE POWER TO BE USED FOR COMPOSITE WEIGHTS

(default=2; PAR5 must be greater than or equal to 0.1, )
ENTER PAR5=-1 TO USE THE AVERAGE (without weights) OF SELECTED COMPOSITES INSTEAD OF
IDW.
PAR6 = CONSTANT TO BE INCLUDED IN CALCULATION OF WEIGHTS BETWEEN

BLOCK MIDPOINTS & EACH SELECTED COMPOSITE AS
WEIGHT = 1.0 / (DISTANCE + PAR6) ** PAR5
PAR8 = MAXIMUM DISTANCE TO THE CLOSEST COMPOSITE (default = PAR7)
NOTE: Use this parameter when the number of composites within the search equal IOP7. The difference
between PAR7 and PAR8 is that PAR7 is tested at all cases whereas PAR8 is tested only when
the number of composites within the search volume is equal to IOP7 (IOP7 is minimum number
of composites to use.).
PAR9 = MINIMUM GRADE VALUE (If IOP5=1)
IV. Optional 3-D search distance at a specified cutoff
Maximum 3-D search distance can be changed for the assays that are greater than a specified cutoff. For this, add the following lines
in your run file:

NOTE: 1) PAR31 and PAR32 apply to the items in the primary (first) calculation only.
2) For composites greater than PAR31 in value, the maximum 3-D search distance will be
ABS(PAR32), instead of regular PAR4. If PAR32 < 0, the grades above cutoff at distances
greater than ABS(PAR32) will be truncated to PAR31. Use IOP27 to store the true grade value
if the closest composite happens to be an outlier.
Similarly, maximum 3-D search distances can be changed for the assays that are less than a specified
cutoff. For this, add the following lines in your run file:

NOTE: 1) For composites < PAR33 in value, the maximum 3-D search distance will be PAR34, instead of PAR4.
2) PAR 33 & PAR34 apply to the items in the primary (first) calculation only.
GREATER THAN ABS(PAR32). OTHERWISE, STORE THE TRUE GRADE OF THE CLOSEST
COMPOSITE (default=0).
= 1 STORE THE TRUE GRADE VALUE OF THE CLOSEST COMPOSITE INDEPENDENTLY OF PAR31
AND ABS(PAR32) VALUES.
NOTE: IOP27is valid if PAR31 (outlier cutoff) is used and PAR32 is negative.
V. GSM and 2-D search:
To interpolate GSM or 2-D surface data, the coordinate selection must be based on X and Y coordinates only without regard to any
bench elevations. If this is the case, then use one of the following commands in your run file depending on which source is appropriate.
ITMn = CARD DATA INPUT SCAN2-D (ASCII input data) or

where
CARD DATA INPUT = Keywords for the program indicating that input is from an ASCII file
FILE DATA INPUT = Keywords for the program indicating that input is from File 8
SCAN2-D = Keyword for the program indicating a 2-D coordinate search
Sample Run File #13 demonstrates the use of this option.
VI. SCAN1-D: Interpolating the seams that branch
When interpolating into the GSM, there may be seams that branch and need to be modeled separately. Use the following command:
ITMn = FILE DATA INPUT SCAN1-D

where
SCAN1-D = Keyword for the program indicating a SCAN1-D search
NOTE: Replace keyword FILE with CARD if input is from an ASCII file. See Input from an ASCII File section for
more information.
The SCAN1-D option allows you to define which codes will be used by allowing up to four additional (alias) codes to be read on
the Area Specification Lines.
VII. Search from mid-point of the bench
Normally, when bench composites are calculated with M501V1, the elevations that are stored for the bench are toe elevations. For
fixed length composites, the midpoint of the composite will not be the midpoint of the bench, the midpoint of the composite must be
stored in a file variable called (ELEV. ). If you have fixed length composites, specify the following interpolation option to correctly
search for the composite elevation.
NOTE: In programs M500V1, M501V1, the midpoint is stored using ITMn= ZMID ELEV. ,whereas the interpolation routines
M620V1, M621V1, M624V1, M625V1, use the following syntax.

CMD = ELEV ZMID (Please note the order and the period placement are significant. In the M501 runfile use
ELEV. with a period and in M620V1 runfile use ELEV without a period.)
where
ELEV ZMID = Keywords for the program indicating the need to search from the mid-point of the bench
NOTE: If you interpolate from the composites stored at mid-bench, use the ZMID command. If you stored the end points of theinterval
when bench compositing with M501V1, then the default items are EAST, NORTH, and ELEV.
VIII. Handling of blocks that are not interpolated:

The disposition of blocks is controlled by using one of the following commands:
RUN = RESET Reset un-interpolated blocks to missing

RUN = ZERO Reset un-interpolated blocks to 0.0
RUN = OMIT Leave un-interpolated blocks as they are (default)
The RUN=RESET or RUN=ZERO commands should be used for the new interpolation results to supersede the existing values.
The RUN=OMIT command should be used when doing multiple program runs (e.g. if you interpolate different geologic zones
with corresponding interpolation parameters). RUN=RESET will reset all blocks in an interpolation run regardless of model
codes.
IX. Matching composite vs block geology codes
Prerequisite: You must have loaded geologic composites to both the composite and block model file. (and its precision must be 1)
Geologic matching can be done only if the pertinent geologic codes or rock types are stored in both File 8 and File 15. For a single
geologic match, include the following lines in your run file:
IOP4 = 1
ITMn = label-15 label-08 MATCH MODEL / 1st geology item
where
Label-15 = Label of model item for geologic codes

label-08 = Label of composite item for geologic codes
MATCH MODEL = Keywords for the program indicating geologic matching
For geologic matching of two different items in File 8 and File 15, include the following lines in your run file:
IOP4 = 2
ITMn = label1-15 label1-08 MATCH MODEL / 1st geology item
ITMn = label2-15 label2-08 MATCH MODEL / 2nd geology item
where
label1-15 = Label of 1st model item for geology codes

label1-08 = Label of 1st composite item for geology codes
label2-15 = Label of 2nd model item for geology codes
label2-08 = Label of 2nd composite item for geology codes
NOTE: You can MATCH on codes with values up to 999999. MATCHing and aliasing will work for 0
block codes and you can alias a 0 code to some other value. A maximum of 5 geologic matchings
is allowed.

X. Assigning and matching geology codes
Prerequisite: You must have loaded geologic codes to File 8 (and its precision must be 1).
If the geology codes are stored in File 8, but not in File 15, it is possible to assign model geology and match geologic codes during
the interpolation run using polygonal assignment of composite geology. To do this, include the following lines in your run file:
IOP4 = 1
ITMn = label-15 label-08 MATCH POLYG
where
label-15 = Label of model item for geology codes

label-08 = Label of composite item for geology codes
MATCH POLYG = Keywords for the program indicating polygonal geology assignment and matching
NOTE: The precision of the geology item in both the composite and model file must be 1.
During the interpolation, the program will assign a code to each block based on the geology code of the nearest composite. It will
then proceed with the standard matching of composite and model geology codes.
This option can only be used with BLOCK LIMIT when different model items are used for each option.
XI. Interpolate selected geology types
Prerequisite: You must have loaded geologic codes, and the precision of the geology item is 1.
Interpolation can be limited to certain mine model blocks based on geology codes or rock types. To do this, use the following lines
in your run file:

where
BLOCK LIMIT CODES = Keywords for the program indicating the option for block limiting
V1, V2 ... Vn = Integer codes from 1 to 9999999999 (10 digits) can be used for block limiting.
More than one code line may be entered if needed.
label-15 = Label of model item with geology codes
BLOCK LIMIT = Keywords for the program indicating the option for block limiting
For limiting on two different items in File 15, include the following lines in your run file.
ITM# = label-15 BLOCK LIMIT 1st block limit

ITM# = label-15 BLOCK LIMIT 2nd block limit
CMD = BLOCK LIMIT label-15 V1 V2 V3 . . .Vn 1st block limit
CMD = BLOCK LIMIT label-15 V1 V2 V3 . . .Vn 2nd block limit
A maximum of five items can be used for geologic limiting per run.

XII. Using alias geology codes
Prerequisite: You must have loaded geologic composites to both the composite and block model file. Precision must be 1.
Use this option to interpolate some blocks with certain geologic codes using composites that have different geologic codes. This option
allows you to assign alias (assumed) geology codes to the blocks to be interpolated so that they can be treated under the assumed
code. Suppose you have blocks coded 1, 2, 3 and 4, and composites coded 1 or 2. To interpolate code 1 and 3 blocks with code 1
composites and code 2 and 4 blocks with code 2 composites, use the alias option. First, include BLOCK LIMITing and MATCHing
options in your run file. On the first geology item (the 1st MATCH MODEL) set the following options:
IOP14 = 0 to alias both composite and model codes

and
IOP13 = n
where n is the maximum numeric value of the 1st geology item. Next enter another line following the END line in your run file
specifying the cross reference codes (n). A maximum of 10 cross reference codes per line is allowed. If IOP13=1 through 10, one
cross reference line is read. If IOP13=11 through 20, two cross reference lines are read.
For the above example, set IOP13=4 and put 1 2 1 2 after the END line in your run file. The 1 2 1 2 indicates that composites with
code 1 are used to interpolate the blocks with codes 1 and 3, and composites with code 2 are used to interpolate the blocks with
codes 2 and 4.
There is an alternate format (IOP13=1) to input alias codes after the END line using actual, alias pairs. This is useful when you
wish to alias only a few, widely separated codes, for example, to interpolate blocks coded 6 and 12 with composites coded 1, include
this line 6, 112, 1 after the END line. If you use this option, a line containing 0, 0 must be included after the last actual, alias pair.
See Section 4, Cross Reference Lines, for format.
XIII. Relative coordinates specification
Enter the following commands in your run file if the relative coordinates are to be used during the interpolation:

CMD = RELX IS label-08 label-15
CMD = RELY IS label-08 label-15
ELEV (RELX, RELY) IS = Keywords for the program indicating to use the relative coordinates
label-08 = Labels of relative coordinate items in File 8

NOTE: This option can be used for 3-D models. The option cannot be used when usingASCII input data. The
program will first test PAR1, PAR2, and PAR3 against the differences between true (original) composite and
block Northing, Easting and Elevations. Select PARs 1, 2, and 3 in such a manner so that the difference in
the original coordinates of a compsite and a block guarantees the desired difference between the composite
relative coordinate and the relative coordinate value of a block.
Further search limitation (as PAR4) will be used against the relative composite and block coordinates.
PAR20 = Optional search distance for the elevation range (Default = PAR3)
NOTE: PAR3 is still applied to the original elevations (both for composites and blocks). Program applies PAR20
to the relative elevations.

XIV. Use of special weighting factor
Enter the following command to weight the composites by a special weighting factor:
ITMn = label-08 FACTR

where
label-08= Label of the composite item to be used for weighting
FACTR= Keyword for the program indicating the special weighting factor option
If this option is used and PAR5 > 0, the program will divide the distance to the composite by the corresponding value of the weighting
item for that composite before computing the inverse distance weights. If PAR5 = -1, the program will use the value of the weighting
item as a weight.
NOTE: This option cannot be used if CARD input is used. The values of the weighting item cannot be zero or
undefined.
XV. ITM/CMD lines for values to be computed, stored, and the method of interpolation:
ITMn = label-15 label-08 CALC INVWT / IDW method

ITMn = label-15 label-08 CALC POLYG / Polygonal method - nearest neighbor
ITMn = label-15 label-08 ALOG INVWT / Use the natural logarithm of the composite
ITMn = label-15 CALC ZCRD INVWT / Interpolate model Z coordinate
ITMn = label-15 LOCAL ERROR 1 / The type of error is defined by IOP18
ITMn = label-15 BLOCK CALC #COMP NCOM / Stores the number of composites used to interpolate each block
ITMn = label-15 BLOCK CALC #COMP NDHO / Stores the number of drillholes used per block
ITMn = label-15 BLOCK CALC RINGS DMIN / Stores the distance to the closest composite for each block
ITMn = label-15 BLOCK CALC RINGS DAVG / Stores the average distance to the block
ITMn = label-15 BLOCK CALC RINGS DMAX / Stores the distance to the farthest composite for each block
CMD = Block DIL% label-15 cutoff
NOTE: 1) At least one ITMn to CALC INVWT or to CALC POLYG must be included in each run. The BLOCK
CALC #COMP [keyword] and BLOCK CALC RINGS [keyword] commands are optional.
2) When interpolating ZTOP or ZBOT for inclined GSM model, use:
ITMn = label-15 CALC ZCRD INVWT

or
ITMn = label-15 CALC ZCRD POLYG
Either command counts as the required one.
3) Only one command ITMn = label-15 CALC ZCRD is allowed. Any item that will be stored in the
model as a Model Z-coordinate value should be interpolated using the CALC ZCRD command. Only
one CALC ZCRD can be used per run, because it interpolates the actual model Z-coordinate values of
composites.
4) Storing dilution/smoothing measure

where

Block and DIL% are keywords

Label-15 is the item to store the dilution. The item values will be between 0 and 100. If this item
is not specified, then no calculation is done.
Cutoff is the value that the dilution or smoothing measure calculation is based on. If the cutoff
is zero, then the calculation is done using all the composites for the block without applying a
cutoff. The result is then a measure of how well the nearby composites match to the calculated
block value.
The dilution% is equal to ((SWTDIF/BLKGRADE) * 100)/SQRT(N),

where
SWTDIF = sum of weighted absolute differences between the block grade and the composites
used that are below the block grade when the block grade is above the cutoff and N = total number
of composites used to calculate the block estimate.
XVI. To limit the number of composites used to interpolate a block
The minimum and maximum number of composites used to interpolate a block can be specified in the run file using IOP7 and IOP16.
For example, to interpolate a block with a minimum of four composites to a maximum of 18 composites, use the following lines in
your run file:
IOP7 = 4
IOP16 = 18
NOTE: IOP7 and PAR8 have a correlation in that when the number of composites within the search distance is
exactly IOP7, then PAR8 is tested.
XVII. To limit the number of composites from an individual hole
The number of composites used to interpolate a block from an individual hole can be limited with IOP19. For example, to use no
more than three composites from an individual hole, set IOP19=3 in your run file. If IOP19=0 (default), there is no limitation on the
number of composites used from an individual hole.
NOTE: The use of IOP19 will increase the computing time for interpolation.
XVIII. The selection of the composites used in interpolation
Composites used in interpolation can be selected using RANGE, OMIT or TABLE with the ITM command. See ITM commands in
the Introduction, Vol. I, for an explanation of these options.
Sample Run File #9 and #17 demonstrates the use of these options.
XIX. Input from an ASCII file
The composite assay data input to the interpolation programs is normally from MineSight Data File 9 (or 8). However, the programs
are also designed to read data from an ASCII file. To use an ASCII input file, follow the steps below:
1. Include REF# (can be DHID), X, Y and Z coordinates (if 3-D interpolation), and a grade item on each line of input.
2. Include 8=CARD in the Names Line of your run file. Also include 19=filename if the data is in a separate file.
3. Also include the following lines in your run file:
INP8= REF# EAST NORTH ELEV. value1 ... geol1

where
REF#, EAST, NORTH, ELEV. = Keywords for the program (not necessarily in this order)
value1, value2, etc. = Grade items to be interpolated
geol1, etc. = Geology items to be interpolated

The format of the data in the ASCII file is free field format.
On the INP8 line, you must specify the column names for all the columns in the ASCII file (max allowed number of columns
is 99). To skip a column, enter DUMMY as a column header, or enter a name that is not used as an input item.
4. The following line is optional and can be included to specify a CALC items minimum value. Otherwise the minimum is
assumed to be zero.

where
CALC keyword which indicates that the corresponding field in the INP8 line will be calculated
MINn indicates which CALC item from the INP line is being set
value the minimum value.
For example:
INP8 = REF# EAST NORTH ELEV. TOTCU MOLY ROCK

CMD = CALC MIN2 0.001
will set the minimum value of MOLY(the second CALC item) to 0.001.
If composite data lines are included within the run file, only one Area Specification Line can be used.
XX. Use of a boundary file
The digitized boundary of an area may be used to define the blocks that will be interpolated. The boundary will be used to determine
a minimum and maximum column to be interpolated in each row. The boundary must be contained in its own file. This file is entered
using the following line in the run file:
NOTE: 1) Any block that has at least 1% of its area inside the boundary will receive interpolated values.
2) All files must have a single point of each line in Easting, Northing order.
3) This option is not available for rotated models.
There are three types of input for a boundary file, with the header line defining each type:
1) Boundary in VBM point file format has a numeric plane number in the header.
3000 1002
13510.20 12006.20
13384.50 11820.40
. .
13510.20 12006.20
0.00 0.00
2) Boundary in Survey file format with BNCH in the header. Keyword SBND is for Survey.
BNCH 3000 SHOT#909

SBND 1 13510.20 12006.20
SBND 2 13384.50 11820.40
. . . .
SBND 71 13510.20 12006.20

3) Boundary in M122IGP overlay format with IDENT in the header. Keyword POINT is for IGP.
IDENT 0 1 3000.0
POINT 1 13510.2 12006.2 3
POINT 1 13384.5 11820.4 2
. . .
POINT 1 13510.2 12006.2 2
POINT -1 0.0 0.0 0
NOTE: Easting values start at column 13 or greater.
END This end card must come at the end of any RUN OPTIONS selected from this section.
XXI. Option to override coordinate items
By default, coordinate items in a composite file are EAST, NORTH, and ELEV (Note the dot of the elevation item label.)
To override any of those item (e.g., use XBOT, YBOT, ZBOT) use the following commands:
For easting:
CMD = XCRD label-08
For northing:
CMD = YCRD label-08
For elevation:
CMD = ZCRD label-08
NOTE: The last command is required when SCAN2-D option is used with inclined models.
XXII. Option to override/enter controlling seam item.
By default, seam numbers are read from the controlling Z item specified in the PCF.
When using MSTorque composites, you have to specify the attribute that was used as seams. In MSTorque the seam attribute has
Enumerated type; the code values of the attribute must match the seam numbers in the PCF.
The command:
CMD = SEAM label-08
will override the controlling seam item stored in the PCF, and use label-08 as teh item with seam numbers.
XXIII. Dynamic Unfolding Option
Prerequisite: You must have an RSI object file available in the \_msresources folder
Dynamic Unfolding is an on the fly calculation of two distances between composites and model blocks: normal to a specific
surface and a geodesic distance (shortest distance) along the surface. These distances are used in place of Euclidean distances
in IDW and Kriging calculations. You may want to use Dynamic Unfolding if the grade intensely follows a known surface. The
RSI object corresponding to one surface or a pair of surfaces must be created in MS3D beforehand.
A Fast Marching Result (FMR) file can be prepared in MS3D beforehand as well. You can also generate an FMR file from a RSI
file using specified parameters.

There are several options how to use dynamic unfolding:
IOP31 = 1 USE DYNAMIC UNFOLDING WITH EXISTING FMR FILE

This option requires the following command line:
CMD = FMR FILE [filename.fmr]

where filename.fmr is prepared beforehand.
IOP31 = 2 RUN FAST MARCHING, CREATE NEW FMR FILE AND USE DYNAMIC UNFOLDING
This option requires the following command lines:

where filename.fmr is a name of fmr file to be created and used to calculate unfolded distances.
CMD = RSI FILE [filename.rsi]

where filename.rsi is a name of existing RSI object files in _msresources folder in the project directory. If it is located in
a subfolder in \_msresources, then the subfolder name has to be included in the filename.rsi (e.g. myrsicollection\surf.
rsi).
CMD = FMR PAR F1 F2 F3 F4 F5 <F6 F7 F8>

where the following Parameters for Fast Marching have to be specified:
F1 and F2 - lower and upper limiting of composites by relative Z from the RSI file. If RSI file is generated from a
single surface, the Rel-Z is a signed distance to that surface. In case of two surfaces the Rel-Z values are between 0 and
1;
F3 - Fast Marching Grid size (it is recommended to make it greater then the max of DX,DY and DZ sizes for a block);
F4 - Fast Marching Grid Range (it has to be greater then the maximum 3-D search distance [PAR4]);
F5 - Size of Euclidean Region (Distances within the Euclidean Region are measured directly, without unfolding. The
size of the Euclidean region is expected to be multiple of the grid size. It will be automatically rounded by the program
to the nearest multiple of the grid size and set to be at least one grid.).
F6 = 0 - dont use Reference North (default) if F6 is not present or it is 0, then F7 and F8 are not used and not
required;
= 1 - use Reference North (this means that azimuths of geodesic directions are counted from the Reference North
direction defined by parameters F7 and F8. This direction should be almost tangent to the surface in all points. You need
geodesic azimuths and the Referecne North (F7 and F8) direction to use an anisotropic search and/or variograms with
any anisotropy along the surface.);
F7 - Azimuth of Reference North direction;
F8 - Dip of Reference North direction;
IOP31 = 3 RETRIEVE PARAMETERS FROM EXISTING FMR FILE, RE-CREATE FMR FILE AND USE DYNAMIC
UNFOLDING
where filename.fmr is the name of the fmr file where the parameters will be retrieved from, and is the file that will be
overwritten after re-running Fast Marching.
END This end card must come at the end of any options selected from this section.

1. CROSS REFERENCE LINES (for alias geology codes, if IOP13 0)
If IOP13>0, read 10 integer codes per line in free-field format, where the first line contains the alias codes for actual codes 110, the
second line contains the alias codes for actual codes 1120, etc.
For example, if IOP13=5 (block codes are 1 to 5) and if 1 1 3 3 3 are input for cross reference, then data with geologic codes 1 and
2 will be used as the same type and codes 3, 4 and 5 will be used together.
If IOP13 = 1, read up to 5 alias pairs per line in a free-field format as actual, aliasactual, alias . .; input is terminated by a 0, 0.
For example, if actual codes 98, 99, 108, and 109 will be used as code 1, actual code 0 will be used as code 5 and other actual codes
will be used as is, the entry could look like:
98, 1 99, 1 108, 1 109, 1

0, 5
0, 0
The 0, 5 pair could also be included in the first line to make 5 pairs. Do it whichever way is the clearest.
2. AREA SELECTION LINES
IX1 IX2IY1 IY2IZ1 IZ2 comp1 comp2 comp3 comp4 ColumnsRowsBenches
where comp1-n are optional composite codes for controlling split seam interpolation. See SCAN1-D and Sample Run File #16. The
run will end on an end-of-file condition. A blank line or a zero will default to the PCF limits and interpolate the entire block model.
3. COMPOSITE DATA LINES (If CARD DATA INPUT was specified)
If Composite Data Lines are included within the run file, then only one Area Specification Line can be used. If Composite Data Lines
are in a separate file, include a 19=filename in the Names Line.


* SAMPLE INVERSE DISTANCE INTERPOLATION *
USR = ABC
RUN = RESET
COM -
COM 3-D MODEL INTERPOLATION COM
COM * * TEST RUN #1: M620V1
COM 3-D SPHERICAL SEARCH WITHIN RECTANGULAR BOX
IOP3 = 1 / 0=2D CIRCULAR; 1=3D SPHERICAL SEARCH

IOP11 = 25 / ROW# FOR DEBUG
IOP16 = 5 / MAX # COMPS FOR INTERP A BLOCK
PAR1 = 750 750 50 / X, Y, Z SEARCH DISTANCES

PAR4 = 750 / LIMITING SEARCH DISTANCE
PAR5 = 2.0 / INVERSE POWER
ITM1 = TCU-1 T-CU CALC INVWT
END
30 30 25 25 20 20 AREA SELECTION LINE


* SAMPLE INVERSE DISTANCE INTERPOLATION, ELLIPSOIDAL SEARCH *
USR = ABC
RUN = RESET
COM -
COM 3-D MODEL INTERPOLATION
COM -
COM ELLIPSOIDAL SEARCH AT N45E DIRECTION

IOP16 = 5 / MAX # OF COMPS FOR INTERP A BLOCK

CMD = SEARCH 750 500 375 45 0 0
END


MEDS-620V1 3=RPT620.LC
* SAMPLE INVERSE DISTANCE INTERPOLATION , MATCH MODEL *
USR = ABC
RUN = RESET
COM -
COM -
COM MATCHING COMPOSITE VS BLOCK GEOLOGY CODES

IOP4 = 1 / 1=ONE GEOLOGIC MATCHING, 0=NONE


ITM2 = GEOL ROCK MATCH MODEL
END


MEDS-620V1 3=RPT620.LD
* SAMPLE INVERSE DISTANCE INTERPOLATION MATCH POLYG. *
USR = ABC
RUN = RESET
COM -
COM -
COM ASSIGN AND MATCH GEOLOGY CODES

COM EXCLUDE SOME COMPOSITES BASED ON DH REF#



ITM2 = GEOL ROCK MATCH POLYG
ITM3 = REF# OMIT 16 21
END


MEDS-620V1 3=RPT620.LE
* SAMPLE INVERSE DISTANCE INTERPOLATION, BLOCK LIMIT *
USR = ABC
RUN = RESET
COM -
COM -
COM INTERPOLATE SELECTED GEOLOGY TYPES

COM MATCH COMPOSITE VS BLOCK GEOLOGY CODES


CMD = BLOCK LIMIT CODES 2 4

ITM2 = GEOL BLOCK LIMIT
END

MEDS-620V1 10=SAMP10.DAT 15=SAMP15.DAT 8=CARD;

MEDS-620V1 3=RPT620.LF
* SAMPLE INVERSE DISTANCE INTERPOLATION, ASCII, MATCH MODEL *
USR = ABC
RUN = RESET
COM -
COM -
COM ASCII DATA INPUT




ITM2 = MO-1 MOLY CALC INVWT
ITM4 = CARD DATA INPUT SCAN3-D
INP8 = REF# EAST NORTH ELEV. T-CU MOLY ROCK

ALF1 = REF# COORD COORD COORD CALC CALC MATCH
FMT1 = (F4.0, 7X, 3F8.0, 2F7.3, F3.0)
END
30 DH-43 12652. 12851. 3600. 0.058 0.003 2 COMPOSITE DATA LINES
31 DH-47 12720. 12752. 3500. 0.066 0.004 3
32 DH-56 12736. 12430. 3650. 0.052 0.003 2
33 DH-60 12705. 12509. 3600. 0.251 0.010 4
34 DH-62 12719. 12603. 3600. 0.126 0.005 3
35 DH-63 12725. 12550. 3650. 0.402 0.009 1


MEDS-620V1 3=RPT620.LG
* SAMPLE INVERSE DISTANCE INTERPOLATION, REL XXX *
USR = ABC
RUN = RESET
COM
COM -
COM USE RELATIVE ELEVATION


CMD = ELEV IS DHTOE DIST

ITM2 = T-CU RANGE .35 .50
END


MEDS-620V1 3=RPT620.LH
* SAMPLE INVERSE DISTANCE INTERPOLATION , ZMID *
USR = ABC
RUN = RESET
COM
COM
COM SEARCH COMPOSITES FROM BENCH MID-POINT

IOP11 = 25 / ROW # FOR DEBUG

CMD = ELEV ZMID

END


MEDS-620V1 3=RPT620.LI
* SAMPLE INVERSE DISTANCE INTERPOLATION , FACTR, COMPOSITES *
USR = ABC
RUN = RESET
COM
COM
COM USE SP.GR AS A SPECIAL WEIGHTING FACTOR

COM USE COMPOSITES WITH ROCK TYPE 2 ONLY

IOP7 = 4 / MIN # COMPS TO INTERP A BLOCK

PAR7 = 600 / MAX DIST TO CLOSEST PT
PAR8 = 250 / MAX DIST TO PROJECT SINGLE COMP VALUE
CMD = SP.GR FACTR

ITM2 = ROCK RANGE 2 2
END


MEDS-620V1 3=RPT620.LJ
* SAMPLE INVERSE DISTANCE INTERPOLATION, ALIAS, MATCH *
USR = ABC
RUN = RESET
COM
COM
COM INTERPOLATE BLOCKS WITH SPECIFIED CODES

COM USE ASSIGNED (ALIAS) COMPOSITE CODES

IOP7 = 1 / MIN # COMPS TO INTERP A BLOCK
IOP13 = 4 / # OF BLOCK GEOL CODES

PAR7 = 600 / MAX DIST TO CLOSEST PT
PAR8 = 250 / MAX DIST TO PROJECT SINGLE COMP VALUE
CMD = BLOCK LIMIT CODES 1 2 3 4

ITM2 = GEOL BLOCK LIMIT
END
1 2 1 2 CROSS REFERENCE LINES


MEDS-620V1 3=RPT620.LL
* SAMPLE INVERSE DISTANCE INTERPOLATION , ASCII*
USR = ABC
RUN = RESET
COM
COM
COM USE ELLIPSOIDAL SEARCH



COM * ELLIPSOIDAL SEARCH (MAJOR AXIS W-E)

CMD = SEARCH 100 50 50 90 0 0

INP8 = REF# EAST NORTH ELEV. T-CU

CMD = CALC MIN1 0.01 / to set the minimum value of T-CU to 0.01
END
30 DH-43 13350. 12450. 3600. 0.058
32 DH-56 13150. 12450. 3600. 0.092
34 DH-62 13250. 12500. 3600. 0.126 COMPOSITE DATA LINES
35 DH-63 13250. 12400. 3600. 0.402
36 DH-65 13250. 12501. 3600. 0.312


MEDS-620V1 3=RPT620.LM
* SAMPLE INVERSE DISTANCE INTERPOLATION , LIMIT XXX*
USR = ABC
RUN = RESET
COM
COM
COM USE ELLIPSOIDAL SEARCH



COM* ELLIPSOIDAL SEARCH

COM* (MAJOR AXIS SW-NE, PLUNGING 35 DEGS @ N45E)
COM* (MINOR AXIS NW-SE, DIPPING 35 DEGS @ S45E)
COM* (HORIZONTAL ANISOTROPY RATIO = 2:1)
COM* (VERTICAL ANISOTROPY RATIO = 3:1)
CMD = SEARCH 180 90 60 45 -35 -35

END
30 DH-43 13350. 12550. 3500. 0.058
32 DH-56 13150. 12350. 3700. 0.092
34 DH-62 13200. 12500. 3650. 0.126
35 DH-63 13300. 12400. 3550. 0.402
36 DH-65 13350. 12550. 3700. 0.312
39 DH-61 13300. 12400. 3650. 0.201


MEDS-620V1 3=RPT620.LN 19=DAT620.IB
* SAMPLE INVERSE DISTANCE INTERPOLATION , 2D*
COM
COM
USR = ABC
RUN = RESET

IOP4 = 0 / 0=NO GEOLOGIC MATCHING, 1=MATCH 1 ITEM
IOP7 = 1 / MIN # OF COMPS FOR INTERPOLATION
IOP16 = 16 / MAX # COMPS TO INTERPOLATE A BLOCK
PAR1 = 1500. 1500. 1. / X, Y, Z SEARCH DISTANCES

PAR4 = 1500. / LIMITING SEARCH DISTANCE
PAR6 = 200 / CONSTANT IN WEIGHT CALC
PAR7 = 1250 / MAX DIST TO CLOSEST POINT
ITM01 = BDROCK TOPO CALC INVWT / 1ST VALUE

INP8 = REF# NORTH EAST TOPO
I-O = 1
END
1 50 1 50 1 1

COAL-620V1 10=COAL10.DAT 15=COAL15.DAT 8=COAL08.DAT;

COAL-620V1 3=RPT620.LA
* INVERSE DISTANCE INTERPOLATION OF SAMPLE PROJECT MODEL *
USR = ABC
RUN = RESET
COM
COM GSM MODEL INTERPOLATION
COM 197
DOC ** INTERPOLATE ALL SEAMS FOR TOP, BOT, THK

IOP4 = 0 / 0=NO GEOLOGIC MATCHING
IOP16 = 25 / MAX # COMPS TO INTERP A BLOCK
PAR1 = 5000 5000 0.1 / X, Y, Z SEARCH DIST

PAR6 = 0.0 / CONSTANT IN WEIGHT CALC
ITM1 = THICK LNGTH CALC INVWT

ITM2 = ZTOP ZTOP CALC INVWT
ITM3 = ZBOT ZBOT CALC INVWT
ITM4 = DIST BLOCK CALC RINGS DMIN
END
1 72 1 96 1 3

COAL-620V1 10=COAL10.DAT 15=COAL15.DAT 8=COAL08.DAT;

COAL-620V1 3=RPT620.LB
USR = ABC
RUN = RESET
COM
COM
DOC ** INTERPOLATE QUALITY FOR ALL SEAMS


ITM1 = MOIST MOIST CALC INVWT

ITM2 = ASH ASH CALC INVWT
ITM3 = SULF SULF CALC INVWT
ITM4 = BTU BTU CALC INVWT
END
1 72 1 96 1 3

COAL-620V1 10=COAL10.DAT 15=COAL15.DAT 8=CARD;

COAL-620V1 3=RPT620.LC
USR = ABC
RUN = RESET
COM
COM
DOC ** INTERPOLATE BTU FOR SEAM# 1

COM ** USE SCAN1-D OPTION

IOP11 = 30 / ROW # FOR DEBUG OUTPUT
PAR1 = 5000 5000 .5 / X, Y, Z SEARCH DIST

ITM1 = BTU BTU CALC INVWT

INP8 = REF# EAST NORTH SEAM BTU
I-O = 2 / 2=LIST COMPOSITES
COM NOTE:
COM SEAM# 1 HAS COMPOSITE CODE 10. THIS SEAM
COM BRANCHES INTO 4 PIECES WHOSE COMPOSITE
COM CODES ARE 11, 12, 13 AND 14. THESE BRANCHES
COM ARE INTERPOLATED TOGETHER WITH THE MAIN SEAM.
END
41 41 30 30 1 1 11 12 13 14
30 DH-43 13350. 12350. 10. 9058.
32 DH-56 13150. 12450. 11. 9092.
34 DH-62 13250. 12505. 12. 9126.
35 DH-63 13050. 12400. 13. 9402.
36 DH-65 13450. 12225. 14. 9312.

MSTorque access
MEDS-620V1 3=RPT620.L17
* SAMPLE INVERSE DISTANCE INTERPOLATION *
COM
COM
-COM * * TEST RUN #17: M620V1
COM COMPLEX RUN FILE
USR = ABC
RUN = RESET

IOP4 = 1 / 1=ONE GEOLOGIC MATCHING, 0=NO MATCHING
IOP31 = 3 5 6 8 10 12 15 16 / ACCEPTABLE DH REF#S
PAR1 = 750 750 50 / X, Y, Z SEARCH DIST

CMD = SEARCH 800 750 600 90 0 0

CMD = BLOCK LIMIT CODES 1

ITM2 = TCU-P T-CU CALC POLYG
ITM5 = CODE BLOCK LIMIT
ITM8 = EXTRA BLOCK CALC #COMP NCOM
ITM9 = LNGTH RANGE 5.0 50.0
ITM10 = SP.GR OMIT 2.5 5.0
ITM11 = REF# TABLE 31 38
END
33 33 25 25 20 20


MEDS-620V1 10=msop10.dat 8=TORQ 15=msop15.all 19=mstorq.inf;
MEDS-620V1 3=rpt620.idw 31=DUMMY
** 3-D model CUIDW interpolation - Inverse Distance Weighting
RUN = RESET
USR = / Thu Jun 2, 2011 9:51:59 AM US Mountain Standard Time
IOP3 = 1 / 1=3-D spherical search; 0=2-D search

IOP4 = 0 / 0=No geologic matching; 1=Match one item
IOP7 = 1 / Min # of comps for interp
IOP11= 0 / Row # for extended debug output
IOP16= 8 / Max.# of composites for interpolating a block
PAR1 = 200. / Primary X-search distance

PAR2 = 200. / Primary Y-search distance
PAR3 = 7.5 / Primary Z-search distance
PAR4 = 200. / Limiting search distance
ITM1 = CUIDW CU CALC INVWT
CMD = ELEV ZMID
I-O = 0 / Debug level

END
000000


1. The program will list all the composites within the search window of each interpolated row if I-O=2 is specified in the run
file. The program will also list all the items in the composite and model files, the total number of blocks interpolated for
each row, and other debug information. This option is not suggested when interpolating the entire model.
2. The program will print the location of composites, the distance to the block and composite grades and weights for each b
lock interpolated if IOP11 is set to the row# for debug output.
3. If ellipsoidal search is used, then the 3-D distance calculated between a composite and the block will be the adjusted
distance based on the anisotropy ratios. This is the distance that is printed on the output file when the debug option is on.
4. The difference between PAR7 and PAR8 is very subtle. PAR7 is tested at all times. PAR8 is tested only if the number of
composites to interpolate the block is equal to IOP7.
5. Default inverse power used by the program is 2 if you do not specify PAR5. The higher the inverse power, the more weight
is given to the nearest sample.
6. Be sure to select composite and model file item labels that are not used as keywords by the program to execute certain
commands.
7. If you are using more than one ITM command, number them sequentially, without repetition.
8 . Multiple Area Selection Lines are allowed. The program will interpolate the blocks specified in the first line, then it will
interpolate the blocks specified in the second line and so on. The only exception is when the ASCII input option is used and
the composite data follows the run file.
9. ** MSIPTS MAX POINTS EXCEEDED nn AT ROW yy
will appear if more than the max number of composites per row. The maximum number of composites that the program
can handle for a single row is 2000 for the basic MineSight and 16000 for the EMPC or workstation versions. If this
limit is exceeded, a segmentation process will automatically be invoked to interpolate 10 columns at a time across the row.
10. *** M620A1 # POINT EXCEED nnn AT BLOCK xxx yyy
will occur if more than the max number of composites are found in a search around one block. The maximum number of
composites that the program can handle for a single block is 2000 for the basic MineSight and 16000 for the EMPC
or workstation versions. If this number is exceeded, the program will give an error message and stop interpolating at that
block. If this happens, first check if you can decrease the X, Y or Z search distances used by the program. If you can,
then try again starting from the row where the program stopped and see if this will solve the problem. If it does not, try to
specify lesser columns to interpolate by using multiple Area Selection Lines.
11. If IOP5=1 (use the minimum grade criterion), then PAR9 must be specified. The minimum grade criterion is based on the
grade of the composite closest to the block being interpolated. If the grade of the closest composite is greater than PAR9,
then the program uses only the composites whose grades are greater than PAR9. If the grade of the closest composite is
less than PAR9, then the program uses only the composites whose grades are less than PAR9.
12. *** ERROR ON INTERPOLATION AREA CARD ***
will occur if the minimum column is greater than the maximum column, or the minimum row is greater than the
maximum row, or the minimum bench is greater than the maximum bench.
13. ** ITEM DEFINITION ERROR MSINL1 **

NO ITEMS HAVE BEEN SET UP TO BE STORED

will appear if you do not specify any ITM lines that will store data in the model file.
14. *** MSINL1 ERROR: PARx NOT ENTERED
will appear if PAR1 or 2 are not entered.
15. ** NO CALC ITEM WAS ENTERED **
will appear if you did not specify an ITMn=CALC INVWT or POLYG.
16. *** MSINLZ ERROR: MORE THAN 2 POLYG ITEMS
will appear if you specify more than two ITMn=CALC POLYG lines.
17. ** MSINLZ ERROR: MORE THAN 2 GEOL ITEMS
will appear if you specify more than two items for geology matching.
18. ** MSIPTS: ERROR IN CARD READING

NUMBER OF CARDS W/NO ERROR = xxx
NUMBER OF CARDS WITH ERROR = xxx
will appear if there are any errors when reading ASCII data.
19. ** M620V1: WARNING. YOU CAN ONLY CHECK FOR DUPLICATE POINTS ON BLASTHOLE
PROJECTS. IOP21 IS BEING RESET TO 0.
IOP21 is applicable to blasthole projects only. There is no need to check for duplicate composites on non-blasthole
projects. If you try to activate IOP21 for a non-blasthole project it will be reset to zero and the program will continue
normally.
20. Also check the MineSight error messages in the Appendix.

trademark of Leica Geosystems AG. M620V2 - IDW INTERPOLATION (Octant Version)
M620V2 INVERSE DISTANCE WEIGHTING INTERPOLATION

(Octant Version)
M620V2 uses a similar interpolation scheme to M620V1. The standard interpolation method used for initial extension of
However, it uses an octant selection scheme to limit the number grades and other values makes use of the principle of gradual
of composites for interpolation. The n closest composites in changes for calculating block values. This technique of gradual
each octant or quadrant around the block are used. changes uses a weighting function calculated from the inverse
distance between each composite and the block midpoint. You
The program works with sub-blocked models and is enabled should have geologic codes in the model and composite data to
to perform individual calculations for each zone of the sub- limit values used in the calculations.
divided block.
M620V2 uses inverse distance weighting to calculate block
values. The equation to calculate the value of a block with this
G= /d1n + v2/d2n + ... + vk/dkn
v1
RUN FILE:
1
/d1n + 1/d2n + ... + 1/dkn
- Interpolation parameters
- Search distances or
ranges where
item labels G = estimated value of block
v = value of sample
d = distance of sample to center of block
n = power (or exponent) of d
k = # of samples
INPUT: CALCS:
The weight assigned to each sample will be affected by the
- PCF - Locate composites within
- Mine model file (File 13, search window exponent used for the distance. More weight can be assigned to
14 or 15) - Determine octant the nearest sample by increasing this exponent. The larger the
- File 9 or File 8 or - Match block/geology exponent, the more polygonal the estimate.
MSTorque composite set codes
- Geology codes - Apply limiting factors
- Determine nearest
M620V2 has the option to limit the number of composites used
composites in interpolation. The limit is specified as a maximum number
- Compute weights of composites (IOP2) that can fall within an octant or quadrant
- Calculate & store grades search (IOP12).

OUTPUT:
compute an adjusted distance based on the anisotropy ratios in
- Updated Mine Model File horizontal and vertical directions.

M620V2 - IDW INTERPOLATION (Octant Version) trademark of Leica Geosystems AG.
COORDINATE PARAMETERS STORAGE OF INTERPOLATED VALUES
PAR1-3 control the primary coordinate selection of data from Interpolated values can be stored in three ways.
File 9 (or File 8) composites, the ASCII composite file or the
MSTorque composite set. These parameters may come from
1) Normally, interpolated values are stored back into the model
geostatistic analysis, preliminary interpolation runs or from
file. The Names Line contains a 15(or13or 14)=filename
deposit experience.
entry.
1. The primary coordinate selection is usually based upon the 2) For ore control purposes, because there is no model file, the
range of ZTOE - PAR3 to ZTOE + PAR3, where ZTOE values are output to an ASCII file (File 20). The Names Line
is the toe elevation of the bench to be used. contains 15=ASCII and 20=filename entries.
If topographic or other 2-D data is to be interpolated, then
this selection is not used. However, set PAR3 to be a small 3) For testing, when data from the model file is needed, as in
non-zero value (e.g., 0.1). BLOCK LIMIT or MATCH MODEL, the model file can be
read but the values stored into an ASCII file. The Names Line
contains 15(or13or14)=filename and 20=filename entries.
2. The secondary coordinate selection is always based upon the
range of YMID - PAR2 to YMID + PAR2, where YMID USE OF BOUNDARY FILE
is the midpoint northing of the row to be used. Eastings are
in the range XMIN - PAR1 to XMAX + PAR1. A digitized boundary of a production area (shot) or any special
area may be used to define the blocks that will be interpolated.
The composites selected for the entire row are kept in program The boundary will be used to determine a minimum and
memory while interpolating the blocks in that row. maximum column to be interpolated in each row. The boundary
must be contained in its own file.

trademark of Leica Geosystems AG. M620V2-IDW INTERPOLATION (OCTANT VERSION)
M620V2 - INVERSE DISTANCE WEIGHTING INTERPOLATION (Octant)
RUN FILE OPERATION

MEDS-620V2 10=filename 15(or 14 or 13)=filename 9(or 8)=filename;

MEDS-620V2 19=filename 3=filename 20=filename 31=Filename
where

from MSTorque
9 = the name of the COMPOSITE FILE
15 = the name of the MINE MODEL FILE OR 15 = ASCII - OR -
19 = the name of the INPUT FILE WITH COMPOSITES (if 8=CARD) -OR- MSTorque info file (mstorq.inf) (if
8=TORQ is used)
20 = the name of the ASCII OUTPUT FILE (optional)
31= the name of the ID WEIGHTS FILES (optional, see IOP11)
NOTE: If 9 = filename is specified on the names line, then composite data will be retrieved from this
file 9. To request an ASCII input DO NOT enter 9 = on the names line and specify 8=CARD.
To access the MSTorque database, use 8=TORQ and include an MSTorque info file (mstorq.
inf). For information about the MSTorque info file, please refer to the M600-Technical Section,
Technical Considerations for Interpolation.
IOP2 = MAXIMUM NUMBER OF COMPOSITES PER OCTANT OR QUADRANT

(see IOP12)

= 0 2-D CIRCULAR SEARCH (uses PAR4 after PAR1 & PAR2)
= 1 3-D SPHERICAL SEARCH (uses PAR4 after PAR1, PAR2 & PAR3)


M620V2-IDW INTERPOLATION (OCTANT VERSION) trademark of Leica Geosystems AG.
IOP5 = USE MINIMUM GRADE CRITERION

NOTE: See the How to Debug section.
IOP8 = 0 SIMPLE DISTANCE LIMITING PROCEDURE

= 1 LIMIT INTERPOLATION BY ELLIPTIC PROCEDURE

NOTE: If File 31 is entered on the names line, setting IOP11>0 will output a file of ID weight spikes that can be
viewed in MineSight.
IOP12 = 0 NO OCTANT/QUADRANT SEARCH

= 1 or -1 FOR OCTANTS
= 2 or -2 FOR QUADRANTS
= 3 or -3 SPLIT OCTANT (8 above + 8 below)
= 4 or -4 SPLIT QUADRANT (4 above + 4 below)
USE IOP12 > 0 OCTANTS/QUADRANTS WITH RESPECT TO ACTUAL (model) COORDINATES.

USE IOP12 < 0 FOR OCTANTS/QUADRANTS WITH RESPECT TO ROTATED (anisotropic) SEARCH
COORDINATES.
NOTE: The closest IOP2 composites in each octant or quadrant will be used.
In order to store the number of octants, etc... add the following line:

CMD = STORE NOCTS INTO label-15 min_value
where

STORE NOCTS INTO are keywords
label-15 is the item to store the number of octants
and
min_value is the minimum number of octants allowed. If the number of octants or quadrants with
a composite value is below the specified number, no interpolation is done.
IOP13 = 1 READ PAIRS OF CROSS REFERENCE CODES TO ALIAS BLOCK CODES

NOTE: If IOP13=1-10, one cross reference line is read. If IOP13=11-20, two cross reference lines are
read.
IOP14 = 0 ALIAS BOTH COMPOSITES AND MODEL CODES

IOP16 = MAXIMUM NUMBER OF COMPOSITES TO INTERPOLATE A BLOCK (default = 25)
IOP18 = 0 STORE LOCAL ERROR AS VARIANCE

= 1 STORE LOCAL ERROR AS STANDARD DEVIATION


IOP20 = 0 MINIMUM # OF OCTANTS OR QUADRANTS WITH AT LEAST ONE VALUE BEFORE INTERPOLATING
THE BLOCK
< 0 STORES THE # OF OCTANTS OR QUADRANTS WITH COMPOSITES, INSTEAD OF STORING THE # OF
COMPOSITES FOR THE BLOCK (works in conjunction with BLOCK CALC #COMP)
*See IOP12 when negative, must also use CALC #COMP (works in conjunction with #COMP)

IOP22 = # OF DECIMAL PLACES TO OUTPUT FOR INTERPOLATED VALUES IN FILE 20 (default=3; max=4)
IOP25 = 0 APPLY WEIGHTING FACTOR BEFORE TAKING POWER OF DISTANCE (default).

= 1 APPLY WEIGHTING FACTOR AFTER TAKING POWER OF DISTANCE.
IOP26 = LIMIT INTERPOLATION BY THE NUMBER OF UNPOPULATED ADJACENT OCTANTS OR QUADRANTS

= 0 NO LIMITATIONS (default)
= n NUMBER OF ADJACENT OCTANTS OR QUADRANTS (depending on the value of IOP12)
NOTE: If there are more than n consecutive empty octants/quadrants, the block will not be interpolated.
If horizontal splitting is used (IOP12= 3 or 4), the upper and lower parts of each octant/quadrant are
combined and treated as one object when counting the number of empty octants/quadrants.
GREATER THAN ABS (PAR32). OTHERWISE STORE THE TRUE GRADE VALUE OF THE
CLOSEST COMPOSITE (default=0)

command line)
PAR1 = X-SEARCH DISTANCE

PAR2 = Y-SEARCH DISTANCE
PAR3 = Z-SEARCH DISTANCE
NOTE: PAR3 not used for SCAN1-D or SCAN2-D. However, enter a small non-zero value (e.g., 0.1).

(default = SQRT ((PAR1)2 + (PAR2)2 + (PAR3)2))
PAR5 > 0 INVERSE POWER TO BE USED FOR COMPOSITE WEIGHTS (Default=2)

= -1 USE AVERAGE OF COMPOSITES INSTEAD OF INVERSE DISTANCE WEIGHT

PAR6 = CONSTANT TO BE INCLUDED IN CALCULATION OF WEIGHTS BETWEEN BLOCK

MIDPOINTS & EACH SELECTED COMPOSITE AS WEIGHT = 1.0 / (DISTANCE + PAR6) ** PAR5
PAR8 = MAXIMUM DISTANCE TO PROJECT SINGLE COMPOSITE VALUE (default = PAR7)

PAR10 = MINIMUM DISTANCE FOR WEIGHTING (default = 0.01)
value is used in the Inverse Distance Weight calculation.
PAR20 = OPTIONAL SEARCH DISTANCE FOR THE ELEVATION RANGE WHEN USING RELATIVE ELEVATION
(DEFAULT = PAR3)

(i.e., for composites greater than or equal to PAR31 in value,
the maximum 3-D search distance will be PAR32, instead of regular PAR4).
NOTE: 1) PAR31 and PAR32 apply to the item in the first calculation only.
2) If PAR32 < 0 the grades above cutoff at a distance greater than ABS (PAR32) will be cut to
PAR31
PAR33 = LOWER GRADE CUTOFF FOR CHANGING THE 3-D SEARCH DISTANCE
PAR34 = THE 3-D SEARCH AT THE SPECIFIED CUTOFF FOR LOW GRADES.
NOTE: 1) For composites less than PAR33 in value, the maximum search distance will be PAR34 instead
of regular PAR4
2) PAR33 and PAR34 apply to the first calculation item only.
IMPORTANT NOTE: All of the options available with M620V1 are available with M620V2. See the M620V1 documentation
for a full explanation of the following options:
CMD = SEARCH RY RX RZ ROTN DIPN DIP

CMD = SEARCH COORD filename RY RX RZ
CMD = ELEV ZMID
INP8 = REF# EAST NORTH ELEV. value1 . . . geol1
ALF = REF# COORD COORD COORD CALC . . . MATCH
CMD = XCRD label-08
CMD = YCRD label-08
CMD = ZCRD label-08
CMD = FMR FILE [filename.fmr] (required for IOP31 = 1 - 3)

CMD = RSI FILE [filename.rsi] (required for IOP31 = 2)

CMD = FRM PAR F1 F2 F3 F4 F5 [F6 F7 F8] (required for IOP31 = 2)

ITMn = CARD DATA INPUT SCAN2-D (ASCII Input Data)
ITMn = CARD DATA INPUT SCAN3-D
ITMn = label-15 label-08 MATCH MODEL
ITMn = label-15 BLOCK CALC #COMP NCOM
ITMn = label-15 BLOCK CALC #COMP NDHO
ITMn = label-15 BLOCK CALC RINGS DMIN
ITMn = label-15 BLOCK CALC RINGS DAVG
ITMn = label-15 BLOCK CALC RINGS DMAX
ITMn = label-15 label-08 CALC INVWT (ISD method)
ITMn = label-15 label-08 CALC POLYG (Polyg method)
ITMn = label-15 LOCAL ERROR
ITMn = label-15 CALC ZCRD INVWT (or POLYG, to interpolate model Z coordinate)
RUN = RESET (Reset uninterpolated blocks to missing)

RUN = ZERO (Reset uninterpolated blocks to 0.0)
RUN = OMIT (Leave uninterpolated blocks as they are)
END
IX1 IX2 IY1 IY2 IZ1 IZ2 comp1 comp2 comp3 comp4
Columns Rows Benches
where comp1-n are optional composite codes for controlling split seam interpolation. See SCAN1-D and M620V1 Sample Run File
#16. The run will end with a 0 for IX1 to IZ2 or on an end-of-file condition.


MEDS-620V2 3=RPT620.LA2
* SAMPLE INVERSE DISTANCE INTERPOLATION - OCTANTS *
USR = ABC
RUN = RESET
COM -
COM -
COMT* * TEST RUN #1: M620V2
COM 3-D SPHERICAL SEARCH WITHIN RECTANGULAR BOX
IOP2 = 2 / MAX # OF COMPOSITES PER OCTANT

IOP12 = 1 / 1=OCTANTS, 2=QUADRANTS

END
0 50 0 50 20 20


1. The program will list all the composites within the search window of each interpolated row if I-O=2 is specified in the
run file. The program will also list all the items in the composite and model files, the total number of blocks interpolated
for each row, and other debug information. This option is not suggested when interpolating the entire model.
2. The program will print the location of composites, the distance to the block, and composite grades and weights for each
block interpolated if IOP11 is set to the row# for debug output.
The program will also indicate the number of the octant each composite falls in when the debug option is on. There are
eight octants. Each octant is defined by a 45o window from the center of the block measured clockwise from north. Thus,
octant #1 is between the north and N45E direction. Octant #2 is between the N45E and east direction and so on.
A negative octant number indicates the composite has not been used in interpolation because the number of composites
in that octant exceeded the number specified in IOP2.
3. If ellipsoidal search is used, then the 3-D distance calculated between a composite and the block will be the adjusted
distance based on the anisotropy ratios. This is the distance that is printed in the output file when the debug option is on.
4. To limit the number of composites to interpolate a block using IOP7, regardless of the distance to the closest composite,
set PAR8 to a small value (such as 0.1). The program first checks if the number of composites to use is less than IOP7.
If so, then it checks the distance to the closest composite against PAR8. If PAR8 is greater than the closest distance, the
program will use the composites although there are less than IOP7 composites.
5. Default inverse power used by the program is 2 if you do not specify PAR5. The higher the inverse power, the more
weight is given to the nearest sample.
6. Be sure to select composite and model file item labels that are not used as keywords by the program to execute certain
commands.
7. If youre using more than one ITM command, number them sequentially, without repetition.
8. Multiple Area Selection Lines are allowed. The program will interpolate the blocks specified in the first line, then it will
interpolate the blocks specified in the second line and so on. The only exception is when the ASCII input option is used
and the composite data follows the run file.
will appear if more than 1200 composites are found. The maximum number of composites that the program can handle
for a single row is 1200. If this number is exceeded the program will print an error message and stop interpolating at that
row. If this happens, first check if you can decrease the X, Y or Z search distances used by the program. If you can, then
try again starting from the row where the program stopped and see if this will solve the problem. If it does not, try to
specify lesser columns to interpolate by using multiple Area Selection Lines.
will occur if more than 400 composites are found in a search around one block. The maximum number of composites
that the program can handle for a single block is 400. If this number is exceeded, the program will give an error message
and stop interpolating at that block. If this happens, try a similar approach as explained in Step 9.
11. If IOP5=1 (use the minimum grade criterion), then PAR9 must be specified. The minimum grade criterion is based on the
grade of the composite closest to the block being interpolated. If the grade of the closest composite is greater than PAR9,
then the program uses only the composites whose grades are greater than PAR9. If the grade of the closest composite is
less than PAR9, then the program uses only the composites whose grades are less than PAR9.

will occur if the minimum column is greater than the maximum column, or the minimum row is greater than the
maximum row, or the minimum bench is greater than the maximum bench.
13. ** ITEM DEFINITION ERROR MSINL1 ** NO ITEMS HAVE BEEN SET UP TO BE STORED
will appear if PAR1-4 are not entered.

18. ** M620V2: WARNING. YOU CAN ONLY CHECK FOR DUPLICATE POINTS ON BLASTHOLE
PROJECTS. IOP21 IS BEING RESET TO 0.
IOP21 is applicable to blasthole projects only. There is no need to check for duplicate composites in non-blasthole
projects. If you try to activate IOP21 for a non-blasthole project it will be reset to zero and the program will continue
normally.


MineSight
Proprietary Software: Mintec, inc. M621V1 - TREND PLANE SEARCH INTERPOLATION
M621V1 TREND PLANE SEARCH INTERPOLATION

M621V1 uses a similar interpolation scheme to M620V1. When 3D trends exist within a deposit, it may be necessary to
However, the search is along the dip and strike of a trend plane use a modification of the standard inverse distance weighting
specified by a mine model code. technique to search and project along the established trend.
The program works with sub-blocked models and is enabled M621V1 uses basically the same procedures as M620V1 with
to perform individual calculations for each zone of the sub- additional logic for using the 3-D trend plane in the search and
divided block. weighting of composites. Geologic codes and the model file are
normally required to use this technique.
The standard interpolation method used for initial extension of
RUN FILE: grades and other values makes use of the principle of gradual
changes for calculating block values. This technique of gradual
- Search distances or changes uses a weighting function calculated from the inverse
ranges distance between each composite and the block midpoint. You
- Controlling & limiting item should have geologic codes in the model and composite data to
labels limit values used in the calculations.
M621V1 uses inverse distance weighting to calculate block

values. The equation to calculate the value of a block with this
INPUT: CALCS:
G= /d1n + v2/d2n + ... + vk/dkn

v1
- PCF - Find the composites
- Mine model file (File 13, within the search window
14 or 15) - Match block with geology
1
/d1n + 1/d2n + ... + 1/dkn
- File 9 or File 8 or class
MSTorque composite set - Apply limiting factors where
- Geology codes - Determine nearest
composites
- Compute weights G = estimated value of block
- Calculate and store v = value of sample
grades d = distance of sample to center of block
n = power (or exponent) of d
k = # of samples
The weight assigned to each sample will be affected by the

OUTPUT: exponent used for the distance. More weight can be assigned to
the nearest sample by increasing this exponent. The larger the
exponent, the more polygonal the estimate.
- Updated Model File
compute an adjusted distance based on the anisotropy ratios in
horizontal and vertical directions.

MineSight
M621V1 - TREND PLANE SEARCH INTERPOLATION Proprietary Software: Mintec, inc.
Coordinate parameters 3. Select the initial interpolation options and parameters to be

used for the test runs.
PAR1-3 control the primary coordinate selection of data from
File 9 (or File 8) composites, the ASCII composite file or the 4. Prepare the dip & strike for each 3-D trend plane to be used
MSTorque composite set. These parameters may come from during the M621V1 interpolation runs.
deposit experience.
5. Interpolate a small test area and print a map of the results
with either M605V1 or M606V2.
1. The primary coordinate selection is usually based upon the
range of ZTOE - PAR3 to ZTOE + PAR3, where ZTOE 6. Modify the interpolation parameters and/or procedure, and
is the toe elevation of the bench to be used. repeat Step 5 until satisfactory grade extensions are achieved.
this selection is not used. However, set PAR3 to be a small 7. Perform production runs for all benches, and print bench
non-zero value (e.g., 0.1). and section maps using programs M606V2 & M609V2.
Some plot maps could also be made using the M606V1 &
M122V1 program combination.
range of YMID - PAR2 to YMID + PAR2, where YMID
in the range XMIN - PAR1 to XMAX + PAR1. Storage of Interpolated Values
The composites selected for the entire row are kept in program Interpolated values can be stored in three ways.
If there is only one trend in the deposit, specify ITMn 1) Normally, interpolated values are stored back into the model
=DUMMY BLOCK TREND. The trend plane specified at file. The Names Line contains a 15(or13or 14)=filename
the end of the run file will describe the search used to find entry.
composites. Geology codes in the model can be used to limit
interpolation by specifying ITMn = label-15 BLOCK LIMIT 2) For ore control purposes, because there is no model file, the
and composites can be matched with model blocks with ITMn values are output to an ASCII file (File 20). The Names Line
= label-15 label-08 MATCH MODEL. contains 15=ASCII and 20=filename entries.
If there is more than one trend in the deposit, store a trend item
3) For testing, when data from the model file is needed, as in
in the model. This item must contain integer codes that define
BLOCK LIMIT or MATCH MODEL, the model file can be
areas in the deposit with different trends. The number of the
plane on the Trend Plane Line should correspond to an integer
code stored in this model item. The item that contains the trend
code is specified with ITMn = label-15 BLOCK TREND.
Geology codes in the model can be used to limit interpolation by
specifying ITMn = label-15 BLOCK LIMIT. Composites can Use of Boundary File
be matched with model blocks with ITMn = label-15 label-08
MATCH MODEL. A digitized boundary of a production area (shot) or any special
area may be used to define the blocks that will be interpolated.
The boundary will be used to determine a mimimum and
maximum column to be interpolated in each row. The boundary
Procedure summary for 3-D trend must be contained in its own file.
interpolation
1. Load trend codes into the mine model. These codes may
represent areas of different geology or areas of different
trends.
2. If geology matching is to be done, geology codes must also

exist in the sorted composite File 8.

MineSight
Proprietary Software: Mintec, inc. M621V1-TREND PLANE SEARCH INTERPOLATION
M621V1 - TREND PLANE SEARCH INTERPOLATION

RUN FILE OPERATION
MEDS-621V1 10=filename 9(or 8)=filename 15(or 14 or 13)=filename;

where

from MSTorque
15 = the name of the MINE MODEL FILE OR 15=ASCII - OR -
19 = the name of the INPUT FILE WITH COMPOSITES (if 8=CARD) -OR- MSTorque info file (mstorq.inf) (if
8=TORQ is used)
31 = the name of the ID WEIGHTS FILE (optional, see IOP11)
Note: If 9 = filename is specified on the names line, then composite data will be retrieved from this file
IOP2 = NUMBER OF TREND PLANES IN RUN (Max=100)
NOTE: If planes are not specified, blocks with that code are not interpolated.


= 1 MATCH 1 ITEM after a block is selected
= 2 MATCH 2 ITEMS after a block is selected
= -1 Match 1 item before a block is selected
= -2 Match 2 items before a block is selected
Note: Only selection by PAR7 is affected by before/after choice

MineSight
M621V1-TREND PLANE SEARCH INTERPOLATION Proprietary Software: Mintec, inc.

NOTE: See the How to Debug section.

= 1 USE ADJUSTED DISTANCES BASED ON ANSIOTROPY
IOP8 = 0 SIMPLE DISTANCE LIMITING PROCEDURE

= 1 LIMIT INTERPOLATION BY ELLIPTIC PROCEDURE
IOP11 = ROW NUMBER FOR EXTENDED OUTPUT FROM CALCULATION (Debug)

NOTE: If File 31 is enterd on the names line, setting IOP11>0 will output a file of ID weight spikes that can be
viewed in MineSight.

NOTE: If IOP13= 1-10, one cross reference line is read. If IOP13= 11-20, two cross reference lines are
read.

IOP16 = MAXIMUM NUMBER OF COMPOSITES TO INTERPOLATE A BLOCK (default = 25)


IOP22 = # OF DECIMAL PLACES TO OUTPUT FOR INTERPOLATED VALUES IN FILE 20 (Default=3; Max=4)
IOP23 = 1 USE PERPENDICULAR DISTANCE FROM A TREND PLANE WHEN DETERMINING

CLOSEST POINTS FROM A DRILLHOLE.
IOP24 = 0 Trend planes angles entered with respect to project coordinates (Default)
= 1 Trend planes angles entered with respect to model coordinates
Note: IOP24 is used with rotated models only.
IOP25 = 0 APPLY WEIGHTING BEFORE TAKING POWER OF DISTANCE (Default).

= 1 APPLYING WEIGHTING FACTOR AFTER TAKING POWER OF DISTANCE.

MineSight
CLOSEST COMPOSITE
(default=0).

NOTE: PAR3 not used for SCAN1-D or SCAN2-D. However, enter a small non-zero value (e.g., 0.1).

(default = SQRT((PAR1)2 + (PAR2)2 + (PAR3)2))
PAR5 > 0 INVERSE POWER TO BE USED FOR COMPOSITE WEIGHTS (Default=2)

= -1 Use average of composites instead of inverse distance weight
PAR6 = CONSTANT TO BE INCLUDED IN CALCULATION OF WEIGHTS BETWEEN

BLOCK MIDPOINTS & EACH SELECTED COMPOSITE AS WEIGHT = 1.0 / (DISTANCE + PAR6) ** PAR5
PAR7 = MAXIMUM DISTANCE TO CLOSEST POINT FOR INTERPOLATION (Default = PAR4)
PAR8 = MAXIMUM DISTANCE TO PROJECT SINGLE COMPOSITE VALUE (Default = PAR7)
PAR9 = MINIMUM GRADE VALUE (If IOP5=1)
PAR10 = MINIMUM DISTANCE (default = 0.01)
value is used in the Inverse Distance calculation.
ITMn = label-15 BLOCK TREND (to retrieve item)

or
ITMn = DUMMY BLOCK TREND (single trend)
(i.e., for composites greater than or equal to PAR31 in value, the maximum 3-D search
distance will be PAR32, instead of regular PAR4).
NOTE: 1) PAR31 and PAR32 apply to the item in the first calculation only.
2) If PAR32 < 0 the grades above cutoff at a distance greater than ABS (PAR32) will be cut to
PAR31
PAR33 = LOWER GRADE CUTOFF FOR CHANGING THE 3-D SEARCH DISTANCE
PAR34 = THE 3-D SEARCH AT THE SPECIFIED CUTOFF FOR LOW GRADES.

MineSight
NOTE: 1) For composites less than PAR33 in value, the maximum search distance will be PAR34 instead
of regular PAR4.
2) PAR33 and PAR34 apply to the first calculation item only.
IMPORTANT NOTE: All of the options available with M620V1 are available with M621V1. See M620V1 documentation
for a full explanation of the following options:

CMD = SEARCH COORD filename RY RX RZ
CMD = Search project
CMD = ELEV ZMID
CMD = XCRD label-08
CMD = YCRD label-08
CMD = ZCRD label-08
CMD = SEAM label-08

ITMn = label-15 CALC ZCRD INVWT (or POLYG, to interpolate model Z coordinate)
ITMn = label-15 BLOCK CALC #COMP NDHO
ITMn = label-15 BLOCK CALC RINGS DMIN
ITMn = label-15 BLOCK CALC RINGS DAVG
ITMn = label-15 BLOCK CALC RINGS DMAX
RUN = RESET (reset uninterpolated blocks to missing)

RUN = ZERO (reset uninterpolated blocks to 0.0)
RUN = OMIT (leave uninterpolated blocks as they are)
INP8 = REF# EAST NORTH ELEV. value1 . . . geol1
4. TREND PLANE LINES (See IOP2)
iplane strike dipang dstnor dstpln dstdip

where
iplane = Number of planemust correspond with the value of the TREND ITEM stored in mine model.
strike = Strike of plane as an azimuth from north, e.g., 45.00 for N45E and -45.00 for N45W
dipang = Dip of plane
NOTE: Dip is measured in the plane that is 90o clockwise from the strike. Ex: -90.00 for a vertical plane.
0.0 is not permitted.

MineSight
dstnor = Perpendicular search distance each side of plane

dststr = Search distance limit along the strike direction
dstdip = Search distance limit along the dip direction
These dip/strike parameters are entered in free-field format (separate values by one or more blanks). There must be one dip/strike
line for each plane. End input of Trend Plane Lines with iplane=0.
where comp1-n are optional composite codes for controlling split seam interpolation. See SCAN1-D and M620V1 Sample Run
File #16. The run will end with a 0 for IX1 to IZ2 or on an end-of-file condition.

MineSight

* SAMPLE INVERSE DISTANCE INTERPOLATION ALONG TREND PLANE *
COM -
COM -
COM ** TEST RUN #1: M621V1
DOC ** TREND PLANE: STRIKE = N45E, DIP = -20 DEGS
USR = ABC
RUN = RESET
IOP2 = 1 / # OF TREND PLANES


PAR5 = 2. / INVERSE POWER
PAR6 = 0. / CONSTANT IN WEIGHT CALC

ITM3 = DUMMY BLOCK TREND
COM ** VERTICAL SEARCH ON THE PLANE= 50 FEET
COM ** SEARCH DISTANCE ALONG STRIKE= 600 FEET
COM ** SEARCH DISTANCE ALONG DIP = 750 FEET
END
1 45 -20 50 600 750
0
0 50 0 50 18 18

MineSight

MEDS-621V1 3=SAM621.LB
COM
COM
DOC ** TREND PLANE: STRIKE = N45W, DIP = -35 DEGS

COM ** ASCII DATA INPUT
USR = ABC
RUN = RESET



ITM2 = DUMMY BLOCK TREND
COM ** VERTICAL SEARCH ON THE PLANE=5 FEET

COM ** SEARCH DISTANCE ALONG STRIKE=75 FEET
COM ** SEARCH DISTANCE ALONG DIP=175 FEET
END
1 -45 -35 5 75 175
0
0 50 0 50 20 20
30 DH-43 13350. 12550. 3500. 0.058
32 DH-56 13150. 12350. 3700. 0.092
34 DH-62 13200. 12500. 3600. 0.126
35 DH-63 13300. 12400. 3600. 0.402
36 DH-65 13350. 12550. 3700. 0.312
39 DH-61 13300. 12400. 3650. 0.201

MineSight

MEDS-621V1 3=SAM621.LC
COM
COM
DOC ** MULTIPLE TREND PLANES
USR = ABC
RUN = RESET



ITM2 = MO-2 MOLY CALC INVWT I
TM3 = GEOL BLOCK TREND
COM* MULTIPLE TREND PLANE SPECIFICATION

COM BASED ON GEOL CODES IN THE MODEL
END
1 45 -20 100 600 750
2 35 -10 100 750 750
3 0 -25 100 500 800 0
0
50 0 50 20 20

MineSight
1. The program will list all the composites within the search window of each interpolated row if I-O=2 is specified in the run file.
The program will also list all the items in the composite and model files, the total number of blocks interpolated for each row,
and other debug information. This option is not suggested when interpolating the entire model.
2. The program will print the location of composites, the distance to the block, and composite grades and weights for each block
interpolated if IOP11 is set to the row# for debug output.
3. If ellipsoidal search is used, then the 3-D distance calculated between a composite and the block will be the adjusted distance
based on the anisotropy ratios. This is the distance that is printed on the output file when the debug option is on.
4. To limit the number of composites to interpolate a block using IOP7, regardless of the distance to the closest composite, set
PAR8 to a small value (such as 0.1). The program first checks if the number of composites to use is less than IOP7. If so, then
it checks the distance to the closest composite against PAR8. If PAR8 is greater than the closest distance, the program will use
the composites although there are less than IOP7 composites.
5. Default inverse power used by the program is 2 if you do not specify PAR5. The higher the inverse power, the more weight is
given to the nearest sample.
6. Be sure to select composite and model file item labels that are not used as keywords by the program to execute certain commands.
8. Multiple Area Selection Lines are allowed. The program will interpolate the blocks specified in the first line, then it will interpolate
the blocks specified in the second line and so on. The only exception is when the ASCII input option is used and the composite
data follows the run file.

will appear if more than 1200 composites are found. The maximum number of composites that the program can handle for a
single row is 1200. If this number is exceeded the program will print an error message and stop interpolating at that row. If this
happens, first check if you can decrease the X, Y or Z search distances used by the program. If you can, then try again starting
from the row where the program stopped and see if this will solve the problem. If it does not, try to specify lesser columns to
interpolate by using multiple Area Selection Lines.

will occur if more than 400 composites are found in a search around one block. The maximum number of composites that the
program can handle for a single block is 400. If this number is exceeded, the program will give an error message and stop
interpolating at that block. If this happens, try a similar approach as explained in Step 9.
11. If IOP5=1 (use the minimum grade criterion), then PAR9 must be specified. The minimum grade criterion is based on the grade
of the composite closest to the block being interpolated. If the grade of the closest composite is greater than PAR9, then the
program uses only the composites whose grades are greater than PAR9. If the grade of the closest composite is less than PAR9,
then the program uses only the composites whose grades are less than PAR9.

will occur if the minimum column is greater than the maximum column, or the minimum row is greater than the maximum row,
or the minimum bench is greater than the maximum bench.

MineSight
13. ** ITEM DEFINITION ERROR - MSINL1 **






19. %M621V1: WARNING: You can only check for duplicate points on blasthole projects. IOP21 is being reset to 0.
IOP21 is applicable to blasthole projects only. There is no need to check for duplicate composites on non-blasthole projects. If
you try to activate IOP21 for a non-blasthole project it will be reset to zero and the program will continue normally.

MineSight
Proprietary Software: Mintec, inc. M624IK - MULTIPLE INDICATOR KRIGING TECHNIQUE
M624IK MULTIPLE INDICATOR KRIGING TECHNIQUE

M624IK is used to interpolate block grades using multiple M624IK is a special version of M624V1 to compute block grades
indicator kriging (MIK). using multiple indicator kriging.
The Program works with sub-blocked models and is enabled The program input parameters and options are the same as
to perform individual calculations for each zone of the sub- M624V1 with a few exceptions. PAR19 is the cutoff above which
divided block. grade and proportion of ore in each block are computed by MIK.
If PAR19=0, then an E-type estimate is calculated where the ore
(or waste) in the block is 100%.
PROGRAM FLOW DIAGRAM IOP18 gives the option to store the proportion of ore as a percent.
The program expects that the first item (ITM1) in the run file is
RUN FILE: for storing MIK grade and the second item (ITM2) is for storing
- Interpolation parameters proportion of ore above the specified cutoff. This second item is
- Search distances or ranges required even when an E-type estimate is calculated.
item labels
- Variogram parameters Variogram parameters of MIK are input to the program through
the variogram parameter file in unit 30.
INPUT: CALCS:

14 or 15) - Match block/geology codes
- File 9 or File 8 or - Apply limiting factors
MSTorque composite set - Determine nearest
- Geology codes composites
- Compute weights
- Calculate and store grades
OUTPUT:

MineSight
M624IK - MULTIPLE INDICATOR KRIGING TECHNIQUE Proprietary Software: Mintec, inc.

MineSight
M624IK - MULTIPLE INDICATOR KRIGING TECHNIQUE
RUN FILE OPERATION

MEDS-624IK 10=filename 9(or 8)=filename 15(or 14 or 13)=filename;

MEDS-624IK 19=filename 3=filename 30=filename
where
MEDS-624IK (must be the first 10 columns)
8 = the name of the SORTED COMPOSITE FILE (obsoleted) -OR- CARD for ASCII input -OR- TORQ for input
from MSTorque
15 = the name of the MINE MODEL FILE15=ASCII -OR-
19 = the name of the INPUT FILE WITH COMPOSITES (If 8=CARD) -OR- MSTorque info file (mstorq.inf) (if
8=TORQ is used).
30 = the name of the VARIOGRAM PARAMETER FILE (required)
IMPORTANT NOTE: All the run options listed for M624V1 are identical for this program, unless stated otherwise. In
addition, M624IK has the following special run options:
IOP18 = 0 STORE ORE AS PROPORTION (default)

= 1 STORE ORE AS PERCENT
IOP24 = MIN # OF COMPOSITES TO USE LOCAL CLASS MEAN (default=global)
PAR19 = CUTOFF GRADE TO USE FOR MULTIPLE INDICATOR KRIGINGTO COMPUTE GRADE AND
PROPORTION OF ORE IN THE BLOCKS
ITM Lines for values to be computed and stored:
ITM1 = label-15 label-08 CALC KRIGE

label-15 = label of model item to store MIK grade
label-09 = label of composite grade item

label-15 = label of model item to store ore% (or proportion) above the specified cutoff
label-09 = must be the same as for ITM1

MineSight
Sample multiple indicator variogram parameter file:
Multiple indicator kriging with 4 cutoffs Comment Line

4 1.10 .29 .4 1.45 1) #of cutoffs 2) affine correction factor 3) mean for the last class 4)
max grade 5) coefficient of variation
.0013 .015 .007 Nugget value 2) indicator cutoff 3) class mean
1 .0245 150 120 60 0 0 0 Parameters for variogram
0 End of input
.008 .032 .022 Nugget value 2) indicator cutoff 3) class mean
1 .0160 120 80 40 45 -10 0 Parameters for nested variogram
0 End of input
.0031 .095 .060
1 .0088 120 120 80 0 0 0
0
.0072 .18 .133
2 .0519 240 240 240 0 0 0
0
The parameter file should have no blank lines. Blanks are shown in the sample file to accomodate the comment lines.
The parameter file 13 is the only way to enter the variogram parameters for M624IK. Both the run file and the parameter file can be
set up using appropriate MSCompass procedures.
If coefficient of variation is entered in the variogram file, indirect lognormal correction is applied instead of affine correction.

MineSight
M624IK SAMPLE RUN FILE

MEDS-624IK 10=mgsc10.DAT 8=mgsc08.dat 15=mgsc15.dat;
MEDS-624IK 3=RPT624.MIK 30=aux624.mik
** MIK INTERPOLATION FOR 3-D BLOCK VALUES ** 0.02 cutoff
RUN = RESET
USR = aa /

IOP6 = 0 / 0=Use true dist.; 1=Use anisotropic dist.
IOP11 = 0 / Row # for extended output
IOP12 = 0 / 1=Octant; 2=Quadrant search; 0=All
IOP16 = 36 / Max.# of composites for interpolating a block
IOP18 = 1 / 0=Store proportion, 1=percent of a block
IOP19 = 5 / Max.# of composites per hole (DEFAULT=No limit)

PAR3 = 40. / Primary Z-search distance
PAR7 = 100. / Max distance to closest point
PAR8 = 100. / Max distance to project single composite
PAR19 = 0.02 / Cutoff grade to compute MIK values
PAR27 = 4 4 1 / Block discretization in X,Y,Z
ITM1 = AUIK2 AUAA CALC KRIGE / Grade item

ITM2 = ORE2 AUAA CALC KRIGE / % item
ITM3 = ROCK Block limit
ITM4 = ROCK RANGE 5. 5.
CMD = Block limit codes 5

END
1 70 1 70 15 15

MineSight

MineSight
Proprietary Software: Mintec, inc. M624MIK - MULTIPLE INDICATOR KRIGING TECHNIQUE w/GSLIB routines
M624MIK MULTIPLE INDICATOR KRIGING TECHNIQUE with

GSLIB routines
M624MIK is used to interpolate block grades using multiple M624MIK is a special version of M624IK to compute block
indicator kriging (MIK). grades using multiple indicator kriging, with the GSLIB routines.
The Program works with sub-blocked models and is enabled The program input parameters and options are the same as
to perform individual calculations for each zone of the sub- M624IK with a few exceptions. Specific options to the program
divided block. are input through the variogram parameter file. PAR19 is the
cutoff above which grade and proportion of ore in each block
are computed by MIK. If PAR19=0, then an E-type estimate is
calculated where the ore (or waste) in the block is 100%.
IOP18 gives the option to store the proportion of ore as a percent.
RUN FILE: The program expects that the first item (ITM1) in the run file is
for storing MIK grade and the second item (ITM2) is for storing
- Search distances or ranges proportion of ore above the specified cutoff. This second item is
- Controlling and limiting required even when an E-type estimate is calculated.
item labels
- Variogram parameters Variogram parameters of MIK are input to the program through
the variogram parameter file in unit 30.
The program can optionally compute the grade and proportion

of ore in each block at multiple cutoffs, for up to 10 cutoffs.
INPUT: CALCS:

14 or 15) - Match block/geology codes
- Geology codes composites
- Compute weights
OUTPUT:


MineSight
M624MIK - MULTIPLE INDICATOR KRIGING TECHNIQUE w/GSLIB routines Proprietary Software: Mintec, inc.

MineSight
Proprietary Software: Mintec, inc. M624MIK - MULTIPLE INDICATOR KRIGING TECHNIQUE w/ GSLIB routines
M624MIK - MULTIPLE INDICATOR KRIGING TECHNIQUE with GSLIB routines
RUN FILE OPERATION

MEDS-624MK 10=filename 9(or 8)=filename 15(or 14 or 13)=filename;

MEDS-624MK 19=filename 3=filename 30=filename
where
MEDS-624MK (must be the first 10 columns)
8 = filename of the SORTED COMPOSITE FILE (obsoleted) -OR- CARD for ASCII input -OR- TORQ for input
from MSTorque
15 = the name of the MINE MODEL FILE15=ASCII -OR-
8=TORQ is used)
30 = the name of the VARIOGRAM PARAMETER FILE (required)
9. To request an ASCII input DO NOT enter 9 = on the names line and specify 8=CARD. To
IMPORTANT NOTE: All the run options listed for M624V1 are identical for this program, unless stated otherwise. In
addition, M624MIK has the following options:
IOP15 = MIN # OF COMPOSITES TO USE LOCAL PDF (PROBABILITY DENSITY FUNCTION)
IOP20 = 0 STORE KRIGING VARIANCE

= 1 STORE STANDARD DEVIATION
= 2 STORE CONDITIONAL VARIANCE (ONLY WHEN E-TYPE ESTIMATE IS OUTPUT)
= 3 STORE CONDITIONAL STD. DEV. (ONLY WHEN E-TYPE ESTIMATE IS OUTPUT)
IOP24 = OUTPUT TYPE

= 1 E-TYPE ESTIMATE (IF CUTOFF IS ZERO)
= 2 GRADE AND PROPORTION ABOVE A SPECIFIED CUTOFF
= 3 GRADE AND PROPORTION BELOW A SPECIFIED CUTOFF
= 4 GRADE CORRESPONDING TO CDF (CUMULATIVE DENSITY FUNCTION) VALUE P
IOP29 = 0 CALCULATE CLASS MEANS FOR E-TYPE ESTIMATE (default)

= 1 READ PREDEFINED CLASS MEANS FROM VARIOGRAM PARAMETER FILE
PAR19 = CUTOFF OR P-VALUE TO COMPUTE MIK VALUES (Single cutoff option).

MineSight
M624MIK - MULTIPLE INDICATOR KRIGING TECHNIQUE w/ GSLIB routines Proprietary Software: Mintec, inc.
CMD Lines for Multiple Cutoff Option:
CMD = CUTGS cut1 cut2 cut3 .... CutN
where
CUTGS is the key word. Cut1, cut2, cut3 .... cutN are the cutoff grades at which the MIK values need to be calculated.
Maximum of 10 cutoffs are allowed.
If the multiple cutoff option is used, the program expects that the first item (ITM1) in the run file is for storing the grade
above the first cutoff, and the second item (ITM2) is for storing the proportion of ore above the first cutoff. ITM3 &
ITM4 correspond to the second cutoff, ITM5 & ITM6 correspond to the third cutoff, etc.
ITM Lines for values to be computed and stored:

label-15 = label of model item to store MIK grade
label-09 = label of composite grade item

label-15 = label of model item to store ore% (or proportion) above the specified cutoff
label-09 = must be the same as for ITM1
Sample multiple indicator variogram parameter file:
Multiple indicator kriging with 4 cutoffs Comment Line

4 1 0.9 .7 50 3 1.0 1 1.0 3 3.0 1.49 See explanation below for these parameters in this line
.0013 .015 .007 0.146 1) Nugget value 2) indicator cutoff 3) proportion (0 to 1) of composites
below cutoff 4) class mean (only for IOP29=1)
1 .0245 150 120 60 0 0 0 Parameters for variogram
0 End of input
.008 .032 .022 0.146 1) Nugget value 2) indicator cutoff 3) proportion (0 to 1) of
composites below cutoff 4) class mean (only for IOP29=1)
0 End of input
.0031 .095 .060 0.11
1 .0088 120 120 80 0 0 0
0
.0072 .18 .133 0.12
2 .0519 240 240 240 0 0 0
0
The parameter file should have no blank lines. Blanks are shown in the sample file to accomodate the comment lines.
The parameter file is the only way to enter the variogram parameters for M624MIK. Both the run file and the parameter file can be
set up using appropriate MineSight Compass procedures.
Description of the parameters in the second line of the sample parameter file above:
1) Number of indicator cutoffs (Max = 30)
2) Variance Correction Method

0 = No correction (Default),
1 = Affine Correction,
2 = Indirect Lognormal Correction

MineSight
3) Variance Correction Factor (Default=1)

This is required for volume support correction.
It should be < 1 to go from point distribution to
smu distribution. It is the ratio of block (smu) variance
to the point (composite) variance.
4) Max. grade to limit the last class (required)

This is to control the upper tail of the distribution
which will be constrained by the specified value.
5) No. of discretizations for cdf (Max = 100)

Both the conditional (e-type) mean and the mean above
the specified cutoff are calculated by summing the z
values at regularly spaced conditional cdf increments. The number
of discretizations defines how many the ccdf values
to calculate. Default = 50. Note that greater
accuracy is obtained with a larger number, but it
slows the program execution time.
6) Lower tail extrapolation type

1 = Linear (Default),
2 = Power model,
3 = Linear using global cdf
7) Lower tail extrapolation parameter (Default=1)

Used with Power model. Default = 1. For Power models,
w = 1 corresponds to the linear cdf model, w < 1 for
positively skewed, w > 1 for negatively skewed distributions.
8) Middle part extrapolation type (see #6)
9) Middle part extrapolation parameter (see #7)
10) Upper tail extrapolation type

1 = Linear (Default),
2 = Power model,
3 = Linear using global cdf
4 = Hyperbolic model extrapolation
11) Upper tail extrapolation parameter

Used with Power or Hyperbolic models. Default = 2.
For Hyperbolic models, w = 1 corresponds to a long tail,
w > 1 controls how fast the cdf reaches the upper limit.
Therefore, for example, w = 1 will be an optimistic case,
whereas w = 5 will be a very pessimistic one.
12) The value of the last class mean (only for IOP29=1).

MineSight
M624MIK SAMPLE RUN FILE#1 - Single Cutoff option

MEDS-624MK 10=mgsc10.DAT 9=mgsc09.dat 15=mgsc15.dat;
MEDS-624MK 3=RPT624.MIK 30=aux624.mik
** MIK INTERPOLATION FOR 3-D BLOCK VALUES ** 0.02 cutoff
RUN = RESET
USR = abc /

IOP24 = 2 /Grade and proportion above cut off

PAR19 = 0.02 / Cutoff grade to compute MIK values
ITM1 = AUIK2 AUAA CALC KRIGE / Grade item

ITM2 = ORE2 AUAA CALC KRIGE / % item
CMD = Block limit codes 5

END
1 70 1 70 15 15

MineSight
M624MIK SAMPLE RUN FILE#2 - Multiple Cutoff option

MEDS-624MK 10=msop10.DAT 9=msop09.dat 15=msop15.dat;
MEDS-624MK 3=rpt624.MIK 30=vario2..mik
** MIK INTERPOLATION FOR 3-D BLOCK VALUES **
DOC MIK 10 cutoffs
RUN = RESET
USR = abc /
IOP2 = 3 / Max # of composites per octant or quadrant

IOP4 = -1 / 0=No geologic matching; 1=Match one item
IOP15 = 5 / Min #comps to use global cdf (DEFAULT=0)
IOP20 = 1 / 0=variance; 1=Std dev; 2= Conditional variance
IOP24 = 2 / Output type 1=e-type estimate (DEFAULT=1)

PAR19 = 0.1 / Cutoff or p-value to compute MIK values
CMD = SEARCH GSLIB 150. 150. 150. 50. 20. 20.

CMD = CUTGS 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.
ITM1 = CUIK1 CU CALC KRIGE / Grade item

ITM2 = CPRB1 CU CALC KRIGE / % item

MineSight

ITM22 = XTRA1 Block error
ITM23 = ROCK ROCK Match model
CMD = Block limit ROCK 1 2
CMD = ELEV ZMID

END
0 0 0 0 11 60

trademark of Leica Geosystems AG. M624V1 - KRIGING INTERPOLATION TECHNIQUE
M624V1 KRIGING INTERPOLATION TECHNIQUE

M624V1 is used to interpolate block grades using ordinary, M624V1 is used to compute block grades using kriging.
lognormal or universal kriging. A single or nested variogram Three types of variograms are allowed: spherical, linear and
maybe used to derive the interpolation weights. exponential. Kriging is a geostatistical tool used to estimate
the grade of blocks as a linear combination of samples in or
The program works with sub-blocked models and is enabled around the blocks, such that the estimates are unbiased and have
to perform individual calculations for each zone of the sub- minimum variances.
divided block.
You are allowed only one variogram for each run. This variogram
may consist of a single model or a nested model which is a
combination of several different variograms. As many as three
PROGRAM FLOW DIAGRAM variograms are allowed for a nested model. Multiple grades may
be kriged with the same or different variograms. However, only
RUN FILE: one estimation error is computed and stored. The number of
items that can be stored to the model during the program run is
- Search distances or ranges limited to 30. If there are more than 30 items to be kriged, then
- Controlling and limiting item the program can be run again.
labels
- Variogram parameters
COORDINATE PARAMETERS

INPUT: CALCS: File 9 (or File 8) composites, the ASCII composite file or the
- Locate composites within MSTorque composite set (see the Technical Section, Figure
- PCF
- Mine model file (File 13, search window 1). These parameters may come from geostatistical analysis,
14 or 15) - Match block/geology codes preliminary interpolation runs or from deposit experience.
- Geology codes composites 1. The primary coordinate selection is usually based upon the
- Compute weights
range of ZTOE - PAR3 to ZTOE + PAR3, where ZTOE
is the toe elevation of the bench to be used.

this selection is not used. However, set PAR3 to be a small
OUTPUT:
non-zero value (e.g., 0.1).
- Printer Output File 2. The secondary coordinate selection is always based upon the
range of YMID - PAR2 to YMID + PAR2, where YMID
in the range XMIN - PAR1 to XMAX + PAR1.
The composites selected for the entire row are kept in program

M624V1 - KRIGING INTERPOLATION TECHNIQUE trademark of Leica Geosystems AG.
USE OF MULTIPLE VARIOGRAMS TYPES OF KRIGING
In general, there are two cases where multiple variograms are 1) Universal - for systematic drift
used: 2) Block Kriging (default)
3) Point
4) Lognormal
1. to specify a different variogram for each item to be kriged
5) Indicator
6) Multiple Indicator (MIK)
2. to specify a different variogram for each geologic unit if 7) Co-Kriging
only one item is to be kriged. 8) Simple Kriging
Multiple variograms cannot be used to specify different 9) Simple Co-Kriging
variograms by grade and rock type together in the same run, 10) Outlier Restricted Kriging
that is, you cannot combine the above two situations in a single 11) Nearest Neighbor Kriging
run. If variograms are broken down by rock type, each grade
must be kriged separately.
CALCULATIONS WHICH MAY BE STORED
Multiple variograms are always specified in an external file listed
in the Names Line in the run file as File 30=filename. 1) Kriging Variance (default)
2) Standard Deviation
3) Relative Kriging Variance
4) Proportion above cutoff indicator
STORAGE OF KRIGED VALUES 5) Grade above cutoff indicator
6) Percent above cutoff indicator
Kriged values can be stored in three ways. 7) Block Error
8) Number of Composites Used
9) Calculation Rings - (distance)
1) Normally, kriged values are stored back into the model file. 10) Number of Drillholes used
The Names Line contains a 15(or13or 14)=filename entry. 11) Dilution / smoothing measure
12) Number of octants
2) For ore control purposes, because there is no model file, the
values are output to an ASCII file (File 20). The Names Line
contains 15=ASCII and 20=filename entries.
3) For testing, when data from the model file is needed, as in

BLOCK LIMIT or MATCH MODEL, the model file can be
USE OF BOUNDARY FILE
A digitized boundary of a production area (shot) or any special

area may be used to define the blocks that will be kriged. The
boundary will be used to determine a minimum and maximum
column to be kriged in each row. The boundary must be contained
in its own file.

trademark of Leica Geosystems AG. M624V1-KRIGING INTERPOLATION TECHNIQUE
M624V1 - KRIGING INTERPOLATION TECHNIQUE

RUN FILE OPERATION
MEDS-624V1 10=filename 9 (or 8)=filename 15(or 14 or 13)=filename 19=filename;

where

8 = filename of the sorted COMPOSITE FILE (obsoleted) - OR - CARD for ASCII input -OR- TORQ for input
from MSTorque
15 = the name of the MINE MODEL FILE15=ASCII - OR -
8=TORQ is used)
30 = the name of the VARIOGRAM PARAMETER FILE (optional)
31 = the name of the KRIGING WEIGHTS FILE (optional, see IOP11)
NOTE: If 9 = filename is specified on the names line, then composite data will be retrieved from this file
IOP2 = MAXIMUM # OF COMPOSITES PER OCTANT OR QUADRANT (If IOP12>0)




M624V1-KRIGING INTERPOLATION TECHNIQUE trademark of Leica Geosystems AG.


= 1 USE ADJUSTED DISTANCES BASED ON ANISOTROPY
NOTE: This option is used with CMD = SEARCH ...

NOTE: If File 31 is entered on names line, setting IOP11>0 will output a file of Kriging weight spikes
that can be viewed with MineSight.
IOP12 = 0 NO OCTANT/QUADRANT SEARCH

= 1 or -1 FOR OCTANTS
= 2 or -2 FOR QUADRANTS
= 3 or -3 SPLIT OCTANT (8 above + 8 below)
= 4 or -4 SPLIT QUADRANT (4 above + 4 below)
USE IOP12 > 0 OCTANTS/QUADRANTS WITH RESPECT TO ACTUAL (model) COORDINATES.
USE IOP12 < 0 FOR OCTANTS/QUADRANTS WITH RESPECT TO ROTATED (anisotropic) SEARCH
COORDINATES.
In order to store the number of octants, etc, add the following line (only available to linear kriging methods):
where
STORE NOCTS INTO are keywords
and
label-15 is the item to store the number of octants to
and
Min_value is the minimum number of octants allowed. If the number of octants or quadrants with a
composite value below the specified number, then no interpolation is done. Default = 1 and it means
there is no minimum. This option is only available if an octant/quad item is specified.

= n READ n CROSS REFERENCE CODES TO ALIAS BLOCK CODES AT 10
VALUES PER LINE (see Section 4, following)
NOTE: If IOP13=1-10, one cross reference line is read. If IOP13=11-20, two cross reference lines are read.

IOP15 = n MAX NUMBER OF SECONDARY DATA TO KRIGE A BLOCK
NOTE: IOP15 is used by co-kriging only (see Section VI, Other Kriging Applications below) This IOP is
used in conjunction with PAR6, and PAR30 & PAR39.
IOP16 = MAXIMUM NUMBER OF COMPOSITES TO KRIGE A BLOCK (default = 15, max = 500)

IOP17 = 0 BLOCK KRIGING (default)

= 1 POINT KRIGING
= 2 BLOCK KRIGING OF INDICATORS
= 3 POINT KRIGING OF INDICATORS
= 5 SIMPLE KRIGING
NOTE: IOP17 = 2 or 3 assumes that composite items must already contain indicators prior to running the
M624V1 program. Indicators should have values of 0 or 1 only.

IOP20 = 0 STORE KRIGING VARIANCE (default)

= 1 STORE STANDARD DEVIATION
= 2 STORE RELATIVE KRIGING VARIANCE
= 3 STORE COMBINED VARIANCE
= 4 STORE COMBINED STD. DEV.
= 5 STORE RVI (RELATIVE VARIABILITY INDEX)
= 6 STORE LOCAL VARIANCE/KRIGING VARIANCE
= 7 STORE SIMPLE KRIGING WEIGHTS (WHEN IOP17 = 5)
= 8 STORE REGRESSION SLOPE OF ESTIMATE

IOP22 = # OF DECIMAL PLACES TO OUTPUT FOR INTERPOLATED VALUES IN FILE 20 (default=3; max=4)
IOP26 = LIMIT INTERPOLATION BY THE NUMBER OF UNPOPULATED ADJACENT OCTANTS OR QUADRANTS

= 0 NO LIMITATIONS (default)
= n NUMBER OF ADJACENT OCTANTS OR QUADRANTS (depending on the value of IOP12)
NOTE: If there are more than n consecutive empty octants/quadrants, the block will not be interpolated.
If horizontal splitting is used (IOP12=3 or 4), the upper and lower parts of each octant/quadrant are
combined and treated as one object when counting the number of empty octants/quadrants.
CLOSEST COMPOSITE. (default)
= 1 STORE TRUE GRADE VALUE OF THE CLOSEST COMPOSITE INDEPENDENTLY OF PAR31 AND
ABS(PAR32) VALUES.
IOP27 is invalid in M624MIK or M624IK.
IOP28 = 0 IF THE INTERPOLATED GRADE IS GREATER (LESS) THAN THE MAXIMUM (MINIMUM)
GRADE OF THE COMPOSITES USED FOR THE BLOCK, SET IT TO THE MAXIMUM (MINIMUM)
AND STORE. (default)
= 1 STORE THE TRUE INTERPOLATED GRADE VALUE IF THE GRADE IS GREATER THAN THE
MINIMUM VALUE OF THE RECEIVING MODEL ITEM. OTHERWISE, STORE THE VALUE AS
UNDEFINED.
NOTE: IOP28=0 applies to the Primary item only. For Simple Kriging or Co-Kriging, the program uses IOP28=1.


command line)
PAR6 = MAX DISTANCE FROM BLOCK CENTROID TO ACCEPT SECONDARY DATA (default=PAR4)
NOTE: PAR6 applies to co-kriging and is used together with IOP15.
PAR20 = OPTIONAL SEARCH DISTANCE FOR THE ELEVATION RANGE (default = PAR3)
PAR27-29 = # OF POINTS IN X,Y,Z DIRECTION IN A BLOCK FOR NUMERICAL APPROXIMATION

IN COVARIANCE CALCULATIONS (Default = 4,4,1)
NOTE: The product of PAR27, PAR28, and PAR29 cannot exceed 1000.
PAR30 = MEAN VALUE OF PRIMARY VARIABLE

PAR39 = MEAN VALUE OF SECONDARY VARIABLE

There are several run options and methods for customizing a M624V1 RUN. The following table lists the primary options and the
page on which the IOPs and PARs which control these options are explained.
Sample 13,
Customizing Run Files 14, Page
Option Description File 8 15 Number
I Primary 3D search parameters defining a box around a block ALL X 624-22
II* Optional full 3D (ellipsoidal) coordinate search definition 2 X 624-22
III Optional interpolation parameters 5 X X 624-23
IV Optional 3D search distance at specified cutoff - X 624-24
V Specification of variogram model parameters ALL X 624-24
VI Other Kriging Applications 6, 10 X 624-26
VII Specification of percent and grade above cutoff - X 624-30
VIII Storing kriging estimation error 1-4, 6, 7 X 624-31
IX SCAN 2D: 2D (X and Y) coordinate search - X X 624-32
X SCAN 1D: Interpolating the seams that branch - X X 624-32
XI Search from mid-point of the bench - X 624-33
XII Handling of blocks that are not interpolated ALL X X 624-33
XIII* Matching composite vs block geology codes - X X 624-33
XIV* Assigning and matching geology codes 7 X 624-34
XV* Interpolate selected geology types 7 X X 624-34
XVI* Using alias geology codes - X 624-34
XVII* Relative coordinates specification - X 624-35
XVIII* Use of special weighting factor - X 624-35
XIX ITM lines for values to be computed & stored ALL 624-36
XX To limit the number of composites used to interpolate a block ALL X 624-36
XXI To limit the number of composites from an individual hole - X 624-36
XXII The selection of the composites used in interpolation 6, 7 X 624-36
XXIII Input from an ASCII file 5 X 624-37
XXIV Multiple variogram specification 7 X 624-37
XXV Use of a boundary file - X X 624-39
XXVI Option to override coordinate items - X 624-40
XXVII Option to override/enter controlling seam item - X X 624-40
XXVIII Negative Kriging Weights - X X 624-41
XXIX Storing dilution/smoothing measure - X X 624-41
XXX* Dynamic Unfolding Option - X 624-41
* Pre-requisited required. NOTE: The above options have major effects on interpolation and should be carefully considered.

I. Primary 3-D search parameters defining a box around a block:

NOTE: PAR3 not used for SCAN1-D or SCAN2-D. However, still enter a small non-zero value (e.g.
0.1).

(default = SQRT ((PAR1)2 + (PAR2)2 + (PAR3)2))
All of the composites within this rectangular box are checked against the maximum 3-D search distance (PAR4). The composites
Figure 1. Definition of Primary Coordinate Search Parameters (PAR1, PAR2, and PAR3).
If there are more than n number of composites for a given block after all the tests, then the composites are sorted by increasing
distance. Only the closest n are retained for calculating the weights. Based on these weights, the grade of the block is computed
and stored.
IMPORTANT NOTE: To interpolate GSM or 2-D surface data, the coordinate selection must be based on X and Y coordinates
only. If this is the case, then depending on which source is appropriate, use one of the following command lines in your run file:
ITMn = CARD DATA INPUT SCAN2-D (ASCII Input Data) OR

II. Optional full 3-D (ellipsoidal) coordinate search definition
To add a full 3-D search within the primary search explained above include the following command in your run file:

or
or
CMD = SEARCH COORD filename FILE RY RX RZ
where

SEARCH = Keyword for the program indicating a 3-D search

RY = Search distance (range) in the new north (major-axis) direction
RX = Search distance (range) in the new east direction
RZ = Search distance (range) in the new up direction
ROTN = Rotation from the old north axis to the new north axis( clockwise is a positive rotation)
DIPN = Dip of the new north axis measured horizontally (negative dip is plunging down)
DIPE = Dip easterly from the new north axis
(the horizontal component of this vector is 90 degrees clockwise from the horizontal component of the
new north axis. The dip is measured as in DIPN.)
GSLIB = Keyword to specify GSLIB rotation entry
ROT1 = Horizontal rotation of north axis
ROT2 = Rotation of the north axis from horizontal
ROT3 = Final rotation around the new north axis
COORD = Keyword to specify rotation with three points
filename = Name of the ASCII file with coordinates of these points
FILE = Keyword following the file name
For a detailed description of rotation parameters, see the 600-series Technical section.

Figures 2, 3, and 4 below and Sample Run File #2 show the relationships of the various parameters for ellipsoidal search.
This search forms an ellipsoid around the center of the block based on the search ranges and angles used. The composites within this
ellipsoid are retained for calculations. The 3-D distances (RX, RY, RZ) between the block center and the composites are adjusted
distances based on anisotropy ratios between the ranges. Therefore, if the full 3-D search is used, the value of the maximum 3-D
search distance (PAR4) must reflect the distance in the new coordinates. This option supercedes the IOP3 setting. This option should
not be used for the GSM mine model or File 13 interpolation.
Figure 2. Definition of ROTN, RY and RX used in Figure 3. Definition of DIPN, RY and RZ used in Figure 4. Definition of DIPE, RX and RZ in 3-D
3-D Ellipsoidal Coordinate Search 3-D Ellipsoidal Coordinate Search Ellipsoidal Coordinate Search
By default, search rotation angles presumed entered with respect to model coordinates. To specify rotation angles with respect to
project coordinates, add command:
III. Optional interpolation parameters

PAR8 = MAXIMUM DISTANCE TO THE CLOSEST COMPOSITE WHEN THE NUMBER OF COMPOSITES
WITHIN THE SEARCH = IOP7 (default = PAR7)

NOTE: The difference between PAR7 and PAR8 is that PAR7 is tested at all cases whereas PAR8 is tested
only when the number of composites within the search volume is equal to IOP7.

PAR18 = MAXIMUM ESTIMATION ERROR ALLOWED
NOTE: If the kriging variance for a block exceeds PAR18, the block estimate is not stored.
IV. Optional 3-D search distance at a specified cutoff
Maximum 3-D search distance can be changed for the assays that are greater than a specified cutoff. For this, add the following lines
in your run file:

NOTE: 1) A negative PAR32 is invalid in M624MIK and M624IK.
2) PAR31 and PAR32 apply to the items in the primary (first) calculation only.
3) For composites greater than or equal to PAR31 in value, the maximum 3-D search distance will
be ABS(PAR32), instead of regular PAR4. If PAR32 < 0, the grades above cutoff at distances
greater than ABS(PAR32) will be truncated to PAR31. Use IOP27 to store the true grade value
if the closest composite happens to be an outlier.
Similarly, maximum 3-D search distance can be changed for the assays that are less than a specified cutoff.
For this, add the following lines in your run file:
NOTE: 1) For composites less than or equal to PAR33 in value, the maximum 3-D search distance will
be PAR34, instead of regular PAR4.
2) PAR33 - PAR34 apply to the items in the primary (first) calculation only.
CLOSEST COMPOSITE (default=0).
NOTE: 1) IOP27 is valid if PAR31 (outlier cutoff) is used and PAR32 is negative.
2) IOP27 is invalid in M624MIK and M624IK.
V. Specification of variogram model parameters
The M624V1 run file must contain the specifications of one variogram model to be used for kriging. To specify the nugget and sill
values for the variogram, enter the following command lines:
CMD = NUGGET nug-value

CMD = SPH sill-value R1 R2 R3 [ROTN DIPN DIPE]
or
CMD = SPH GSLIB sill-value R1 R2 R3 ROT1 ROT2 ROT3

or
CMD = SPH COORD filename FILE sill-value R1 R2 R3
where
NUGGET = Keyword for the program (could be abbreviated NUG)
nug-value = Nugget value for the program. Enter even when it is zero.
SPH = Keyword for the program for spherical model.
Use LIN for a linear variogram or EXP for an exponential.
sill-value = Individual sill value for the specified variogram (C1 or C2, etc.).
For a single model, this value equals to total sill minus the nugget.
R1 = Range in the new north (major-axis) direction
R2 = Range in the new east direction
R3 = Range in the new up direction
ROTN = Rotation from the old north axis to the new north axis (clockwise is a positive rotation)
DIPN = Dip of the new north axis measured horizontally (negative dip is plunging down)
DIPE = Dip easterly from the new north axis (the horizontal component of this vector is 90o clockwise from
the new north axis projected in the old horizontal plane. The dip is measured as in DIPN.)
ROTN, DIPN, DIPE = MEDS rotation angles
ROT1, ROT2, ROT3 = GSLIB rotation angles
filename = Name of the ASCII file with coordinates of points defining rotation
FILE = Keyword following the filename
You can use extra values to control the variogram values. If the computed variogram value between a block and the sample exceeds
the user specified value corresponding to the controlling item, then the sample is rejected.
You need to add a CMD line in the run file:
Example:
CMD = VGLIM label09 .25 .33 .44 .55 .66 .45 .75 .70 .70
where
VGLIM is a keyword, label09 is the composite controlling item and the 10 numbers are the 10 maximum variogram values
allowed for composites with label09 values of 1, 2, 3, 4, 5, 6, 7, 8, 9, and 10 respectively.
By default, rotation angles are presumed to be entered with respect to model coordinates. To enter variogram rotation angles with
respect to project coordinates, add command:
CMD = VGM PROJECT
NOTES:
1. Nested variogram models can be entered by adding more Variogram Specification Lines in your run file (max = 3). For
example, a nested spherical model could be entered as:
CMD = NUGGET CO
CMD = SPH C1 R1 R2 R3 ... CMD = SPH C2 R4 R5 R6 ...
where
CO=NUGGET, CO+C1+C2=SILL, R1 R2 R3= 3-D ranges of the first structure, R4 R5 R6=3-D ranges of the second
structure, etc.
Angles are either all with respect to model coordinates (default), or all with respect to poject coordinates (if CMD =
VGM PROJECT above is entered).

2. The program allows the interpolation of multiple grades provided that these grades have the same variogram parameters.
3. Horizontal and vertical anisotropy ratios are calculated based on the 3-D ranges entered. For example, if R1=100, R2=50
and R3=40, then horizontal anisotropy ratio = R1/R2 = 2.0 vertical anisotropy ratio = R1/R3 = 2.5
4. If ROTN, DIPN or DIPE angles are specified, the 3-D ranges will be in the new coordinate system defined by these
angles. For example, by default R1 is the range in the north-south direction. However, if ROTN=45, then R1 will be
the range in the NE-SW direction. The direction of R2 and R3 will similarly be affected based on these angles. See the
Technical Section, Figures 2, 3 and 4.
Sample Run File #2 demonstrates the use of these commands.
See the Technical section for a detailed description of rotation parameters.
VI. Other Kriging Applications
Universal kriging
Universal kriging can be an alternative method to interpolate grades in the presence of systematic drift in the ore body. To use
universal kriging, enter the following command line in your run file:
CMD = UNIV KRIGE ITEM label-08 label-15

or
CMD = UNIV KRIG ITEM label-08
where
UNIV KRIGE ITEM = Keywords for the program. For the case of File 8 ONLY, use KRIG
LABEL-08 = Label of universal kriging item in sorted composite File 8.
LABEL-15 = Label of universal kriging item in mine model File 15
NOTES:
1. Label-15 is not necessary if the 3-D coordinate items (NORTH, EAST or ELEV.) are used for universal kriging. For
example, the following command line is acceptable:
CMD = UNIV KRIG ITEM EAST
2. Up to three universal kriging items may be specified in a run file. However, only one of these items can be other than
EAST, NORTH or ELEV. For example, the following command lines could be used together:
CMD = UNIV KRIGE ITEM label-08 label-15

CMD = UNIV KRIG ITEM ELEV.
3. Block Discretization is not available for Universal kriging if Dynamic Unfolding option is used (IOP31 > 0). Point
Kriging will be employed instead of Block Kriging.
Ordinary Co-Kriging and Simple Co-Kriging
Ordinary co-kriging and simple co-kriging can be performed using a secondary variable. Prior to cokriging, the variograms for
primary and secondary variables, and the cross variogram between these variables need to be computed. By default, the co-
kriging type is ordinary.
The following line is needed in the run file to retrieve the secondary item from File 8 to be used in co-kriging. Without this line,
the program performs ordinary kriging.

CMD = CO KRIGE ITEM label-09 / secondary item for co-kriging

where
CO KRIGE ITEM are a keywords, and label-09 is the secondary item to krige.
VARIOGRAM SPECIFICATION:
You must already have a variogram parameter file set up before you can proceed for co-kriging. The name of the variogram
parameter is specified in the names line as 30=<filename>.
The variograms in this file must be in the following order:
1. Primary data variogram

2. Secondary data variogram
3. Cross variogram between variables 1 and 2.
NOTE: These variograms cannot be specified in the run file. They must be specified in the variogram parameter file. It
is not allowed to use the VGLIM option (see Section V) to control the variogram values for co-kriging.
Sample variogram parameter file for co-kriging:
Co-kriging variogram parameters -- ug=4

0.32429
1 0.69706 250.0 75.0 110.0 15 0 0
0
0.00520
1 1.10400 155.0 60.0 80.0 15 0 0
0
0.30000
1 1.10000 195.0 66.0 114.0 15 0 0
0
COMPOSITE FILE SETUP FOR CO-KRIGING:
The program can only access one composite file (File 9 or File 8). Therefore, both co-kriging items must be in the same composite
file. If co-kriging is performed using drillhole and blasthole data, then both data sets need to be merged or one set must be
appended to the other.
SIMPLE CO-KRIGING ONLY:
To use Simple Co-kriging, the following PARs must be added to the run file:
PAR30 = Mean of primary variable

PAR39 = Mean of secondary variable
NOTE: 1) If PAR30 > 0, then the program performs simple co-kriging. Otherwise ordinary co-kriging is performed. If
you want simple cokriging, but want to use a mean of zero for the primary variable, then enter a small number
for PAR30, such as 0.000001.
NOTE ABOUT USING CO-KRIGING OR SIMPLE CO-KRIGING WITH MULTIPLE ROCK TYPES:
If you want to co-krige multiple rock types using different variograms, then the program will need to be run separately for each
rock type. When doing multiple runs, use RUN=OMIT line in the run file.

OPTIONAL PARAMETERS:
1. You can optionally specify the maximum number of composites to use when kriging a block and you can set the
maximum distance from the block centroid to limit the amount of data used in interpolation.
IOP15 = MAX NUMBER OF SECONDARY DATA TO KRIGE A BLOCK (default = IOP16)

PAR6 = MAX 3-D DISTANCE FROM BLOCK CENTROID TO ACCEPT SECONDARY DATA (default = PAR4)
2. Ellipsoidal search for secondary data, add the following line in the run file:
CMD = SRCH#2 RY RX RZ ROTN DIPN DIPE

where
SRCH#2 is the key word for the program indicating a 3-D ellipsoidal search for the secondary data.
The definitions of RX, RX, RZ, ROTN, DIPN, and DIPE are the same as described in Section II above.
3. To enter block variances for primary and/or secondary variables, add the following lines in the run file:
CMD = BLOCK VAR1 <var1>

CMD = BLOCK VAR2 <var2>
where
BLOCK VAR1 are the key words for the program indicating that the block variance of the primary variable is <var1>.
BLOCK VAR2 are the key words for the program indicating that the block variance of the secondary variable is <var2>.
4. To enter block discretizations for primary and/or secondary variables, add the following lines in the run file:
CMD = BLOCK DISC1 <dx1> <dy1> <dz1>

CMD = BLOCK DISC2 <dx2> <dy2> <dz2>
where
BLOCK DISC1 are the key words for the program indicating that the block discretization of the primary variable are
<dx1> <dy1> <dz1>.
BLOCK DISC2 are the key words for the program indicating that the block discretization of the secondary variable are
<dx2> <dy2> <dz2>.
5. To store information used in kriging for the secondary item, add the following line(s) to the run file. To store this
information for the secondary item, you must include the same line for the primary item. The order of the lines
determines which line refers to the primary item and which line is the secondary item. If there is only one ITM line, then
the program assumes you are storing the information for the primary data only. See also Section XIX, ITM lines for
values to be computed and stored.
ITMn = label-15 BLOCK CALC #COMP NCOM / stores the # of data used for the primary item
ITMn = label-15 BLOCK CALC #COMP NCOM / stores the # of data used for the secondary item
ITMn = label-15 BLOCK CALC #COMP NDHO / stores the # of drillholes used for the primary item

ITMn = label-15 BLOCK CALC RINGS DMIN / stores the distance to the closest data for the primary item
ITMn = label-15 BLOCK CALC RINGS DMIN / stores the distance to the closest data for the secondary item
ITMn = label-15 BLOCK CALC RINGS DMAX / stores the distance to the farthest data for the primary item
ITMn = label-15 BLOCK CALC RINGS DMAX / stores the distance to the farthest data for the secondary item
ITMn = label-15 BLOCK CALC RINGS DAVG / stores the average distance from the data for the primary item
ITMn = label-15 BLOCK CALC RINGS DAVG / stores the average distance from the data for the secondary item

COMPOSITE FILE SETUP FOR CO-KRIGING:
The program can only access one composite file (File 9 or File 8). Therefore, both co-kriging items must be in the same composite
file. If co-kriging is performed using drillhole and blasthole data, then both data sets need to be merged or one set must be
appended to the other.
SIMPLE CO-KRIGING ONLY:
To use Simple Co-kriging, the following PARs must be added to the run file:
PAR30 = Mean of primary variable

PAR39 = Mean of secondary variable
NOTE: 1) If PAR30 > 0, then the program performs simple co-kriging. Otherwise ordinary co-kriging is performed. If
you want simple cokriging, but want to use a mean of zero for the primary variable, then enter a small number
for PAR30, such as 0.000001.
Sample Run File #10 demonstrates the use of this option
NOTE: Ordinary Kriging and Simple Co-Kriging are not available for the Dynamic Unfolding option (IOP31 > 1).
Lognormal Kriging
Use:
ITMn=label-15 label-08 ALOG KRIGE
It uses the log transformed data values to calculate the block grade, which is then transformed for the final result.
NOTE: Block Discretization is not available for Lognormal Kriging if the Dynamic Unfolding option is used (IOP31 > 1). Point
Outlier Restricted Kriging (ORK)
In your run file for M624V1, add the following line for ORK:
CMD=ORK KRIGE ITEM label-08 label-15

where
ORK KRIGE ITEM are the keywords,

label-08 is the label of the File 8 item that has the indicators,
label-15 is the label of the file 15 item that has the probabilities (0 to1).
The remainder of the run file is the same as the Ordinary Kriging run file.
Call Technical Support if you need help on how to calculate those items.
NOTE: Block Discretization is not available for Outlier Restricted Kriging if the Dynamic Unfolding option is used (IOP31 > 0).
Point Kriging will be employed instead of Block Kriging.
Nearest Neighbor Kriging
An extra line is added in the run file:
CMD = USE NNK #samples factor

where

USE NNK keywords, #samples is the nearest number of samples to utilize (>0), and factor is the smoothing correction factor (min=0,
max=1).
If #samples = 1, the nearest sample will have the most influence on the block grade. If factor = 0,
maximum smoothing is achieved (like ordinary Kriging). If factor = 1, there is no smoothing (like the polygonal approach).
NOTE: Block Discretization is not available for Nearest Neighbor Kriging if the Dynamic Unfolding option is used (IOP31 > 0).
Simple Kriging
Simple Kriging can be performed by setting:
IOP17=5
PAR30 = mean grade of the area to be kriged.
Without these parameters, the program performs ordinary Kriging.
The program also allows you to use the mean of composite data within a specified distance,
instead of PAR30, for simple Kriging. The distance is specified in PAR5.
In order to use a mean value from the model add the following CMD line:
CMD = label-15 FOR SK MEAN
The value stored in the item will be used as the mean value. If no value is stored in the item, the mean value from PAR30 will be
used by default.
Simple Kriging can only be performed on one item in the model.
NOTE: Block Discretization is not available for Simple Kriging if the Dynamic Unfolding option is used (IOP31 > 0). Point
Area Influence Kriging
An extra line is added in the run file:
CMD = USE AIK factor

where
USE AIK keywords,
factor is the proportion of area of influence. If this proportion is 1.0, a sample will have 100% influence to the blocks within its area
of influence. However, that does not mean that the blocks will be assigned the grade of the nearest sample.
NOTE: Block Discretization is not available for Area of Influence Kriging if the Dynamic Unfolding option is used (IOP31 > 0).
VII. Specification of percent and grade above cutoff
The program can optionally calculate and store both the percent and the grade of ore above a specified cutoff using lognormal short
cut technique.
a) Percent or proportion of tonnage above cutoff

Enter the following command line in your run file:
CMD = label-15 IS PERCENT ABOVE CUTOFF

where
label-15 =the label of mine model item to store the result

IS PERCENT ABOVE CUTOFF = keywords for the program
NOTE: Replace PERCENT by PROPORTION if you want the numbers stored from 0 to 1.0 instead of 0 to 100.
b) Grade of ore above cutoff

Enter the following command line in your run file:
CMD = label-15 IS GRADE ABOVE CUTOFF
For any of the above command lines, enter the following parameters:
PAR19 = CUTOFF GRADE TO BE USED FOR CALCULATIONS

IOP18 = 0 IF THE GRADES WITHIN BLOCKS ARE ASSUMED TO BE
NORMALLY DISTRIBUTED
= 1 IF THE GRADES WITHIN BLOCKS ARE ASSUMED TO BE
LOGNORMALLY DISTRIBUTED
(Default for IOP18 = 0 if CALC KRIGE is used, = 1 if ALOG is used)
Although a kriging estimation error is calculated for each block, the program will not store the result unless the following
command line is specified:
VIII. Storing kriging estimation error
ITMn = label-15 BLOCK ERROR

where
label-15 = the label of mine model item to store estimation error

BLOCK ERROR = keywords for the program
NOTE: The estimation error can be stored in six different ways. This is specified in IOP20 in your run
file. Relative kriging variance = kriging variance divided by the square of the estimated grade.
Combined Variance = square root of the result of local variance multiplied by Kriging variance
where local variance of the weighted average (2 w) is:
2 w = w2i*(Z0 - zi)2 i = 1, n(n>1)

where n is the number of data used,
wi are the weights corresponding to each datum,
Z0 is the block estimate,
and zi are the data values.
Relative Variability Index = square root of combined variance divided by the Kriging grade.
Sample Run File #1 demonstrates the use of this option as described above.
If the following lines are used instead, then items can be stored simultaneously:
CMD = STORE KRGVR INTO label-15 option#
for storing kriging variance

and
option# = 0 for storing variance
1 for storing standard deviation

2 for storing relative variance
CMD = STORE COMVR INTO label-15 option#
for storing combined variance

and
option# = 0 for storing variance
1 for storing standard deviation
2 for storing RVI
3 for storing local error variance
CMD = STORE SKWTS INTO label-15
for storing the sum of simple kriging weights
CMD = STORE RGSLP INTO label-15
for storing regression slope
IX. SCAN 2-D: 2-D (X and Y ) coordinate search
To interpolate GSM or 2-D surface data, the coordinate selection must be based on X and Y coordinates only without regard to any
bench elevations. If this is the case, then use one of the following commands in your run file depending on which source is appropriate.
ITMn = CARD DATA INPUT SCAN2-D (ASCII input data) OR

where
CARD DATA INPUT = Keywords for the program indicating that input is from an ASCII file
SCAN2-D = Keywords for the program indicating a 2-D coordinate search
X. SCAN1-D: Interpolating the seams that branch
When interpolating into the GSM, there may be seams that branch and need to be modeled separately. Use the following command:

where
SCAN1-D = Keyword for the program indicating a SCAN1-D search
NOTE: Replace keyword FILE with CARD if input is from an ASCII file. See Input from an ASCII File
section for more information.
The SCAN1-D option allows you to define which codes will be used by allowing up to four additional (alias) codes to be read on
the Area Specification Lines.
M620V1 Sample Run File #16 demonstrates the use of this option.

XI. Search from mid-point of the bench
Normally, when bench composites are calculated with M501V1, the elevations that are stored for the bench are the elevations.
However, there is an option to store bench midpoint elevations in the composite file. If this option is used, you must specify the
following interpolation option to correctly search for the composite elevation.
CMD = ELEV ZMID

where
ELEV ZMID = Keywords for the program indicating the need to search from the mid-point of the bench
XII. Handling of blocks that are not interpolated
The disposition of blocks is controlled by using one of the following commands:
RUN = RESET Reset uninterpolated blocks to missing (default)

RUN = ZERO Reset uninterpolated blocks to 0.0
RUN = OMIT Leave uninterpolated blocks as they are
The RUN=RESET or RUN=ZERO commands should be used for the new interpolation results to supersede the existing values.
The RUN=OMIT command should be used when doing multiple program runs (e.g., if you interpolate different geologic zones
with corresponding interpolation parameters). RUN=RESET will reset all blocks in an interpolation run regardless of model codes.
XIII. Matching composite vs block geology codes
Geologic matching can be done only if the pertinent geologic codes or rock types are stored in both File 8 and File 15. For a single
geologic match, include the following lines in your run file:
IOP4 = 1
where
label-15 = Label of model item for geologic codes

label-08 = Label of composite item for geologic codes
For geologic matching of two different items in File 8 and File 15, include the following lines in your run file:
IOP4 = 2
ITMn = label1-15 label1-08 MATCH MODEL
ITMn = label2-15 label2-08 MATCH MODEL
where
label1-15 = Label of 1st model item for geology codes

label1-08 = Label of 1st composite item for geology codes
label2-15 = Label of 2nd model item for geology codes
label2-08 = Label of 2nd composite item for geology codes
NOTE: The program can MATCH on codes with values up to 999999. MATCHing and aliasing will
work for 0 block codes and you can now alias a 0 code to some other value. A maximum of 5
geologic matchings is allowed.

XIV. Assigning and matching geology codes
If the geology codes are stored in File 8, but not in File 15, it is possible to assign model geology and match geologic codes during
the interpolation run using polygonal assignment of composite geology. To do this, include the following lines in your run file:
IOP4 = 1
where
label-15 = Label of model item for geology codes

label-08 = Label of composite item for geology codes
MATCH POLYG = Keywords for the program indicating polygonal geology assignment and matching
NOTE: The precision of the geology item in both the composite and model files must be equal to 1.
During the interpolation, the program will assign a code to each block based on the geology code of the
nearest composite. It will then proceed with the standard matching of composite and model geology codes.
This option can only be used with BLOCK LIMIT when different model items are used for each option.
XV. Interpolate selected geology types
Interpolation can be limited to certain mine model blocks based on geology codes or rock types. The precision of the block codes
must be equal to 1. To do this, use the following lines in your run file:

where
BLOCK LIMIT CODES = Keywords for the program indicating the option for block limiting.
V1, V2 ... Vn = Integer codes from 1 to 9999999999 (10-digits) can be used for block limiting.
More than one code line may be entered if needed.
label-15 = Label of model item with geology codes
BLOCK LIMIT = Keywords for the program indicating the option for block limiting.
For limiting on two different items in File 15, include the following lines in your run file.
ITM# = label-15 BLOCK LIMIT/ 1st block limit

ITM# = label-15 BLOCK LIMIT/ 2nd block limit
CMD = BLOCK LIMIT label-15 V1 V2 V3 . . .Vn/ 1st block limit
CMD = BLOCK LIMIT label-15 V1 V2 V3 . . .Vn/ 2nd block limit
A maximum of five items can be used for geologic limiting per run.
XVI. Using alias geology codes
Use this option to interpolate some blocks with certain geologic codes using composites that have different geologic codes. This option
allows you to assign alias (assumed) geology codes to the blocks to be interpolated so that they can be treated under the assumed
code. Suppose you have blocks coded 1, 2, 3 and 4, and composites coded 1 or 2. To interpolate code 1 and 3 blocks with code 1
composites and code 2 and 4 blocks with code 2 composites, use the alias option. First, include BLOCK LIMITing and MATCHing
options in your run file. Then set the following options:

IOP14 = 0 to alias both composite and model codes and

IOP13 = n
where n is the number of cross reference codes to alias block codes. Next enter another line following the END line in your run file
specifying the cross reference codes (n). A maximum of 10 cross reference codes per line is allowed. If IOP13=1 through 10, one
cross reference line is read. If IOP13=11 through 20, two cross reference lines are read.
For the above example, set IOP13=4 and put 1 2 1 2 after the END line in your run file. The 1 2 1 2 indicates that composites with
code 1 are used to interpolate the blocks with codes 1 and 3, and composites with code 2 are used to interpolate the blocks with
codes 2 and 4.
There is an alternate format (IOP13=1) to input alias codes after the END line using actual, alias pairs. This is useful when you
wish to alias only a few, widely separated codes, for example, to interpolate blocks coded 6 and 12 with composites coded 1, include
this line 6,1 12,1 after the END line.
XVII. Relative coordinates specification
Enter the following commands in your run file if the relative coordinates are to be used during the interpolation:

CMD = RELX IS label-08 label-15
CMD = RELY IS label-08 label-15
ELEV (RELX, RELY) IS = Keywords for the program indicating to use the relative coordinates

NOTE: This option can be used for 3-D models. The option cannot be used when usingASCII input data.
The program will first test PAR1, PAR2, and PAR3 against the differences between true (original)
composite and block Northing, Easting and Elevations. Select PARs 1, 2, and 3 in such a manner
so that the difference in the original coordinates of a compsite and a block guarantees the desired
difference between the composite relative coordinate and the relative coordinate value of a block.
Further search limitation (as PAR4) will be used against the relative composite and block
coordinates.
PAR20 = Optional search distance for the elevation range (Default = PAR3)

NOTE: PAR3 is still applied to the original elevations (both for composites and blocks). Program
applies PAR20 to the relative elevations.
XVIII. Use of special weighting factor
Enter the following command to weight the composites by a special weighting factor:
where
label-08 = Label of the composite item to be used for weighting
FACTR = Keyword for the program indicating the special weighting factor option
If this option is used, the program will multiply the kriging weight of the composite by the corresponding value of the weighting
item for that composite before computing the adjusted weights.

NOTES: 1) This option cannot be used if CARD input is used. The values of the weighting item cannot be zero or
undefined.

XIX . ITM lines for values to be computed & stored
To execute ordinary kriging enter this command: ITMn = label-15 label-08 CALC KRIGE
To execute lognormal kriging enter this command: ITMn = label-15 label-08 ALOG KRIGE
The following optional ITM lines that have Keywords can be used in the run file to store the number of composites used to interpolate
each block, the number of drillholes used for each block, the distance to the closest composite for each block, the distance to the
farthest composite for each block, and/or the average distance from the composites for each block:
ITMn = label-15 BLOCK CALC #COMP NCOM / Stores the number of composites used to interpolate each block
ITMn = label-15 BLOCK CALC #COMP NDHO / Stores the number of drillholes used per block
For example,
where
label-15 = Label of model item to store # of composites used to interpolate a block
BLOCK CALC #COMP NCOM = Keywords for the program
Sample Run Files #7 demonstrates the use of these options.
NOTE: You may optionally select composites by specifying RANGE, OMIT or TABLE.
XX. To limit the number of composites used to interpolate a block
The minimum and maximum number of composites used to interpolate a block can be specified in the run file using IOP7 and IOP16.
For example, to interpolate a block with a minimum of four composites to a maximum of 18 composites, use the following lines in
your run file:
IOP7 = 4
IOP16 = 18
NOTE: IOP7 will work only if the distance to the closest composite is greater than PAR8. To use only
the minimum number of composites criterion, then specify PAR8 = a small number (such as .01)
XXI. To limit the number of composites from an individual hole
The number of composites used to interpolate a block from an individual hole can be limited with IOP19. For example, to use no
more than three composites from an individual hole, set IOP19=3 in your run file. If IOP19=0 (default), there is no limitation on the
number of composites used from an individual hole.
NOTE: The use of IOP19 will increase the computing time for interpolation.
XXII. The selection of the composites used in interpolation
Composites used in interpolation can be selected using RANGE, OMIT or TABLE with the ITM command. See ITM commands in
the Introduction, Vol. I, for an explanation of their use.

Sample Run File #7 demonstrates the use of these options.
XXIII. Input from an ASCII file
The composite assay data input to the interpolation programs is normally from MineSight Data File 9 (or 8) or from an MSTorque
database. However, the programs are also designed to read data from an ASCII file. To use an ASCII input file, follow the steps below:
1. Include REF# (or DHID), X, Y and Z coordinates (if 3-D interpolation), and a grade item on each line of input.
2. Include 8=CARD in the NAMES LINE of your run file. Also include 19=filename if the data is in a separate file
3. Also include the following lines in your run file.

INP8 = REF# EAST NORTH ELEV. value1 ... geol1
where
REF#, EAST, NORTH, ELEV. = Keywords for the program (not necessarily in this order)
value1, value2, etc. = Grade items to be interpolated
geol1, etc. = Geology items to be interpolated
The format of the data in the ASCII file is free field format.
On the INP8 line, you must specify the column names for all the columns in the ASCII file (max allowed number of columns
is 99). To skip a column, enter DUMMY as a column header, or enter a name that is not used as an input item.
4. The following line is optional and can be included to specify a CALC items minimum value. Otherwise the minimum is
assumed to be zero.
CMD=CALC MINn value

where
CALC = keyword
MINn = indicates which CALC item from the INP line is being set
value = the minimum value
For example:
INP8 = REF# EAST NORTH ELEV. TOPO ROCK

CMD = CALC MIN2 7
will set the minimum value of ROCK (the second CALC item) to 7.
If composite data lines are included within the run file, only one Area Specification Line can be used.
XXIV. Multiple Variogram Specification
Multiple variograms are used for two cases.
CASE 1 - There are multiple items to krige and each item has its own variogram, e.g., kriging gold and silver grades with the same
run file but having different variograms for gold and silver.
Warning: When kriging multiple items, the program assumes that the same number of composites are avalable for the secondary
items as for the primary item. In other words, inconsistent missing intervals such as a missing value for one item but not the other
ones, will produce erroneous results.

CASE 2 - Only one item is to be kriged but there are different variograms for each geologic unit, e.g., kriging gold grades with a
different variogram for each rock type. For this case, the label of the geologic item must be specified with either of the following
commands:
ITMn = label-15 label08 MATCH MODEL
ITMn = label-15 BLOCK LIMITand CMD=BLOCK LIMIT CODES V1 V2 . . . Vn
In both cases, parameters for multiple variograms are entered through an external input file. The variogram parameter file name
is entered in the run file on the names line as 30=filename. When there is a file name specified in the run file, the program will
automatically look for this file and try to read it. Any variogram parameter specified in the run file through the CMD function is
ignored. Examples of the variogram file for each case follow.
NOTE: There has to be one set of variogram parameters specified for each item to be kriged even when
the variogram parameters are the same for more than one item. As many as nine items or geologic
codes can be kriged simultaneously. However, the total number of model items to be stored cannot
exceed ten.
CASE 1 - The lines of a variogram parameter file are as follows:
Line #1: Description or comment line

Line #2: Nugget value for the first item
Line #3: TYPE SILL R1 R2 R3 ROTN DIPN DIPE
or
TYPE SILL R1 R2 R3 ROT1 ROT2 ROT3 GSLIB
or
TYPE SILL R1 R2 R3 0.0 0.0 0.0 COORD filename,
where
TYPE = Variogram type: 1=Spherical, 2=Linear, 3=Exponential, 4=Gaussian

SILL = Sill of the variogram excluding the nugget value
R1
R2
R3 The same as specified earlier in this documentation
ROTN, DIPN, DIPE = MEDS rotation angles
ROT1, ROT2, ROT3 = GSLIB rotationa angles
filename = the name of the file with coordinates of points specifying rotation

Rotation angles should be entered either with respect to model coordinates for ALL variograms (default), or with respect to project
coordinates for ALL variograms. To enter angles with respect to project coordinates, add command in the run-file:
CMD = VGM PROJECT (see section V of the current documentation)

Line #3A, #3B Optional (Nested variogram parameters if necessary)
Line #4: 0 or -1: End of the variogram parameters input
Line #5, #6, #6A, #6B, #7 Repeat of Lines 2-4 for the variogram parameters to be used for krig item #2.
NOTE: Specify a set of variograms for each item to be kriged. For example, if five items are to be kriged,
there must be five sets of variogram parameters.
If there are more variograms than the number of kriging items, the program ignores the extra
variograms. However, if there are more kriging items than variograms, the program stops with
an error message. The maximum number of variograms is 9.
Calculation information stored in model items will be for the first kriging item. Options affected
are:

BLOCK ERROR
BLOCK CALC #COMP
BLOCK CALC RINGS
IS PERCENT ABOVE CUTOFF
IS GRADE ABOVE CUTOFF
CASE 1 - Sample variogram parameter file:
Parameters for items LEAD, ZINC, SILV, TCU Comment Line

.0013 Nugget value
1 .0245 150 120 60 0 0 0 Parameters
0 End of input
.008 Nugget value
0 End of input
.0031
1 .0088 120 120 80 0 0 0
0
.0072
2 .0519 240 240 240 0 0 0
0
CASE 2 - The lines of a variogram parameter file are as follows:
Line #1: VARITM = label-15(Identifies item to be used and signals that this is Case 2)
Line #2: Nugget value for the first geologic codeInteger geologic code
Lines #3, #3A, #3B, #4 are the same as Case 1.
Lines 24 repeat for the remaining geologic codes.
CASE 2 - Sample variogram parameter file:
VARITM = Rock Item to use

.0013 2 Nugget value; geologic code
1 .0245 150 120 60 0 0 0 Parameters
0 End of input
.008 5 Nugget value; geologic code
0 End of input
.0031 10
1 .0088 120 120 80 0 0 0
0
XXV. Use of a boundary file
The digitized boundary of an area may be used to define the blocks that will be interpolated. The boundary will be used to determine
a minimum and maximum column to be kriged in each row. The boundary must be contained in its own file; this file is entered using
the following line:
NOTE: 1) Any block that is inside or touching the boundary will receive interpolated values.
2) All files must have a single point of each line in Easting, Northing order.

3) This option is not available for rotated models.
There are three types of input for a boundary file, with the header line defining each type:
1) Boundary in VBM point file format has a numeric plane number in the header.
3000 1002
13510.20 12006.20
13384.50 11820.40
. .
13510.20 12006.20
0.00 0.00
2) Boundary in Survey file format with BNCH in the header. Keyword SBND is for Survey.
BNCH 3000 SHOT#909

SBND 1 13510.20 12006.20
SBND 2 13384.50 11820.40
. . . .
SBND 71 13510.20 12006.20
3) Boundary in M122-IGP overlay format with IDENT in the header. Keyword POINT is for IGP.
IDENT 0 1 3000.0
POINT 1 13510.2 12006.2 3
POINT 1 13384.5 11820.4 2
. . .
POINT 1 13510.2 12006.2 2
POINT -1 0.0 0.0 0
NOTE: Easting values start at column 13 or greater.
XXVI. Option to override coordinate items.
By default, coordinate items in a composite file are EAST, NORTH, and ELEV. (note the dot of the elevation item label).
To override any of those items, (e.g., use XBOT, YBOT, ZBOT) use the following commands:
For easting:
CMD = XCRD label-08
For northing:
CMD = YCRD label-08
For elevation:
CMD = ZCRD label-08
NOTE: The last command is required when SCAN2-D option is used with inclined models.
XXVII. Option to override/enter controlling seam item.
By default, seam numbers are read from the controlling Z item in the PCF.

When using MSTorque composites you have to specify the attribute that was used as seams. In MSTorque the seam attribute has
Enumerated type; the code values of the attribute must match the seam numbers in the PCF.
The command:
CMD = SEAM label-08
will override the controlling seam item stored in the PCF, and use label-08 as the item with seam numbers.
XXVIII. Negative Kriging Weights option
Use
CMD = NEG KRIGE WTS 1
If you want the negative kriging weights to be set to zero only when the block value estimated is below the minimum value set in
the model file. If this happens, the sum of all other weights is normalized to 1.
Use
If you want the negative kriging weights to be always set to zero and the sum of all other weights to be normalized to 1
Use
if you want to remove the samples with negative weights. The program will recalculate the kriging matrix and the weights, and it
will continue until no more negative weights are encountered within tolerance. This option is only available for Ordinary Kriging.
Tolerance (optional):
If the negative weight is below the tolerance, the sample is removed. The tolerance should be a negative value. Suggested tolerance
is -0.001 to tolerate samples with negligible weights.
XXIX. Storing dilution/smoothing measure

where
Block and DIL% are keywords, label-15 is the item to store the dilution. The item values will be between 0 and 100. If this item
is not specified, then no calculation is done.
The dilution% is equal to ((SWTDIF/BLKGRADE) * 100)/SQRT(N)

where
SWTDIF = sum of weighted absolute differences between the block grade and the composites used that are below the block
grade when the block grade is above the cutoff and N = total number of composites used to calculate the block estimate.
and
Cutoff is the value that the dilution or smoothing measur ecalculation is based on. If the cutoff is zero, then the calculation
is done using all the composites for the block without applying a cutoff. The result is then a measure of how well the nearby
composites match to the calculated block value.
XXX. Dynamic Unfolding Option
Prerequisite: You must have an RSI object file available in the \_msresources folder

Dynamic Unfolding is an on the fly calculation of two distances between composites and model blocks: normal to a specific
surface and a geodesic distance (shortest distance) along the surface. These distances are used in place of Euclidean distances
in IDW and Kriging calculations. You may want to use Dynamic Unfolding if the grade intensely follows a known surface. The
RSI object corresponding to one surface or a pair of surfaces must be created in MS3D beforehand.
A Fast Marching Result (FMR) file can be prepared in MS3D beforehand as well. You can also generate an FMR file from a RSI
file using specified parameters.
There are several options how to use dynamic unfolding:
IOP31 = 1 USE DYNAMIC UNFOLDING WITH EXISTING FMR FILE


where filename.fmr is prepared beforehand.
IOP31 = 2 RUN FAST MARCHING, CREATE NEW FMR FILE AND USE DYNAMIC UNFOLDING
This option requires the following command lines:

where filename.fmr is a name of fmr file to be created and used to calculate unfolded distances.
CMD = RSI FILE [filename.rsi]

where filename.rsi is a name of existing RSI object files in _msresources folder in the project directory. If it is located in
a subfolder in \_msresources, then the subfolder name has to be included in the filename.rsi (e.g. myrsicollection\surf.
rsi).
CMD = FMR PAR F1 F2 F3 F4 F5 <F6 F7 F8>

where the following Parameters for Fast Marching have to be specified:
F1 and F2 - lower and upper limiting of composites by relative Z from the RSI file. If RSI file is generated from a
single surface, the Rel-Z is a signed distance to that surface. In case of two surfaces the Rel-Z values are between 0 and
1;
F3 - Fast Marching Grid size (it is recommended to make it greater then the max of DX,DY and DZ sizes for a block);
F4 - Fast Marching Grid Range (it has to be greater then the maximum 3-D search distance [PAR4]);
F5 - Size of Euclidean Region (Distances within the Euclidean Region are measured directly, without unfolding. The
size of the Euclidean region is expected to be multiple of the grid size. It will be automatically rounded by the program
to the nearest multiple of the grid size and set to be at least one grid.).
F6 = 0 - dont use Reference North (default) if F6 is not present or it is 0, then F7 and F8 are not used and not
required;
= 1 - use Reference North (this means that azimuths of geodesic directions are counted from the Reference North
direction defined by parameters F7 and F8. This direction should be almost tangent to the surface in all points. You need
geodesic azimuths and the Referecne North (F7 and F8) direction to use an anisotropic search and/or variograms with
any anisotropy along the surface.);
F7 - Azimuth of Reference North direction;
F8 - Dip of Reference North direction;
IOP31 = 3 RETRIEVE PARAMETERS FROM EXISTING FMR FILE, RE-CREATE FMR FILE AND USE DYNAMIC
UNFOLDING

where filename.fmr is the name of the fmr file where the parameters will be retrieved from and is the file that will be
overwritten after re-running Fast Marching.
END This end card must come at the end of any options selected from this section.
1. CROSS REFERENCE LINES (for alias geology codes, if IOP13>0)
If IOP13>0, read 10 integer codes per line in free-field format, where the first line contains the alias codes for actual codes, 110,
the second line contains the alias codes for actual codes 1120, etc.
For example, if IOP13=5 (block codes are 1 to 5) and if 1 1 3 3 3 are input for cross reference, then data with geologic codes 1 and
2 will be used as the same type and codes 3, 4 and 5 will be used together.
If IOP13 = 1, read up to 5 alias pairs per line in a free-field format as actual, aliasactual, alias . .; input is terminated by a 0, 0
as the first pair of a line.
For example, if actual codes 98, 99, 108, and 109 will be used as code 1, actual code 0 will be used as code 5 and other actual codes
will be used as is, the entry could look like:
98, 1 99, 1 108, 1 109, 1

0, 5
0, 0
The 0, 5 pair could also be included in the first line to make 5 pairs. Do it whichever way is the clearest.
IX1 IX2IY1 IY2IZ1 IZ2 comp1 comp2 comp3 comp4
where comp1-n are optional composite codes for controlling split seam interpolation. See SCAN1-D and M620V1 Sample Run
File #16. The run will end on an end-of-file condition. A blank line or zero will default to the PCF limits and interpolate the entire
block model.
If Composite Data Lines are included within the run file, then only one Area Specification Line can be used. If Composite Data Lines
are in a separate file, include a 19=filename in the Names Line.


* SAMPLE ORDINARY KRIGING INTERPOLATION *
USR = ABC
RUN = RESET
COM
COM
COM - 3-D SPHERICAL SEARCH WITHIN RECTANGULAR BOX


CMD = NUG 0.01

CMD = SPH 0.14 600 600 600 0 0 0
ITM1 = TCU-K T-CU CALC KRIGE

ITM2 = E-ERR BLOCK ERROR
END
30 30 25 25 20 20


USR = ABC
RUN = RESET
COM
COM
COM - USE ELLIPSOIDAL SEARCH

COM - ASCII DATA INPUT


COM* ELLIPSOIDAL SEARCH

COM* (MAJOR AXIS SW-NE, PLUNGING 35 DEGS @ N45E)
COM* (MINOR AXIS NW-SE, DIPPING 35 DEGS @ S45E)
COM* (HORIZONTAL ANISOTROPY RATIO = 2:1)
COM* (VERTICAL ANISOTROPY RATIO = 3:1)
CMD = SEARCH 180 90 60 45 -35 -35

CMD = NUG 0.01
CMD = LIN 0.07 360 180 120 45 -35 -35
ITM1 = TCU-K T-CU CALC KRIGE I

END
33 33 25 25 20 20
30 DH-43 13350. 12550. 3500. 0.058
32 DH-56 13150. 12350. 3700. 0.092
34 DH-62 13200. 12500. 3650. 0.126
35 DH-63 13300. 12400. 3550. 0.402
36 DH-65 13350. 12550. 3700. 0.312
39 DH-61 13300. 12400. 3650. 0.201


MEDS-624V1 3=RPT624.LC
USR = ABC
RUN = RESET
COM
COM
COM ** STORE GRADE ABOVE 0.5 CUTOFF

COM ** STORE PROPORTION OF TONNAGE ABOVE CUTOFF

IOP18 = 1 / DISTRBTN OF PTS IN BLOCKS 0=NORMAL,1=LOG.

PAR19 = .50 / CUTOFF FOR T-CU
CMD = NUG 0.01

CMD = SPH 0.12 700 700 700 0 0 0
CMD = EQ-CU IS GRADE ABOVE CUTOFF

CMD = EXTRA IS PROPO ABOVE CUTOFF

END
30 30 25 25 20 20


MEDS-624V1 3=RPT624.LD
* SAMPLE LOGNORMAL KRIGING INTERPOLATION *
USR = ABC
RUN = RESET
COM
COM
COM ** LIMIT COMPOSITE ROCK TYPES


CMD = NUG 0.01

CMD = SPH 0.12 700 700 700 0 0 0
ITM1 = TCU-K T-CU ALOG KRIGE

ITM3 = ROCK OMIT 2 2
END
30 30 25 25 20 20


MEDS-624V1 10=SAMP10.DAT 13=SAMP13.DAT 8=DUMMY;
MEDS-624V1 3=RPT624.LE 19=SAM620.IB 15=DUMMY.DAT
* SAMPLE UNIVERSAL KRIGING INTERPOLATION *
COM
COM
USR = ABC
RUN = RESET
DOC ** INTERPOLATE SOILZ IN FILE 13 - USE TOPO FROM M657V1
COM NOTE: SAM657.A2 RUN FILE CREATES SAM620.IA

COM WHICH IS SORTED INTO SAM620.IB


CMD = NUG 0.01

CMD = SPH 1.00 1500 1500 1500 0 0 0
CMD = UNIV KRIG ITEM NORTH

CMD = UNIV KRIG ITEM EAST
ITM1 = SOILZ TOPO CALC INVWT

INP8 = NORTH EAST TOPO REF#

ALF1 = COORD COORD CALC REF#
FMT1 = (2F9.0,F6.0,F4.0)
I-O = 1
END
1 50 1 50 1 1


MEDS-624V1 3=RPT624.LF
* SAMPLE UNIVERSAL KRIGING INTERPOLATION *
USR = ABC
RUN = RESET
COM
COM
COM ** SELECT COMPOSITE ROCK TYPES

IOP16 = 5 / MAX # COMPS FOR KRIGING A BLOCK
IOP17 = 0 / 0=BLOCK, 1=POINT KRIGING

CMD = NUG 0.01

CMD = SPH 0.14 600 600 600 0 0 0
CMD = UNIV KRIG ITEM ROCK GEOL

END
30 30 25 25 20 20


MEDS-624V1 3=RPT624.LG 30=VPARAM.INP
COM
COM
COM - COMPLEX RUN FILE / VARIOGRAM INPUT FROM VPARAM.INP
USR = ABC
RUN = RESET

IOP4 = 1 / 1=ONE GEOLOGIC MATCHING, 0=NO MATCHING
IOP20 = 2 / 2=STORE RELATIVE KRIG. VARIANCE
IOP31 = 3 5 6 8 10 12 15 16 / ACCEPTABLE DH REF#S

CMD = SEARCH 800 750 600 90 0 0

CMD = BLOCK LIMIT CODES 1

ITM2 = TCU-P T-CU CALC POLYG
ITM3 = MO-K MOLY CALC KRIGE
ITM5 = CODE BLOCK LIMIT
ITM8 = EXTRA BLOCK CALC #COMP NCOM
ITM9 = LNGTH RANGE 5.0 50.0
ITM10 = SP.GR OMIT 2.5 5.0
ITM11 = REF# TABLE 31 38
END
33 33 25 25 20 20


COAL-624V1 10=COAL10.DAT 15=COAL15.DAT MSTorque
8=COAL08.DAT; access
COAL-624V1 3=RPT624.LA
* KRIGING INTERPOLATION OF SAMPLE PROJECT MODEL *
USR = ABC
RUN = RESET
COM
COM
DOC ** INTERPOLATE SULFUR FOR SEAM# 2


CMD = NUG 0.08

CMD = SPH 0.30 4000 4000 4000 0 0 0
ITM1 = SULF SULF CALC KRIGE
END
1 72 1 96 2 2


MEDS-624V1 10=msop10.dat 8=TORQ 15=msop15.all 19=mstorq.inf;
MEDS-624V1 3=rpt624.ok 31=DUMMY 30=
** 3-D model CUKRG interpolation - Ordinary Kriging
RUN = RESET
USR = / Wed Jun 1, 2011 4:11:18 PM US Mountain Standard Time

IOP11= 0 / Row # for extended debug output
IOP16= 8 / Max.# of composites for interpolating a block

PAR3 = 7.5 / Primary Z-search distance
CMD = NUG 0.1

CMD = SPH GSLIB 0.9 500. 500. 500. 0. 0. 0.
ITM1 = CUKRG CU CALC KRIGE

CMD = ELEV ZMID

END
000000


MEDS-624V1 10=msop10.dat 9=msop09.dat 15=msop15.dat;
MEDS-624V1 3=rpt624.cok 30=vario.cok
* 3-D model CUKRG interpolation - Cokriging *
RUN = RESET
USR = / Mon Mar 5, 2012 4:37:02 PM US Mountain Standard Time

IOP11 = 0 / Row # for extended debug output
IOP15 = 12 / Max.# of composites for secondary item
IOP16 = 8 / Max.# of composites for primary item
IOP20 = 0 / 0=Store Variance, 1=Std dev, 2=Relative Variance
IOP28 = 1 / 0=If the estimated grade is greater (or less) than
COM the max (or min) value of the composites that were
COM used to estimate the block, set the block value to
COM the max (or min) and store.
COM / 1=Store as is.
PAR1 = 400 / Primary X-search distance

PAR2 = 400 / Primary Y-search distance
PAR3 = 50 / Primary Z-search distance
PAR4 = 400 / Limiting search distance
PAR6 = 100 / Limiting search distance (Secondary item)
PAR7 = 350 / MAX DISTANCE TO CLOSEST POINT
PAR8 = 250 / MAX DISTANCE TO PROJECT SINGLE COMPOSITE
PAR27 = 2 2 1 / block descritization
CMD = SEARCH 400 300 200 15 0 0

CMD = SRCH#2 155 60 80 15 0 0
CMD = CO KRIGE ITEM MO
ITM1 = CUKRG CU CALC KRIGE

ITM2 = dmin1 BLOCK CALC RINGS DMIN / Min dist to data primary item
ITM3 = dmin2 BLOCK CALC RINGS DMIN / Min dist to data secondary item
ITM4 = dmax1 BLOCK CALC RINGS DMAX / Max dist to data primary item
ITM5 = dmax2 BLOCK CALC RINGS DMAX / Max dist to data secondary item
ITM6 = davg1 BLOCK CALC RINGS DAVG / Avg dist to data primary item
ITM7 = davg2 BLOCK CALC RINGS DAVG / Avg dist to data secondary item
ITM8 = ncom1 BLOCK CALC #COMP NCOM / Number data used primary item
ITM9 = ncom2 BLOCK CALC #COMP NCOM / Number data used secondary item
ITM10 = ndhs1 BLOCK CALC #COMP NDHO / Number dhs used primary item
ITM11 = ndhs2 BLOCK CALC #COMP NDHO / Number dhs used secondary item
CMD = ELEV ZMID

END
1 0 1 0 1 30

1. The program will list all the composites within the search window of each interpolated row if I-O=2 is
specified in the run file. The program will also list all the items in the composite and model files, the
total number of blocks interpolated for each row, and other debug information. This option is not sug-
gested when interpolating the entire model.
2. The program will print the location of composites, the distance to the block, and composite grades and
weights for each block interpolated if IOP11 is set to the row# for debug output.
3. If ellipsoidal search is used, then the 3-D distance calculated between a composite and the block will
be the adjusted distance based on the anisotropy ratios. This is the distance that is printed on the output
file when the debug option is on.
4. The difference between PAR7 and PAR8 is very subtle. PAR7 is tested at all times. PAR8 is test only if
the number of composites to interpolate the block is equal to IOP7.
5. Be sure to select composite and model file item labels that are not used as keywords by the program to
execute certain commands.
7. Multiple Area Selection Lines are allowed. The program will interpolate the blocks specified in the
first line, then it will interpolate the blocks specified in the second line and so on. The only exception
is when the ASCII input option is used and the composite data follows the run file.
8. *** M620A1 # POINT EXCEED nnn AT BLOCK xxx yyy will

occur if more than 1500 composites are found in a search around one block. The maximum number
of composites that the program can handle for a single block is 1500. If this number is exceeded, the
program will give an error message and stop interpolating at that block. If this happens, check to see if
you can decrease the X, Y or Z search distances used by the program.
9. If IOP5=1 (use the minimum grade criterion), then PAR9 must be specified. The minimum grade cri-
terion is based on the grade of the composite closest to the block being interpolated. If the grade of the
closest composite is greater than PAR9, then the program uses only the composites whose grades are
greater than PAR9. If the grade of the closest composite is less than PAR9, then the program uses only
the composites whose grades are less than PAR9.
will occur if the minimum column is greater than the maximum column, or the minimum row is
greater than the maximum row, or the minimum bench is greater than the maximum bench.


will appear if you did not specify an ITMn=CALC KRIGE or POLYG.

17. %M621V1: WARNING: You can only check for duplicate points on blasthole projects. IOP21 is
being reset to 0.
IOP21 is applicable to blasthole projects only. There is no need to check for duplicate composites on
non-blasthole projects. If you try to activate IOP21 for a non-blasthole project it will be reset to zero
and the program will continue normally.
18. Also check the MineSight error messages in the Appendix.


MineSight
Proprietary Software: Mintec, inc. M625V1 - GRADIENT INTERPOLATION TECHNIQUE
M625V1 GRADIENT INTERPOLATION TECHNIQUE

M625V1 uses gradients to neighboring points for weighting the M625V1 uses the tangent plane or gradient method to interpolate
sorted composites during interpolation of mine model values. block values in a mine model. Tangent planes are calculated
between all composites and a specified number of neighboring
composites (IOP2). Each plane must satisfy the following
conditions:
the plane must pass through the function value at the
RUN FILE:
point in question (i.e. through the Z (grade) value)
- Search distances or the angles the plane makes with vectors or lines to
ranges
all of the various points in the neighborhood must be
item labels minimized
- Gradient options
The angles are weighted by a function of how far or near the
various neighboring points are from the point of interest.
After the tangent planes are generated, block values are

calculated from neighboring composites (now with gradients).
INPUT: CALCS: Specify how many neighbors are used in this calculation (IOP3).
- PCF - Find the composites
- Mine model file (File 13, - Match block vs geology The gradient information for each composite is evaluated at the
14 or 15) codes block location and the calculation of the block value is weighted
- File 9 or File 8 or - Apply limiting factors by the distance from the block to each composite.
- Geometry codes composites
- Calculate & store grades
Coordinate parameters
- Calculate weights
File 9 (File 8) composites, the ASCII composite file or the
MSTorque composite set. These parameters may come from
deposit experience.
OUTPUT:
- Updated Model File 1. The primary coordinate selection is usually based upon the
- Printer Output File range of ZTOE - PAR3 to ZTOE + PAR3, where ZTOE is
the toe elevation of the bench to be used.
this selection is not used. However, set PAR3 to be a small
non-zero value (e.g. 0.1).

range of YMID - PAR2 to YMID + PAR2, where YMID is
the midpoint northing of the row to be used. Eastings are in
the range XMIN - PAR1 to XMAX + PAR1.
The composites selected for the entire row are kept in program
memory while interpolating the blocks in that row. Currently,
the maximum number of composites that the program can handle
for a single row is 64,000. If this limit is exceeded, the program
Revised: 26-October-11 Page 625-1

MineSight
M625V1 - GRADIENT INTERPOLATION TECHNIQUE Proprietary Software: Mintec, inc.
will stop with an error message. To bypass this problem, limit

the number of columns interpolated by a single run.
Page 625-2 Revised: 26-October-11

MineSight
M625V1 - GRADIENT INTERPOLATION TECHNIQUE
RUN FILE OPERATION

MEDS-625V1 10=filename 9(or 8)=filename 15(or 14 or 13)=filename;

where

8 = the name of the SORTED COMPOSITE FILE (obsoleted) -OR- CARD for ASCII input -OR- TORQ for input
from MSTorque
15= the name of the MINE MODEL FILE -OR-
19= the name of the INPUT FILE WITH COMPOSITES (If 8=CARD) -OR- MSTorque info file (mstorq.inf) (if
8=TORQ is used)
USR= USER INITIALS (e.g. ABC)
IOP2 = NUMBER OF NEIGHBORS FOR TANGENT PLANE CALCULATIONS (default=8; MAX=16)
IOP3 = NUMBER OF NEIGHBORS FOR BLOCK VALUE CALCULATIONS (default=IOP2; MAX=16)
Primary 3-D search parameters defining a box around a block

NOTE: PAR3 not used for SCAN1-D or SCAN2-D. However, still enter a small non-zero value (e.g. 0.1).
These parameters define a rectangular box around the block to be interpolated. This is illustrated in the Technical Section, Figure 1.

MineSight
All of the composites within this rectangular box are checked against the maximum 3D search distance (PAR4). The composites
If there are more than n number of composites for a given block after all the tests, then the composites are sorted by increasing distance.
Only the closest n are retained for calculating the weights. Based on these weights, the grade of the block is computed and stored.
IMPORTANT NOTE: To interpolate GSM or 2D surface data, the coordinate selection must be based on X and Y coordinates only.
If this is the case, then use one of the following command lines in your run file:
ITMn = CARD DATA INPUT SCAN2-D (ASCII Input Data) -OR-

depending on which source is appropriate.
ITM lines for values to be computed & stored:
ITMn = label-15 label-08 CALC INVWT (Inverse Distance Weighting method) -OR-
ITMn = label-15 label-08 CALC POLYG (Polygonal method)
NOTES ON ITM LINES:
1. BLOCK CALC RINGS <keyword> causes the distance to the closest, average, or farthest composite to be stored in the specified
model item, with the specified precision.
2. ALOG INVWT can be used in place of CALC INVWT, if you want to use the natural logarithms of grades instead of the actual
grades.
IMPORTANT NOTE: All of the options available with M620V1 are available with M625V1. See M620V1 documentation
for a full explanation of the options below.

CMD = ELEV ZMID
CMD = XCRD label-09
CMD = YCRD label-09
CMD = ZCRD label-09
CMD = SEAM label-09

RUN = RESET (Reset uninterpolated blocks to missing)

RUN = ZERO (Reset uninterpolated blocks to 0.0)
RUN = OMIT (Leave uninterpolated blocks as they are)

MineSight
where comp1-n are optional composite codes used to interpolate split seams. The run will end with a 0 value for IX1 to IZ2 or on
an end-of-file condition.
See the Technical Section for a complete description of these lines. If Composite Data Lines are included within the run file, then only
one Area Specification Line can be used. If Composite Data Lines are in a separate file, include a 19=filename in the Names Line.

USR = ABC
RUN = RESET
COM
COM TREND PLANE INTERPOLATION
COM
IOP2 = 8 / NUMBER OF NEIGHBORS FOR TANGENT PLANE CALCS

IOP3 = 8 / NUMBER OF NEIGHBORS FOR BLOCK VALUE CALCS
PAR1 = 750 750 50/ X, Y, Z SEARCH DIST
ITM1 = TCU1TCUCALCINVWT
END
32 32 24 24 18 18
1. Multiple Area Selection Lines are allowed. The program will interpolate the blocks specified in the first line, then it will interpolate
the blocks specified in the second line and so on. The only exception is when the ASCII input option is used and the composite
data follows the run file.
2. ?M625V1: ERROR. You have exceeded the maximum number of composites 4000
The maximum number of composites that the program can handle for a single row is 4000. If this number is exceeded, the
program will print an error message and stop interpolating at that row. If this happens, first check if you can decrease the X, Y
or Z search distances used by the program. If you can, then try again starting from the row where the program stopped and see
if this will solve the problem. If it does not, try to specify fewer columns to interpolate by using multiple Area Selection Lines.
3. ?M625V1: ERROR. No file 15, 14 or 13 specified on the NAMES line.


MineSight

You MUST initialize your model file with M601V1 before any other MineSight program can access it.
5. ?M625V1: Summary of RUN Setup ERRORs

NERS = 3 Total ERRORsI
ERSYS = 2 MEDSYS ERRORs
INLZER = 0 MSINLZ ERRORs
IER15 = 0 MEDF15
IER08 = 1 MEDF08
IERPW = 0 MEDPWD
M625V1 encountered 3 errors setting up your run. There will be additional error messages describing the three errors.
6. ?M625V1: ERROR. You have selected BENCH xxx with an AREA SELECTION LINE. However, your model is only
initialized thru BENCH yyy.
The IZ2 on one of your area selection lines exceeds the last initialized bench in your model. If you really want to run M625V1
through bench xxx, then you need to go back and run M601V1 to initialize your model through bench xxx.
7. ?M625V1: ERROR. The AREA specified on the following AREA SELECTION LINE is badly defined.
For example:
IX1 IX2 IY1 IY2 IZ1 IZ2
0 0 23 1 0 0 - in the run file
1 100 23 1 1 40 - with default values for X and Z
In this case, IY2 is less than IY1.
8. ?M625V1: ERROR reading in composite file

Number of lines without ERRORs=YYY
Number of lines with ERRORs=X
X errors were encountered while reading your composite file. To find the questionable composites, try listing your file with
M503V1.



MineSight
Proprietary Software: Mintec, inc. M630V1 - LOAD 2-D SURFACE FILE (FILE 13)
M630V1 LOAD 2-D SURFACE FILE (FILE 13)

M630V1 is used to load topography or other surface data into M630V1 is used to update a 2-D topography matrix. It can also
File 13. It can also be used to update File 13. be used to update any 2-D matrix of data, such as thickness of
overburden or elevations of some horizon within a deposit.
The input can be manually coded data or can be obtained from

PROGRAM FLOW DIAGRAM programs M657V1 and M657V2 if the surface contours have
been digitized and loaded into a VBM file.
RUN FILE:
- X and Y offsets You can specify offset constants so that the topography can be
- Format of input data shifted in easting and northing in terms of column and row
- File 13 item label numbers. The coded matrix data can be at the end of the run file
or in a separate file.
Procedure summary for entry of 2-D matrix
1. Set up File 13 item descriptors with M102TS.

INPUT: CALCS:
2. Initialize File 13 using M601V1.
- PCF - Create or update 2-D
- File 13 matrix
- Input ASCII file - Store in File 13 3. For manual entry, overlay a topography map with the grid
used for the mine model area and manually code the aver-
age topo elevation for each block. Prepare an input file.
(See Topo Matrix Values in the Run File Operation Sec-
tion.)
4. For digitized topography data that is stored in a VBM, run

OUTPUT:
M657V1 and M657V2. A file will be created that is suit-
- Updated File 13 able for entry with M630V1.
5. Load the topography matrix using M630V1.
6. Plot the topography data with M606V1 or M607V1. Check

the data for errors and inconsistencies. Update the raw data
if necessary and reload the topography file.

MineSight
M630V1 - LOAD 2-D SURFACE FILE (FILE 13) Proprietary Software: Mintec, inc.

MineSight
M630V1 - LOAD 2-D SURFACE FILE (FILE 13)
RUN FILE OPERATION


where

19 = the name of the INPUT FILE (If IOP5=1)
IOP1 = X-OFFSET (COLUMNS) ADDED TO ALL INPUT

IOP2 = Y-OFFSET (ROWS) ADDED TO ALL INPUT
IOP4 = # OF TOPO VALUES PER LINE (default=10, max value =20)
IOP5 = 0 INPUT DATA IS IN RUN FILE

= 1 INPUT DATA IS IN A SEPARATE FILE
FMT1 = FORMAT FOR INPUT DATA (default is free format)

NOTE: If input data is from M657V2 output, use (3I3,10F7.1).
PUT13 = LABEL OF TOPO ITEM IN FILE 13
END
4. TOPO MATRIX VALUES (If IOP5=0)
row# col1 col2 values

where
row# = Matrix row number

col1 = First column number
col2 = Last column number
values = Topo values (Do not exceed IOP4)

MineSight

** LOAD TOPO FOR SAMPLE PROJECT; DATA IN SEPARATE FILE **
USR = ABC
IOP4 = 10 / # OF VALUES PER LINE

IOP5 = 1 / 1= READ DATA FROM FILE 19
PUT13 = TOPOG
FMT1 = (3I3, 10F7.1)

END

** UPDATE PART OF FILE 13; DATA IN RUN FILE; OFFSET ROW #S BY CONSTANT **
USR = ABC
IOP1 = 0 / # OF COLUMNS ADDED TO ALL INPUT DATA (X-OFFSET)

IOP2 = 10 / # OF ROWS ADDED TO ALL INPUT DATA (Y-OFFSET)
IOP4 = 5 / # OF VALUES PER LINE (DEFAULT = 10)
IOP5 = 0 / 0= DATA IS IN THIS FILE
PUT13 = TOPOG
FMT1 = (3I3, 5F7.1)
I-O = 2 / 2= LIST FILE 13 ITEMS

END
1 1 5 4350.0 4350.0 4350.0 4350.0 4350.0 Topo Matrix Values
1 6 10 4347.3 4342.7 4338.1 4333.5 4328.9

MineSight

COAL-630V1 10=COAL10.DAT 13=COAL13.DAT 3=RPT630.LB
** UPDATE FILE 13 SEAM VALUES **
USR = ABC
IOP1 = 20 / # OF COLUMNS ADDED TO ALL INPUT DATA (X-OFFSET)

IOP2 = 18 / # OF ROWS ADDED TO ALL INPUT DATA (Y-OFFSET)
IOP4 = 4 / # OF VALUES PER LINE (DEFAULT = 10)

IOP5 = 0 / 0= DATA IS IN THIS FILE
PUT13 = SEAM
FMT1 = (3I3, 4F5.0)
I-O = 2 / 2= LIST FILE 13 ITEMS

END
19 21 24 10. 10. 10. 11.

MineSight
1. M630V1 will automatically output the input values to the Printer Output File. This output can be checked for input or format
errors.
2. The best way to quickly check the 2-D matrix loaded to File 13 is to generate printer grid or contour maps using M606V2 or
M607V2, respectively. Minor updates can be done interactively using M602FS/TS.
3. A list of File 13 items can be output to the screen if the run file contains I-O=2. This may be useful to see what other items are
available in File 13.

Your File 13 must be initialized using M601V1 before any MineSight program can access it.
5. %M630V1: WARNING. Error reading line xx. DATA not used.

There was a READ error when accessing line xx of your TOPO data. Make sure the data on that line conforms to the format
youve selected with the FMT1 command.
6. ?M630V1: ERROR. No TOPO item specified.

You have not specified the File 13 item in which to store your TOPO data. Select the TOPO item using a PUT13 command.

MineSight
Proprietary Software: Mintec, inc. M633V1 - ADD TOPOGRAPHY PERCENT TO THE MINE MODEL
M633V1 ADD TOPOGRAPHY PERCENT TO THE MINE

MODEL
M633V1 uses the 2-D Surface file (File 13) to determine the Topography percent is entered into the mine model by
percentage of each block that is below the ground surface and calculating the percent of each block that is below the ground
stores the percent in the mine model. surface (in File 13) and storing this value in File 15. Only add
topographic percentages to the mine model after the topo matrix
has been created and verified.
PROGRAM FLOW DIAGRAM If you have initialized the topo percent item of the mine model
to 100%, the M633V1 run(s) can be limited to those benches
RUN FILE: that interact with the ground surface. If the topo percent item
- Area selection has not been initialized to 100%, all benches within the mine
- Item selection model must be accessed by M633V1. You may elect to add the
topo to the mine model using several M633V1 runs, since the
calculations are time consuming.
As mining progresses, M633V1 may be used to update the topo

percent in the block model to reflect the new ground surface
resulting from mining. This updating could be performed on an
annual basis when a new pit outline surface topo map is
INPUT: CALCS: produced.
- PCF - Retrieve topography
- File 13 elevation from File 13 M633V1 also allows you to store a code in your model file to
- File 15 - Set topography percent in indicate if the majority of a block is above or below a file 13
File 15
surface (IOP10=1). PARs 11 and 12 specify the codes to be
stored for blocks above and below the surface. By using an item
RANGE command and multiple M633V1 runs you can store
different codes for blocks above different surfaces. For example,
if you have two pits you can store 3 codes: 1) blocks above both
pits; 2) blocks between pits; and 3) blocks below both pits. See
OUTPUT:
Sample Run Files 2 and 3.
- Updated File 15

MineSight
M633V1 - ADD TOPOGRAPHY PERCENT TO THE MINE MODEL Proprietary Software: Mintec, inc.

MineSight
M633V1 - ADD TOPOGRAPHY PERCENT TO THE MINE MODEL
RUN FILE OPERATION


where

15 = the name of the 3-D MINE MODEL FILE
IOP1 = FIRST BENCH ON WHICH TO ADD TOPO (default=1)

IOP2 = LAST BENCH ON WHICH TO ADD TOPO (default=last bench initialized in the model file)
IOP3 = FIRST COLUMN IN MODEL TO ADD TOPO (default=1)

IOP4 = LAST COLUMN IN MODEL TO ADD TOPO (default=NX)
IOP5 = FIRST ROW IN MODEL TO ADD TOPO (default=1)

IOP6 = LAST ROW IN MODEL TO ADD TOPO (default=NY)
IOP7 = OPTION TO ACCESS BENCHES THAT INTERACT WITH SURFACE (If IOP10=0)
= -1 SET ALL BENCHES
= 0 SET ONLY BENCHES ABOVE SURFACE
NOTE: Topography item must be initialized to 100% for IOP7=0 to work.
IOP10 = 0 PUT PERCENT (0-100) IN BLOCK

= 1 PUT INTEGER CODE (PAR11 ABOVE, PAR12 BELOW) IN BLOCK
To enter TOPO% to 3-D model (IOP10=0)
ITMn = label-13 TOPO (Topo item from File 13)

ITMn = label-15 BLK% (% item for File 15)

MineSight
To enter a code to 3-D model (IOP10=1)
ITMn = label-13TOPO (Topo item for File 13)

ITMn = label-15CODE (Code item for File 15)
Optional data selection:

ITMn = label-15 OMIT min-value max.value
PAR1 = CONSTANT TO SUBTRACT FROM TOPOG ELEVATION RETRIEVED FROM FILE 13
PAR11 = CODE ABOVE SURFACE (default=1, omit=1)

PAR12 = CODE BELOW SURFACE (default=2, omit=1)
END

MineSight

** LOAD TOPO TO MINE MODEL **
USR = ABC
IOP1 = 1 0 / FIRST AND LAST BENCHES

IOP3 = 1 0 / FIRST AND LAST COLUMNS
IOP5 = 1 0 / FIRST AND LAST ROWS
IOP7 = 0 / SET BENCHES ABOVE SURFACE
ITM1 = TOPOG TOPO / FILE # 13 TOPO ITEM

ITM2 = TOPO BLK% / FILE # 15 TOPO PERCENT
END

** LOAD THE CODE TO MINE MODEL SAMP15.DAT **
USR = / 07-27-94 13:03:42

IOP10 = 1 / 0=PUT TOPO%, 1 = PUT CODE
PAR11 = 1 /CODE ABOVE SURFACE

PAR12 = 7 /CODE BELOW SURFACE
ITM1 = TOPOG TOPO / FILE # 13 TOPO ITEM

ITM2 = ZONE CODE / FILE #15 TOPO PERCENT
END

MineSight

** LOAD THE CODE TO MINE MODEL SAMP15.DAT **
USR = ABC

IOP10 = 1 / 0=PUT TOPO%, 1 = PUT CODE
PAR11 = 2 /CODE ABOVE SURFACE

PAR12 = 3 /CODE BELOW SURFACE
ITM1 = TOPOI TOPO / FILE # 13 TOPO ITEM

ITM2 = ZONE CODE / FILE #15 TOPO CODE ITEM
END
NOTE: By running Runfile #2 then Runfile #3, you will set ZONE in File 15 to 1 for all blocks above
TOPOG in file 13. Blocks between TOPOG and TOPOI will have ZONE set to 2 and all blocks below
TOPOI will have ZONE set to 3.


Your BENCH/ROW/COLUMN selections, IOP 1 through IOP6, are badly defined. In the above example, note that the Last
BENCH (100) exceeds the Maximum BENCH (52). The Maximum BENCH is the last bench initialized with M601V1, not the
last bench in the model. Also in the above example, note that the First ROW exceeds the Last ROW.
3. ?M633V1: ERROR. No ITEM was entered for BLK% OR

?M633V1: ERROR. No ITEM was entered for TOPO
You have not specified either your %item from File 15 or your topo item from File 13.

MineSight
Proprietary Software: Mintec, inc. M635V1 - CREATE A DIGITAL TERRAIN MODEL
M635V1 CREATE A DIGITAL TERRAIN MODEL

M635V1 will create a Digital Terrain Model (DTM) from an A DTM is a triangular mesh where each point is connected to
ASCII file of input data points. two other points to form a triangle. The elevation or Z attribute
of each of the points in a triangle gives the triangle an orientation
in 3-D space. The DTM surface is a group of connected triangular
planes.
The program will honor breaklines in the input data. A breakline
RUN FILE: is defined as a string of sequential points having the same point
- ASCII input file with codes code that is associated with a line type. For example, a toe would
- Boundary options be this type of point. To accurately represent a surface with
- Plot options triangulation, no triangles should be allowed to form across a
breakline.
The DTM surface limits will be either a convex boundary created

by the extent of the input data or an imposed polygonal boundary.
A polygonal boundary must be clockwise and closed. There are
several types of boundary: a 2-D boundary that is imposed within
INPUT: CALCS: the area of the input data, a 2-D boundary that extends beyond
- Survey data - Create Digital Terrain the area of the input data, or a 3-D boundary. It is important to
- Boundary file Model understand how the boundary may affect the DTM and thus
- Code parameters - Honor breaklines
- Honor boundary
any volume that may be calculated between 2 D.T.Ms.
IOP1 = 1
A 2-D boundary imposed within the input data area limits the
extent of the surface. The Z-value of each boundary point is
determined by the surface it is imposed on; the surface geometry
OUTPUT: is determined entirely by the input data. The program actually
- DTM File will make 2 DTMs, a preliminary DTM to calculate the Z-values
- M122 Plot File of the boundary points and a final DTM that contains the points
- Printer Output File on or inside the boundary polygon and the boundary points.
IOP1 = 2
A 3-D boundary uses all input data within the boundary area.
The Z-value of each boundary point is input; the surface
geometry near the boundary may be substantially altered. The
edge of the DTM is forced to the Z-values of the boundary
without regard to the surface geometry of the input data in the
same area. For example, if 2 different sets of input data used in
the same 3-D boundary, the resulting DTM surfaces would be
pinched together at the edge.
IOP1 = 3
A 2-D boundary that extends beyond the input data area uses all
input data within the boundary. The Z-value of each boundary
point is a linear estimation based on data points that are
connected to it in the triangular mesh; the geometry of the surface

MineSight
M635V1 - CREATE A DIGITAL TERRAIN MODEL Proprietary Software: Mintec, inc.
near the boundary is estimated. This option is suitable to extend

a relatively level surface out to a boundary. It may be used in
underground surveying applications to extend centerline
elevations out to the edge of a stope.
The number of points that can be used in a triangular mesh is

limited to 300,000. If this point limitation is a problem, the
input can be restricted either by a boundary or by the point codes
used. Since a limitation on the point code input will affect the
surface geometry, it is more common to impose a boundary to
meet the point limitation.

MineSight
M635V1 - CREATE A DIGITAL TERRAIN MODEL
RUN FILE OPERATION


where
10 = the name of the PROJECT CONTROL FILE -OR- enter 10=TEMP to use a dummy PCF
19 = the name of the M122 OUTPUT FILE
23 = the name of the DIGITAL TERRAIN MODEL (DTM) OUTPUT FILE
30 = the name of the SURVEY PARAMETER CODE FILE (if IOP6 = 0)
31 = the name of the BOUNDARY FILE (IOP1> 0)
NOTE: The ASCII file of input data is entered after the END line.
IOP1 = 0 NO BOUNDARY
= 1 BOUNDARY FILE (31) IS 2-D AND WITHIN INPUT DATA AREA;
SURFACE GEOMETRY IS DETERMINED BY INPUT DATA ONLY
= 2 BOUNDARY FILE (31) IS 3-D;
SURFACE GEOMETRY NEAR THE BOUNDARY IS DETERMINED BY BOUNDARY POINT INPUT
= 3 BOUNDARY FILE (31) IS 2-D;
SURFACE GEOMETRY NEAR THE BOUNDARY ESTIMATED BASED ON INPUT DATA
NOTE: IF IOP1=1, 2 OR 3, a boundary filename must be specified on the names line as File 31. The boundary
must be clockwise and closed.
IOP2 = 0 BOUNDARY FILE IS IN SURVEY FILE FORMAT

= 1 BOUNDARY FILE IS IN FREE-FIELD FORMAT
= 2 BOUNDARY FILE IS IN VBM READY FORMAT
IOP3 = 0 WRITE PLOT COMMANDS TO FILE 19

= 1 DO NOT WRITE PLOT COMMANDS
IOP4 = 0 OMIT LABEL PLOT COMMANDS FOR NODES

= 1 LABEL EACH DTM NODE WITH THE Z VALUE (If IOP3=0)
IOP5 = 0 HONOR BREAKLINE STRINGS (If IOP6=0 OR 1)

= 1 DO NOT CHECK BREAKLINES. TREAT ALL DATA AS SINGLE POINTS
(THIS WILL SPEED UP PROGRAM).

MineSight
IOP6 = 0 INPUT DATA IS IN SURVEY FILE FORMAT

= 1 INPUT DATA IS IN VBM READY FORMAT
= 2 INPUT DATA FORMAT SPECIFIED WITH FMT1
NOTE: If IOP6=1, or 2, the Point Code Parameter file (FILE 30) will not be used.
If IOP6=1, VBM strings will be used as breaklines for IOP5.
If IOP6=2, include:
FMT1 = FORTRAN format for input data. Example; FMT1 = (3F10.1)
(Order of input coordinates is: East, North, Z-value)
PAR1 = TOLERANCE FOR DUPLICATE POINTS (default=0.1)

NOTE: Single duplicate points will be deleted while duplicate points that are part of a string will be offset
slightly to retain the integrity of the string.
Color Coding:
If IOP3 = 0, the line segments between nodes may be color coded according to slope (in degrees) between them using either the PLT
command or the CMD=PLOT CUT and CMD=PLOT PEN commands as shown below:
For up to 4 pen colors:
PLT = slope1, slope2, slope3, slope4, pen1, pen2, pen3, pen4
where: slope x is a value from 0 to 90, and

Slope is less than slope1 use pen 1
slope2 use pen 2
slope3 use pen 3
slope4 use pen 4
For up to 16 pen colors:
CMD = PLOT CUT V1 V2 V3 .... V15 (for cutoffs)

CMD = PLOT PEN V1 V2 V3 .... V16 (for pen numbers)
NOTE: Always list one more pen number than you have cutoffs. This additional pen is for any material greater
than the last cutoff.
END
4. ASCII FILE OF INPUT DATA
FILENAME, CODES 1 through 10

where
FILENAME ASCII file of input data

CODES Data items to process (Up to 4 characters each; optional-default is to use all data)

MineSight

MEDS-635V1 -10=TEMP 19=PLT635.PAA 23=GRID.DTM 3=RPT635.LA;
MEDS-635V1 30=PARAM.COD 31=9103.BND
*** CREATE DTM FOR GRIDDING ***
USR = ABC
IOP1 = 1 / 0=NO BOUNDARY, 1=BOUNDARY FILE (31) IS 2-D

COM 2=BOUNDARY FILE (31) IS 3-D
IOP2 = 0 / BOUNDARY FILE FMT: 0=SURVEY FILE, 1=FREE FORMAT
IOP3 = 0 / 0=WRITE PLOT COMMANDS TO FILE 19, 1=DO NOT MAKE PLOT
IOP4 = 0 / 0=OMIT LABEL PLOT COMMANDS FOR NODES
COM 1=LABEL EACH DTM NODE WITH THE Z VALUE (IF IOP3=0)
PAR1 = 0.1 / TOLERANCE FOR DUPLICATE POINTS (default=0.1)
I-O = 0 / IOLEV
END
9102.PIT
SAMPLE INPUT FILE - 9102.PIT

CST 58 5682.670 4153.450 1792.000 Code Pt# East North Elev
CST 57 5704.950 4145.620 1793.300
CST 56 5732.170 4139.950 1795.300
CST 55 5758.100 4142.570 1797.601
CST 53 5791.550 4152.390 1801.120
CST 52 5819.890 4173.400 1801.565
CST 354 5847.000 4169.000 1800.500
CST 355 5861.000 4162.000 1804.100
CST 356 5873.000 4141.000 1804.900
CST 357 5876.000 4111.000 1804.900
CST 358 5835.000 4103.000 1802.400
$
CST 228 5882.520 4105.160 1800.727
CST 229 5890.960 4056.880 1800.372
...
SAMPLE BOUNDARY FILE - 9103.BND

TOE 309 5656.900 3777.590 1800.007
TOE 310 5675.680 3787.970 1800.390
TOE 3 11 5677.490 3826.310 1800.323
...
ELEV 2 5671.950 3741.050 1809.190
CST 339 5656.000 3768.000 1809.500
TOE 3 09 5656.900 3777.590 1800.007

MineSight
SAMPLE M122 OUTPUT FILE - PLT635.PAA

LINE 1 5682.7 4153.5 5819.9 4173.4 0.
LINE 1 5705.0 4145.6 5682.7 4153.5 0.
LINE 1 5682.7 4153.5 5694.2 4125.0 0.
LINE 1 5664.7 4133.5 5682.7 4153.5 0.
...

MineSight
1. %M635V1: No input file was specified.

A filename for the input data points must be specified after the END line.
2. %M635V1: INTRC0 ERROR# -1 (or -2)

Cannot calculate Z VALUE for boundary point # 27 @ 5785.71 3711.49
Point will be discarded!
An elevation cannot be calculated for this point. The program will continue but will not use this boundary point.
3. %M635V1: WARNING Your ENTIRE DATA FILE has been read in as a single string.
All input data points have the same code and are being treated as a single string. The program will try to honor the single string
as a breakline. If the data should be treated as multiple strings, either break codes are missing from the input data or the
parameter code file is incorrect.
4. %EDGE: WARNING 1 occurred for nodes 45 209

There is a problem forcing the connection of these two points. Look at the plot of the DTM to check for any geometry problems.
Reference the node locations in the report file.
5. %M635V1: DELBND ERROR - Arc not deleted.

A point SHOULD be on boundary but is NOT, OR
Cannot delete exterior segment due to dtm geometry, OR
Error in dtm adjacency array
Endpoint coordinates: 5677.50 3826.30 5675.70 3788.00
Either, the deletion of this arc would cause the DTM to lose integrity or the DTM structure has somehow become corrupted. A
deletion of this arc would either leave the triangulated mesh incomplete or divide it into 2 separate meshes.
6. %M635C1: WARNING
MAXIMUM NUMBER OF BOUNDARY POINTS ALLOWED = 2000
YOU HAVE EXCEEDED THE MAXIMUM - CHECK RESULTS CAREFULLY!
The program will continue to run using only the first 2000 points as the boundary.

MineSight

MineSight
Proprietary Software: Mintec, inc. M636V1 - GRID A DIGITAL TERRAIN MODEL
M636V1 GRID A DIGITAL TERRAIN MODEL

M636V1 will calculate the elevation at grid points that fall within The output from this program is an ASCII file in the input format
the limits of a DTM created by M635V1. A block in the grid is for M630V1. The output specifies grid values in terms of rows
considered inside the DTM limits if its center is within the DTM and columns. The row and column location for a block is
boundary. calculated using PAR1 through PAR6. These parameters will
default to the PCF values.

RUN FILE:
- Grid limits
- Grid increments
INPUT: CALCS:
- PCF - Elevations at each grid

- DTM file point (block centers)
OUTPUT:
- ASCII file of grid elevation


MineSight
M636V1 - GRID A DIGITAL TERRAIN MODEL Proprietary Software: Mintec, inc.

MineSight
Proprietary Software: Mintec, inc. M636V1 - GRID A DIGITAL TERRAIN MODEL
M636V1 - GRID A DIGITAL TERRAIN MODEL
RUN FILE OPERATION


where
MEDS-636V1 (must be the first 10 columns

19 = the name of the GRIDDED OUTPUT FILE
IOP1 = 1 /GRID VALUE PRECISION TO ONE DECIMAL PLACE (default)

= 2 /GRID VALUE PRECISION TO TWO DECIMAL PLACES
= 3 /GRID VALUE PRECISION TO THREE DECIMAL PLACES
= 4 /GRID VALUE PRECISION TO FOUR DECIMAL PLACES
IOP2 = 0 USE DTM WITH BOUNDARY INFORMATION

= 1 USE DTM WITHOUT BOUNDARY INFORMATION
NOTE: IOP2=1 if the DTM is exported from MineSight
IOP3 = 0 /PLAN DTM

= 1 /EW VERTICAL DTM
= 2 /NS VERTICAL DTM
IOP4 = 0 GRID IS IN MODEL COORDINATES (DEFAULT)

= 1 GRID IS IN PROJECT COORDINATES
PAR1 = Minimum Easting of the Grid (PCF XMIN)

PAR2 = Maximum Easting of the Grid (PCF XMAX)
PAR3 = Minimum Northing of the Grid (PCF YMIN)
PAR4 = Maximum Northing of the Grid (PCF YMAX)
PAR5 = Block size in the Easting (PCF DX)
PAR6 = Block size in the Northing (PCF DY)
END
4. INPUT FILENAME
The input file is a binary DTM created by the program M635V1.

MineSight
M636V1 - GRID A DIGITAL TERRAIN MODEL Proprietary Software: Mintec, inc.

MEDS-636V1 10=SURV10.DAT 19=DAT630.IA 3=RPT636.LA
* GRID A DTM SURFACE *
USR = ABC
COM
COM THE FOLLOWING PARAMETERS DEFAULT TO THE PCF VALUES
COM
PAR1 = 4600. 6100. / XMIN XMAX

PAR3 = 3400. 5500. / YMIN YMAX
PAR5 = 5. 5. / XINC YINC
END
GRID.DTM
SAMPLE OUTPUT FILE (row, col1, col2, values for col1 through col2)
62 228 231 1809.9 1809.9 1809.9 1810.0
63 225 234 1809.7 1809.8 1809.8 1809.9 1809.9 1809.9 1809.9 1810.0 1810.0 1810.0
63 235 237 1810.0 1810.0 1810.0
64 222 231 1809.6 1809.6 1809.7 1809.7 1809.8 1809.8 1809.8 1809.9 1809.9 1809.9
...
1. ERROR - DEFINE GRID LIMITS

The grid limits will default to your PCF limits if an actual PCF has been used. Either specify PAR1 through PAR4 or make sure
the actual PCF (not 10=TEMP) is on the Names Line.
2. %M636V1: ERROR READING INPUT REQUEST

Make sure a DTM filename is included as input after the End Line in your run file.
3. ERROR - Maximum grid size exceeded Limit is 1000 x 1000

The grid limits and increment are not correct. Change PAR1 through PAR4 as needed.
4. ERROR - ONLY 1000 INTERSECTIONS WILL BE PROCESSED

The program has a limit of 1000 DTM arcs that can be processed for any row.

MineSight
Proprietary Software: Mintec, inc. M637V1 - CROSS SECTION THRU A DTM
M637V1 CROSS SECTION THRU A DTM

M637V1 will produce plot commands for a section line through A DTM section plot is a good means of verifying the integrity
a Digital Terrain Model (DTM). A DTM is a binary file that of the DTM. A series of sections may be plotted by running
must first be created using program M635V1. M637V1 and M122V1 for each section. MEDTOOL procedure
secdtm.dat may be used with TOOLPAN & TOOLAUTO to
automate this process.
PROGRAM FLOW DIAGRAM Section plots of several DTMs may be plotted together on a
single map to verify DTM surfaces relative to each other. To
RUN FILE: produce a map with several DTM surfaces on the same section,
- Plot options
run M637V1 once for each surface and use all of the plot
- Scale, Min, Max commands files (one for each DTM) in the M122V1 run file.
MEDTOOL procedure secdtm.dat can be used to plot up to 3
DTM surfaces on a section.
The section line is defined by 2 endpoints. A plot command

will be generated for each intersection of the section line and a
DTM arc (line connecting nodes). A line connecting the
intersecting points will be plotted (DASHL plot command). A
INPUT: CALCS: section line that passes nearby a DTM node may have many
- PCF - Connect points or curve fit intersecting points depending on the number of other nodes
- DTM file connected by the nearby node. When many intersections are
found in a local area, elevation labels, if opted for, will overwrite
each other and generally be illegible.
There are options to:
plot a smooth line through the intersecting points

(FLINE plot command)
OUTPUT:
- Printer Report File plot a symbol at each intersecting point

- Plot Commands File
plot the elevation at each intersecting point

MineSight
M637V1 - CROSS SECTION THRU A DTM Proprietary Software: Mintec, inc.

MineSight
M637V1 - CROSS SECTION THRU A DTM
RUN FILE OPERATION


where

10 = the name of the PROJECT CONTROL FILE (-10 FOR A DUMMY PCF)
19 = the name of the DTM INPUT FILE
30 = the name of the PLOT COMMANDS FILE
IOP1 = 0 Simply connect points

= 1 Plot a smooth curve through data points.
IOP2 = Line type for section line. (DASHL PATTERN# -SEE M122V1 DOC)
IOP4 = Pen number for section line (default = 1)
IOP5 = Pen number for annotation (default = 5)
IOP6 = Symbol number for intersections (0 = DO NOT PLOT SYMBOL)
PAR5 = SCALE (no default)

PAR6 = ZMIN
PAR7 = ZMAX
PAR8 = HEIGHT OF SYMBOL (default = 0.12)
NOTE: Item commands for plotting. To plot elevation at intersection of the section line and DTM connecting
arcs.
ITMn = ELEV Fw.d xoffset yoffset height
where:
Fw.d = elevation display format (e.g. F5.0)
xoffset = horizontal offset from intersection in inches (default = 0.05)
yoffset = vertical offset from intersection in inches (default = 0.00)
height = label height in inches (default = 0.08)
4. SECTION LINE INPUT

X1 Y1 X2 Y2
where: X1 is section starting X Coordinate, Y1 is section starting Y Coordinate

X2 is section ending X Coordinate, Y2 is section ending Y Coordinate

MineSight

MEDS-637V1 10=SURV10.DAT 19=UPPER.DTM 3=RPT637.TM1 30=SURF1.PAA
** GENERATE SECTION FROM SURVEY DTM FOR PLOTTING **
USR = ABC
IOP1 = 0 / 0=SIMPLY CONNECT POINTS, 1=PLOT SMOOTH CURVE
IOP2 = 0 / LINETYPE FOR PLOTTING
IOP3 = 0 / 0=NO LABELS, 1=PLOT ELEV LABELS
IOP4 = 2 / PEN# FOR SECTION LINE
IOP5 = 2 / PEN# FOR ELEV LABELS
IOP6 = 0 / 0=DO NOT PLOT SYMBOLS, N=SYMBL# FOR DATA POINTS
PAR5 = 25. / SCALE

PAR6 = 1700. 1850. / ZMIN, ZMAX
PAR8 = .07 / HEIGHT OF SYMBOL
END
5600. 3800. 5850. 3800.
SAMPLE OUTPUT FILE - SURF1.PAA

PEN# 2
ARAY1 1 76.25 1800.37 1
ARAY1 1 78.71 1803.71 2
ARAY1 1 82.98 1809.50 3
ARAY1 1 88.45 1809.50 4
ARAY1 1 102.91 1809.50 5
ARAY1 1 112.00 1809.50 6
ARAY1 1 114.87 1809.50 7
ARAY1 1 119.21 1809.50 8
ARAY1 1 139.70 1809.50 9
ARAY1 1 148.87 1804.66 10
ARAY1 1 155.19 1800.98 11
DASHL 1 0.2 0

MineSight
SAMPLE PLOT RUN FILE

MEDS-122V1 10=TEMP 3=RPT122.TMP
* PLOT DTM SECTION PROFILES
USR = ABC
MAP = 0 250. 25. 1657.5 1850. 25. /XMIN,XMAX,XSCAL,YSCAL
IOP1 = 0 / 0 = NORMAL PLOT, 1=ROTATE BY 90 DEG.

IOP2 = 1 / USE PAR37
IOP3 = 0 / 1 = LABEL DH AT BOTTOM
IOP31 = 0 / 0 = PREVIEW METAFILE, 1=MAKE METAFILE
PAR30 = 3800. / METAF SECT/ELEV #
PAR32 = 0. / BANNER: -1=NO
PAR36 = 0. / SCALE PLOT FACTOR

PAR37 = 0.1 / INCHES BEYOND XMAX TO LEAVE PEN
PAR38 = 0.1 / METAFILE TEXT HEIGHT
FMT1 = (DTM SECT) / METAF GROUP
END
PEN# 1
USERF SURF1.PAA
USERF SURF2.PAA
PEN# 1
GRID 1. 0.0 250. 1700. 1850. 50. 150.
GRID 1. 0.0 250. 1700. 1850. 250. 50.
COORD 1 50. 1700. 250. 1700. 50. 0.08 90 0 5650. 50.
COORD 1 0.0 1700. 0.0 1800. 50. 0.08 0 0 1700. 50.
ENDOC

MineSight

MEDS-637V1 10=SURV10.DAT 19=LOWER.DTM 3=RPT637.TM1 30=SURF2.PAA
** GENERATE SECTION FROM SURVEY DTM FOR PLOTTING **
USR = SRV
IOP1 = 0 / 0=SIMPLY CONNECT POINTS, 1=PLOT SMOOTH CURVE

IOP2 = 0 / LINETYPE FOR PLOTTING
IOP4 = 3 / PEN# FOR SECTION LINE
IOP5 = 3 / PEN# FOR ELEV LABELS
IOP6 = 4 / 0=DO NOT PLOT SYMBOLS, >0=SYMBL# FOR DATA POINTS
PAR5 = 25. / SCALE

PAR6 = 1700. 1850. / ZMIN, ZMAX
PAR8 = .07 / HEIGHT OF SYMBOL
ITM01 = ELEV F6.1 -0.08 0.0 0.08
END
5600. 3800. 5850. 3800.
SAMPLE OUTPUT FILE - SURF1.PAA

PEN# 2
ARAY1 1 76.25 1800.37 1
ARAY1 1 78.71 1803.71 2
ARAY1 1 82.98 1809.50 3
ARAY1 1 88.45 1809.50 4
ARAY1 1 102.91 1809.50 5
ARAY1 1 112.00 1809.50 6
ARAY1 1 114.87 1809.50 7
ARAY1 1 119.21 1809.50 8
ARAY1 1 139.70 1809.50 9
ARAY1 1 148.87 1804.66 10
ARAY1 1 155.19 1800.98 11
DASHL 1 0.2 0

MineSight
1. ?M637V1: ERROR: PAR5 = MAP scale is required

Define PAR5 in the run file.
2. ?M637V1: ERROR. Exceeded maximum # intersections per row: 10000

A section line may have at most 10000 intersection points. The section line must be redefined to meet this constraint.
3. ?M637V1: ERROR. Section line does not intersect DTM

The plane defined by the Section Line does not intersect the xy area occupied by the DTM. The x and y extents of the DTM are
output in the m637v1 print file.
4. ?M637V1: ERROR reading Section Line input

An error occurred reading the section endpoints. The section endpoints are defined immediately after the END line in the run
file. The coordinates are entered in free field format.

MineSight

MineSight
Proprietary Software: Mintec, inc. M639V1 - GENERATE BLOCK PARTIALS BETWEEN TWO SURFACES
M639V1 GENERATE BLOCK PARTIALS BETWEEN TWO

SURFACES

M639V1 generates block partials between two surfaces in File The item names for the lower and upper surfaces are specified
13. in the run file. A block partial is calculated only if:
a) both items have a defined value
PROGRAM FLOW DIAGRAM b) the toe of the block is below the upper surface
RUN FILE: c) the crest of the block is above the upper surface
- Area selection
- Item selection The output file is in the same format as M659V1 and can be
- Level requests used as input to M711V1. The upper surface is usually the
original topography or an intermediate pit. The lower surface is
usually an intermediate or ultimate pit. The surfaces may
intersect.
INPUT: CALCS:
- PCF - (Top - Bottom)/DZ*100

- File 13
OUTPUT:
- Output Partials File

MineSight
M639V1 - GENERATE BLOCK PARTIALS BETWEEN TWO SURFACES Proprietary Software: Mintec, inc.

MineSight
Proprietary Software: Mintec, inc. M639V1-GENERATE BLOCK PARTIALS
M639V1 - GENERATE BLOCK PARTIALS BETWEEN TWO SURFACES
RUN FILE OPERATION


where

19= the name of the OUTPUT PARTIALS FILE
IOP3 = FIRST COLUMN TO PRINT (default=1)

IOP4 = LAST COLUMN TO PRINT (default=PCF)
IOP5 = FIRST ROW TO PRINT (default=1)

IOP6 = LAST ROW TO PRINT (default=PCF)
ITM1 = item LOWER

Lower surface item from File 13, usually an intermediate or ultimate pit
ITM2 = item UPPER
Upper surface item from File 13, usually original topography or a previous intermediate pit
END
4. LEVEL REQUEST LINES
Put level number or range of level number, one per line in any order. Terminate with end-of-file or a blank line.

MineSight
M639V1-GENERATE BLOCK PARTIALS Proprietary Software: Mintec, inc.

MEDS-639V1 10=SAMP10.DAT 13=SAMP13.DAT 19=SAM639.OA;
* PARTIALS BETWEEN TOPO AND ULTIMATE DIPPER PIT *
USR = ABC
IOP3 = 10 / USE ALL COLUMNS

IOP5 = 10 / USE ALL ROWS
ITM1 = TOPO LOWER/ LOWER SURFACE

ITM2 = TOPO UPPER/ UPPER SURFACE
END
2
3
4
5
6
7
8
9
10
11
12
13
14
15

1. ?M639V1: ERROR. You have selected x items. You MUST select exactly 2 items.
You must have exactly two ITM lines in your run file. Make sure that the lower surface has values less than the upper
surface.
2. ?M639V1: ERROR. Your file 13 is empty

You must initialize your File 13 with M601V1 before any MineSight program can access it.
3. ?M639V1: ERROR. Youve requested level xx but your last bench is yy.
You are requesting a level (xx) that exceeds the last bench in your model (yy).

MineSight
Proprietary Software: Mintec, inc. MSB2PR - CALCULATE FULL BLOCK VALUES FROM SUB-BLOCKS
MSB2PR BLOCK VALUES FROM SUB-BLOCK DATA

MSB2PR - Calculates block values from sub-blocked data. This Grade data AND geological codes are examples of items that
program calculates full block value from sub-blocks and stores can be entered with this program.
it into 3D block model file. The Mine Model File 15 requires
associated sub-block file to run the program.

RUN FILE:
- Sub-blocked items to use
- Parent block items to
store the results
- Type of calculation
INPUT: CALCS:
- PCF - Retrieve data
- Mine Model File 15 - Select data ranges
- Sub-blocked file - Calculate Values
OUTPUT:
- Updated Model File 15
- Printer Ourput File
Revised: 22-July-13 Page B2PR-1

MineSight
MSB2PR - CALCULATE FULL BLOCK VALUES FROM SUB-BLOCKS Proprietary Software: Mintec, inc.
Page B2PR-2 Revised: 22-July-13

MineSight
Proprietary Software: Mintec, inc. MSB2PR - CALCULATE FULL BLOCK VALUES FROM SUB-BLOCKS
MSB2PR - BLOCK VALUES FROM SUB-BLOCK DATA
RUN FILE OPERATION

MEDS-B2PR 10=filename 15=filename 3=filename;

where
MEDS-B2PR - (must be the first 10 columns)

15 = the name of the MINE MODEL FILE (corresponding sub-block file is required too)
3. RUN OPTIONS MSB2PR (in any order & free-field format)
IOP5 = IX1 FIRST MODEL COLUMN (default = 1)

IOP6 = IX2 LAST MODEL COLUMN (default = PCF nx)
IOP7 = IY1 FIRST MODEL ROW(default = 1)
IOP8 = IY2 LAST MODEL ROW (default = PCF ny)
IOP9 = IZ1 FIRST MODEL BENCH (default = 1)
IOP10 = IZ2 LAST MODEL BENCH (default = PCF nz)
IOP14 = MIN NUMBER OF SUB-BLOCKS TO DEFINE PARENT BLOCK (default = 1)
NOTE: If there are less than IOP14 defined sub-blocks, then the undefined value will be assigned to the resulting
value for a parent block.
IOP15 = 0 DO NOT COUNT UNDEFINED SUB-BLOCKS FOR MAJORITY CODE / PERCENT / PARTIAL (default)
= 1 COUNT UNDEFINED FOR MAJORITY CODE / PERCENT / PARTIAL
PAR2 = DEFAULT SG VALUE (if no value is entered, 1 will be used)
ITMn = AVOL LABEL-15PR LABEL-15SB / VOLUME AVERAGE

ITMn = ATON LABEL-15PR LABEL-15SB LABEL-SG-15SB / TONNAGE AVERAGE WITH SG VALUE IN THE
SUB-BLOCKED ITEM
ITMn = CMAJ LABEL-15PR LABEL-15SB / MAJORITY CODE
ITMn = PART LABEL-15PR LABEL-15SB / PARTIAL OF MAJORITY CODE
ITMn = PRCT LABEL-15PR LABEL-15SB / PERCENTAGE OF MAJORITY CODE
ITMn = SSUM LABEL-15PR LABEL-15SB / SUM OF SUB-BLOCKED VALUES
ITMn = SMAX LABEL-15PR LABEL-15SB / MAX VALUE OF LABEL-15SB ITEM FOR A PARENT BLOCK
ITMn = SMIN LABEL-15PR LABEL-15SB / MIN VALUE OF LABEL-15SB ITEM FOR A PARENT BLOCK
where,
LABEL-15SB is the sub-blocked item and LABEL-15PR is the name of the model item which can be sub-blocked as
or not. LABEL-15PR is where the results of operations on sub-blocked data will be stored in file 15.

If LABEL-15PR is different from LABEL-15SB, it should not be sub-blocked to avoid unpredictable results.
Revised: 23-July-13 Page MSB2PR-3

MineSight
MSB2PR - CALCULATE FULL BLOCK VALUES FROM SUB-BLOCKS Proprietary Software: Mintec, Inc.
LABEL-SG-15SB is a specific gravity sub-blocked item. If LABEL-SG-15SB is unavailable, PAR2 is used.
END
MSB2PR SAMPLE RUN FILE #1

MEDS-SB2PR 10=msop10.dat 15=msop15.sbc 3=rptmsb.la
* POPULATE MODEL WITH SUBBLOCKED VALUES *
USR = ABC
IOP5 = 100 100 / Columns to output

IOP7 = 61 61 / Rows to output
IOP9 = 35 35 / Level
IOP14 = 1 / MINIMUM NUMBER OF DEFINED BLOCKS TO DO CALC

IOP15 = 0 / 1 - COUNT UNDEFINED BLOCK AS DEFINED
ITM1 = CMAJ ROCK ROCK

ITM2 = SSUM SUM CU
ITM3 = PRCT VALPT ROCK
ITM4 = smax PIT1 CU
ITM5 = smin PIT2 CU
ITM6 = avol vol MO
ITM7 = aton ton CUID sg
END
Page MSB2PR-4 Revised: 23-July-13

trademark of Leica Geosystems AG. MSCS - CONDITIONAL SIMULATION
MSCS CONDITIONAL SIMULATION

MSCS computes conditionally simulated estimates for the 3D The program MSCS can perform Conditional Simulation using
grid points using the composite or blasthole data information. two different methods:
PROGRAM FLOW DIAGRAM 1) Sequential Gaussian Simulation (SGS)

2) Sequential Indicator Simulation (SIS)
RUN FILE:
MSCS can compute the normal scores transformation of the input
data prior to Conditional Simulation using SGS. If the input data
is already transformed, then this option should be turned off.
- Area selection
- Item selection
- Data selection It is possible to run the program with the normal scores
- Random number seed transformation only option. In that case, the program will
only output the normal scores transformation of the data. No
simulation is performed. This gives the user an opportunity to
check the transformation results. Its is recommended that the
INPUT: CALCS: input composite or blasthole data should be declustered before
using it for Conditional Simulation.
MSCS can perform Despiking, if the option is checked.

- PCF - Normal Scores Trans.
- File 9 (optional) - Despiking (optional) Despiking is a method where identical values of a histogram
ASCII File, or - Simulated grades are transformed into a series of different values by adding small
MSTorque composite increments. This might be useful for better normal scores
set transformation of the data.
- File 15 (optional)
The program input could be from ASCII data, from a MineSight

OUTPUT: composite file (File9), or an MSTorque database. The simulation
results are stored into a MineSight block model (file 15). The
results can alternatively be output to ASCII and loaded into the
- Normal Scores block model later, if needed. If MineSight files are not used
Transformation Table for input and storing the results, then the item selection from
- Despiking results these files are not possible.
- Report File
Conditional Simulation provides many equally probably
realization, instead of one single model as in the case of
interpolation. Therefore, it can be very useful to measure the
variability to the encountered and for sensitivity analysis of
various problems. A different realization can be obtained by
changing the random number seed (IOP15) used to generate
the results.
If the seed number entered in IOP15 is negative, the program

reads the seed information from the file specified on the names
line as 35=filename. For multi-runs, enter a seed number for the
first run, and specify a file that does not exist. The program will
write out the random number seed information to the specified
file at the end of the simulation. For the following runs, enter
-1 for the seed, and keep the same seed information filename.
The program will read this file and retrieve the last set of random
Revised: 12-August-14 Page MSCS-1

MSCS - CONDITIONAL SIMULATION trademark of Leica Geosystems AG.
seed information to run the simulation. Each simulation results

should be written to a different item in the model file.
To speed up the program it is recommended to perform multiple

simulatiosn for the same item in a single run instead of multi-run.
The number of simulations requested (IOP4) should match the
number of items in the model file where the simulated results
will be stored.
Page MSCS-2 Revised: 12-August-14

MSCS - PROGRAM FOR CONDITIONAL SIMULATION
RUN FILE OPERATION

MEDS-CS 10=filename 9 (or 8)=filename 15 (or 14 or 13)=filename 3=filename;

MEDS-CS 19=filename 20=filename 30=filename 31=filename;
MEDS-CS 32=filename 33=filename 34=filename 35=filename
where
MEDS-CS - (must be the first 10 columns)

9 = the name of the COMPOSITE FILE OR TORQ for input from MSTorque (Optional; if file 9 is absent,
must have 30 = filename)
15 = the name of the MINE MODEL FILE (Optional) -OR-
14 = the name of the GSM SUMMARY FILE (Optional) -OR-
13 = the name of the 2-D SURFACE FILE (Optional)
19 = the name of the Output File (ASCII) with CS results if IOP27=0 -OR-
the name of the Output File with Normal Scores with coordinates if IOP15=0
20 = MSTorque info file (mstorq.inf) (if 9=TORQ is used)
30 = the name of the Optional Input Data File (if no File 9 is specified)
31 = the name of the Output Data File for Normal Scores with no coordinates if IOP5=0 -OR-
the name of the Input Data File with Normal Scores with no coordinates if IOP5=1
32 = the name of the Output Data File for Despiked data (if IOP18>0)
33 = the name of the Intput Data File for variogram parameters
34 = the name of the Input Data File for soft data (Optional - SIS Only)
35 = the name of the Input/Output file for random number seed (Optional)
NOTE: The use of File 19 and File 31 depends on the use of IOP20, IOP9 and IOP5. For details, please refer to the
explanation for IOP20 under Run Options.
3. RUN OPTIONS MSUC (in any order & free-field format)
IOP1 = M09 FIRST DATA UNIT OF FILE #9 TO ACCESS (default = 1)

IOP2 = N09 LAST DATA UNIT OF FILE #9 TO ACCESS (default = last data unit stored)
IOP3 = 0 2-D INPUT (X and Y only) - cannot be used with relative elevation.
= 1 3-D INPUT (X, Y, and Z)
IOP4 = NUMBER OF INPUT DATA POINTS TO LIST (default = 5, -1 = no list)
IOP5 = 0 TRANSFORM THE DATA TO NORMAL SCORES (SGS only)

= 1 DO NOT TRANSFORM THE DATA (already transformed) (SGS only)


IOP6 = MINIMUM DATA FOR SIMULATION (default=1)

IOP7 = MAXIMUM DATA FOR SIMULATION (default=8)
IOP8 = 0 SIMPLE KRIGING

= 1 ORDINARY KRIGING
= 2 LOCALLY VARYING MEAN (SGS only)
= 3 EXTERNAL DRIFT (SGS only)
= 4 COLLOCATED KRIGING (SGS only)
NOTE: if IOP8=4, see also PAR30 and PAR36.
IOP9 = 0 TWO PART SEARCH

= 1 DATA NODES
NOTE: if IOP9=0, see PAR10 for distance tolerance.
IOP10 = NUMBER OF SIMULATED NODES TO USE
IOP11 = NUMBER OF GRIDS IN X DIRECTION

IOP12 = NUMBER OF GRIDS IN Y DIRECTION
IOP13 = NUMBER OF GRIDS IN Z DIRECTION
IOP14 = NUMBER OF SIMULATIONS (default=1)
IOP15 = n RANDOM NUMBER SEED (must be an integer value)

= 0 NO SIMULATION. Only normal scores transformation
IOP16 = 0 NO OCTANT SEARCH

= 1 OCTANT SEARCH
IOP17 = 0 NO WEIGHT ITEM

= 1 USE WEIGHT ITEM
IOP18 = 0 BLOCKS ARE REFERENCED BY COL, ROW, BENCH NUMBER IN OUTPUT (if IOP27=0)
= 1 BLOCKS ARE REFERENCED BY COORDINATES (AT CENTROID) (if IOP27=0)
IOP19 = NUMBER OF LINES TO SKIP AT THE BEGINNING OF THE ASCII INPUT FILE
IOP20 = BENCH REF# FOR SIMULATION ZMIN (if IOP18=0 and IOP27=0)
IOP21 = LOWER TAIL OPTION

= 1 LINEAR
= 2 POWER MODEL EXTRAPOLATION
IOP22 = UPPER TAIL OPTION

= 1 LINEAR
= 3 LINEAR BETWEEN RESCALED GLOBAL CDF (SIS only)
= 4 HYPERBOLIC MODEL

IOP23 = MULTIPLE GRID SEARCH (default=1, Max=5)
IOP24 = 0 NO BOUNDARY (use PAR1-PAR6)

= 1 BOUNDARY APPLIES ONLY TO COMPOSITE DATA INPUT
= 2 BOUNDARY APPLIES ONLY TO SIMULATED DATA OUTPUT
= 3 BOUNDARY APPLIES ONLY TO BOTH INPUT AND OUTPUT (default=1)
IF IOP24 > 0, inlcude one of the following lines:
IOP25 = NUMBER OF MODEL RANGE ITEMS (default=0, max=2)

IOP26 = NUMBER OF MODEL SELECTION ITMES (default=0, max=2)
IOP27 = 0 OUTPUT RESULTS TO AN ASCII FILE

= 1 WRITE RESULTS TO THE BLOCK MODEL
IOP28 = 0 NO RELATIVE COORDINATES

= 1 RELATIVE COORDINATE (currently elevation only)
NOTE: Cannot be used with 2-D or ASCII input
IOP29 = 0 NO DESPIKING (if IOP29 is not equal to 1)

= 1 DESPIKING
IOP30 = DESPIKING OUTPUT OPTION (if IOP29 IS

= 0 ORIGINAL ORDER
= 1 SORTED BY VALUE
= -1 NO OUTPUT
IOP31 = 0 SGS
= 1 SIS
= 2 SIS WITH LOCAL VARYING MEAN
IOP32 = 0 CATEGORICAL VARIABLE (SIS only)

= 1 CONTINUOUS VARIABLE (SIS only)
IOP33 = 0 STANDARD INDICATOR KRIGING SIMULATION

= 1 MARKOV-BAYES SIMULATION (used with soft data input)
IOP34 = MAXIMUM NUMBER OF SOFT INDICATOR DATA TO USE
IOP35 = MIDDLE TAIL OPTION

= 0 LINEAR
IOP36 = OMIT/RESET OPTION

= 0 OMIT (default)
= 1 RESET ACCESSED MODEL BLOCKS

PAR1 = MIN EASTING (default = PCF limits)

PAR2 = MAX EASTING (default = PCF limits)
PAR3 = MIN NORTHING (default = PCF limits)
PAR4 = MAX NORTHING (default = PCF limits)
PAR5 = MIN ELEV. (default = PCF limits)
PAR6 = MAX ELEV. (default = PCF limits)
PAR7 = MIN GRADE (default = 0.)
PAR8 = MAX GRADE (default = 99999)
NOTE: PAR1-8 ARE USED ONLY FOR INPUT DATA LIMITS
PAR9 = MAXIMUM SEARCH RADIUS (major axis)

PAR10 = DISTANCE TOLERANCE FOR ASSIGNING DATA TO NEAREST NODE WHEN IOP9=0 (default=0.0001)
PAR11 = X GRID SIZE

PAR12 = Y GRID SIZE
PAR13 = Z GRID SIZE
PAR21 = LOWER TAIL PARAMETER (default = 2)

PAR22 = UPPER TAIL PARAMETER (default = 3)
PAR23 =
MAJOR AXIS ROTATION
PAR24 =
MAJOR AXIS DIP
PAR25 =
PLUNGE
PAR26 =
MINOR AXIS SEARCH DISTANCE
PAR27 =
VERTICAL AXIS SEARCH DISTANCE
PAR28 =
MINIMUM VALUE FOR TAIL EXTRAPOLATION
PAR29 =
MAXIMUM VALUE FOR TAIL EXTRAPOLATION
PAR30 =
CORRELATION COEFFICIENT BETWEEN THE PRIMARY AND SECONDAR VARIABLE WHEN IOP8=4
(default=1)
PAR31 = MINIMUM EASTING FOR SIMULATION GRID (default=PCF)
PAR32 = MINIMUM NORTHING FOR SIMULATION GRID (default=PCF)
PAR33 = MINIMUM ELEVATION FOR SIMULATION GRID (default=PCF)
PAR34 = SEARCH DISTANCE FOR DESPIKING (default=100.)

PAR35 = DELTV TOLERANCE BETWEEN DATA FOR DESPIKING WHEN IOP29=1 (default = 0.0001)
PAR36 = VARIANCE REDUCTION FACTOR WHEN IOP8=4 (default=1)
PAR37 = MEDIAN IK CUTOFF (default=0, Standard Indicator Kriging is used - SIS only).
PAR38 = MIDDLE TAIL PARAMETER (SIS only)
GET09 = EAST NORTH ELEV. RELEV GRADE WT RANGE ITEMn
NOTE: ELEVATION, WEIGHT ITEMS and RANGE ITEMSare optional (see IOP3, IOP17, IOP28 and ITM lines)
UPD15 = CUS1 CUS2 CUS3 CUS<NSIM> (and optional items)
NOTE: NSIM IS A NUMBER OF SIMULATIONS (IOP14=NSIM). FIRST NSIM POSITIONS ARE RESERVED
FOR SIMULATED ITEMS STORED TO THE MODEL. ADDITIONAL ITEMS FOLLOW <NSIM>
ITEMS.
THE MODEL ITEMS HAVE TO BE IN A CERTAIN ORDER TO PROPERLY ACCESS THE MODEL
positions 1 to NSIM: Simulated grade items to store (required)
position nsim + 1 Relative elevation item (optional)
position nsim + 2 Selection item1 (optional) - uses min, max
position nsim + 3 Selection item2 (optional) - uses min, max
position nsim + 4 Selection item3 (optional) - uses block limit codes (max 10)

FOR A LARGE NUMBER OF SIMULATIONS AND SIMILAR ITEM NAMES ONE MAY USE GROUP CMD
COMMAND ( CMD = GROUP UPD15 prefix start_index end_index zeropad):
CMD = GROUP UPD15 CUS 1 N1 IDIG (INSTEAD OF UPD15 = CUS1 ... CUS<N1>)
CMD = GROUP UPD15 CUR 1 N2 IDIG (INSTEAD OF UPD15 = CUR1 ... CUR<N2>)
NOTE: N1 + N2 = NSIM !!! IDIG IS FOR LABEL FORMAT:

IF IDIG = 1 THEN CUS1,CUS2...
IF IDIG = 2 THEN CUS01,CUS02,...
IF THERE ARE ADDITONAL ITEMS THEY MIGHT BE LISTED IN ADDITIONAL UPD15 LINE
UPD15 = RELEV ROCK1 ROCK2
NOTE: different format for collocated cokriging option (IOP8=4 and SGS only)
SIMULATED AND SECONDARY ITEMS HAVE TO BE ENTERED PAIRWISE:
UPD15 = CUS1 CO-CUS1 CUS2 CO-CUS2 CUS3 CO-CUS3 ... CUS<NSIM> CO-CUS<NSIM> (and
optional items)
NOTE: The model items have to be in certain order to properly access to the model:
positions from 1 to 2*NSIM. Simulated grade items to store AND Secondary attribute items
position 2*nsim+1. Relative elevation item (optional)
position 2*nsim+2. Selection item1 (optional) - uses min, max
position 2*nsim+3. Selection item2 (optional) - uses min, max
position 2*nsim+4. Selection item3 (optional) - uses block limit codes
FOR A LARGE NUMBER OF SIMULATIONS AND SIMILAR ITEM NAMES ONE MAY USE
GROUP CMD COMMAND (CMD = GROUP UPD15 prefix1 prefix2 start_index end_index zeropad)
CMD = GROUP UPD15 CUS CUIS 1 N1 IDIG

(INSTEAD OF UPD15 = CUS1 CUIS1 ... CUS<N1> CUIS<N1>)
CMD = GROUP UPD15 CUR CUIR 1 N2 IDIG
(INSTEAD OF UPD15 = CUR1 CUIR1 ... CUR<N2> CUIR<N2>)
STORING TO FILE 15 IS OPTIONAL(see IOP27)
ITMn = LABEL09 RANGE MIN MAX
NOTE: 5 RANGE items can be used.
CMD = SELCT ITEM1 MIN MAX

CMD = SELCT ITEM2 MIN MAX
CMD = MOD3D CODES CODE1, CODE2, .... CODE10
NOTE: SELCT, ITEM1, ITEM2, MOD3D, and CODES are all key words
END

4. INPUT THROUGH AN ASCII FILE: USE THE FOLLOWING COMMAND LINE IN THE RUN FILE.
NOTE: If File 9 is not specified, ASCII input is assumed.
CMD = CARD INPUT LABEL1 LABEL2 LABEL3 LABEL4 ETC.

where
LABEL1 . . . LABELN must be following labels:
X = Easting
Y = Northing
Z = Elevation (Optional if IOP3 = 1)
GRADE = Grade item
WT = Weight item (Optional if IOP17 = 1)
Use format line to read above items:

FMT1 = (5F8.0) <-- Example only
Free format is allowed if data columns are in the same order as the item labels.

MSCS SAMPLE RUN FILE #1 - example of Sequential Gaussian Simulation (SGS)

MEDS-CS 10=msop10.DAT 9=msop09.dat 3=rptsim.t1 15=msop15.cs;
MEDS-CS 19=datsim.out 31=bounds.dat 32=datsim.dsp 33=varcun.rk1
* SGS using CU - input from msop09.dat
USR = abc / Wed May 13, 2009 2:13:55 PM US Mountain Standard Time
IOP1 = 1 0 / M09, N09

IOP3 = 1 / 0=2D; 1=3D input
IOP4 = 0 / No. of input data to print
IOP5 = 1 / transform the data? 0=no 1=yes
IOP6 = 2 / minimum data for simulation
IOP7 = 8 / maximum data for simulation
IOP8 = 0 / 0=SK, 1=OK, 4=Colloc. kriging
IOP9 = 0 / 0=two part search, 1=data-nodes
IOP10= 8 / number of simulated nodes to use
IOP11= 150 125 1 /# grids in x, y, z
IOP14= 3 / # of simulations
IOP15= 123789 / random number seed
IOP16= 0 / 1=octant search
IOP17= 0 / 1=use weight item, 0=none
IOP18= 0 / 0=output IX,IY,IZ; 1=x,y,z coords
IOP21= 1 2 / Lower and upper tail option
IOP23= 2 / Multiple grid search (Default=0)
IOP24= 2 / 0=no boundary
IOP25= 1 / No. of model range selection items (Max=2)
IOP26= 1 / No. of block limiting items (Max=1)
IOP27= 1 / 1=write to model, 0=ascii output
IOP29= 1 / 1=despiking, 0=no despiking
IOP30= 0 / Despiking output type
IOP36= 0 / 0=Omit, 1=Reset accessed blocks before simulation
PAR1 = 1000. 4000. / xmin, xmax for input data

PAR3 = 4000. 6500. / ymin, ymax for input data
PAR5 = 2000. 2960. / zmin, zmax for input data
PAR7 = 0. 999999. / min and max input value
PAR9 = 150. / max search radius
PAR10 = 10. / Distance tolerance (Default=0.0001)
PAR11 = 20. 20. 15. / dx, dy, dz
PAR21 = 2. 3. / Lower and upper tail parameters
PAR23 = 190. 0. 0. / Anisotropy angles
PAR26 = 100. 50. / Minor and vertical axis search distances
PAR28 = 0. 3.7 / Min and max value for tail extrapolation
PAR30 = 0. / Correl coeff (if IOP8=4) Default=1
PAR31 = 1000. / xmin for the simulation grid
PAR32 = 4000. / ymin for the simulation grid
PAR33 = 2600. / zmin for the simulation grid
PAR34 = 250. / Search radius for despiking
CMD = SELCT ITEM1 0. 100.

CMD = MOD3D CODES 1 0
GET09 = EAST NORTH ELEV. CU ROCK

UPD15 = CUS1 CUS2 CUS3 TOPO ROCK


CMD = INCL LOCPT file bound.xyz
I-O = 0
END
MSCS SAMPLE RUN FILE #2 - example of Sequential Indicator Simulation (SIS)

MEDS-CS 10=msop10.DAT 9=msop09.xcs 3=rptsis.t1 15=msop15.xcs;
MEDS-CS 19=datsim.out 33=vario.sis
* SIS using ROCK - input from msop09.xcs
DOC sis - with local means
USR = abc / Wed May 6, 2009 8:33:22 AM US Mountain Standard Time
IOP1 = 1 0 / M09, N09

IOP3 = 1 / 0=2D; 1=3D input
IOP8 = 0 / 0=SK, 1=OK
IOP10 = 8 / number of simulated nodes to use
IOP11 = 150 125 1 /# grids in x, y, z
IOP14 = 1 / # of simulations
IOP15 = 2975123 / random number seed
IOP16 = 0 / 1=octant search
IOP17 = / 1=use weight item, 0=none
IOP18 = 0 / 0=output IX,IY,IZ; 1=x,y,z coords
IOP21 = 1 1 / Lower and upper tail option
IOP23 = 1 / Multiple grid search (Default=0)
IOP24 = 0 / 0=no boundary
IOP25 = 1 / No. of model range selection items (Max=2)
IOP26 = 1 / No. of block limiting items (Max=1)
IOP27 = 1 / 1=write to model, 0=ascii output
IOP31 = 2 / 0=SGS 1=SIS 2=SIS LM
IOP32 = 0 / 0=Categorical 1=Continuous variable
IOP35 = 1 / Middle tail option
IOP36 = 1 / 0=Omit, 1=Reset accessed blocks before simulation

PAR10 = 8.3 / Distance tolerance (Default=0.0001)
PAR11 = 20. 20. 15. / dx, dy, dz
PAR28 = 1. 3. / Min and max value for tail extrapolation


PAR38 = 1. / Middle tail parameter

CMD = MOD3D CODES 1 2 3
GET09 = EAST NORTH ELEV. ROCK ROCK

UPD15 = ROCKI TOPO ROCK
UPD15 = RCKP1 RCKP2 RCKP3
I-O = 0
END
MSCS SAMPLE RUN FILE #3 - example of SIS with continuous variable option
MEDS-CS 10=msop10.DAT 9=msop09.xcs 3=rptsis.t2 15=msop15.xcs;
MEDS-CS 19=datsim.out 33=vario.sis
* SIS using ROCK - input from msop09.xcs
DOC sis using continuous variable
USR = / Wed May 13, 2009 3:59:38 PM US Mountain Standard Time
IOP1 = 1 0 / M09, N09

IOP3 = 1 / 0=2D; 1=3D input
IOP8 = 0 / 0=SK, 1=OK
IOP11 = 150 125 1 / # grids in x, y, z
IOP17 = 0 / 1=use weight item, 0=none
IOP31 = 1 / 0=SGS, 1=SIS, 2=SIS LM
IOP32 = 0 / 0=Categorical, 1=Continuous variable
IOP35 = 1 / Middle tail option



PAR11 = 20. 20. 15. / dx, dy, dz
PAR28 = 1. 3. / Min and max value for tail extrapolation
PAR38 = 1. / Middle tail parameter
GET09 = EAST NORTH ELEV. ROCK ROCK

UPD15 = MINEC ROCK
I-O = 0
END
MSCS SAMPLE RUN FILE #4 - example of SGS with input from dat507.oa
MEDS-CS 10=msop10.DAT 30=dat507.oa 3=rptsim.t5 15=msop15.xcs;
MEDS-CS 19=datsim.out 31=bounds.dat 32=datsim.dsp 33=varcun.rk1
* SGS - ascii input from dat507.oa
USR = abc / Fri May 15, 2009 10:05:45 AM US Mountain Standard Time
IOP3 = 1 / 0=2D; 1=3D input

IOP8 = 0 / 0=SK, 1=OK, 4=Colloc. kriging
IOP11 = 150 125 1 /# grids in x, y, z
IOP17 = 0. / 1=use weight item, 0=none
IOP29 = 1 / 1=despiking, 0=no despiking
IOP30 = 0 / Despiking output type


PAR11 = 20. 20. 15. / dx, dy, dz
PAR28 = 0. 3.7 / Min and max value for tail extrapolation
PAR30 = 0. / Correl coeff (if IOP8=4) Default=1
PAR34 = 250. / Search radius for despiking

UPD15 = CUS5 CUPLY ROCK

CMD = CARD INPUT X Y Z GRADE
I-O = 0
END
MSCS SAMPLE RUN FILE #5 - example of Normal Scores Transformation only

MEDS-CS 10=msop10.DAT 9=msop09.dat 3=rptsim.lns;
MEDS-CS 19=datsim.nor 31=bounds.dat 32=datsim.dsp
* Normal Scores using CU - input from msop09.dat
USR = / Tue May 19, 2009 3:40:21 PM US Mountain Standard Time
IOP1 = 1 0 / M09, N09

IOP3 = 1 / 0=2D; 1=3D input
IOP17 = 0 / 1=use weight item, 0=none
IOP29 = 1 / 1=despiking, 0=no despiking
IOP30 = 0 / Despiking output type

GET09 = EAST NORTH ELEV. CU ROCK

I-O = 0
END

HOW TO DEBUG AN MSCS RUN
1. A debug option is available with MSCS by entering I-O=1 or greater in the run file. The higher the debug number, the more
debugging can be done. The program will print the debug data for each block. In order to avoid large amounts of printout, use
this option for test purposes using a relatively small number of blocks.
2. You can optionally specify an input format if ASCII input if used (30=Filename). Default is free format read.
3. ?MSCS : ERROR. No samples were found.

This error message will appear if the program cannot find any sample data for the simulation.
4. ?MSCS : WARNING. No. of Lines read from normal scores transformation file = xxx. This does not match the # input
data.
This message will appear if IOP5=1 and your transformation table is incompatible with input.
5. ?MSCS : ERROR. Must use 3D input (IOP3 = 1) with Rel Elevation.
This message will appear if the user is trying a 2D search with the Relative Elevation option.
6. ?MSCS : ERROR. Must use 3D input (IOP3 = 1) with inclined models.
The error message will appear if the user is trying 2D search with inclined models.
7. ?MSCS : ERROR reading file line in <filename>
This error message will appear if the program cannot read the optional soft data input during SIS. If this happens, check the input
data and make sure its format is compatible with the specific format required by the program. First line in the file should be the
column (field) locations. The columns are x, y, z, and one column of data for each indicator. The second line and thereafter are
the data.
8. ?MSCS : WARNING. Exceeding the max number of composites allowed.
This error message refers to the ASCII input data, which is currently limited to 32,000. If MineSight composite file (File 9)
is used, there is no limit.

MineSight
Proprietary Software: Mintec, inc. MSPCS - CONDITIONAL SIMULATION POST PROCESSING
MSPCS CONDITIONAL SIMULATION POST PROCESSING

The program MSPCS performs statistical analysis of results from The program performs post-processing by calculating one of
multiple conditional simulation runs. the following statistics:
PROGRAM FLOW DIAGRAM 1) Mean and Variance

2) The probability of exceeding a specified cutoff, and the mean
RUN FILE: value above and below a specified cutoff.
3) The corresponding Z-percentile (grade) at a given cdf value.
4) The symmetric P probability interval (around the mean).
- Simulation items 5) Mean and the probability within a specified percent of the
- Data limiting (Optional) mean.
- Desired statistics
Only one method per run is allowed and it should be selected by
specifying an option (IOP8) in the run file.
The program input consists of simulation results that must be

INPUT: CALCS: stored as File 15 items.
Optional data ranging and code limiting items are allowed.

- PCF - Statistical analysis per
- File 15 block. The results can be stored back to the model or can be written
into an ASCII file.
The program allows up to 500 total items (including simulation

items and items storing and for data ranging).
OUTPUT:
- Results stored to file 15

OR
- Results stored to an
ASCII file
- Report File
Revised: 19-March-10 Page MSPCS-1

MineSight
MSPCS - CONDITIONAL SIMULATION POST PROCESSING Proprietary Software: Mintec, inc.
Page MSPCS-2 Revised: 19-March-10

MineSight
MSPCS - CONDITIONAL SIMULATION POST PROCESSING
RUN FILE OPERATION

MEDS-PCS 10=filename 15=filename 3=filename; 31=filename

where
MEDS-PCS - (must be the first 10 columns)

31 = the name of the ASCII Output Data File if IOP9>0
NOTE: The use of File 31 depends on the use of IOP9. For details, please refer to the explanation for IOP9 under Run
Options.
IOP1 = IZ1 START BENCH REF# (default = 1)

IOP2 = IZ2 END BENCH REF# (default = PCF nz)
IOP3 = IY1 START ROW REF# (default = 1)

IOP4 = IY2 END ROW REF# (default = PCF ny)
IOP5 = IX1 START COLUMN REF# (default = 1)

IOP6 = IX2 END COLUMN REF# (default = PCF nx)
IOP8 = OUTPUT OPTION

= 1 COMPUTE THE E-TYPE MEAN AND THE CONDITIONAL VARIANCE (default)
= 2 COMPUTE THE PROBABILITY OF EXCEEDING THE CUTOFF
THE MEAN VALUE ABOVE THE CUTOFF, AND
THE MEAN VALUE BELOW THE CUTOFF
= 3 COMPUTE THE CORRESPONDING Z-PERCENTILE (GRADE) AT A GIVEN CDF VALUE
= 4 COMPUTE THE SYMMETRIC P PROBABILITY INTERVAL (AROUND THE MEAN)
= 5 COMPUTE THE PROBABILITY WTIHIN +/- SPECIFIED PERCENT OF THE MEAN
= 6 COMPUTE THE PROBABILITY WITHIN ITEMS PRECISION OF THE SPECIFIED VALUE
= 7 FIND VALUE WITH MAX PROBABILITY AND THAT PROBABILITY
IOP9 = 0 STORE RESULTS TO THE MODEL (default)

= 1 ASCII OUTPUT - BLOCKS REFERENCED BY COL, ROW, BENCH#
= 2 ASCII OUTPUT - BLOCKS REFERENCED BY COORDINATES (CENTROID)
= 3 ASCII OUTPUT - GSLIB FORMAT - ONLY THE VALUES ARE OUTPUT
IOP10 = 1 RANK SIMULATIONS BY MEAN TOP DOWN (LARGEST FIRST)

= -1 RANK SIMULATIONS BY MEAN IN INCREASING ORDER (SMALLEST MEAN FIRST)

MineSight
MSPCS - CONDITIONAL SIMULATION POST PROCESSING Proprietary Software: Mintec, Inc.
IOP11 = 0 DO NOT STORE SAMPLE SIZE (default)

= 1 STORE SAMPLE SIZE (NUMBER OF VALUES WITHIN PAR1 - PAR2 LIMITS)
NOTE: If storing to file 15, the item should be entered with an ITM=label STORE SIZE command.
IOP14 = NUMBER OF SIMULATIONS (default= all items entered on GET15 and GROUP GET15 lines)
PAR1 = MIN GRADE (default = 0)

PAR2 = MAX GRADE (default = 999999)
NOTE: Statistics are based on the sample of simulation values within PAR1/PAR2 range.
PAR3 = CUTOFF TO COMPUTE Z-PERCENTILE, ETC. VALUE (if IOP8 = 2)
PAR4 = CDF VALUE FOR Z-PERCENTILE COMPUTATION (if IOP8 = 3)
PAR5 = PROBABILITY VALUE FOR THE P INTERVAL AROUND THE MEAN (if IOP8 = 4)
PAR6 = PERCENT VALUE TO USE FOR COMPUTING PROBABILITY WITHIN PERCENT OF THE MEAN
(if IOP8 = 5)
PAR7 = VALUE TO COMPUTE PROBABILITY OF (WITHIN ITEMS PRECISION, IOP8=6).
Simulation items:
GET15 = CUS1 CUS2 CUS3 ROCK ...
Or
CMD = GROUP GET15 prefix start_index end_index zeropad
NOTE: The GET 15 line items are used first, and CMD next.
Items to store results should be entered with UPD line (IOP9=0)

UPD15 = LABEL1 LABEL2 LABEL3
Codes can be checked on one item to be entered with command:

ITM1 = label MODEL CODE
CMD = MODEL CODE code1 code2 ... (up to 10 codes allowed)
Item to store sample size (if storing to model):

ITM1 = label STORE SIZE
Range/omit items can be entered as an ITM or via CMD

ITM = label RANGE val1 val2
ITM = label OMIT val1 val2
or
CMD = RANGE label val1 val2

CMD = OMIT label val1 val2
END

MineSight
MSPCS SAMPLE RUN FILE #1 - Example of how to export to ASCII

MEDS-PCS 10=msop10.DAT 3=rptpcs.asc 15=msop15.500;
MEDS-PCS 31=pstsim.out
* POST SIM starting item
DOC CS Post Processing- Store to ASCII
USR = cus / Thu Mar 18, 2010 11:07:08 AM US Mountain Standard Time
IOP1 = 1 20 / Min, max z ref#

IOP3 = 1 100 / Min, max row#
IOP5 = 10 150 / Min, max col#
IOP8 = 5 / output option

IOP9 = 2 / output type
IOP10 = 1 / Report simulation ranking by Mean

COM 1 = largest first
COM -1 = smallest first
IOP11 = 1 / Store sample size

PAR3 = 0. / Cutoff (IOP8 = 2)
PAR4 = 0. / Cdf value (IOP8 = 3)
PAR5 = 0. / Probability level for Probability interval (IOP8 = 4)
PAR6 = 10. / Percent from mean (IOP8 = 5)
GET15 =
UPD15 = EMEAN PROB
CMD = GROUP GET15 CUS 1 99 1
ITM1 = ALTR RANGE 1. 10.

ITM2 = ROCK MODEL CODE
ITM3 = SAMP STORE SIZE
CMD = MODEL CODE 1 2 4
END

MineSight
MSPCS SAMPLE RUN FILE #2 - Example of listing items

MEDS-PCS 10=msop10.DAT 3=rptpcs.itm 15=msop15.500;
MEDS-PCS 31=
* POST SIM starting cus1 item
DOC CS Post Processing - list items in run file
USR = / Thu Mar 18, 2010 11:17:06 AM US Mountain Standard Time




GET15 = CUS1 CUS2 CUS3 CUS4 CUS5 CUS6 CUS7 CUS8 CUS9 CUS10
UPD15 = EMEAN CONVR
END

MineSight
MSPCS SAMPLE RUN FILE #3 - Example of how to group items

MEDS-PCS 10=msop10.DAT 3=rptpcs.grp 15=msop15.500;
MEDS-PCS 31=
DOC CS Post Processing - group of items
USR = CUS / Thu Mar 18, 2010 11:39:42 AM US Mountain Standard Time




GET15 =
UPD15 = EMEAN CONVR
END

MineSight
MSPCS SAMPLE RUN FILE #4 - Example of Post Processing E-type mean and the
conditional variance (IOP8=1, default)
MEDS-PCS 10=msop10.DAT 3=rptpcs.1 15=msop15.500;
MEDS-PCS 31=
DOC CS Post Processing- E-type mean and the conditional variance.




GET15 =
UPD15 = EMEAN CONVR

END

MineSight
MSPCS SAMPLE RUN FILE #5 - Example of Post Processing Probability exceeding a

specified cutoff (IO8=2)
MEDS-PCS 31=
DOC CS Post Processing- Probability of exceeding a specified cutoff




PAR3 = 0.5 / Cutoff (IOP8 = 2)
GET15 =
UPD15 = PROB MEANA MEANB

END

MineSight
MSPCS SAMPLE RUN FILE #6 - Example of Post Processing Corresponding Z-percentile

(grade) at a given cdf value (IOP8=3)

MEDS-PCS 31=
DOC CS Post Processing- Corresponding Z-percentile (grade) at a given cdf value




PAR4 = 0.5 / Cdf value (IOP8 = 3)
GET15 =
UPD15 = ZPERC

END

MineSight
MSPCS SAMPLE RUN FILE #7 - Example of Post Processing Symmetric P probability

interval (around the mean) (IOP8=4)

MEDS-PCS 31=
DOC CS Post Processing- Symmetric "P" probability interval (around the mean)




PAR5 = 0.5 / Probability level for Probability interval (IOP8 = 4)
GET15 =
UPD15 = MEANA MEANB

END

MineSight
MSPCS SAMPLE RUN FILE #8 - Example of Post Processing E-type Mean and the
probability within +/- specified percent (IOP8=5)

MEDS-PCS 31=
DOC CS Post Processing- E-type Mean and the probability within +/- specified percent




GET15 =
UPD15 = EMEAN PROB

END

MineSight
HOW TO DEBUG AN MSPCS RUN
1. ?MSPCS : ERROR. No file 15 specified on the NAMES line.

This error message will appear if file 15 is missing on the NAMES line in the run file.
2. ?MSPCS ERROR: Number of storing items entered is less than required by IOP8.
This message will appear if the number of items on the PUT15/UPD15 line is less than required by the calculation option IOP8.
3. ?MSPCS : ERROR processing CMD = GROUP GET15 line.
This message will appear if the program cannot make a GET list from teh CMD = GROUP GET15 line. Make sure that the prefix
length combined with the minimum number of decimals does not exceed 5 (max allowed label length).
4. ?MSPCS : ERROR. No simulation items specified.
This message will appear if no items are entered with either GET15 lines or with CMD = GROUP GET15 lines.

MineSight

trademark of Leica Geosystems AG. MSUC - UNIFORM CONDITIONING
MSUC UNIFORM CONDITIONING

MSUC computes recoverable reserves based on kriged estimates The program computes the normal scores transformation of the
of the blocks or panels using a change of support model. input data prior to Uniform Conditioning (UC). If the input data
is already transformed, then this option should be turned off.
It is possible to run the program with the normal scores
RUN FILE: transformation only option. In that case, the program will
only output the normal scores transformation of the data. No
UC is performed.
- Area selection
- Item selection MSUC can perform Despiking if the option is checked.
- Level requests Despiking is a method where identical values of a histogram
- Cutoffs are transformed into a series of different values by adding
small increments. This might be useful for better normal scores
transformation of the data.
INPUT: CALCS: The program input could be from ASCII data, from a MineSight
composite file (File 9), or an MSTorque database. The
program requires the kriged estimates of the blocks or panels
- PCF - Hermite polynomials
to be computed prior to running it, since the calculation of the
- File 9 (optional), - Normal Scores Trans. recoverable reserves are based on the estimated grades from
ASCII File, or - Despiking (optional) kiriging using the change of support model.
MSTorque composite
set The program computes the change of support of coefficients for
- File 15 (optional)
the SMU and panel size blocks. These coefficients are listed
in the report file. Optionally, these coefficients can be input to
OUTPUT: the program directly if they are computed prior to running UC.
The UC results from the program consist of the grade, proportion

- Normal Scores and quantity of metal of the specified cutoffs for each block.
Transformation Table These results are stored into a MineSight block model (File
- Coefficients of Hermite 15). The results can alternatively be output to ASCII.
Polynomials (optional)
- Reserves Summary in
Report File
Revised: 12-August-14 Page MSUC-1

MSUC - UNIFORM CONDITIONING trademark of Leica Geosystems AG.
Page MSUC-2 Revised: 12-August-14

MSUC - PROGRAM FOR UNIFORM CONDITIONING
RUN FILE OPERATION

MEDS-UC 10=filename 9=filename 15(or 14 or 13)=filename 19=filename;

MEDS-UC 20=filename 30=filename 31=filename 32=filename;
MEDS-UC 33=filename 3=filename
where
MEDS-UC - (must be the first 10 columns)

9 = the name of the COMPOSITE FILE OR TORQ (Optional; if file 9 is absent or no MSTorque input,
must have 30 = filename)
15 = the name of the MINE MODEL FILE (Optional) -OR-
14 = the name of the GSM SUMMARY FILE (Optional) -OR-
13 = the name of the 2-D SURFACE FILE (Optional)
19 = the name of the Output File (ASCII) with UC results if IOP20=0 and IOP9=1 -OR-
the name of the Output File with Normal Scores with coordinates if IOP20=1
20 = MSTorque info file (mstorq.inf) (if 9=TORQ is used)
30 = the name of the Optional Input Data File (if no File 9 is specified)
31 = the name of the Output Data File for Normal Scores with no coordinates if IOP5=0 -OR-
the name of the Input Data File with Normal Scores with no coordinates if IOP5=1
32 = the name of the Output Data File for Despiked data (if IOP18>0)
33 = the name of the Intput Data File for Hermite Polynomials (if IOP5=2)
NOTE: The use of File 19 and File 31 depends on the use of IOP20, IOP9 and IOP5. For details, please refer to the
explanation for IOP20 under Run Options.
IOP1 = M09 FIRST DATA UNIT OF FILE #9 TO ACCESS (default = 1)

IOP2 = N09 LAST DATA UNIT OF FILE #9 TO ACCESS (default = last data unit stored)
IOP3 = 1 3-D INPUT (X, Y, and Z)
IOP4 = NUMBER OF INPUT DATA POINTS TO LIST (default = 5, -1 = no list)
IOP5 = 0 TRANSFORM THE DATA

= 1 DO NOT TRANSFORM THE DATA (already transformed)
= 2 THE ANAMORPHOSIS COEFFICIENTS ALREADY CALCULATED (Requires File 33 Input)
NOTE: For additional information, please refer to the explanation for IOP20.

IOP6 = HIGHEST ORDER HERMITE POLYNOMIAL TO USE (default = 10, max = 30)

IOP7 = NUMBER OF CUTOFFS (default = 3, max=10)
IOP8 = UNIFORM CONDITIONING TYPE:

0 = HERMITE POLYNOMIAL
1 = INTEGRAL
IOP9 = OUTPUT:
0 = WRITE TO FILE 15 (default)
1 = GEO-EAS
2 = EXCELL CSV
NOTE: For additional information, please refer to the explanation for IOP20.
IOP10 = TYPE OF ESTIMATE:

0 = Z
1 = Y
IOP11 = ix1 MIN COL (default = 1)

IOP12 = ix2 MAX COL (default = pcfmax)
IOP13 = iy1 MIN ROW (default = 1)
IOP14 = iy2 MAX ROW (default = pcfmax)
IOP15 = iz1 MIN BENCH/LEVEL (default = 1)
IOP16 = iz2 MAX BENCH/LEVEL (default = pcfmax)
IOP17 = 1 USE WEIGHT ITEM (if IOP5 = 0)
IOP18 = 1 PERFORM DESPIKING (if IOP5 = 0) - OUTPUT IN ORIGINAL ORDER

= 2 PERFORM DESPIKING (if IOP5 = 0) - OUTPUT SORTED BY VALUE
IOP20 = 0 UNIFORM CONDITIONING (default)

= 1 NORMAL SCORES TRANSFORMATION AND HERMITE POLYNOMIALS ONLY (no access to model
blocks).
NOTE: The use of File 19 and File 31 depends on the use of IOP20, IOP9 and IOP5:
IOP20 IOP9 IOP5 File 19 and File 31:
1 --- --- When IOP20=1, IOP9 and IOP5 are irrelevant, and
19 = Normal Scores with coordinates (output)
31 = Normal Scores wtih no coordinates (output)
0 0 0 19 = Not used
31 = Normal Scores wtih no coordinates (output)
0 0 1 19 = Not Used
31 = Normal Scores with no coordinates (input)
0 0 2 19 = Not Used
31 = Not Used
0 1 or 2 0 19 = Output File (ASCII) with UC results (output)
31 = Normal Scores with no coordinates (output)
0 1 or 2 1 19 = Output File (ASCII) with UC results (output)
31 = Normal Scores with no coordinates (input)
0 1 2 19 = Output File (ASCII) with UC results (output)
31 = Not Used

IOP21 = NUMBER OF LINES TO SKIP (If the ASCII input option is used, 30=Filename)

IOP24 = 0 NO BOUNDARY (default)

= 1 USE BOUNDARY ON INPUT DATA
IOP25 = NUMBER OF MODEL RANGE ITEMS (default = 0, max = 2)

IOP26 = NUMBER OF MODEL SELECTION ITEMS (default = 0, max = 1)
PAR1 = MIN X
PAR2 = MAX X
PAR3 = MIN Y
PAR4 = MAX Y
PAR5 = MIN Z
PAR6 = MAX Z
PAR7 = MIN GRADE (trimming limits)
PAR8 = MAX GRADE (trimming limits)
NOTE: PAR1-8 ARE USED ONLY FOR INPUT DATA LIMITS
PAR9 = MINIMUM DATA VALUE (required if IOP5=2)

PAR10 = MAXIMUM DATA VALUE (required if IOP5=2)
PAR11 = MINIMUM CUTOFF

PAR12 = CUTOFF INCREMENT
PAR13 = VARIANCE AT SMU SUPPORT (calculated with gammabar)
PAR14 = VARIANCE AT PANEL SUPPORT (calculated from estimates)
PAR34 = SEARCH DISTANCE FOR DESPIKING (default=100.)

PAR35 = DELTV TOLERANCE BETWEEN DATA FOR DESPIKING WHEN IOP18=1 (default = 0.0001)
GET09 = EAST NORTH ELEV. GRADE WT
NOTE: ELEVATION AND WEIGHT ITEMS ARE OPTIONAL (see IOP3 and IOP17)
UPD15 = CUKRG ROCK1 ROCK2 GEOL

UPD15 = PROP1 PROP2 ... METL1 METL2 ... GRAD1 GRAD2 ... ( required if IOP9=0)
NOTE: THE MODEL ITEMS HAVE TO BE IN A CERTAIN ORDER TO PROPERLY ACCESS THE MODEL
1. KRIGED GRADE ITEM TO ACCESS (required)
2. SELECTION ITEM1 (optional) - uses min, max
3. SELECTION ITEM2 (optional) - uses min, max
4. SELECTION ITEM3 (optional) - uses block limit codes
5-N. UNIFORM CONDITIONING ITEMS (proportion, metal and grade above cutoff for each cutoff)
STORING TO FILE 15 IS OPTIONAL(see IOP9)
END

4. INPUT THROUGH AN ASCII FILE: USE THE FOLLOWING COMMAND LINE IN THE RUN FILE.
NOTE: If File 9 is not specified, ASCII input is assumed.
CMD = CARD INPUT LABEL1 LABEL2 LABEL3 LABEL4 ETC.

where
LABEL1 . . . LABELN must be following labels:
X = Easting
Y = Northing
Z = Elevation (Optional if IOP3 = 1)
GRADE = Grade item
WT = Weight item (Optional if IOP17 = 1)
Use format line to read above items:

FMT1 = (5F8.0) <-- Example only
Free format is allowed if data columns are in the same order as the item labels.

MSUC SAMPLE RUN FILE #1

MEDS-UC 10=cs2m10.DAT 30=clusta.dat 3=rptuc.t9 15=cs2m15.uc;
MEDS-UC 19=datuc3.out 31=bound2.dat
* MSUC - ascii input from clusta.dat - output ascii also
USR = / Wed Jan 3, 2007 2:57:54 PM US Mountain Standard Time
IOP3 = 1 / 0=2D; 1=3D input

IOP4 = / No. of input data to print
IOP6 = 30 / highest order hermite polynomial to use
IOP7 = 3 / No. of cutoffs (default=3, max=10)
IOP8 = / uc type: 0=hermite polynomials, 1=integral
IOP9 = 1 / output 0=write to Model, 1=Geo-EAS, 2=CSV
IOP10= 0 / type of estimate: 0 = Z, 1 = Y
IOP11= 0 0 / ix1, ix2
IOP13= 0 0 / iy1, iy2
IOP15= 5 5 / iz1, iz2
IOP17= 0. / 1=use weight item, 0=none
IOP20= 0 / output 0=uc, 1=normal scores and hp only

PAR7 = 0. 60. / min and max input value (trimming limits)
PAR11= 1. / minimum cutoff
PAR12= 1. / cutoff increment
PAR13= 0.7 / Variance at smu support
PAR14= 0.4 / Variance at panel support
UPD15 = CUKRG
I-O = 0
END


MEDS-UC 19=datuc2.nor 31=bound2.dat
* MSUC - ascii input from clusta.dat - write to the model
USR = / Wed Jan 3, 2007 11:46:45 AM US Mountain Standard Time
IOP3 = 1 / 0=2D; 1=3D input

IOP11= 0 0 / ix1, ix2
IOP13= 0 0 / iy1, iy2
IOP15= 4 5 / iz1, iz2

UPD15 = CUKRG
UPD15 = PAC1 PAC2 PAC3
UPD15 = MAC1 MAC2 MAC3
UPD15 = GAC1 GAC2 GAC3
I-O = 0
END


MEDS-UC 10=cs2m10.DAT 9=cs2m09.sgs 3=rptuc.t5 15=cs2m15.uc;
MEDS-UC 19=datuc2.nor 31=bound2.dat
* MSUC using CU - input from cs2m09.sgs, output to model.
USR = / Wed Jan 3, 2007 11:44:34 AM US Mountain Standard Time
IOP1 = 1 0 / M09, N09

IOP3 = 1 / 0=2D; 1=3D input
IOP5 = 0 / transform the data? 0=no 1=yes,2=direct input
IOP11= 0 0 / ix1, ix2
IOP13= 0 0 / iy1, iy2
IOP15= 4 5 / iz1, iz2
IOP17= / 1=use weight item, 0=none
IOP20= / output 0=uc, 1=normal scores and hp only

GET09 = EAST NORTH ELEV. CU

UPD15 = CUKRG
I-O = 0
END


MEDS-UC 19=datuc2.nor 31=bound2.dat 32=datuc2.dsp
* MSUC - ascii input from clusta.dat - use selection items from model
USR = / Wed Jan 3, 2007 12:25:55 PM US Mountain Standard Time
IOP3 = 1 / 0=2D; 1=3D input

IOP11= 0 0 / ix1, ix2
IOP13= 0 0 / iy1, iy2
IOP15= 4 5 / iz1, iz2
IOP25= 2. / No. of model range selection items (Max=2)
IOP26= 1. / No. of block limiting items (Max=1)

CMD = SELCT ITEM1 2 3

CMD = SELCT ITEM2 0.001 1.0
CMD = MOD3D CODES 1
UPD15 = CUKRG GEOL KVAR ZONE

I-O = 0
END

MSUC SAMPLE INPUT FILE

x y z grade wt
39.5 18.5 1. .06 .22
5.5 1.5 1. .06 .27
38.5 5.5 1. .08 .40
20.5 1.5 1. .09 .39
27.5 14.5 1. .09 .24
40.5 21.5 1. .10 .48
15.5 3.5 1. .10 .21
6.5 25.5 1. .11 .36
38.5 21.5 1. .11 .22
23.5 18.5 1. .16 .30
MSUC SAMPLE HP COEFFICIENTS INPUT FILE (if IOP5=2)

PRE_UC Output
2 0.16413188 0.12441459
hermite polynomial order
hermite polynomial coefficients:
0 4.3504257
1 -5.0645275
2 3.5173271
3 -1.5052732
4 0.25566572
5 0.25154215
6 -0.40147409
7 0.32525215
8 -0.50526887E-01
9 -0.23318386
10 0.26586273
11 -0.12512329E-01
12 -0.24396314
13 0.19855297
14 0.92267171E-01
15 -0.25474918
16 0.80439284E-01
17 0.18950680
18 -0.19327511
19 -0.59169326E-01
20 0.21536362
21 -0.71741499E-01
22 -0.16070116
23 0.16008578
24 0.64618267E-01
25 -0.19128238
26 0.37978891E-01
27 0.17119071
28 -0.12293898
29 -0.11485103
30 0.17762768

HOW TO DEBUG AN MSUC RUN
1. A debug option is available with MSUC by entering I-O=2 in the run file. The program will print the input data for each block.
In order to avoid large amounts of printout, use this option for test purposes using a relatively small number of blocks.
2. You can optionally specify an input format if ASCII input if used (30=Filename). Default is free format read.
3. ?MSUC : ERROR. No samples were found.

This error message will appear if the program cannot find any sample data.
4. ?MSUC : WARNING. No. of Lines read from normal scores transformation file = xxx. This does not match the # input
data.
This message will appear if IOP5=1 and your transformation table is incompatible with input.
5. ERROR : smu block variance is less than the panel variance
This message will appear if PAR13 < PAR14.

MineSight
Proprietary Software: Mintec, inc. ELLIPSE2MS - ELLIPSOID FROM INTERPOLATION RESULTS
ELLIPSE2MS - ELLIPSOID FROM INTERPOLATION RESULTS

ELLIPSE2MS creates the debug ellipsoid which contains The program ELLIPSE2MS requires output file 31 from
information about the interpolated block, including a list of the interpolation programs. The parameters for the ellipsoid search
composites used, their weights and locations inside the ellipsoid. must be specified since the program uses these parameters to
generate the object. This option works with only kriging and
PROGRAM FLOW DIAGRAM inverse distance weighting methods.
RUN FILE: It is recommended to run ELLIPSE2MS through the corresponding

procedure (PINTRP.DAT, PINTRPQ.DAT, P624BDG.DAT) to
ensoure consistency of the input generated by the interpolation
- Geometry of the ellipsoid
programs and parameters provided in the run file.
- Zone material type
- Object name
INPUT: CALCS:
- PCF - Retrieve data from

- File with block interpolation output.
coordinates - Calculate ellipsoids
- File with composites geometry
- Create table of
composites
OUTPUT:
- ASCII File
- Table of composite
weights File
Revised: 26-Dec-13 Page ELLIPSE2MS-1

MineSight
ELLIPSE2MS - ELLIPSOID FROM INTERPOLATION RESULTS Proprietary Software: Mintec, inc.
Page ELLIPSE2MS-2 Revised: 26-Dec-13

MineSight
Proprietary Software: Mintec, inc. ELLIPSE2MS - ELLIPSOID FROM INTERPOLATION RESULTS
ELLIPSE2MS - PROGRAM FOR ELLIPSE TO MINESIGHT
RUN FILE OPERATION

MEDS-ELLIP 10=filename 19=filename 3=filename;

MEDS-ELLIP 30=filename 31=filename 32=filename;
where
MEDS-ELLIP - (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE (-10=TEMP FOR A DUMMY PCF)
19 = the name of the Input File with Blocks coordinates
30 = the name of the Input File with Composites (output file 31 from interpolation programs)
31 = the name of the ASCII Output File to be used in program ASCII2MS.EXE to create a MineSight object
32 = the name of the Output File of table of composites weights
IOP1 = NUMBER OF INCREMENTS BETWEEN ELLIPSES ALONG HALF OF MAJOR AXIS (default = 5)
IOP2 = NUMBER OF POINTS ON EACH QUADRANT OF THE ELLIPSE (default = 15)
NOTE: IOP2 CONTROLS THE TRIANGULATION POINTS FOR THE SURFACE OF THE ELLIPSOID. THE
BIGGER THE NUMBER, THE SMOOTHER THE ELLIPSOID SURFACE. MIN=2, MAX=100.
IOP3 = 0 CREATE ELLIPSE

= 1 CREATE ELLIPSE AND COMPOSITE ARRAYS FROM COMPS.XYZ
IOP4 = 0 ANGLES ARE GSLIB ANGLES (ROT1, ROT2, ROT3)

1 ANGLES ARE MEDS ANGLES (ROTN, DIPE, DIPN)
IOP5 = 0 ANGLES WITH RESPECT TO PROJECT COORDINATES (default)

= 1 ANGLES WITH RESPECT TO MODEL COORDINATES

IOP6 = 0 ORIGIN IS IN PROJECT COORDINATES
= 1 ORIGIN IS IN MODEL COORDINATES
NOTE: IOP5 AND IOP6 ARE USED ONLY IF 10=PCF IS ENTERED ON THE NAMES LINE. ANY DUMMY
PCF (-10=TEMP) IS CONSIDERED UNROTATED AND IOP 5 AND IOP 6 ARE IGNORED.
IOP7 = 0 SHOW DRILLHOLE REF# (IF INTERPOLATION PROGRAMS USE COMPOSITES FROM FILE 9)
= 1 SHOW DRILLHOLE ID DHID (IF INTERPOLATION PROGRAMS USE MSTORQUE COMPOSITES)
PAR1 = MAJOR ELLIPSOIDAL AXIS

PAR2 = MINOR ELLIPSOIDAL AXIS
PAR3 = VERTICAL ELLIPSOIDAL AXIS
Revised: 26-Dec-13 Page ELLIPSE2MS-3

MineSight
ELLIPSE2MS - ELLIPSOID FROM INTERPOLATION RESULTS Proprietary Software: Mintec, Inc.
PAR4 = ANGLE1
PAR5 = ANGLE2
PAR6 = ANGLE3
END
Object_Name (default = ellipse)
Object_Material (default = geometry)
ZONE_material_prefix (default = 1)
ELLIPSE2MS SAMPLE RUN FILE #1

MEDS-ELLIP 10=-TEMP 19=block.xyz 3=ellips.rpt;
MEDS-ELLIP 19=comps.xyz 31=tmp.msa 32=tmp.kwt
** Generate Ellipse for MineSight from Interpolation Parameters **
USR = abc
IOP1 = 5 / Number of increments between ellipses along half of major axis

IOP2 = 15 / Number of points on each quadrant of the ellipse
IOP3 = 1 / read and produce composite arrays
IOP4 = 0 / GSLIB-MS rotation angles
IOP7 = 1 / DHID IN HEADER - TORQUE INPUT
PAR1 = 250. / X Major

PAR2 = 250. / X Minor
PAR3 = 80. / X Vertical
PAR4 = 0. / ROT1
PAR5 = 0. / ROT2
PAR6 = 0. / ROT3
END
ellipse
geometry
mat
HOW TO DEBUG AN ELLIPSE2MS RUN
1. ** WARNING ** No object name provided.
If no information is provided after the END line in the run file, default names are used for the object: ellipse, for object mate-
rial: geometry, and 1 for zone prefix (in the case of sub-blocked data).
2. ELLIPSE2MS: WARNING. Exceeded max allowed number of composites. Only the first 500 will be used.
The composite input is limited to 500 and only the first 500 will be saved in the resulting geometry object (ASCII output that
can be processed by ASCII2MS).
Page ELLIPSE2MS-4 Revised: 26-Dec-13

trademark of Leica Geosystems AG. M600-TECHNICAL SECTION
CONCEPTS OF GEOLOGIC ITEMS
Geologic data items serve primarily as qualifiers for each block Use of digitized geologic outlines
of material in the mine model. Qualifiers are usually, but not
always, series of integer codes used during interpolation, reserves Plan maps that show geologic boundaries can be used to
and production scheduling. determine block codes by digitizing the outlines for input to
program M615V1. This program determines the blocks that
Initialization of geologic and physical codes lie within each outline and enters the appropriate code into the
regular 3-D Block Model. This procedure could also be used on
When the 3-D Block Model or Gridded Seam Model is set up a Gridded Seam Model.
(initialized) with M601V1, each geologic code should be set to
the value of the predominant type of material. Then one of the Use of digitized cross-sections
following procedures can be used to enter exceptions or codes
for different areas. M601V1 can also be used to reset or zero There are many projects where cross-sections prepared by
out a code if necessary. geologists or engineers do not correspond exactly to the mine
model because they are spaced at a greater lateral distance than
Use of generated or manually coded data the spacing between the rows of a mine model. In these cases,
it is necessary to project the sections into the model using some
Geologic codes can be manually coded from existing maps to logic. Program M615V2 may be used to input digitized data
provide maximum control in complex physical situations and section-by-section and determine which model blocks fall within
to provide an optional method to update model values. The corresponding geologic units between each pair of sections.
M610V1 program is used to enter manually coded data into a
mine model (3-D or GSM). Store model geology into the composite file
Use of intersecting 3-D planes There are projects where geology is not available in a form that
is convenient to enter for drillhole data. These cases usually
Intersecting 3-D planes can be used to define geological involve creating mine model geology directly from manual
structures such as fault blocks in the regular 3-D Block Model interpretations, usually with one of the 610-series programs.
only. This procedure could also be used to define property Program M617V1 can then be used to read each composite
divisions for different leases or owners. Program M611V1 will value, access the mine model for the code and store that code
calculate the intersection of the specified 3-D planes for each into the composite file.
bench to determine the geometry and then calculate the blocks
that fall within each area. Nearest neighbor assignment of geologic codes
User coded subroutines to define model geology Preliminary geologic codes for the 3-D mine model may be
assigned directly from composites during interpolation using
Geologic surfaces represented by regression equations or by one of the interpolation programs in the 620-series when grades
other algorithms can be used within a user coded subroutine. are being interpolated. The assignment is simply taking the code
This routine can also be used for project calculations and special of the nearest composite as the code of the mine model block.
summaries of the mine model. The main routine, M612V1, is
loaded with the user routine to be used with any model file. A 3D block model or a Gridded Seam model can be rotated
Revised: 12-August-14 PageTEC600-1

M600-TECHNICAL SECTION trademark of Leica Geosystems AG.
MODEL ROTATIONS
with respect to the project coordinates (e.g. to align with the

ore body based on variography or geologic strike, or to follow
a near-vertical vein). Model limits and the project bounds are
independent from each other. The model rotation parameters
are stored in the PCF, and they are the same for all model files
in the project.
Definition of a model rotation.
To define a rotated model one has to specify the rotation origin

and three rotation angles.
Below we will use terms Easting, Northing, and Elevation 3) The third rotation (rot3) is a rotation around the new Y-axis
for project coordinates, and Model X, Model Y, Model Z to finally position new Model X-axis. Positive direction of
for model coordinates. Sometimes the term rotated PCF is the third rotation is up. Figure 3 shows a model rotation with
used instead of a PCF with rotated model. rot1 =25o, rot2 = 0o, and rot3 = -15o.
The first step in defining model rotation is to select the rotation

origin. Rotation origin is the point with model coordinates (0.,
0., 0.). To specify rotation origin one must enter the Easting,
Northing and Elevation of the origin in project coordinates.
The next step in defining model rotation is to enter the rotation

angles. Rotation consists of three consecutive rotations:
1) The first rotation is a horizontal rotation, positive = clock-

wise. We denote the angle of this rotation as rot1. Figure 1
shows horizontal rotation with rot1 = 25o.
Finally, you have an option to change direction of the Z-axis. To

implement this, set the flag to invert the Model Z-axis. Figure
4 shows a model with rot1 = 0o, rot2 = 90o, rot3 = 0o, and with
an inverted Z-axis.
2) The second rotation (rot2) is a rotation around the new

X direction. That rotation should place Model Y-axis into
desired position. Positive direction of the second rotation Figure 4
is up. Figure 2 shows a model rotation with rot1 = 25o and
rot2 = 15o.
Page TEC600-2 Revised: 12-August-14

Model limits. PCF465 = Min Elevation,

PCF466 = Max Elevation.
The model is defined by model limits: XMIN, YMAX, DX,
NX, YMIN, YMAX, DY, NY, ZMIN, ZMAX, DZ, NZ. These The variables reserved for the model rotation parameters:
limits, as well as BENCH TOES should be entered in MODEL
COORDINATES. PCF458 = Easting of the model rotation origin,
PCF459 = Northing of the model rotation origin,
Project bounds. PCF460 = Elevation of the model rotation origin,
PCF467 = Model rotation azimuth (First rotation angle),
Project bounds limit the project area in PROJECT PCF468 = Model rotation dip (Second rotation angle),
COORDINATES. They are used as defaults for plotting and as PCF469 = Model rotation plunge (Third rotation angle),
a default boundary. These limits are independent from the model PCF470 = Flag to invert Z-axis (stored as an integer).
limits, though it is expected that the model is contained within
the project bounds (see Figure 5). Bench/seam compositing with respect to inclined models.
If you performed only a horizontal rotation of your model, the

direction of the Z-axis and the bench elevations do not change.
In this case bench/seam compositing with respect to the model
does not change. However, your project bounds may have
changed, and if you initially composited your file9 using the
PCF boundaries, you may need to reinitialize items EAST and
NORTH to account for new project bounds and then recomposite
the file again.
Figure 5
If your new model is inclined and your composite file was bench
Data in projects with rotated models. (seam) composited (as opposed to length composited), your
file9 will no longer be valid. You will have to recomposite your
All coordinate data in the survey (12), assay (11), and composite
file(s) 9. For bench compositing use the procedure p50101.dat,
(9) files, as well as orientation data in VBM (25) files is stored
for seam compositing use p50102.dat. The options for bench/
in PROJECT COORDINATES.
seam compositing with respect to an inclined model are the same
The grids in the surface (13), GSM summary (14), and model as for regular bench compositing.
files (15) are in MODEL COORDINATES. The surface level
For bench compositing by default the EAST, NORTH, ELEV.
(elevation) in files 13, 14, and GSM file 15 should be stored
items will contain the coordinates of a composite point at a
as the MODEL Z-COORDINATE.
toe plane, which will now be inclined (see Figure 6). As in the
Whenever boundary is used it should be entered in the PROJECT
Easting and Northing coordinates.
Rotating a model using the model rotation tool in ms2.
To initialize a rotated model we suggest initializing a non-rotated

model in ms2compass (File->New->PCF) and then rotating it
using the model rotation tool in ms2 (File->Rotate MineSight
Model (PCF)). Using ms2 allows you to immediately visualize
how a rotated model will be positioned in 3D project space.
PCF variables for model rotation.

Figure 6
Variables in the PCF array reserved for Model limits are:
PCF21 = XMIN, PCF22 = XMAX, PCF23 = DX, PCF24 = NX,
PCF25 = YMIN, PCF26 = YMAX, PCF27 = DY, PCF28 = NY, non-rotated case this point is the projection of the midpoint of
PCF29 = ZMIN, PCF30 = ZMAX, PCF31 = DZ, PCF32 = NZ. a composite interval onto the toe plane. We recommend storing
the TOP and BOTTOM coordinates of the composite as well. If
The variables reserved for project limits are: you use the SLOPE option, then the length along the drillhole
PCF461 = Min Easting, is stored. If you select the THICK option, the length along
PCF462 = Max Easting, the Model Z-axis is stored. It may be advantageous to use the
PCF463 = Min Northing, option to store the actual midpoint of the composite (this option
PCF464 = Max Northing, is invoked by the command, ITMn = ZMID ELEV.). If you

use the ZMID option, you should remember to select the ZMID ellipsoidal search, you do not need to change anything in the
option in interpolation programs. Figure 7 shows the position way you enter your interpolation options and parameters.
of composite points when the ZMID option is chosen.
If you do want to perform an ellipsoidal search, you have an
option to specify rotation of the search ellipsoid. By default,
rotation is in model coordinates. If you align your model based on
variography, then your search ellipsoid will be aligned along the
model axis, and the model search angles will be all zeroes. You
have an option, however, to enter the angles of a search ellipsoid
in project coordinates. Make sure to select the corresponding
toggle on the search parameters procedure panel.
Similarly, variogram rotation angles are by default presumed

to be in model coordinates. You have an option to enter the
variogram rotation angles in project coordinates. If you use
multiple variograms, the angles for all of them must be entered
in the same coordinate system (either model or project).
Figure 7
Note that the model rotation angles are defined exactly in the
same way as the angles used with the GSLIB option for both
For seam composting the EAST, NORTH, ZTOP items store search parameters and variograms (see the following section
the coordinates of a point at the TOP of the seam. It is important Rotation Parameters for Modeling and Variograms).
to remember that for an inclined model, the top and the bottom
of the composite will not only have different Elevations, but In the case of a GSM project with an inclined model, you must
Eastings and Northings as well. Therefore, for seam composites provide an item in a composite file where the composite elevation
you must have not only a ZBOT item, but also XBOT and is stored. If you are using the default EAST and NORTH items
YBOT items. for the composite Easting and Northing, then your Elevation
item is ZTOP. The new option was added to override the default
Using boundary with inclined models. items where composite coordinates are stored. You now have
a choice to use another triple of coordinate items (e.g. XBOT,
The boundary file is always entered in the project (Easting, YBOT, ZBOT).
Northing) coordinates. When you use a boundary with inclined
model files, it is not sufficient to know row and column of the For inclined GSM models you cannot interpolate composite
block to position it properly. Model Z coordinate plays a role ZTOP/ZBOT coordinate into the corresponding seam top/
in determining the Easting and Northing of the block. The bottom coordinate in the model, because they are in different
programs that perform a point boundary check with the model coordinate systems; the latter is a model Z-coordinate value (see
files are m603v1, m607v1, m608v1, m612rp, and m617v1. Figure 8). A new command was added to interpolate the model
For 3D block models all of these programs will check whether Z-coordinate value:
the center of the block is within the boundary. The center of the
block is positioned at the mid-bench. ITMn = label-15 CALC ZCRD INVWT (or POLYG).
For GSM projects special consideration should be taken. There

is no constant model Z-value that can be assigned to the block.
In all programs but one, you should select an item that will
contain model Z value of the block (e.g. ZTOP). The exception
is m607v1, where you will have to select a model Z level. All
blocks will be processed as if positioned on the selected level.
Interpolation and kriging into rotated models.
All of the interpolation programs now have an option to

interpolate from file 9 directly. If your model is rotated, then
you must use file 9. Interpolation from a sorted composite file is
not available in this case. The program will create a temporary
file 8 with composite model coordinates stored and will sort it Figure 8
by model Y coordinate values.
If you work with a 3D Block Model and do not perform an

TECHNICAL CONSIDERATIONS FOR INTERPOLATION
Geologic relationships form the first class of technical on how rapidly the influence of drillhole data is to diminishthe
considerations when planning an interpolation. These higher the power, the less influence a drillhole value has that is
considerations include structural controls, mineralogical controls farther away from a block than another value.
and rock type controls. A code from the mine model is matched
against a code stored on the composites to screen out drillhole If the relative elevation option is used for the z-direction with
values which have characteristics that are different from a given CMD=ELEV IS .. then the relative distance values will be used
block. You may request that one or two geologic items be used for calculating interpolation weights in interpolation instead
in the selection. The block code may be determined from the of the actual elevation values. Similarly for RELX and RELY.
closest composite just prior to the selection process.
The 620-series programs are available in 32-bit and 64-bit
There are many deposits which have definite three-dimensional versions. The results of 32-bit and 64-bit versions may not
trends that must be observed during interpolation. 3-D trend match exactly, however, the 64-bit is faster and more accurate.
planes, specified by a dip and strike, are used to control the Therefore, we recommend you use the 64-bit version.
selection of composites and serve as a basis for weighting the
values used for each block. Since most deposits have multiple Selection of drillhole composites
trends, which are not represented by a single trend, an item must
be included in the model to specify which trend is to be used to Each of the 620-series programs searches the composites file
govern the block calculations. to find data which may be needed for the entire row to be
interpolated. This selection of composite data is performed as
Zones with different characteristics may have to be handled in follows:
separate interpolation runs when areas of influence and weighting
functions are different. The 620-series programs allow you to 1. Composites must lie within the bounds on northings
limit the type of blocks which will be used during a given run, by which is the block midpoint northing + or - PAR2.
using an existing item from the model and a lookup table input [see figure 1]
at run time. The zone codes would normally be stored on the
composites so that a geologic selection can also be performed. 2. Optionally check for RANGE, OMIT and/or TABLE limits
on specified composite items.
When sampling density varies throughout a deposit, you may
need to include an item in the model to keep track of the relative 3. If the SCAN3-D option is specified (DEFAULT=SCAN3-D)
distance from each block to the closest drillhole composite. The then elevation coordinate (ELEV. item in regular composite)
distance can then be used to qualify material within the inventory. must be within the bounds of ZTOE + or - PAR3.
[see figure 1]
The degree of continuity of values within a deposit will heavily
influence the choice of different parameters within interpolation. NOTE: If seams are being interpolated (for a GSM), with
In deposits with poor continuity, you may not be overly concerned discrete codes (1, 2, etc.) for each seam, PARn=0.1 should
with fine tuning the weighting parameters. However, in deposits be used to select data within each seam. However, IOP3=0
with good continuity you will have to find appropriate distance for 2-D circular search should also be used. If the SCAN2-D
ranges, trends and possibly anisotropic factors to properly extend option is specified, no test is performed on the elevation
values. Coal quality parameters often have good continuity, while coordinateSCAN2-D should only be used to interpolate
uranium grades often have poor continuity. File 13 surfaces.
Ideally, search distances in 3-D should be large enough to include 4 Composites must also lie within the bounds on eastings
several values around each block. Variograms and other studies and are determined as X-WEST = (EASTING AT IX1)
should give sufficient information on which to base the selection -PAR1 and X-EAST = (EASTING AT IX2) + PAR1, where
of these distances. When large search distances are used in IX1 and IX2 are specified on an AREA CARD.
inverse distance methods, you may want to limit the maximum [see figure 1]
number of values to be used by utilizing octant selection.
Using MSTorque drillhole composites
The weighting factor for M620V1 to M621V1 is based on the
inverse power of a distance and you must choose the power to be To access the data in an MSTorque database for interpolation,
used. The second or third power (inverse square of the distance, an MSTorque info file must be located in the project directory.
etc.,) are commonly used and the actual choice should be based

Figure 1: Definition of Primary Coordinate Search Parameters (PAR1, PAR2, and PAR3)
This file is created by procedures that provide MSTorque access Example 2:

(e.g., pintrpq.dat). The contents of this file is discussed below.
version 2.0.0.0
The MSTorque info file consists of 7 keywords: torquepath c:\minesight\MSTorque
datasourcefile msop.MSTorqueDataSource.xml
coverage comp1
version - 2.0.0.0 type blastholes
torquepath - the path to MSTorque.exe, usually %medexe%\

MSTorque.
connection - this and project are used if you are using

Windows authentication. If datasource occurs in this file,
then connection and project are ignored.
project - the MSTorque project name.
datasource - SQL authentication. If you have this keyword

in the info file, then connection and project are ignored.
Datasource uses an .xml file - do not edit this file or try to
prepare it by hand. The content is created by MSCompass
when the MSTorque database you are using is attached.
coverage - the composite set in the MSTorque database.
type - the type of sample site. To access drillholes only

use drillholes for the keyword value, for blastholes use
blastholes, to access other composite sample site types use
other, and to get all types of composite sample sites use
all. If the keyword type is not present, all will be used
by default.
Two examples of an MSTorque info file (mstorque.inf):
Example 1:
version 2.0.0.0
torquepath c:\minesight\MSTorque
connection TUCN-LT019-1\SQLEXPRESS2008
project COMPSfromfile9
coverage comp1

Rotation Parameters for Modeling and Variograms
There are many ways to define the same rotation in 3-D space.
MineSight programs now allow three methods to enter rotation. In this section the terms new Northing and new major axis,
and the terms new Easting and new minor axis are used interchangeably.
A. MineSight (MEDS) rotation is defined by the new North direction and the new North-East plane. Three angles, ROTN,
DIPN and DIPE, are used to specify the rotation.
ROTN is the azimuth of the new major (North) axis. ROTN is measured clockwise from the old North axis.
DIPN is the dip of the new major (north) axis.
DIPN is measured from horizontal, positive direction is upwards.
To define the third angle DIPE we will describe the DIPE vector. DIPE vector lies in the new North-East plane. Its
orthogonal projection on the old horizontal plane makes a 90 degree angle clockwise with the new Northing direction
(see figure 2). The angle DIPE is the dip of the DIPE vector. DIPE is measured from horizontal, positive direction is up.

Another way to describe DIPE is the following. Start from the horizontal vector orthogonal to the new Northing and
rotate it by DIPE in the vertical plane until it reaches the new North-East plane.
Figure 2
B. Geostatistical Software Library (GSLIB). This definition follows the book GSLIB Geostatistical Software Library and
Users Guide by C.V. Deutsch and A.G. Journel [1]. The rotation is split into three elementary rotations.

The first one rotates the original North axis in the horizontal plane by the angle ROT1. Positive direction is clockwise.

The second type rotates the North (major) axis from horizontal. Positive direction is up. The angles ROT1 and ROT2 are
exactly the azimuth and dip of the new major (North) axis.

The third rotation leaves the new Northing axis intact. It rotates the minor axis by the angle ROT3 to its final position
(see Figure 3). Note that in this case rotation is performed in the plane orthogonal to the new major (North) axis.
Positive direction is clockwise if looking from the end of the major axis towards the origin.

Figure3
Another way to describe ROT3 is the following. Start from the horizontal vector orthogonal to the new Northing
direction and rotate it by ROT3 in the plane orthogonal to the new Northing axis untilFigure 3 it reaches the new Easting
axis.
Relations between GSLIB and MEDS angles are:
ROT1 = ROTN
ROT2 = DIPN
tanROT3 = cosDIPN * tanDIPE
C. Using coordinates of three points on the new major-minor plane (COORD).
MineSight programs now provide an option to define rotation with coordinates of three points on the new North-East
plane. The first point should be the ORIGIN of rotation. The second point shoud be on the positive ray of the MAJOR
(new North) axis. The third point should be any point of the new North-East plane with positive value of the new East
coordinate (Figure 4). MineSight programs expect coordinates of three points to be prepared in an ASCII file. The first
line contains three coordinates (Northing, Easting, Elevation) of the Origin. The second line contains three coordinates of
a point of the major axis, and the third line contains the three coordinates of a point on the new North-East plane.
Figure 4
LITERATURE.
[1] Clayton V. Deutsch, Andre G. Journel, GSLIB Geostatistical Software Library and User s Guide
Oxford University Press, New York, Oxford, 1992

Sub-blocked Model Data Access
A MineSight Sub-blocked file is an extension of the 3DBM file15 M617V1 (p61701.dat):

that allows storing detailed information for selected items in Back-coding of composites.
areas such as contact zones. The Sub-blocked file can be created
in the MineSight Sub-block File Editor which is invoked from M620V1/V2 (pintrp.dat, pintrpq.dat, p62001.dat):
the Model Menu in MineSight 3D (MS3D). [see also the MS3D IDW interpolation.
help documentation, MS3D.CHM]
M621V1 (pintrp.dat, pintrpq.dat, p62001.dat):
Sub-blocking is uniform in all blocks and is defined by the IDW with trend planes.
number of sub-divisions of a parent block in each of model
directions (X, Y, and Z). M624IK (pintrp.dat, pintrpq.dat, p62402.dat):
Indicator kriging.
Each item in the sub-blocked file is stored independently.
M624MIK (pintrp.dat, pintrpq.dat, pmik01.dat):
The sub-block file stores data only for blocks where the item Multiple indicator kriging.
has multiple values within a parent block. If an item is not sub-
divided in a given block, the value is retrieved from the model M624V1 (pintrp.dat, pintrpq.dat, p624db.dat, p624p1.dat,
file15. p62403.dat):
Kriging.
Geologic domains can be entered to the sub-blocked model by
coding with MSCODE.EXE or within MS3D. [Note: for help BLKINF (sblkinfo.dat):
with MSCODE, see StandaloneEngines.CHM and for help with Report number of zones per block and volume by zones.
model coding within MS3D, refer to the Model View Properties
documentation in MS3D.CHM]. MSB2MOP (sblktomop.dat):
Calculate majority percents, codes and grades (average or
The grades can be interpolated or kriged using standard majority) from selection of sub-blocked items defining zones.
interpolation/kriging procedures and programs. The result can be stored to a different (not sub-blocked) file 15.
When grades are interpolated to sub-blocked items, the search MSB2PR (sblkparent.dat):
distances are measured from the block center. However, if you Calculation of parent values from sub-blocked data; volume and
are using block limiting or geologic matching, the grades are tonnage average, majority coding and other methods are allowed.
stored only to sub-blocks with the corresponding geologic codes. MSB2PR can populate the parent block value of a sub-blocked
item, or store the value into another parent block item.
User calculations are also available for sub-blocked data.
MSBCODE (sblkmajpct.dat):
The MSBasis programs modified for sub-blocking access use Calculate majority percents and codes from sub-blocked zones
sub-blocked values for a block, if sub-blocked data is present. based on selection of sub-blocked items defining zones.
Programs with access to sub-blocked values: QUICKDUMP (qdump.dat):

List zone values and the sub-block count for selected items.
M601V1 (procedure p60103.dat):
Reset model value reset parent block value and clears sub-
blocked data. cp-modelCalcTool.pyz:
This MSCompass script accesses sub-blocked data.
M608V1 (p60801.dat, p60802.dat):
Basic bench and cutoff statistics
All other programs will access the parent block values only.
M612RP (p61201.dat):
User calculations.

MineSight
Proprietary Software: Mintec, inc. Writing MineSight User Subroutines
Writing MineSight User Subroutines
The User Subroutine Programs provide a way to directly access Mintec provides a compiled driver routine (known as an object
and manipulate data in your MineSight files. User subroutine module) that reads and/or writes data to your MineSight file.
programs will allow you to access data in your assay file (File You provide the User Subroutine to manipulate the data. Your
11), composite file (File 9), model files (Files 13,14, and 15), User Subroutine must be compiled and then linked to the driver
and Dipper files. routine to form an executable program. Your executable program
is run just like all the other MineSight programs - with a run file.
To build and run a User Subroutine program, you need:
The steps necessary to build a User Subroutine program are
1. A working command of FORTRAN outlined in detail in the documentation that follows. Examples
are discussed for each type of User Subroutine program and
2. The appropriate FORTRAN compiler and linker for your the actual programs, run files, and output for each example are
computer. given at the end of the section.
MineSight Program
Quick Overview
The following is an example of the steps necessary to build a

User Subroutine program. If you are not already familiar with
User Subroutines, you should go through at least one of the
detailed examples that follow.
Example: Build a User 208 program (M208V1)
Step 1: Write the User Subroutine. The subroutine name

MUST be USR208. The file containing the subroutine MUST
have a .f extension. For example, assume your user routine is
in file fil208.f
Step 2: Build the User Subroutine Program. Use the batch

file bldusr.bat located in the USER subdirectory of your
%MEDEXE% directory. The command to build an executable is:
bldusr m208v1 fil208
You should have executable M208V1.EXE in your local

directory.
Step 3: Run the User Subroutine program. Make a run file

and execute the program as specified in the documentation for
program M208V1.
Revised: 25-July-13 Page TEC600-10

MineSight
Writing MineSight User Subroutines Proprietary Software: Mintec, inc.
Running a User Subroutine Program - an Overview Skeleton Driver Program Object Module
usr208.f m208v1
1) First, check with Mintec. We have many existing user
subroutines. We might even have one that performs the usr508.f m508v1
operation you want or a similar operation. These are avail-
able at no cost to clients. Mintec will also be happy to write u612d1.f m612d1 99-item m612v1; unlimited columns
or modify a user subroutine to your specifications. For this & rows & benches
service we charge a nominal fee. u612db1.f m612db1 500-item m612v1; unlimited columns
& rows & benches
2) Determine which program to use. Start by determining
which program accesses the file you want to manipulate. u612d2.f m612d2 99-item m612v2; unlimited columns
& rows & benches
You can access data in composite files (9), assay and survey u612db2.f m612dl2 500-item m612v2; unlimited columns
files (11, 12), 2-D surface files (13) GSM summary files (14), & rows & benches
3-D block model files (15) and DIPPER files.
u708d1.f m708d1 99-item m708v1; unlimited columns
FILES PROGRAM
& rows & benches
11, (12) M208V1 u708db1.f m708db1 500-item m708v1; unlimited columns
9, (12) M508V1 & rows & benches
13, 14, or 15 M612V1 (bench) usr718.f m718v2

13, 14, and 15 M612V2 (section)
b) First note the order in which the user subroutine is called
13, 14, or 15 M708V1 (read only) in the program. For example, program M208V1 will call
the user subroutine:
DIPPER files M718V2
i) at the beginning of the program run (initialization),
Although you can read and write to File 12 (M208V1 and ii) for each assay in the current survey interval,
M508V1), in most cases it is not necessary. If you have iii) at the end of the current survey interval,
a situation that requires accessing File 12, please contact iv) at the end of the current drillhole, and
Mintec for assistance. v) at the end of the program run.
c) Next examine the manner in which the data is accessed.
3) Write your subroutine. Write a FORTRAN subroutine to Recall that in FORTRAN there are only two ways to pass
perform the required manipulations and output the desired data between subroutines; the data must be in a Common
results. block or in the argument list.
a) Mintec provides skeletons of possible User Subroutines For example, program M208V1 retrieves data one assay
located in the user subdirectory of the %MEDEXE% at a time and the data is stored in array RDAT in common
directory (the files with the .f extension). These skeletons block /ITM/. M612V1 retrieves data for an entire model
give you a starting point to begin writing your User row and stores it in array RMX in the user subroutine
Subroutine. Each file has the basic logic structure cor- argument list. For specifics on each program, see the
responding to the order in which the User Subroutine is examples that follow.
called (see below). Each skeleton will also contain any
relevant Common blocks. d) Select the file items that you want to read or write. Also
note the information needed that is not contained in your
The table below shows the correspondence between the MineSight file, e.g., your model Easting and Northing
skeleton files and driver program object modules. Note or a drillhole name. Much of this information is available
that some object modules have been compiled using the via common blocks (see Useful COMMON BLOCK
same source program. For example, object modules Variables, page TEC600-17), or the user subroutine
m612d1 & m612db1 have been compiled using source argument list.
program m612v1; the major differences being that
m612d1 is limited to 99 items and m612db1 is limited
to 500 items. The same note applies to source programs e) Write the user subroutine. The file name of your user
m612v2 and m708v1. subroutine should have an .f extension (e.g., usr208.f).
Page TEC600-11 Revised: 25-July-13

MineSight
f) Although it is common to name the file the same name 6) Make production runs. Now your program is ready to
as the subroutine (e.g., the file name is USR208.F, and make production runs. Make sure you periodically check
therefore the object module name is USR208.OBJ for the the stored results.
subroutine USR208), it is not necessary that they have
the same name. In fact, you will most likely have more
than one user subroutine for M208V1 and do not want to Example: M208V1 (M508V1)
overwrite the .OBJ and .EXE files each time you build a
M208V1 allows you to read and/or write data to File 11. For
new user subroutine program for M208V1. To prevent
example, say you want to use items T-CU and MOLY to compute
this, name your subroutine files something different than
an equivalent grade (EQCU) and store this value back into File
the subroutine name. For example, if you were to have
11. Say also that you want to compute the number of equivalent
three different user subroutines for M208V1, you could
grade values in each drillhole that exceed a specified cutoff. And
name the files U208A.F, U208B.F, and U208C.F. In each
finally, you want to list this number by drillhole to an external file.
of these files the first executable line would be SUBROU-
TINE USR208 (NTRY, IDH). When you compile in the The name of your user subroutine must be USR208 although
next step, the resulting .OBJ files will be U208A.OBJ, your filename can be anything as explained in step 3f above.
U208B.OBJ, and U208C.OBJ. However, when linking, Routine USR208 has two arguments: NTRY and IDHN. These
the resulting executable will always be M208V1.EXE. arguments should not be modified in the user subroutine.
In order to keep with your nomenclature and not to over- Argument NTRY tells the user subroutine which action to take.
write previous executables, you can copy this executable As noted above, M208V1 calls the user subroutine :
to U208A.EXE, U208B.EXE, and finally, U208C.EXE.
i) At the beginning of the program run (NTRY=1)
4) Build your executable. Mintec provides a command file ii) For each assay in the current survey interval (NTRY=2)
called BLDUSR.BAT to make it easy to compile and link
your User Subroutine program. To use bldusr, you must iii) At the end of the current survey (NTRY=3)
have a FORTRAN compiler, linker, and library in your path.
If you get a Command not found error when executing iv) At the end of the current drillhole (NTRY=4)
bldusr, its likely that your FORTRAN directory is not in v) At the end of the program run (NTRY=5)
your path.
To use bldusr, the source file containing your user sub-

routine must be in your local directory. The driver routine
object module (e.g. m208v1.obj) and the MineSight library
LIBUSRDYN.LIB (LIBUSRDYNB.LIB) can either be in
your local directory or in the %MEDEXE% directory.
As an example, the following bldusr command makes a

User 718 program from subroutine USR718 located in file
dip718.f:
BLDUSR M718V2 DIP718
By default, the resulting executable will be named by the

object module name (M718V2.EXE in the above example).
You can optionally specify a different name for your
executable. Use:
BLDUSR M718V2 DIP718 -OUT DIP718.EXE
to create a DIP718.EXE program.
5) Test your subroutine. Before you test your subroutine,

make a backup of all MineSight files that it accesses. Run
your program on a small subset of your data first, making
sure to use the NO STORE option. Use your subroutine to
list the computed data. CAREFULLY check that the results
are correct.

MineSight
Argument IDHN is the drillhole reference number. Other Once youve compiled your user subroutine and have linked
useful information is available in common blocks (see Useful it with the M208V1 object module, youre ready to test
COMMON BLOCK Variables, page TEC600-17). In our your executable. After making backups of your MineSight
example, we will need: files, try it on a small portion of your assay file. IOP1 and
IOP2 allow you to select the survey records you want to
access. Also, while youre testing your program, set IOP6=0.
a) The drillhole name: ADH in /EXTRA1/. This is a character
This will prevent any data from being stored back to File
string variable of length 10.
11. Thoroughly check the values being computed by your
routine. Use your routine to print out intermediate and final
b) The logical file numbers (LFN) for the screen and report results of your computations.
file: LPR and IPR in /SYS/. Note that LPR is the LFN for
the screen and IPR is the LFN for the report file. When everything is working properly, youre ready to make
a production run. Dont forget to reset IOP6=1 if you want
c) The File 11 data. The data is stored in RDAT in /ITM/. The to store values back into File 11.
pointers to a particular items data are given by K11GET
and K11PUT in /USR/ (see Sample Program for M208V1, Example: M612V2 (M612V1)
page TEC600-22). For example, if in your run file you have
the lines: M612V1 and M612V2 provide access to your model files: 13, 14,
GET11 = T-CU MOLY and 15. Both programs operate on rows of data. The difference is
PUT11 = EQCU that M612V1 will process all the rows in a bench and M612V2
will process the rows in an east-west section. Additionally,
Then: M612V2 lets you access two model files in one run.
RDAT(K11GET) will have the T-CU value Suppose you have two surfaces in your File 13 that define a
RDAT(K11GET+1) will have the MOLY value geologic zone. For blocks in this zone, we want to assign a
RDAT(K11PUT) should have the computed grade value relative elevation, say a fraction between 0 and 1 that indicates
a blocks elevation relative to the zones bottom elevation.
Note that the pointers are a function of the order in which
the item is specified in the run file. Therefore, all your
GET11 items must occur consecutively in your run file, as
must all your PUT11 items. Do NOT, for example, have:
GET11 = T-CU
PUT11 = EQCU
GET11 = MOLY
In this case K11GET+1 would point to EQCU and not to

MOLY.
d) Unused IOPs and PARs (as well as the IOPs and PARs
already used by the program) are available in /SYS/. For
example, we can use PAR1 in the run file to parametrically
enter different cutoffs. So if the run file contains line:
PAR1 = .2
then PAR(1) in /SYS/ will have the value .2 and can be Since we need to simultaneously access Files 13 and 15, we will
accessed directly in your subroutine. Caution: Before you use M612V2. This means the model data will be accessed by
use an IOP or PAR, check the program documentation section. For both M612V1 and M612V2, the user subroutine is
to make sure it is not already used by the program. For called USR612D. (See documentation for each program). Both
example, IOP1 is used to select the initial survey record, programs use the argument NTRY to tell the user subroutine
so although this value is available to your user subroutine, what action to take. For IOP3=2, program M612V2 calls the
it should not be redefined for another purpose by the user subroutine:
subroutine.
i) At the beginning of the program run (NTRY=-1)
Now we have all the information necessary to write the ii) After a row of data has been read (NTRY=0)
subroutine (see Sample Program for M208V1, page iii) At the end of each row (NTRY=1)
TEC600-20). iv) At the end of the program run (NTRY=2)

MineSight
The MAXITM argument is derived from the number of items

in file 10; thus the program sets MAXITM=ITEMS. If using
object module m612d1 or m612d2, MAXITM cannot exceed
99 items. If using object module m612db1 or m612db2,
MAXITM cannot exceed 500 items. The Fortran program makes
use of a PARAMETER statement setting constant MXITM=99
(for m612d1 & m612d2) or MXITM=500 (for m612db1 &
m612db2) to ensure MAXITM <= MXITM (take care not to
confuse variable MAXITM with constant MXITM). The ITEMS
value is found in common block /ITM/.
For this example, say the upper elevation of the zone is stored
in item TOPOI in File 13. The bottom elevation is stored in
item TOPOD, also in File 13. We want to store the computed
relative elevation in item EXTRA in file 15. Thus, if the run file
contains the lines:
PUT15 = EXTRA
GET13 = TOPOI TOPOD
Using index IC to range from arguments MCOL to NCOL, we
can access specific values within the RMX array. RMX(IC,1)
should be the computed value of EXTRA. RMX(IC,2) will be
the retrieved value of TOPOI. RMX(IC,3) will be the retrieved
value of TOPOD.
Note that it is up to you to compute and store a value in

The M612 programs use the following subroutine argument list: RMX(IC,1). Since this element corresponds to a PUT item,
SUBROUTINE USR612D (NTRY, IZ, ZMID, IROW, values assigned to it will be stored back to the model file. Model
YROW, MCOL, NCOL, MAP, RMX, MXCOL, MXROW, values will be retrieved for RMX(IC,2) and RMX(IC,3) since
MAXITM) they correspond to GET items. Modifications made to these
items will NOT be stored back into the model file. If you want
In addition to NTRY, the other arguments are defined as: to both retrieve and store a model item, either declare it as a
UPD item (e.g., UPD15 = EXTRA) or declare it as both a GET
IZ the current bench
and a PUT item (eg, GET15=EXTRA, PUT15=EXTRA). In the
ZMID mid-point elevation of the current bench second case, the EXTRA value thats retrieved will be a separate
element in the RMX array from the EXTRA item thats stored.
IROW the current row
YROW mid-point northing of the current row If a retrieved value is undefined (either UNSET or MISSING),
its value in the RMX array will be equal to the value stored in
MCOL, NCOL range of columns (IOP5 and IOP6) array element PCF(490) in common block /F10/ (see Useful
COMMON BLOCK Variables, page TEC600-17). This value
MAP array for storing integer values used in the
is known as the OMIT constant. Note that PCF(490) is a floating
symbol map (IOP10)
point (real) number as are the elements of RMX. You can not do
FORTRAN calculations on undefined values, so your subroutine
RMX array containing the model values for 1 row
should make some provision in the event it encounters one.
MXCOL column dimension for RMX & MAP and any
user defined array This is all the information needed to write the subroutine (see
MXROW row dimension for any user defined array Sample Program for M612V2 page TEC600-23).
MAXITM item number dimension for RMX and any user
defined array Again, after backing up your files, test your program on a small
subset of the model. While youre testing, set IOP4=-1 so that
The MXCOL and MXROW arguments are derived from no values are stored back to your model file.
the NX & NY PCF values in file 10; thus the program sets
MXCOL=NX=PCF(24) and MXROW=NY=PCF(28). The
PCF values are found in common block /F10/.

MineSight
Example: M708V1 The other arguments in M708V1 are very similar to those in
the M612 programs:
Program M708V1 is intended to produce customized reserves
reports, but you do not have to use it for this purpose. M708V1 IZ the current bench
provides read-only access to your model files. You can not
NSEQ sequence number for the current partial
use this program to modify your model values. M708V1 also
(see sequence number in the description for the
processes block partial information, either from a separate file
partials file contents)
or following the run file END line.
IROW the current row
For this example, we want to calculate total copper (TCU-1) and
moly (MO-1) reserves based on cutoffs and ore types (CODE). YROW mid-point northing of the current row
The user subroutine is called USR708D. See the M708V1 MCOL, NCOL range of columns (IOP5 and IOP6)
documentation for details. Again argument NTRY is used to tell MTX array containing the undecoded model values
the subroutine what action to perform. For IOP3=2, program for 1 row.
M708V1 calls the user subroutine:
MXCOL column dimension for MTX and any user defined
i) At the start of program run (NTRY=-1) array
ii) After a row of data has been read (NTRY=0)
iii) At the end of each row (NTRY=1) MXROW row dimension for any user defined array
iv) At the end of the program run (NTRY=2)
MAXITM item number dimension for MTX and any user
defined array
See the program documentation for details.
Note that M708V1 passes information to the user routine via
an INTEGER array (MTX) which has undecoded values in
it. This means two things:
1) The undefined (UNSET/MISSING) values must be checked
against an INTEGER value, not a floating point. This is array
element PCF(489) in common block /F10/.
2) Before a value can be used, it must be converted to a float-
ing point (real) number. The integer values in MTX must be
multiplied by its precision (array CODE in common block
/ITM/) to convert it into a real number. An items precision
is in the same array elements as its value in MTX.
You must check if the variable is well-defined (i.e., its not
UNSET or MISSING) first before you convert it to a floating
point number.
For example, if the item used for computing the reserves is TCU-
1 (i.e., the run file contains the line GET15 = TCU-1 ) then to
use and decode the value for TCU-1, assuming its the first item
specified in the run file:
C
IF ( MTX(IC,1).NE.IPCF(489))THEN
C TCU-1 is defined
TCU1=MTX(IC,1)*CODE(1)
C
ELSE
C TCU-1 is not defined...skip calcs
GOTO 100
END IF
(perform calculations)
100 CONTINUE

MineSight
Alternatively, M708V1 can be instructed to use the floating point CONCLUSIONS

array RMX. See M708V1 documentation for details.
The examples given above demonstrate the basic capabilities of
We now have enough information to write the subroutine (see the User Subroutine Programs. Additional options and ideas can
Sample Program M708V1, page TEC600-27). be found in the MineSight documentation for each program. If
you need help or advice please contact Mintec.
As always, test your program on a small portion of your model.
Since M708V1 cannot write to your model file, there is no option
to prevent storing data and no need for backup.
Example: M718V2
Program M718V2 reads the 2-D surface file (File 13) and the 3-D
block model file (File 15) and condenses them creating a DIPPER
set B-file and S-file. Your DIPPER set must be initialized prior to
running M718V2. You can initialize DIPPER by either running
M717TS or M717V1 to set up the DIPPER descriptors.
In this example, we will create a $DIPPER set with file 15
items TCU-1 and TCU-P. Using TCU-1 and TCU-P (which are
percentages of copper), the tonnage factor specified in PAR10,
and the price of copper (cents/lb) specified in PAR11, we will
calculate the gross dollar value of copper in a block (VALUE).
Subroutine USR718 is called for every block specified by IOP1
through IOP6. There are 4 items in the argument list:
VALUE The computed dollar value for the block. This
value must be assigned by your user subroutine.
IX,IY,IZ The column, row, and bench number of the
current block. These values should NOT be
modified by your user subroutine.
The values for block model items selected via the ITM command
are returned in array RDAT in common block ITM. An items
location in ITM is given by LOCDAT in common block USR.
For example:
Run file: ITM1 = TOPOG TOPO
ITM2 = TCU-P GRADE
ITM3 = TCU-1 USER
ITM4 = CODE CODE
Program: RDAT(LOCDAT(1) ) has the block model

value for TCU-P
RDAT(LOCDAT(2) ) has the block model
value for TCU-1
RDAT(LOCDAT(3) ) has the block model
value for CODE
Note that File 13 item in TOPOG can not be accessed through
the RDAT array.
To use the tonnage factor to compute a tons-per-block conversion
factor, you need to know the block volume. The block dimensions
are stored in array PCF in common block /F10/.
For additional examples of information available in common
blocks, see Useful COMMON BLOCK Variables, page
TEC600-17.

MineSight
Proprietary Software: Mintec, inc. M600-TECHNICAL SECTION
Useful COMMON BLOCK Variables
These descriptions are relative only to source programs M208V1, M508V1, M612V1, M612V2, M708V1 and M718V2. All variables
are available to all programs unless otherwise indicated. Complete listings of the common blocks follow the variable descriptions.
IMPORTANT NOTE: m612db1, m612db2, m708db1 use /ITMB/ and /SYSB/ common blocks. In common blocks /SYS/ and
/SYSB/ some arrays are dimensioned differently. In common block /ITMB/ arrays are not only dimensioned differently, but one
mode array is added.
Variable Common Comments
ADH EXTRA1 Ten character string containing the current drillhole name.
Used in M208V1 and M508V1.
RX1, EXTRA2 The current assays starting and ending xyz coordinate.
RX2, Used in M208V1.
RY1,
RY2,
RZ1,
RZ2
NDAT USR Number of file 15 items in the run file used in M718V1.
K11GET USR Pointer to the first GET11 item whose information is stored in /ITM/.
Used in M208V1.
L11GET USR Pointer to the last GET11 item. Used in M208V1.
K11PUT USR Pointer to the first PUT11 item. Used in M208V1.
L11PUT USR Pointer to the last PUT11 item. Used in M208V1.
K09GET USR Pointer to the first GET09 item whose information is stored in /ITM/.
Used in M508V1.
L09GET USR Pointer to the last GET09 item. Used in M508V1.
K09PAK USR Pointer to the first PUT09 item. Used in M508V1.
L09PAK USR Pointer to the last PUT09 item. Used in M508V1.
LOCDAT USR 40 element array containing pointers to each file 15 ITMs location in RDAT.
Used in M718V2.
IOP SYS 40 (in /SYS/) or 500 (in /SYSB/) element array corresponding to the IOP values specified in
the run file.
PAR SYS 40 (in /SYS/) or 500 (in /SYSB/) element array corresponding to the PAR values specified in
the run file.
ICR SYS The logical file number (LFN) for reading from the run file.
IPR SYS The LFN for writing to the report file.
LPR SYS The LFN for writing to the screen.
IOLEV SYS The I-O level set in the run file.
ITM ITM/ITMB ITM(3,MXITM) contains three elements of information for items. The array is dimensioned
to ITM(3,99) in the /ITM/ common blocks and to ITMB(3,500) in the /ITMB/ common block.
The latter is used in USR612D/USER708D subroutines when linked with m612db1,
m612db2 and m708db1 object modules.
The items include all the GETxx, PUTxx, UPDxx, INPxx, and OUTxx items specified in the run file as well as all the items specified
with ITMxx commands. Additionally, some programs may add required items to ITM. Of the three elements of information, the
important one is the item label. This label can be retrieved as follows:
DIMENSION LABEL(5)
CHARACTER ALABEL*5
CALL NEWSMR ( 1, 1, ITM(2,i), 5, LABEL )
Revised: 31-January-12 Page TEC600-17

MineSight
M600-TECHNICAL SECTION Proprietary Software: Mintec, inc.
WRITE ( ALABEL, ( 5A1 ) ) LABEL
In the above, i indicates the ith item whose information is stored in /ITM/
and string variable ALABEL will be its label. See the M708V1 sample program.
ITEMS ITM/ITMB Total number of items with information stored in /ITM/.

VMIN ITM/ITMB VMIN(MXITM). An items minimum value. MXITM=99 in /ITM/ and MXITM=500 in /ITMB/.
VMAX ITMB only VMAX(MXITM=500). An items initialized maximum value.
CODE ITM/ITMB CODE(MXITM). An items precision. MXITM=99 in /ITM/ and MXITM=500 in /ITMB/.
RDAT ITM/ITMB RDAT(MXITM). An items value. Used in m208v1 and m508v1.
PCF F10 PCF(512). An array containing PCF information as set in M101V1.

Integer values can be retrieved by EQUIVALENCing (see sample program m612v2).
PRTL PRT PRTL(MXCOL). An array containing a blocks partial fraction, i.e., a value between 0 and 1. Used in m708v1.
This is a summary of commonly used PCF values. All the values in this summary are stored as floating point (real) numbers, except
element 489, the integer OMIT constant. See the M612V2 and M718V1 examples for usage.
Number What It Is
21 Minimum Easting
22 Maximum Easting
23 Easting block size
24 Number of blocks in East-West direction
25 Minimum Northing
26 Maximum Northing
27 Northing block size
28 Number of blocks in North-South direction
29 Minimum Elevation
30 Maximum Elevation
31 Vertical block size
32 Number of blocks in vertical direction
50 Crest of top bench
51-450 Bench elevations or seam names and numbers
489 Integer OMIT constant
490 Floating point OMIT constant.
Page TEC600-18 Revised: 31-January-12

MineSight
COMMON BLOCK Listings:

CHARACTER ADH*10
COMMON / EXTRA1 / ADH
COMMON / EXTRA2 / RX1, RX2, RY1, RY2, RZ1, RZ2
COMMON /SYS/ NAMES(80), RNID(20), IOP(40), PAR(40), IFMT(20,4),
& LDAY(4), LALF(20), ICR, IPR, LCR, LPR, LINE, LLIM,
& IHS, JUCMD, IRTYPE , IOLEV, RUNUMB, USER, LBTS,
& IPDP, IHEAD(8), NPAGE, NDOCL, LDOC(15,5)
COMMON /SYSB/ NAMES(80), RNID(20), IOP(500), PAR(500), IFMT(20,4),

& IHS, JUCMD, IRTYPE, IOLEV, RUNUMB, USER, LBTS,
C
COMMON / ITM / ITM(3,99), NIC(5,40), ITEMS, NICNO,
1 LWRD(99), NBIT(99), LBIT(99),
2 VMIN(99), CODE(99), ROND(99),
3 VFCT (99), MAXV(99), RDAT(99),
4 IDAT(99)
C
COMMON / ITMB / ITM(3,500), NIC(5,500), ITEMS, NICNO,
1 LWRD(500), NBIT(500), LBIT(500),
2 VMIN(500), CODE(500), ROND(500),
3 VFCT(500), VMAX(500), MAXV(500),
4 RDAT(500), IDAT(500)
COMMON / F10 / PCF(512), XDUMD(142)
COMMON / USR / K11GET, L11GET, K11PUT, L11PUT, XDUM0(12)
COMMON / USR / K09GET, L09GET, K09PUT, L09PUT, XDUM0(12)
COMMON / USR / LOCDAT(40), NDAT
POINTER :: KNW(:), KNE(:), PRTL(:)

COMMON / PRT / KNW, KNE, PRTL
The pointer arrays in the /PRT/ common block are allocated in the m708v1 program source to MXROW & MXCOL dimensions
as follows:
ALLOCATE (KNW(MXROW), KNE(MXROW), PRTL(MXCOL))
Note that there are three /USR/ common blocks. The first is for use with M208V1 and file 11, the second for use with M508V1 and
file 9, and the third for use in M718V2.
CONVERTING OLD USER SUBS TO NEW USER SUBS

If you have written user subs for m612v1, m612v2, or m708v1 prior to the 2011 Update CD, you may notice changes in the way
newer object modules (namely m612d1.obj, m612d2.obj, m612db1.obj, m612db2.obj, m708d1.obj, and m708db1.obj) are being
called versus the manner older object modules were being called (what was once distributed as m612v1.obj, m612v2.obj, m612b1.
obj, m612b2.obj, m612e1.obj, m612e2.obj, m708v1.obj, m708b1.obj, m708e1.obj). The process to convert an older user sub to
the newer standard first involves identifying whether /ITM/ & /SYS/ or /ITMB/ & /SYSB/ common blocks will be used. If you
need to access more than 99 items, you will need to use /ITMB/ & /SYSB/ common blocks. Thus use the following conversion for
replacing object modules:

MineSight
There is a subroutine name change - all m612* objects now are named USR612D and all m708* objects now are named USR708D.
All newer subroutines will have MXCOL, MXROW, MAXITM added to the argument list.
SUBROUTINE USR612 (NTRY, IZ, ZMID, IROW, YROW, MCOL, NCOL, MAP, RMX)
... to this:
SUBROUTINE USR612D(NTRY, IZ, ZMID, IROW, YROW, MCOL, NCOL, MAP, RMX, MXCOL, MXROW, MAXITM)
Likewise convert the old m708 argument list from this:
SUBROUTINE USR708 (NTRY, IZ, NSEQ, IROW, YROW, MCOL, NCOL, MTX )
... to this:
SUBROUTINE USR708D (NTRY, IZ,NSEQ, IROW,YROW, MCOL,NCOL, MTX, MXCOL, MXROW, MAXITM)
Since MAXITM is now passed as an argument, the various older subroutine names of USE612, U99612, U25612, USR612 are
no longer neccessary and all may now be renamed to USR612D. Likewise older subroutine names of USE708, U99708, U25708,
USR708 may now be renamed to USR708D. Remember to add MXCOL, MXROW, MAXITM to the argument list.
Arrays passed in the argument list (namely MAP, RMX, MTX) need to be dimensioned accordingly. Thus, redimension these arrays
as such using the MXCOL,MAXITM parameters passed in the subroutine argument list:
DIMENSION MTX(MXCOL,MAXITM)
Since m708d1 allocates pointer arrays in the /PRT/ common block and dimensions them as KNW(MXROW),KNE(MXROW),PRTL
(MXCOL), subroutine USR708D would need to have them declared as such.
Thus convert the old m708 declaration from this:
COMMON / PRT / KNW(1000), KNE(1000), PRTL(1000)
... to this:

COMMON / PRT / KNW, KNE, PRTL
Since MXCOL,MXROW are passed as arguments to subroutine USR708D, you will have access to the dimension size of these arrays.

MineSight
Sample Program for M208V1

This subroutine computes an equivalent grade. It was originally written with the algorithm EQCU = T-CU + 2*MOLY, although
items other than T-CU and MOLY can be used, depending on which are specified with the GET11 command in the run file.
Note: The subroutine is called USR208.
PAR1 is used is used to parameterize a cutoff which is specified in the run file.
Output can be sent to: LPR, the report file.

IPR, the screen.
file 19, the external file specified on the Names Line of the run file .
Sample Run File:

MEDS-208V1 10=SAMP10.DAT 11=SAMP11.DAT 12=SAMP12.DAT =RPT208.LA
MEDS-208V1 19=OUT208.A
USR = ABC
IOP1 = 8 / First Survey Record to access

IOP2 = 28 / Last Survey Record to access
IOP6 = 1 / Store data from the User routine to file 11

IOP7 = 1 / Open an external file
PAR1 = .2 / Cutoff for equivalent grade
GET11 = T-CU MOLY / Data to retrieve from file 11

PUT11 = EQCU / Data to store in file 11
END

MineSight
Sample User Routine:

SUBROUTINE USR208 ( NTRY, IDH )
C================================================================
C
C Compute an equivalent grade for a file 11 item
C
C The GET11 items are assumed to be (in order): T-CU and MOLY
C The PUT11 item is EQCU
C
C The CUTOFF is specified in PAR1
C
C The summary goes to LFN 19 as specified on the NAMES line
C================================================================
C
CHARACTER ADH*10
COMMON / EXTRA1 / ADH
COMMON / ITM / ITM(3,99), NIC(5,40), ITEMS, NICNO, LWRD(99),
1 NBIT(99), LBIT(99), VMIN(99), CODE(99), ROND(99),
2 VFCT(99), MAXV(99), RDAT(99), IDAT(99)
COMMON / SYS / XDUM1(100), IOP(40), PAR(40), XDUM2(104),
1 ICR, IPR, LCR, LPR, XDUM3(5), IOLEV, XDUM4(89)
COMMON / F10 / PCF(512), XDUM5(142)
COMMON / USR / K11GET, L11GET, K11PUT, L11PUT, LOC11, J11, K11,
1 L11, K12GET, L12GET, K12PUT, L12PUT, LOC12, J12,
2 K12, L12
C
C=======================================================================
GOTO ( 100, 200, 900, 400, 500, 900, 900, 900 ), NTRY
C
C.................................................... NTRY = 1
100 CONTINUE
NOVER = 0
CUTOFF = PAR(1)
C
NATOT = 0
NOTOT = 0
C
WRITE ( LPR, 110 )
WRITE ( IPR, 110 )
110 FORMAT( /, 10X, Compute an equivalent grade using T-CU ,
1 and MOLY )
C
WRITE ( 19, 120 ) CUTOFF
120 FORMAT( Number of assays , /,
1 Drillhole with eq. grade >, F4.1, /,
2 __________________________ -, / )
GOTO 900
C
C..................................................... NTRY = 2
200 CONTINUE
NATOT = NATOT + 1

MineSight
C compute equivalent grade: EQCU = T-CU + 2*MOLY

IF ( RDAT( K11GET ).GE.0. .AND. RDAT( K11GET+1 ).GE.0 )
1 RDAT( K11PUT ) = RDAT( K11GET ) + 2.*RDAT( K11GET+1 )
C
C accumulate assays for this DH with grade over CUTOFF
IF ( RDAT( K11PUT ) .GT. CUTOFF ) THEN
NOVER = NOVER + 1
NOTOT = NOTOT + 1
END IF
GOTO 900
C
C..................................................... NTRY = 4
400 CONTINUE
C
C summarize the assays exceeding cutoff
WRITE ( 19, 410 ) ADH, NOVER
410 FORMAT( 3X, A, T24, I5 )
C
NOVER = 0
GOTO 900
C
C..................................................... NTRY = 5
500 CONTINUE
WRITE ( 19, 510 ) NOTOT, NATOT, CUTOFF
510 FORMAT( /, I5, of , I5, assays had an equivalent ,
1 copper grade exceeding, F5.2 )
C
C..................................................... EXIT
900 CONTINUE
RETURN
END
Sample File 19 Output:

Number of assays
Drillhole with eq. grade > 0.2
SM-008 69
SM-009 76
SM-010 80
SM-011 73
SM-012 0
SM-013 0
SM-014 79
SM-015 81
SM-016 83
SM-017 80
SM-018 0
SM-019 33
SM-020 79
SM-021 82
SM-022 46
861 of 1040 assays had an equivalent copper grade exceeding 0.20

MineSight
Sample Program for M612V2 (using object module M612D2)

This routine computes the relative elevation of a block with respect to two surfaces. In this case the lower surface elevation is stored in
TOPOD (file 13) and the upper surface elevation is stored in TOPOI (also in file 13). So for example, if a blocks midpoint elevation
is 200, TOPOD=0, and TOPOI=1000 then the relative elevation will be .2.
Note: This subroutine is called USR612D where RMX is dimensioned MXCOL by MAXITM which are passed as arguments
to the subroutine.
The TOPOI and TOPOD values are tested to make sure they have appropriate values compared with PCF(490).
The values of MAP are scaled from 1 to 26. See the symbol map.
Sample Run File:

MEDS-612V2 10=SAMP10.DAT 13=SAMP13.DAT 15=SAMP15.DAT 3=RPT612.LA2
USR = ABC
IOP2 = 1 / Read UPD data

IOP3 = 2 / Call user routine at end-of-bench & run
IOP10 = 1 / Print symbol map
PUT15 = EXTRA / File 15 item to compute

GET13 = TOPOI TOPOD / File 13 items use in the computation
END

MineSight
Sample USR612D

C=======================================================================
C
C Compute a relative elevation for file 15 item EXTRA.
C
C Use file 13 items TOPOI and TOPOD
C
C=======================================================================
PARAMETER (MAXPAR = 40, MXITM = 99, MXNIC = 40)

C
COMMON
& /SYS/ NAMES(80), RNID(20), IOP(MAXPAR), PAR(MAXPAR), IFMT(20,4),
& IHS, JUCMD, IRTYPE , IOLEV, RUNUMB, USER, LBTS,
C
COMMON
& /ITM/ ITM(3,MXITM), NIC(5,MXNIC), ITEMS, NICNO,
& LWRD(MXITM), NBIT(MXITM), LBIT(MXITM),
& VMIN(MXITM), CODE(MXITM), ROND(MXITM),
& VMAX(MXITM), MAXV(MXITM), RDAT(MXITM), IDAT(MXITM)
C
DIMENSION IPCF(512)
COMMON /F10/ PCF(512), XDUMD(142)
EQUIVALENCE ( PCF(1), IPCF(1) )
C
C ... Limit R2 by R1 below and R3 above
C
C----&---1---------2---------3-----+---4---------5---------6---------7--
C
C .................................................. NTRY=-1(Init)
C .................................................. INITIALIZE
IF ( NTRY .EQ. -1 ) THEN
C here once at the beginning of the run
C
OMIT = PCF(490)
WRITE ( LPR,110 )
WRITE ( IPR,110 )
110 FORMAT( /, 10X, Computing Relative Elevations, // )
C
C .................................................. NTRY=0 (Row)
C .................................................. PROCESS SECTION
ELSE IF ( NTRY .EQ. 0 ) THEN
C here after data for an entire model row is read
C
ZONTOP = RMX(IC,2)

MineSight
ZONBOT = RMX(IC,3)
IF ( ZONTOP.EQ.OMIT .OR. ZONBOT.EQ.OMIT ) THEN
C this block is not well-defined
EXTRA = 0.
ELSE IF ( ZONBOT.LE.ZMID .AND. ZMID.LE.ZONTOP ) THEN
C the center of this block is inside the zone
EXTRA = ( ZMID-ZONBOT ) / ( ZONTOP-ZONBOT )
EXTRA = RLIMIT( 0., EXTRA, 1. )
ELSE
C the center of the block is outside the zone
EXTRA = 0.
ENDIF
RMX(IC,1) = EXTRA
MAP(IC) = INT( 26.*EXTRA )
410 CONTINUE
C
C .................................................. NTRY=1 (Section)
C here after data for the last row in the current EW section
C
WRITE ( IPR, 1410 ) , IROW, YROW
WRITE ( LPR, 1410 ) +, IROW, YROW
1410 FORMAT( A1, 5X, Finished with row:, I5, 2X, F10.2 )
C
C .................................................. NTRY=2 (End)
C here once at the end of the run
C
WRITE ( LPR, 810 )
810 FORMAT( /, 10X, Successful Program Completion )
END IF
C
900 CONTINUE
RETURN
END

MineSight
Sample Symbol Map: This is in the report file.

RUN# 519. PAGE 51 METL 612V2 DATE 02-16-93 TIME 13:39:58
_________________________________________________________
* SAMPLE METAL PROJECT - INITIALIZE P.C.F. PARAMETERS *
Symbol Plot: Row 49 Northing= 14850.
1020 30 40 50
Z +....+....+....+....+....+....+....+....+....+....+
1 !..................................................
2 !..................................................
3 !..................................................
4 !..................................................
5 !..................................................
6 !..................................................
7 !..................................................
8 !...P......................P.........P.............
9 !...M..N........O.ONKP.OO.MLL..P...O.KP.OO........O
10 !...J.KG.......OG.KFDJ.JLHJHG..JMN.J.FK.KKOLLM.N.ML
11 !INMG.E9ON...NOJ9PH85ENEH8GECH.CJBCD.AG.GGKHGI.H.HH
12 !9EDCJ82FJJMMHGE2KD..8I9E.DA7..6F..8G6BMDCHCBENAJCD
13 !.459.2.6FBHGB8A.F9..3D4A.A62...B..2516D99D77AH3C7A
14 !...6....A4CB4.5.A6...9.7.72....7.....14559227B.426
15 !...3....6.75..1.62...4.3.3.....3.......115..35...3
16 !........2.2.....1........................1........
17 !..................................................
18 !..................................................
19 !..................................................
20 !..................................................
21 !..................................................
22 !..................................................
23 !..................................................
24 !..................................................
25 !..................................................
26 !..................................................
27 !..................................................
28 !..................................................
29 !..................................................
30 !..................................................
31 !..................................................
32 !..................................................
33 !..................................................
34 !..................................................
35 !..................................................
36 !..................................................
37 !..................................................
38 !..................................................
39 !..................................................
40 !..................................................
Z +....+....+....+....+....+....+....+....+....+....+
10 20 30 40 50
Finished with row: 49 14850.00

MineSight
Sample Program for M708V1 (using object module M708DB1)

This routine calculates reserves based on cutoffs and ore types. This example has two (IOP13) grade items, TCU-1 and MO-1. The
ore type is in item CODE. There will be two possible ore types (IOP20).
Note: The subroutine is called USR708D, so MTX is dimensioned MXCOL by MAXITM which are passed as arguments to
the subroutine.

NEWSMR is used to convert the item label into a character string (AITM). This subroutine is in libusrdynb.lib.

Note the EQUIVALENCing of PCF to IPCF. Thus PCF(23), the model column width, is used as a floating point number
and IPCF(489) is used as an integer.

See how the MTX values are decoded, for example:

GRADE = FLOAT( MTX(IC,1) ) * CODE(1)
Sample Run File:

MEDS-708V1 10=SAMP10.DAT 15=SAMP15.DAT 19=OUT708.A 3=RPT708.LA
USR = ABC
IOP3 = 2 / Also call USR708D after each bench and at end

IOP4 = 1 / Summarize geologic reserves
IOP9 = 1 / Use an external file
GET15 = TCU-1 MO-1 CODE / 2 grades and 1 ore type items
COM====== The following IOPs and PARs are specific for this USR708D
IOP11 = 1 / First cutoff to print

IOP12 = 6 / Last cutoff to print
IOP13 = 2 / Number of grades
IOP20 = 2 / Number of ore types
PAR1 = .2 / Class interval for reserves determination
PAR2 = 1. / Maximum cutoff grade
PAR3 = 12. / Tonnage factor
END
DAT705.OA
File DAT705.OA contains the lines:
11 1 1 50 1 50
12 1 1 50 1 50

MineSight
Sample USR708:
SUBROUTINE USR708D (NTRY, IZ,NSEQ, IROW,YROW, MCOL,NCOL, MTX,

C=======================================================================
C
C Compute geologic reserves
C
C=======================================================================
DIMENSION MTX(MXCOL,MAXITM)
C
PARAMETER (MAXPAR = 500, MXITM = 500, MXNIC = 500)
PARAMETER (MXBOX = 20, MXLIN = 50)
C
CHARACTER AITM(MXITM)*5
C
DIMENSION IDUM(5), GRAD(MXITM), BLK(MXBOX), TG(MXBOX, MXITM),
& AV(MXBOX, MXITM), TOTN(MXBOX), TBLK(MXBOX)
C
COMMON
& /SYSB/ NAMES(80), RNID(20), IOP(MAXPAR), PAR(MAXPAR), IFMT(20,4),
& IHS, JUCMD, IRTYPE, IOLEV, RUNUMB, USER, LBTS,
COMMON
& /ITMB/ ITM(3,MXITM), NIC(5,MXNIC), ITEMS, NICNO,
& LWRD(MXITM), NBIT(MXITM), LBIT(MXITM),
& VMIN(MXITM), CODE(MXITM), ROND(MXITM),
& VFCT(MXITM), VMAX(MXITM), MAXV(MXITM),
& RDAT(MXITM), IDAT(MXITM)
C
DIMENSION IPCF(512)
COMMON /F10/ PCF(512), IAB10(20), I10, NW10, LBF(2,40),
& IPW10(40)
EQUIVALENCE (PCF(1), IPCF(1))
C
COMMON /PRT/ KNW, KNE, PRTL
C
COMMON /M708/ GP(20,5), TON(20), WASTN
C
DATA EPSLON / .0001 /
C
C Limit J2 by J1 below and J3 above
LIMIT(J1, J2, J3) = MIN0(MAX0(J1, J2), J3)
C
C----&---1---------2---------3-----+---4---------5---------6---------7--
C
C
IF (NTRY) 100, 200, 300
C
C..................................................... NTRY=-1
100 CONTINUE
NLIN = MXLIN

MineSight
KERR = 0
KUT1 = IOP(11)
KUT2 = IOP(12)
IOMIT = IPCF(489)
C
IF (KUT1 .EQ. 0) KUT1 = 1
IF (KUT2 .EQ. 0) KUT2 = 5
C
C cutoffs
CLASS = PAR(1)
CUTMX = PAR(2)
KMX = CUTMX/CLASS + 1.0049
C
C tonnage factor
IF (PAR(3) .GT. 0.) THEN
FACTR = PCF(23) * PCF(27) * PCF(31) / PAR(3)
ELSE
WRITE (IPR, 110)
WRITE (LPR, 110)
110 FORMAT(/, ?M708V1: ERROR. You MUST have a PAR3 ,
& (tonnage factor) in your run file.)
KERR = KERR + 1
ENDIF
C
C number of grade items
IF (IOP(13) .GT. 0) THEN
NGRADS = MIN0(MXITM, IOP(13))
ELSE
WRITE(IPR, 120)
WRITE(LPR, 120)
120 FORMAT(/, ?M708V1: ERROR. You MUST have some grade ,
& items (IOP13).)
KERR = KERR + 1
ENDIF
C
C ore code items
LORE = NGRADS + 1
NORE = MAX0(1, IOP(20))
IF (KMX*NORE .GT. MXBOX) THEN
WRITE(IPR, 130) MXBOX
WRITE(LPR, 130) MXBOX
130 FORMAT(/, ?M708V1: ERROR. The number of cutoffs times ,
& the number of, /, 10X, ore codes exceeds the ,
& maximum:, I3)
KERR = KERR + 1
ENDIF
C
C set up the item labels
DO 140 I = 1, NGRADS
CALL NEWSMR(1, 1, ITM(2,I), 5, IDUM)
WRITE(AITM(I), (5A1)) IDUM
140 CONTINUE
C
WRITE (LPR, 150)
150 FORMAT(//, 10X, Begin USER 708 Program)

MineSight
WRITE (19, 160) KMX, NORE, CLASS, CUTMX, FACTR

160 FORMAT(//, 10X, M708V1 Initialization, //,
& 10X, Number of cutoffs , I6, /,
& 10X, Number of ore types , I6, /,
& 10X, Reserve increment , F9.2, /,
& 10X, Maximum cutoff , F9.2, /,
& 10X, Quantity per block , F9.2)
C
GOTO 900
C
C..................................................... NTRY = 0
200 CONTINUE
C
C make sure the retrieved data is well-defined
DO 205 IQ = 1, LORE
IF (MTX(IC,IQ) .EQ. IOMIT) GOTO 250
205 CONTINUE
C
C controlling value
GRADE = FLOAT(MTX(IC,1)) * CODE(1)
KUT = MIN0(INT(GRADE/CLASS + 1.0049), KMX)
C
C KORE is the ore type at location NGRADS+1 in MTX
KORE = MTX(IC, LORE)
KORE = LIMIT(1, KORE, NORE)
C
C reserve class index
KLASS = KMX*(KORE-1) + KUT
C
C grades
DO 210 IG = 1, NGRADS
GRAD(IG) = FLOAT(MTX(IC,IG)) * CODE(IG)
210 CONTINUE
C
IF (PRTL(IC) .GE. .001) THEN
TONAGE = FACTR * PRTL(IC)
KLASS = MAX0(1, KLASS)
C
C accumulate tons and weighted grade
GP(KLASS,IG) = GP(KLASS,IG) + TONAGE*GRAD(IG)
220 CONTINUE
TON(KLASS) = TON(KLASS) + TONAGE
BLK(KLASS) = BLK(KLASS) + PRTL(IC)
ENDIF
250 CONTINUE
GOTO 900
C
C..................................................... NTRY = 1
300 CONTINUE
IF (NTRY .EQ. 2) GOTO 400
C
C accumulate and output resources by cutoff interval
DO 350 IW = 1, NORE

MineSight
KLASS = KMX * (IW-1)

DO 340 I = 1, KMX
J = KLASS + KMX - I + 1
IF (J .LT. KMX) THEN
K = J + 1
GP(J,IG) = GP(J,IG) + GP(K,IG)
310 CONTINUE
TON(J) = TON(J) + TON(K)
BLK(J) = BLK(J) + BLK(K)
ENDIF
TG(J,IG) = TG(J,IG) + GP(J,IG)
AV(J,IG) = 0.
320 CONTINUE
TOTN(J) = TOTN(J) + TON(J)
TBLK(J) = TBLK(J) + BLK(J)
IF (BLK(J) .GE. .001) THEN
IF (TON(J) .GT. 0.) THEN
AV(J,IG) = GP(J,IG) / TON(J)
ELSE
AV(J,IG) = 0.
ENDIF
330 CONTINUE
ENDIF
340 CONTINUE
350 CONTINUE
C
C output the results
DO 390 IW = 1, NORE
DO 380 IK = KUT1, KUT2
J = KLASS + IK
CUTOFF = FLOAT(IK-1) * CLASS
IF (ABS(TON(J)).GT.EPSLON .OR. IK.LE.KUT1) THEN
NLIN = NLIN + 1
IF (NLIN .GT. MXLIN) THEN
C new page
NLIN = 0
WRITE(19,360) CHAR(12), (AITM(IG), IG=1,NGRADS)
360 FORMAT(A,/,5X,Bench Ore Cutoff ,Tonnage,5(3X,A5))
ENDIF
WRITE(19,370) IZ,IW,CUTOFF,TON(J),(AV(J,IG),IG=1,NGRADS)
370 FORMAT(5X, 2I5, F8.3, F12.0, 5F8.3)
ENDIF
380 CONTINUE
WRITE(19,(1X))
390 CONTINUE
GOTO 900
C
C..................................................... NTRY = 2
400 CONTINUE
WRITE(19, 410) CHAR(12), (AITM(IG), IG=1,NGRADS)
410 FORMAT(A, /, 5X, Summary for Entire Run, //, 7X,

MineSight
& Ore Cutoff Tonnage, 5(3X,A5))

WRITE(19,(1X))
C
DO 450 IW = 1, NORE
DO 440 IK = KUT1, KUT2
J = KLASS + IK
CUTOFF = FLOAT(IK-1) * CLASS
IF (ABS(TBLK(J)) .GT. EPSLON) THEN
IF (TOTN(J) .GT. 0.) THEN
AV(J,IG) = TG(J,IG) / TOTN(J)
ELSE
AV(J,IG) = 0.
ENDIF
420 CONTINUE
WRITE(19, 430) IW, CUTOFF, TOTN(J),
& (AV(J,IG), IG=1,NGRADS)
430 FORMAT(5X, I5, F8.3, F12.0, 5F8.3)
ENDIF
440 CONTINUE
WRITE (19,(1X))
450 CONTINUE
GOTO 900
C
C..................................................... EXIT
900 CONTINUE
RETURN
END

MineSight
Sample Output: OUT708.A (file 19)

Bench Ore Cutoff Tonnage TCU-1 MO-1
11 1 0.000 78124920. 1.002 0.128
11 1 0.200 71041592. 1.092 0.128
11 1 0.400 63749932. 1.184 0.128
11 1 0.600 55499944. 1.286 0.128
11 1 0.800 47083292. 1.392 0.128
11 1 1.000 39333304. 1.489 0.127
11 2 0.000 2500000. 0.095 0.108

11 2 0.200 2166666. 0.302 0.117
11 2 0.400 2958334. 0.497 0.124
11 2 0.600 2791667. 0.701 0.132
11 2 0.800 2541667. 0.894 0.134
11 2 1.000 13083357. 1.490 0.126
12 1 0.000 78124936. 1.008 0.123

12 1 0.200 70541616. 1.106 0.123
12 1 0.400 63458292. 1.196 0.121
12 1 0.600 55708304. 1.294 0.120
12 1 0.800 47374984. 1.398 0.120
12 1 1.000 40083328. 1.489 0.120
12 2 0.000 2208333. 0.088 0.113

12 2 0.200 2124999. 0.306 0.125
12 2 0.400 2333333. 0.499 0.136
12 2 0.600 2541667. 0.695 0.127
12 2 0.800 2916667. 0.895 0.133
12 2 1.000 13916697. 1.491 0.122
Summary for Entire Run
Ore Cutoff Tonnage TCU-1 MO-1
1 0.000 156249856. 1.005 0.126

1 0.200 141583200. 1.099 0.125
1 0.400 127208224. 1.190 0.124
1 0.600 111208248. 1.290 0.124
1 0.800 94458272. 1.395 0.124
1 1.000 79416632. 1.489 0.124
2 0.000 4708333. 0.092 0.111

2 0.200 4291665. 0.304 0.121
2 0.400 5291667. 0.498 0.129
2 0.600 5333334. 0.698 0.129
2 0.800 5458334. 0.894 0.133
2 1.000 27000054. 1.491 0.124

MineSight
Sample Program for M718V2

This routine calculates dollar value of copper for each model block. It combines TCU-1 and TCU-P from the block model to get a
percent copper value for each block. The percent copper value is converted to dollar value using the tonnage factor (PAR10) and
copper price (PAR11).
Note: TCU-1 and TCU-P are tested (using the OMIT constant) to make sure they contain actual values and are not UNSET or
MISSING.
The common block variable LOCDAT is used to point at appropriate data.
PCF variables define the block dimensions (see PCF Variables, page TEC600-16).
Sample Run File:

MEDS-718V2 10 =SAMP10.DAT 15=SAMP15.DAT 13=SAMP13.DAT;
MEDS-718V2 3=RPT718.LA 21=SAMPDP.P00 22=SAMPDP.BLK
USR = ABC
CMD = CONDENSE MODEL / Create the DIPPER set
IOP1 = 10 20 / First and Last column to access

IOP3 = 10 20 / First and Last row to access
IOP5 = 1 20 / First and Last bench to access
PAR1 = .01 / Mimimum block value to condense

PAR2 = 99999 / Maximum block value to condense
ITM1 = TOPOG TOPO / File 13 TOPO item

ITM2 = TCU-P GRADE / File 15 GRADE item
ITM3 = TCU-1 USER / Additional File 15 item
COM======== The following PARS are specific for this USR718
PAR10 = 12.5 / Tonnage Factor

PAR11 = 40. / cents/lb for copper
END

MineSight
Sample USR718:
SUBROUTINE USR718 ( VALUE, IX, IY, IZ )
C=================================================================
C
C Create a $DIPPER set for file 15 items TCU-1 + TCU-P
C
C TCU-1 and TCU-P are percents
C
C The Tonnage Factor is specified in PAR10
C The Copper price (cents/lb) is specified in PAR11
C
C=================================================================
C
COMMON /SYS/ XDUM1(100), IOP(40), PAR(40), XDUM2(104),
1 ICR, IPR, LCR, LPR, XDUM3(5), IOLEV, XDUM4(89)
C
COMMON /F10/ PCF(512), XDUMA(142)
C
COMMON / ITM/ ITM(3,99), NUC(5,40), ITEMS, NICNO, LWRD(99),
1 NBIT(99), LBIF(99), VMIN(99), CODE(99), ROND(99),
2 VFCT(99), MAXV(99), RDAT(99), IDAT(99)
C
COMMON /USR/ LOCDAT(40), NDAT
C
DATA NTRY / 0 /
C Limit R2 by R1 below and R3 above
C
C================================================================
C
C..................................................... initialize
IF ( NTRY .EQ. 0 ) THEN
NTRY = 1
OMIT = PCF(490)
KERR = 0
C
IF ( PAR(10) .GT. 0 ) THEN
C tons per block = dx*dy*dz / tf
TPBLK = PCF(23)*PCF(27)*PCF(31) / PAR(10)
ELSE
KERR = KERR + 1
WRITE(LPR,100)
100 FORMAT( /, ERROR: No Tonnage Factor (PAR10) was ,
1 entered)
END IF
C IF ( PAR(11) .LE. 0 ) THEN
KERR = KERR + 1
WRITE(LPR,110)
110 FORMAT( /, ERROR: No Copper price (PAR11) was ,
1 entered )
END IF
C
IF ( KERR .GT. 0 ) STOP

MineSight
C
C -
C compute FACTOR. FACTOR when multiplied by the total
C percent of copper in a block will yield the gross
C dollar value of copper in the block. build FACTOR
C in steps so you can see how I got it.
C
C convert percent to fraction
FACTOR = 1. / 100.
C
C convert fraction to tons/block
FACTOR = FACTOR * TPBLK
C
C convert tons/block to lbs/block
FACTOR = FACTOR * 2000.
C
C convert lbs/block to dollars/block
FACTOR = FACTOR * PAR(11) / 100.
C -
C
END IF
C
C..................................................... gross value
TCU1 = RDAT( LOCDAT(1) )
TCUP = RDAT( LOCDAT(2) )
IF ( TCU1.EQ.OMIT .OR. TCUP.EQ.OMIT ) THEN
C copper values for this block are not well-defined
VALUE = 0.
C
ELSE
PRCENT = RLIMIT( 0., TCU1+TCUP, 100. )
VALUE = FACTOR*PRCENT
END IF
C
C..................................................... exit
RETURN
END

MineSight

M 600

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

M 600

Uploaded by

Copyright:

Available Formats

MineSight

Proprietary Software: Mintec, inc. M600 - MINE MODEL OPERATIONS

MINE MODEL OPERATIONS

MineSight 600-Series Programs M602FS - Interactive Mine Model File Editing.

This program summarizes mine model data using a frequency

Revised: 09-December-10 Page 600-i

M612SM - Surface Generation M620V2 - Inverse Distance Weighting Interpolation (Octant

Page 600-ii Revised: 09-December-10

M635V1 - Create a Digital Terrain Model M600-Technical Section

M637V1 - Cross Section Thru a DTM Sub-blocked Model Data Access

M639V1 - Generate Block Partials Between Two Surfaces

This program is used to generate block partials between two

MSCS - Conditional Simulation 3-D Block Model

Revised: 26-Dec-13 Page 600-iii

2. Create the mine model file 3-D distribution of values

Page 600-iv Revised: 26-Dec-13

The following table shows an example of typical items to

ITEM LABEL MIN MAX PRECISION

1 ORTYP 0.00 5.0 1.000

ORTYP = ore type for reserve calculations (M711)

The following table shows an example of typical items to be

ZTOP = top of seam

Revised: 26-Dec-13 Page 600-v

Page 600-vi Revised: 09-December-10

M601V1 INITIALIZE A MINE MODEL FILE

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

percent topography - initialize to 100%

M601V1 can be used to copy levels within a model. New benches

- Updated Model File Reset

Revised: 12-August-14 Page 601-1

Page 601-2 Revised: 12-August-14

M601V1 - INITIALIZE A MINE MODEL FILE

RUN FILE OPERATION

MEDS-601V1 10=filename 15 (or 14 or 13)=filename;

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

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

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

USR = USER INITIALS (e.g. ABC)

IOP6 = # BENCHES TO COPY (default=1)

IOP7 = OPTIONAL # TIMES TO REPEAT THE COPY

IOP8 = FIRST ROW TO RESET (default=1)

Revised: 12-August-14 Page 601-3

IOP10 = FIRST COLUMN TO RESET (default=1)

IOP12 = 1 PREVENT ACTUAL RESET

IOP13 = 0 DO NOT RESET VALUES OF UNSPECIFIED ITEMS (default)

PUTnn = ITEMS TO BE INITIALIZED OR RESET (optional)

PAR1 = value1 value2 ... valuen

I-O = 1 LIST INTERNAL FILE INFORMATION

Page 601-4 Revised: 12-August-14

M601V1 SAMPLE RUN FILE #1

COM SAMP15.DAT ITEMS TO BE INITIALIZED:

M601V1 SAMPLE RUN FILE #2

COM NOTE THAT YOU DO NOT HAVE TO INITIALIZE ANY ITEMS

Revised: 12-August-14 Page 601-5

M601V1 SAMPLE RUN FILE #3

IOP4 = 20 / STARTING BENCH TO COPY FROM

COM BENCH 20 WILL BE COPIED TO BENCH 41;

M601V1 SAMPLE RUN FILE #4

IOP4 = 20 / STARTING BENCH TO COPY FROM

COM BENCH 20 WILL BE COPIED TO BENCH 41;

Page 601-6 Revised: 12-August-14

M601V1 SAMPLE RUN FILE #5

RUN = RESET / READ SAMP15.DAT & ZERO VALUES FOR CODE

RESET A SUBSET OF THE 3-D BLOCK MODEL