MineSight

Proprietary Software: Mintec, inc. M500BHS - LOAD BH ASSAY DATA TO FILES

M500BHS - LOAD BLASTHOLE ASSAY

DATA TO BH FILE 9

PROGRAM SUMMARY
This program is used to load standard blasthole data into File 9.
The blasthole data is usually created by the BHSMERG utility
or by program M507BHS.
The blasthole data that is loaded should have the following
variables present:
BHS# blasthole identifier. Must be no more than 4
characters. System defined format is A4.

PROGRAM FLOW DIAGRAM REF# Pushback number

ELEV. elevation of blasthole.

EAST easting of blasthole.

RUN FILE:
- Blasthole labels
- Area Selection
- Blastholes (optional)
NORTH northing of blasthole.
Blastholes that are generated with BHSMERG are stored using
toe elevation, which is the default for plotting and interpolation
routines. The collar elevation may also be stored.

Other data such as grades and geology may be loaded for each
blasthole. If there are fields that will not be stored, they must be
skipped over with an nX format specification on the FMT2 line
INPUT: CALCS: in the run file.
- PCF - Load blastholes into File 9
- ASCII file of and 12 File 12 is loaded at the same time as File 9 and the minimum
blastholes (optional) - OR - and maximum coordinates of the shot are stored in File 12. This
-Update existing blasthole information will be appended to any existing data in File 12
data
unless IOP2=1. In this case, File 12 will be overwritten and any
existing data lost.

OUTPUT:
- Survey File 12
- Blasthole File 9
- Prnter Output File
REQUIREMENTS AND CONSIDERATIONS
Input data that is less than the minimum value for the item will
be stored by the program as missing values. Input data that is
greater than the maximum value for the item will be truncated
to the maximum value.
HOW TO RUN M500BHS TO STORE DATA
M500BHS is normally accessed from the MS-Compass menu
under the ASSAY OPS submenu using procedure PBH500.DAT.
As with standard MineSight programs, M500BHS may be run
directly from the command line with the appropriate run file.

Program M500BHS will read blasthole data from the run file or
a separate file and then load Files 9 and 12. This allows you to
use blastholes that have been generated outside of MineSight.
You may also create an ASCII file of blastholes with M507BHS,
modify them and load them back into the blasthole files with
M500BHS.

Revised: 24-Oct-04 Page 500BH-1

 MineSight
M500BHS - LOAD BH ASSAY DATA TO FILE 9 Proprietary Software: Mintec, inc.

Page 500BHS-2 Revised: 16-February-2000

MineSight
Proprietary Software: Mintec, inc. M500BHSLOAD BLASTHOLE ASSAY DATA TO BH FILE 9

M500BHSLOAD BLASTHOLE ASSAY DATA TO BH FILE 9

RUN FILE OPERATION

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

MEDS-500BH 10=filename 9=filename 12=filename;

MEDS-500BH 19=filename 3=filename
where

MEDS-500BH (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
9 = the name of the BLASTHOLE ASSAY FILE
12 = the name of the BLASTHOLE INDEX FILE
19 = the name of the ASCII INPUT FILE (If IOP5 = 1)
3 = the name of the PRINTER OUTPUT FILE

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

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

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

USR = USER INITIALS (e.g. ABC)

IOP1 = N09 FIRST LOCATION OF FILE #09 TO BE STORED.

IOP2 = N12 FIRST LOCATION OF FILE #12 TO BE STORED.

IOP3 = -1 USE ALL BHS REGARDLESS OF LOCATION

= 0 USE BHS WITHIN PROJECT LIMITS
= 1 USE BHS WITHIN SPECIFIED BOUNDARY

NOTE: If IOP3=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)

IOP4 = 0 FILE 9 COMPOSITES WITH MATCHING BLASTHOLE FILE 12

= 1 FILE 9 COMPOSITES WITHOUT A FILE 12

IOP5 = 0 INPUT DATA IS CONTAINED IN THIS RUN FILE

= 1 INPUT DATA IS CONTAINED IN THE ASCII FILE 19

IOP6 = 0 DO NOT ALLOW LOADING OF DUPLICATE SHOT #s IN FILE 12

= 1 ALLOW LOADING OF DUPLICATE SHOT #s IN FILE 12

PUT09 = BHS# REF# coord_labels assay_labels other_labels

e.g. PUT09= BHS# REF# ELEV. EAST NORTH TOTCU ASCU MOLY ORE

FMT1 = (*) FREE-FIELD OR (...SPECS...) for fixed fields on the shot header lines.

Revised: 04-October-99 Page 500BHS-3

 MineSight
M500BHSLOAD BLASTHOLE ASSAY DATA TO BH FILE 9 Proprietary Software: Mintec, inc.

FMT2 = (*) FREE-FIELD OR (...SPECS...) for fixed fields on the blasthole data lines.

NOTE: If you specify a FMT1 statement, the first format field must be A6 for the SHOT#, and the PB#,
AUX# and DATE fields must be integer fields. If you specify a FMT2 statement, the first format field
must be A4 for BHS#, and the rest should be real format fields.

END

4. BOUNDARY POINT LINES (If IOP3=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 (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.

5. BLASTHOLE DATA INPUT LINES (If IOP5=0)

1. SHOT HEADER LINE(SHOT#, PB#, AUX#, DATE, IDENT)

2. BLASTHOLE ASSAY LINES(BHS#, PB#, items labels)

3. END OF SHOT ASSAYS(a blank line)

Page 500BHS-4 Revised: 04-October-99

MineSight
Proprietary Software: Mintec, inc. M500BHSLOAD BLASTHOLE ASSAY DATA TO BH FILE 9

M500BHS SAMPLE RUN FILE #1

MEDS-500BH 10=METL10.BHS 12=METL12.BHS 3=RPT500.LA;
MEDS-500BH 9=METL09.BHS
** LOAD RAW BLASTHOLE DATA FROM RUN FILE **

USR = ABC

COM
COM B H D A T A L O A D F U N C T I O N
COM

IOP1 = 00 / STARTING RECORD #S FOR FILES 09 & 12

IOP3 = -1 / LOAD ALL BHS REGARDLESS OF COORDINATES
IOP5 = 0 / 1=READ BHS FROM FILE 19=..., 0=DATA IN RUN.

PUT09 = BHS# REF# ELEV. EAST NORTH TOTCU ASCU MOLY ORE
FMT2 = (1X,A4,F3.0, F7.0,2F10.2, 2F6.3,F7.4,F4.0)
END
8699 16 1 19870701 BLAST#8699 Shot header line
101 14 3450. 96529.00 99776.70 0.110 0.000 0.0170 0 Blasthole assay lines
102 14 3450. 96512.50 99795.30 0.090 0.000 0.0160 0
103 14 3450. 96498.13 99810.90 0.110 0.000 0.0200 0
104 14 3450. 96481.50 99831.50 0.150 0.000 0.0270 0
105 14 3450. 96465.00 99849.10 0.190 0.000 0.0390 0

M500BHS SAMPLE RUN FILE #2

MEDS-500BH 10=METL10.BHS 19=BLASTH.OLE 3=RPT500.LB;
MEDS-500BH 9=METL09.BHS 12=METL12.BHS
** LOAD RAW BLASTHOLE DATA FROM BLASTH.OLE **

USR = ABC

COM
COM B H D A T A L O A D F U N C T I O N
COM

IOP1 = 00 / STARTING RECORD #S FOR FILES 09 & 12

IOP3 = -1 / LOAD ALL BHS REGARDLESS OF COORDINATES

IOP5 = 1 / 1=READ BHS FROM FILE 19=...

COM INPUT DATA IS READ IN FREE-FIELD FORMAT

PUT09 = BHS#REF#ELEV.EASTNORTHTOTCUASCUMOLYLEADORE

FMT1 = (*)
FMT2 = (*)
END

Revised: 04-October-99 Page 500BHS-5

 MineSight
M500BHSLOAD BLASTHOLE ASSAY DATA TO BH FILE 9 Proprietary Software: Mintec, inc.

HOW TO DEBUG AN M500BHS RUN

1. A common error is a mismatch between the FMT1 line and the PUT09 line in the run file. Make sure you have specified enough
format fields to account for all items on the PUT09 line. Dont forget to specify the first format field as A4 for the BHS#. Check
that your format matches the data that is being read in.

2. M500 ERROR IN COORDINATES

will appear if you have not specified the standard coordinate items EAST, NORTH and ELEV. on the PUT09 line.

3. If IOP6=0, M500BHS only allows you to load a shot to Files 9 and 12 once. If you would like to load duplicate shot#s use
IOP6=1. If you would like to reload a shot that has already been loaded, the shot must first be deleted with M502FSB, then
reloaded with M500BHS. If you are updating the shot, use M502BHX.

4. Also check the MineSight error messages in the Appendix.

Page 500BHS-6 Revised: 04-October-99

MineSight
Proprietary Software: Mintec, inc. M502BHX - UPDATE BLASTHOLE ASSAY DATA IN BH FILE 9

M502BHX UPDATE BLASTHOLE ASSAY DATA

IN BH FILE 9

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

This program is used to update standard blasthole data in File 9
which has been previously loaded with M500BHS. The blasthole
data is usually created by the BH4MERG utility or by program
M507BHS.
PROGRAM FLOW DIAGRAM
Program M502BHX will read blasthole data from a separate
file and then update Files 9 and 12. This allows you to use
blastholes that have been generated outside of MineSight. You
may also create an ASCII file of blastholes with M507BHS,
modify them and load them back into the blasthole files with
M502BHX. It should be noted that M502BHX only allows
blastholes which currently exist in File 9 to be updated, and is
used to update only 1 shot at a time.

RUN FILE:
- Blasthole labels
- Area selection
The blasthole data that is loaded should have the following
variables present:
BHS# blasthole identifier. Must be no more than 4
characters. System defined format is A4.

REF# pushback number

ELEV elevation of blasthole

INPUT: CALCS:
EAST easting of blasthole.
- PCF - Replace old data with
- Files 9 and 12 updated values for Files 9
- ASCII input file and 12 NORTH northing of blasthole

Blastholes that are generated with BHSMERG are stored using

toe elevation, which is the default for plotting and interpolation
routines. The collar elevation may also be stored.

Other data such as grades and geology may be updated for each
OUTPUT: blasthole. If there are fields that will not be stored, they must be
skipped over with an nX format specification on the FMT2 line
- Update Files 9 and 12
in the run file.

Input data that is less than the minimum value for the item will
not be stored by the program as missing values if IOP4 = 0 and
a value already exists for this item. This allows you to load assay
data as soon as it is received from the assay lab, regardless as to
whether particular assay items are included in the file. If, for
example, the lab sends fire assay data on one day, and AA
another, we are now able to load these items independently of
each other without overwriting the data previously stored into
File 9.

Revised: 3-March-03 Page 502BHX-1

 MineSight
M502BHX - UPDATE BLASTHOLE ASSAY DATA IN BH FILE 9 Proprietary Software: Mintec, inc.

HOW TO RUN M502BHX TO STORE DATA

M502BHX is normally accessed from the Ore Control menu in

MS Compass, under the ASSAY OPS submenu using procedure
UPDATE ASSAYS (PBH50X.DAT) . As with standard
MineSight programs, M502BHX may be run directly from the
command line with the appropriate run file.

HOW TO RUN M502BHX TO UPDATE DATA

Performing batch updates to blasthole File 9 is done outside the

Blasthole menu. Set up a run file using the system editor. Then
run M502BHX from the command line.

Page 502BHX-2 Revised: 3-March-03

MineSight
Proprietary Software: Mintec, inc. M502BHX - UPDATE BLASTHOLE ASSAY DATA IN BH FILE 9

M502BHX - UPDATE BLASTHOLE ASSAY DATA IN BH FILE 9

RUN FILE OPERATION

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

MEDS-502BH 10=filename 9=filename 12=filename;

MEDS-502BH 19=filename 3=filename
where:

MEDS-502BH (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
9 = the name of the BLASTHOLE ASSAY FILE
12 = the name of the BLASTHOLE INDEX FILE
19 = the name of the ASCII INPUT FILE
3 = the name of the PRINTER OUTPUT FILE

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

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

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

USR = USER INITIALS (e.g. ABC)

IOP1 = M12 FIRST LOCATION OF FILE #12 TO BE STORED

IOP2 = N12 LAST LOCATION OF FILE #12 TO BE STORED

IOP3 = 0 MATCH BHS#, EASTING, AND NORTHING

= 1 MATCH EASTING, NORTHING ONLY
= 2 MATCH BLASTHOLE# ONLY

IOP4 = 0 ONLY LOAD VALUES THAT ARE DEFINED (e.g., non-missing)

= 1 ALLOW VALUES TO BE UPDATED TO MISSING VALUES

IOP5 = 0 DONT UPDATE COORDINATES

= 1 UPDATE COORDINATES (X and Y) FROM .BHS FILE

PAR1 = TOLERANCE TO MATCH EASTING COORDINATES IF IOP4=1

PAR2 = TOLERANCE TO MATCH NORTHING COORDINATES IF IOP4=1

UPD09 = BHS# ELEV. EAST NORTH assay_labels

e.g.UPD09 = BHS# ELEV. EAST NORTH TOTCU ASCU MOLY ORE

FMT1 = (*) FREE FIELD OR (...SPECS...) for header line

FMT2 = (*) FREE-FIELD OR (...SPECS...) for fixed fields on the blasthole data lines

END

Revised: 24-July-97 Page 502BHX-3

 MineSight
M502BHX - UPDATE BLASTHOLE ASSAY DATA IN BH FILE 9 Proprietary Software: Mintec, inc.

FORMAT FOR ASCII FILE OF INPUT BLASTHOLE DATA

1. SHOT HEADER LINE (SHOT#, PB#, AUX#, DATE, IDENT)

2. BLASTHOLE ASSAY LINES (BHS#, PB#, items labels)

3. END OF SHOT ASSAYS (a blank line)

Page 502BHX-4 Revised: 24-July-97

MineSight
Proprietary Software: Mintec, inc. M502BHX - UPDATE BLASTHOLE ASSAY DATA IN BH FILE 9

M502BHX SAMPLE RUN FILE #1

MEDS-502BH 10=METL10.BHS 19=S908.BHS 3=RPT500.LB;
MEDS-502BH 9=METL09.BHS 12=METL12.BHS
** UPDATE FILES 9 AND 12 FROM S908.BHS **

USR = ABC

COM
COM BH DATA UPDATE FUNCTION
COM

IOP1 = 00 / STARTING RECORD #S FOR FILES 09 & 12

IOP3 = 2 / MATCH BLASTHOLE# ONLY

IOP4 = 0 / 0=ALLOW LOADING OF ONLY DEFINED VALUES

COM INPUT DATA IS READ IN FREE-FIELD FORMAT

UPD09 = BHS# ELEV. EAST NORTH TOTCU ASCU MOLY LEAD ORE

FMT1 = (*)
END

SAMPLE INPUT FILE

19484 0 0 19940
1712 0 5300.0 -7127.0 18446.0 .58 .01 -2.00
1713 0 5300.0 -7126.0 18420.0 .87 .01 -2.00
1714 0 5300.0 -7158.0 18416.0 .63 .01 -2.00
1715 0 5300.0 -7158.0 18447.0 .61 -1.00 -2.00
1716 0 5300.0 -7181.0 18424.0 .98 -1.00 -2.00
1717 0 5300.0 -7184.0 18449.0 .53 -1.00 -2.00
1718 0 5300.0 -7207.0 18431.0 1.22 -1.00 -2.00
1719 0 5300.0 -7205.0 18455.0 .83 -1.00 -2.00
1720 0 5300.0 -7236.0 18439.0 .25 -1.00 -2.00
1721 0 5300.0 -7234.0 18459.0 .75 -1.00 -2.00
1722 0 5300.0 -7258.0 18474.0 .73 -1.00 -2.00

HOW TO DEBUG AN M502BHX RUN

1. A common error is a mismatch between the BLASTHOLE# in the ASCII input file and File 9. Make sure that all of the BHS#
in the input file exist in File 9.

Revised: 24-July-97 Page 502BHX-5

 MineSight
M502BHX - UPDATE BLASTHOLE ASSAY DATA IN BH FILE 9 Proprietary Software: Mintec, inc.

Page 502BHX-6 Revised: 24-July-97

MineSight
Proprietary Software: Mintec, inc. M503BHS - LIST/DUMP BLASTHOLE ASSAY DATA

M503BHS LIST or DUMP BLASTHOLE ASSAY DATA FILE

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M503BHS lists or dumps the blasthole data files. The data
selection and the order of data output from the program may be
specified.
PROGRAM FLOW DIAGRAM
M503BHS is used to list or dump specified portions of blastholes
in File 9 or 12. The three options are:
List File 9 using the shot index retrieved from File 12.
File 12 must have been created (M500BHS) at the same
time as File 9.(IOP6=0)

RUN FILE: List File 12 shot index with data unit numbers on the
- Blasthole selection report. No reference is made to File 9. (IOP6=1)
- Item selection
- Area selection Dump File 9 blasthole data in BHS point format used
in modeling.(IOP6=1)

The data retrieval function is controlled by the GET09 command

line as shown in the sample run file. Data selection can be made
through the use of Range, Omit or Table command lines and by
specifying a point boundary (see IOP3). Data retrieval can also
INPUT: CALCS:
be controlled by IOP7 through IOP14 and PAR1 through PAR4.
- PCF - Select data and generate
- File 9 blasthole report Listings should always be made after program runs of
- File 12 (optional) M502FSB, and should be checked closely before proceeding to
other programs.

HOW TO RUN THIS PROGRAM

OUTPUT:
- - Optional ASCII output file
- Printer Output File
Within the Ore Control System, M503BHS is accessed from
the Composite Report selection in the ASSAY OPS submenu
of the MS-Compass menu. The program is also run whenever
Dump .BLK/BHS File is selected from the MODELING submenu
to provide an accurate assessment of the assays used in
modeling.

Revised: 24-Oct-04 Page 503BH-1

MineSight
Proprietary Software: Mintec, inc. M503BHS -LIST or DUMP BLASTHOLE ASSAY DATA FILE

M503BHS - LIST or DUMP BLASTHOLE ASSAY DATA FILE

RUN FILE OPERATION

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

MEDS-503BH 10=filename 9=filename 12=filename;

MEDS-503BH 19=filename 3=filename
where

MEDS-503BH (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
9 = the name of the BLASTHOLE ASSAY FILE
12 = the name of the BLASTHOLE INDEX FILE
19 = the name of the ASCII OUTPUT FILE (if IOP6 = -1)
3 = the name of the PRINTER OUTPUT FILE

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

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

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

USR = USER INITIALS (e.g. ABC)

IOP1 = M12 FOR FILE 12 REF -OR- IOP1 = M09 FOR FILE 9
IOP2 = N12 FOR FILE 12 REF -OR- IOP1 = N09 FOR FILE 9
IOP3 = -1 LIST ALL BHS REGARDLESS OF LOCATION
= 0 LIST BHS WITHIN PROJECT LIMITS
= 1 LIST BHS WITHIN SPECIFIED BOUNDARY

NOTE: If IOP3=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)

IOP4 = 0 LIST FILE 9 BLASTHOLES WITH FILE 12 CROSS-REF (default)

= 1 LIST FILE 9 BLASTHOLES ALONE

IOP6 = 1 LIST FILE 12 SHOT INFORMATION ONLY

= 0 LIST FILE 9 AND FILE 12 SHOT INFORMATION (default)
= -1 DUMP FILE 9 BLASTHOLES ALONG WITH THE LIST

IOP7 = Optional MINIMUM SHOT#

IOP8 = Optional MAXIMUM SHOT#
IOP9 = Optional MINIMUM PUSHBACK#
IOP10 = Optional MAXIMUM PUSHBACK#
IOP11 = Optional MINIMUM AUXILLIARY#
IOP12 = Optional MAXIMUM AUXILLIARY#

IOP13 = Optional MINIMUM DATE, YEARMODA

IOP14 = Optional MAXIMUM DATE

Revised: 25-September-97 Page 503BH-3

 MineSight
M503BHS -LIST or DUMP BLASTHOLE ASSAY DATA FILE Proprietary Software: Mintec, inc.

PAR1 = Optional EASTING ORIGIN FOR DUMP

PAR2 = Optional NORTHING ORIGIN FOR DUMP
PAR3 = Optional MINIMUM ELEV. FOR RUN
PAR4 = Optional MAXAMUM ELEV. FOR RUN

GET09 = Labels of file #9 ITEMS to be listed

NOTE: You are limited tp 20 items on the GET09 line unless you specify a FMT1. If using FMT1, you
may report up to 99 items.

FMT1 = Format for output data (required if reporting more than 20 items).

NOTE: Specify fields the BHS#, the UNIT, and every item on the GET09 line.

Example: FMT1 = (A7, I12,4F10.2, 25F10.3)

FMT3 = Format for output Labels in the report file (3=file).

NOTE: Default = (2X, 5A1, 7X, 5A1, 97(3X,5A1)).

If you use the Default FMT3, the item labels may not align properly with the columns of data specified
using the FMT1 statement. We recommend that the FMT3 statement should be compatible with FMT1.

Optional data selection by RANGE, OMIT, TABLE

ITMn = label-09 RANGE min-value max-value

= label-09 OMIT min-value max-value
= label-09 TABLE min-value max-value

END

4. BOUNDARY POINT LINES (if IOP3=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 (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.

M503BHS SAMPLE RUN FILE #1

MEDS-503BH 10=METL10.BHS 12=METL12.BHS 9=METL09.BHS;
MEDS-503BH 3=RPT503.LA
** B L A S T H O L E L I S T E X A M P L E

USR = ABC

IOP1 = 10 / STARTING LOCS TO ACCESS BHS

IOP3 = -1 / USE BHS REGARDLESS OF COORDS

GET09 = EAST NORTH ELEV. TOTCU ASCU MOLY ORE /

END

Page 503BH-4 Revised: 25-September-97

MineSight
Proprietary Software: Mintec, inc. M503BHS -LIST or DUMP BLASTHOLE ASSAY DATA FILE

M503BHS SAMPLE RUN FILE #2

MEDS-503BH 10=METL10.BHS 12=METL12.BHS 9=METL09.BHS;
MEDS-503BH 19=SELECT.BHS 3=RPT503.LB
** B L A S T H O L E D U M P E X A M P L E

USR = ABC

IOP1 = 1 0 / FILE #9 LOCS TO ACCESS BH DATA

IOP3 = -1 / USE BHS REGARDLESS OF COORD
SIOP6 = -1 / 1=LIST SHOTS ONLY; 1=DUMP & LIST
IOP7 = 7690 7700 / SHOT# LIMITS

GET09= EAST NORTH ELEV. TOTCU ASCU MOLY /

END

M503BHS SAMPLE RUN FILE #3

MEDS-503BH 10=METL10.BHS 12=METL12.BHS 9=METL09.BHS;
MEDS-503BH 3=RPT503.LC
** B L A S T H O L E S H O T I N F O **

USR = ABC

IOP1 = 1 00 / FILE #12 LOCS TO ACCESS BH DATA

IOP3 = -1 / USE BHS REGARDLESS OF COORD
IOP6 = 1 / 1=LIST SHOTS ONLY; -1=DUMP & LIST

GET09= EAST NORTH ELEV. TOTCU ASCU MOLY /

END

HOW TO DEBUG AN M503BHS RUN

1. If you limit the blasthole data by ITMn = label-09 RANGE, OMIT or TABLE, the label-09 must be
specified on the GET line.

2. Check the MineSight error messages in the Appendix.

Revised: 25-September-97 Page 503BH-5

 MineSight
M503BHS -LIST or DUMP BLASTHOLE ASSAY DATA FILE Proprietary Software: Mintec, inc.

Page 503BH-6 Revised: 25-September-97

MineSight
Proprietary Software: Mintec, Inc. M507BHSDUMP BLASTHOLE FILE 9 TO ASCII

M507BHS DUMP BLASTHOLE FILE 9 TO ASCII DATA FILE

PROGRAM SUMMARY REQUIREMENTS AND CONSIDERATIONS

M507BHS creates a sequential ASCII file from the blas- Blasthole data that has already been stored into File 9 may
thole files 9 and 12 be dumped into an ASCII file in preparation for condensing
or creating a new file 9. Once data is in an ASCII file,
special editing or changes can be made with the editor on
your computer system.
PROGRAM FLOW DIAGRAM
M507BHS will dump existing blasthole data from Mine-
RUN FILE:
Sight File 9 under control of File 12. You can specify
- Optional selection the output format to the ASCII file with a FMT1 line, but the
- Output format program will generate a default format.

The first two data fields output from M507BHS include the
blasthole number and the pushback number. The blasthole
INPUT: CALCS: number should be given an alphanumeric format of A4, and
the pushback number should be given an integer format
- PCF - Select data specification of I5.
- File 9 - Create ASCII file
- File 12
The next three data fields output normally contain the
ELEV., EAST and NORTH coordinates of the blastholes. If
this data will be used to create a File 9, ELEV. precedes
EAST which precedes NORTH, by convention. These fields
are followed by assays and geology, as applicable.

OUTPUT: The ASCII output file contains a header line before the
actual blasthole data. This is the standard blasthole format
- ASCII output file that is generated during the merge function of blasthole
- Printer Output File preparation.

Optional data selection can be made through the use of IOP7

to IOP12, and PAR1 to PAR4. Data selection can also be
made through the use of RANGE, OMIT or TABLE com-
mands. Several runs may be required to dump different files
with blasthole (shot) selections in order to condense a large
blasthole file.

HOW TO RUN THIS PROGRAM

M507BHS must be set up and executed independently of the

regular Blasthole Menu.

Revised: 1August94 Page 507BHS1

MineSight
Proprietary Software: Mintec, inc. M507BHS - DUMP BLASTHOLE FILE 9 TO ASCII DATA FILE

M507BHS - DUMP BLASTHOLE FILE 9 TO ASCII DATA FILE

RUN FILE OPERATION

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

MEDS-507BH 10=filename 9=filename 12=filename;

MEDS-507BH 19=filename 3=filename
where

MEDS-507BHS (must be the first 10 columns)

10 = the name of the PROJECT CONTROL FILE
9 = the name of the BLASTHOLE ASSAY FILE
12 = the name of the BLASTHOLE INDEX FILE
19 = the name of the ASCII OUTPUT FILE
3 = the name of the PRINTER OUTPUT FILE

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

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

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

USR = USER INITIALS (e.g. ABC)

IOP1 = M12 first location of file #12 to be dumped.

IOP2 = N12 last location of file #12 to be dumped.

IOP3 = -1 USE ALL BHS REGARDLESS OF LOCATION

= 0 LIST BHS WITHIN PROJECT LIMITS

IOP7 = Optional MINIMUM SHOT#

IOP8 = Optional MAXIMUM SHOT#
IOP9 = Optional MINIMUM PUSHBACK#
IOP10 = Optional MAXIMUM PUSHBACK#
IOP11 = 0 BHS DUMP FORMAT
= 1 SRV DUMP FORMAT
= 2 ASY DUMP FORMAT

PAR1 = Optional EASTING ORIGIN FOR DUMP

PAR2 = Optional NORTHING ORIGIN FOR DUMP
PAR3 = Optional MINIMUM ELEV. FOR RUN
PAR4 = Optional MAXIMUM ELEV. FOR RUN

GET09 = Labels of file #9 ITEMS to be listed

NOTE: You are limited to 20 items on the GET09 line unless you specify a FMT1. If you are using
FMT1, you may report up to 99 items.

FMT1 = Format for output data (required if reporting more than 20 items)
Specify fields for the BHS#, the Pushback# (ref#), and every item on the GET09 line.

Example: FMT1 = (A4,I5,4F10.2,5F10.3)

Revised: 22-October-99 Page 507BHS-3

 MineSight
M507BHS - DUMP BLASTHOLE FILE 9 TO ASCII DATA FILE Proprietary Software: Mintec, inc.

Optional data selection by RANGE, OMIT, TABLE

ITMn = label-09 RANGE min-value max-value

= label-09 OMIT min-value max-value
= label-09 TABLE min-value max-value
END

4. BOUNDARY POINT LINES (if IOP3=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 (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.

M507BHS SAMPLE RUN FILE #1

MEDS-507BH 10=MBHS10.DAT 9=MBHS09.DAT 12=MBHS12.DAT;
MEDS-507BH 19=BHDUMP.BHS 3=RPT507.LB
** MBHS09.DAT BLASTHOLE DUMP, ALL SHOTS **

USR =

COM

IOP1 =0 0 / RECORD #S FOR FILE 12 DHS TO BE LISTED

IOP3 = -1 / -1=LIST ALL BHS; 0=WITHIN PROJ COORD LIMITS

COM BLASTHOLE ITEMS ORDER FOR OUTPUT REPORT.

GET09 = ELEV. EAST NORTH AU AU1 AU2

PAR3 = 2300. 2350. / MIN-MAX ELEV.

END

SAMPLE OUTPUT FILE FROM M507BHS

Shot 901
901 1 0 19890701
147 1 2320.0 8835.1 1154.0 0.008 0.008 0.008
148 1 2320.0 8836.1 1139.0 0.006 0.005 0.007
149 1 2320.0 8835.0 1125.0 0.003 0.003 0.003
. . . . . . . .
257 1 2320.0 8933.0 1194.1 0.017 0.017 0.017
258 1 2320.0 8933.0 1209.1 0.010 0.010 0.011
259 1 2320.0 8933.0 1223.0 0.015 0.015 0.015

Page 507BHS-4 Revised: 22-October-99

MineSight
Proprietary Software: Mintec, inc. TECHNICAL SECTION 500

CALCULATION OF COMPOSITES

Limiting Angle

Two types of fixed length composites can be calculated with M501V1: vertical and horizontal. The limiting angle controls which
method is used for a hole. By default, the limiting angle is:

Limiting Angle = ARCTAN (DZ/DX)

where
DZ = PCF Bench Height
DX =PCF E-W direction Block Size

NOTE: If you choose a non-default limiting angle in M501V1 (PAR4), then you must remember to include this
value in your M505V1 (PAR1) and M516V1 (PAR13) runfiles.

Vertical Composites

If the dip angle of a drillhole is greater than the limiting angle, a vertical composite is calculated. The vertical bench height (DZ) is
used as the control for compositing. The weight used in compositing is the calculated vertical length of each sample interval, not the
slope length of the interval.

Horizontal Composites

When the dip angle of a drillhole is less than the limiting angle, a horizontal composite is calculated. This prevents long vertical
composites being generated for near-horizontal drillholes. The E-W direction block size (DX) is used as the control for compositing.
The weight used in compositing is the calculated horizontal length of each sample interval, not the slope length of the interval.

Once the compositing calculation is begun with either the vertical or horizontal method, it will be used for the entire hole regardless
of subsequent surveys. There may be times when you will want to specify a limiting angle to prevent horizontal compositing of a few
holes that are close to, but less than the default angle. You should check for any holes that have surveys that are close to the limiting
angle and decide if they should be composited horizontally or vertically.

Revised: 8-November-01 Page TEC500-1

 MineSight
TECHNICAL SECTION 500 Proprietary Software: Mintec, inc.

Note about using the DHID option in the composite file (File 9) without the survey file (File 12):

Starting with the 2001 update you can store drillhole labels with composites in files 9 and 8. To use this option, you must reserve two
full-word items in file9. By default, MineSight programs expect those items to be named DHID1 and DHID2, but you can name
them differently. These items are similar to DLAB1 and DLAB2 in the survey file (File 12). To initialize a full-word item enter min
= max = 0., and precision = 1.

NOTE: A 10-character drillhole ID is coded and packed into two words. The actual DH ID can be retrieved only programmatically,
and you must direct MineSight programs to retrieve DHID from file9. The option to use DHID from file9 directly was added to all
the relevant procedures.

Page TEC500-2 Revised: 8-November-01

MineSight
Proprietary Software: Mintec, inc. TECHNICAL SECTION 500

NOTES FOR M508VA DRIVER PROGRAM

M508V1 calls the user routine USR508 as follows:

CALL USR508 (NTRY,IDHN), where

1. NTRY is an integer argument specifying entry control as follows: NTRY=1 for subroutine initialization. The call is
made after program initialization but before any drillhole data is accessed.

NTRY=2 for each drillhole interval within the current survey data unit. Interval data is subject to ITM restrictions as are
survey data units. Collar survey data units are also subject to boundary restrictions.

NTRY=3 for user calculations at the end of a survey data unit.

NTRY=4 for user calculations at the end of all survey data units for the current drillhole.

NTRY=5 for user calculations at the end of all drillholes (or end of run).

NTRY=6 same as NTRY=2 but in the optional second pass of the data. It follows an NTRY of 4 for each drillhole.

NTRY=7 same as NTRY=3 for the optional second pass.

NTRY=8 same as NTRY=4 for the optional second pass.

2. IDHN is an integer argument containing the current drillhole reference number. IDHN is zero for NTRY=l and
NTRY=5.

Revised: 8-November-01 Page TEC500-3

 MineSight
TECHNICAL SECTION 500 Proprietary Software: Mintec, inc.

In addition to other system common blocks, the following common block data is available:

/BUF/B12(1024), B09(1024)

1. B12 is an array containing the File 12 record in which the current survey data unit is located. See the /USR/ common
block for information of addressing data units.

2. B09 is an array containing the File 9 record in which the current interval data unit is located. Most words in B12 are
accessible directly although you may have to equivalence a floating point array to avoid conversion problems. File 9
data is usually packed in array B09 so, unless you understand MineSight packing schemes, you are advised to keep
your paws off this array.

/USR/K09GET, L09GET, K09PAK, L09PAK, LOC09, J09, K09, L09, K12GET, L12GET,
K12PAK, L12PAK, LOC12, J12, K12, L12

1. K09GET is the integer subscript for information in the ITM common block for the first File 9 GET item. Arrays of
interest are ITM(3,99), RDAT(99) and IDAT(99).

2. L09GET is the subscript for the last File 9 GET item.

3. K09PAK is the subscript for the first File 9 PAK item.

4. L09PAK is the subscript for the last File 9 PAK item. If you use UPD09 in your run file, then GET subscripts will fall
within the range of the PUT subscripts.

5. LOC09 is the base subscript of the current interval data unit and is addressed by B09 (LOC09 + 1).

6. J09 is the current File 9 data unit number.

7. K09 is the first data unit number of interval data for the current survey data unit.

8. L09 is the last data unit number for the current survey data unit.

THE REMAINING INTEGERS ARE THE SAME AS ABOVE BUT APPLICABLE TO File 12.

Page TEC500-4 Revised: 8-November-01