M500Bhs - Load Blasthole Assay Data To BH File 9: Program Summary

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. REF# Pushback number ELEV. elevation of blasthole. EAST easting of blasthole. NORTH northing of blasthole.
PROGRAM FLOW DIAGRAM
RUN FILE:
- Blasthole labels - Area Selection - Blastholes (optional)
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 in the run file. File 12 is loaded at the same time as File 9 and the minimum and maximum coordinates of the shot are stored in File 12. This information will be appended to any existing data in File 12 unless IOP2=1. In this case, File 12 will be overwritten and any existing data lost. 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.
INPUT:
- PCF - ASCII file of blastholes (optional)
CALCS:
- Load blastholes into File 9 and 12 - OR -Update existing blasthole data
OUTPUT:
- Survey File 12 - Blasthole File 9 - Prnter Output File
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.
REQUIREMENTS AND CONSIDERATIONS

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
M500BHS - LOAD BH ASSAY DATA TO FILE 9
Page 500BHS-2
Revised: 16-February-2000
M500BHSLOAD BLASTHOLE ASSAY DATA TO BH FILE 9

RUN FILE OPERATION
1. NAMES LINE (must be the first line entered) MEDS-500BH MEDS-500BH where 10=filename 19=filename 9=filename 3=filename 12=filename;
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 IOP1 IOP2 IOP3 = = = = = = USER INITIALS (e.g. ABC) N09 N12 -1 0 1 FIRST LOCATION OF FILE #09 TO BE STORED. FIRST LOCATION OF FILE #12 TO BE STORED. USE ALL BHS REGARDLESS OF LOCATION USE BHS WITHIN PROJECT LIMITS 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 1 0 1 0 1 FILE 9 COMPOSITES WITH MATCHING BLASTHOLE FILE 12 FILE 9 COMPOSITES WITHOUT A FILE 12 INPUT DATA IS CONTAINED IN THIS RUN FILE INPUT DATA IS CONTAINED IN THE ASCII FILE 19 DO NOT ALLOW LOADING OF DUPLICATE SHOT #s IN FILE 12 ALLOW LOADING OF DUPLICATE SHOT #s IN FILE 12
IOP5
IOP6
PUT09 =
BHS# REF# coord_labels assay_labels other_labels e.g. PUT09= BHS# REF# ELEV. EAST NORTH TOTCU ASCU MOLY ORE (*) FREE-FIELD OR (...SPECS...) for fixed fields on the shot header lines. Page 500BHS-3
FMT1
Revised: 04-October-99
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. 2. 3. SHOT HEADER LINE(SHOT#, PB#, AUX#, DATE, IDENT) BLASTHOLE ASSAY LINES(BHS#, PB#, items labels) END OF SHOT ASSAYS(a blank line)
Page 500BHS-4
M500BHS SAMPLE RUN FILE #1

MEDS-500BH 10=METL10.BHS 12=METL12.BHS 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 IOP3 IOP5 = = = 00 -1 0 / STARTING RECORD #S FOR FILES 09 & 12 / LOAD ALL BHS REGARDLESS OF COORDINATES / 1=READ BHS FROM FILE 19=..., 0=DATA IN RUN. 3=RPT500.LA;
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 Blasthole assay lines 101 14 3450. 96529.00 99776.70 0.110 0.000 0.0170 0 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

MEDS-500BH 10=METL10.BHS 19=BLASTH.OLE MEDS-500BH 9=METL09.BHS 12=METL12.BHS ** LOAD RAW BLASTHOLE DATA FROM BLASTH.OLE ** USR = ABC 3=RPT500.LB;
COM COM B H D A T A L O A D F U N C T I O N COM IOP1 IOP3 IOP5 COM PUT09 = FMT1 FMT2 END = = = = = 00 -1 1 / STARTING RECORD #S FOR FILES 09 & 12 / LOAD ALL BHS REGARDLESS OF COORDINATES / 1=READ BHS FROM FILE 19=...
INPUT DATA IS READ IN FREE-FIELD FORMAT BHS#REF#ELEV.EASTNORTHTOTCUASCUMOLYLEADORE (*) (*)
Page 500BHS-5
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
M502BHX - UPDATE BLASTHOLE ASSAY DATA IN BH FILE 9
M502BHX UPDATE BLASTHOLE ASSAY DATA IN BH FILE 9

PROGRAM SUMMARY
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 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. The blasthole data that is loaded should have the following variables present:

RUN FILE: - Blasthole labels - Area selection

INPUT: - PCF - Files 9 and 12 - ASCII input file CALCS: - Replace old data with updated values for Files 9 and 12
BHS# blasthole identifier. Must be no more than 4 characters. System defined format is A4. REF# pushback number ELEV elevation of blasthole EAST easting of blasthole. 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 blasthole. If there are fields that will not be stored, they must be skipped over with an nX format specification on the FMT2 line 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.
OUTPUT: - Update Files 9 and 12
Revised: 3-March-03
Page 502BHX-1
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

RUN FILE OPERATION
1. NAMES LINE (must be the first line entered) MEDS-502BH MEDS-502BH where: 10=filename 19=filename 9=filename 3=filename 12=filename;
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 IOP1 IOP2 IOP3 = = = = = = = = = = = = USER INITIALS (e.g. ABC) M12 N12 0 1 2 0 1 0 1 FIRST LOCATION OF FILE #12 TO BE STORED LAST LOCATION OF FILE #12 TO BE STORED MATCH BHS#, EASTING, AND NORTHING MATCH EASTING, NORTHING ONLY MATCH BLASTHOLE# ONLY ONLY LOAD VALUES THAT ARE DEFINED (e.g., non-missing) ALLOW VALUES TO BE UPDATED TO MISSING VALUES DONT UPDATE COORDINATES UPDATE COORDINATES (X and Y) FROM .BHS FILE
IOP4
IOP5
PAR1 PAR2
TOLERANCE TO MATCH EASTING COORDINATES IF IOP4=1 TOLERANCE TO MATCH NORTHING COORDINATES IF IOP4=1 BHS# ELEV. EAST NORTH assay_labels e.g.UPD09 = BHS# ELEV. EAST NORTH TOTCU ASCU MOLY ORE (*) FREE FIELD OR (...SPECS...) for header line (*) FREE-FIELD OR (...SPECS...) for fixed fields on the blasthole data lines
UPD09 =
FMT1 FMT2 END
= =
Revised: 24-July-97
Page 502BHX-3
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
M502BHX SAMPLE RUN FILE #1

MEDS-502BH 10=METL10.BHS 19=S908.BHS MEDS-502BH 9=METL09.BHS 12=METL12.BHS ** UPDATE FILES 9 AND 12 FROM S908.BHS ** USR = ABC 3=RPT500.LB;
COM COM BH DATA UPDATE FUNCTION COM IOP1 IOP3 IOP4 COM UPD09 = FMT1 END = = = = 00 2 0 / STARTING RECORD #S FOR FILES 09 & 12 / MATCH BLASTHOLE# ONLY / 0=ALLOW LOADING OF ONLY DEFINED VALUES
INPUT DATA IS READ IN FREE-FIELD FORMAT BHS# ELEV. (*) EAST NORTH TOTCU ASCU MOLY LEAD ORE
SAMPLE INPUT FILE

19484 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 0 0 0 0 0 0 0 0 0 0 0 0 0 5300.0 5300.0 5300.0 5300.0 5300.0 5300.0 5300.0 5300.0 5300.0 5300.0 5300.0 19940 -7127.0 -7126.0 -7158.0 -7158.0 -7181.0 -7184.0 -7207.0 -7205.0 -7236.0 -7234.0 -7258.0 18446.0 18420.0 18416.0 18447.0 18424.0 18449.0 18431.0 18455.0 18439.0 18459.0 18474.0 .58 .87 .63 .61 .98 .53 1.22 .83 .25 .75 .73 .01 .01 .01 -1.00 -1.00 -1.00 -1.00 -1.00 -1.00 -1.00 -1.00 -2.00 -2.00 -2.00 -2.00 -2.00 -2.00 -2.00 -2.00 -2.00 -2.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
Page 502BHX-6
Revised: 24-July-97
M503BHS - LIST/DUMP BLASTHOLE ASSAY DATA
M503BHS LIST or DUMP BLASTHOLE ASSAY DATA FILE
PROGRAM SUMMARY
M503BHS lists or dumps the blasthole data files. The data selection and the order of data output from the program may be specified.

M503BHS is used to list or dump specified portions of blastholes in File 9 or 12. The three options are:

RUN FILE:
- Blasthole selection - Item selection - Area selection
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) List File 12 shot index with data unit numbers on the report. No reference is made to File 9. (IOP6=1) Dump File 9 blasthole data in BHS point format used in modeling.(IOP6=1)
INPUT:
- PCF - File 9 - File 12 (optional)
CALCS:
- Select data and generate blasthole report
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 be controlled by IOP7 through IOP14 and PAR1 through PAR4. Listings should always be made after program runs of M502FSB, and should be checked closely before proceeding to other programs.
HOW TO RUN THIS PROGRAM

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.
OUTPUT:
- - Optional ASCII output file - Printer Output File
Revised: 24-Oct-04
Page 503BH-1
M503BHS -LIST or DUMP BLASTHOLE ASSAY DATA FILE
M503BHS - LIST or DUMP BLASTHOLE ASSAY DATA FILE

RUN FILE OPERATION
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 IOP1 IOP2 IOP3 = = = = = = USER INITIALS (e.g. ABC) M12 N12 -1 0 1 FOR FILE 12 REF -OR- IOP1 = M09 FOR FILE 9 FOR FILE 12 REF -OR- IOP1 = N09 FOR FILE 9 LIST ALL BHS REGARDLESS OF LOCATION LIST BHS WITHIN PROJECT LIMITS 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 1 1 0 -1 LIST FILE 9 BLASTHOLES WITH FILE 12 CROSS-REF (default) LIST FILE 9 BLASTHOLES ALONE LIST FILE 12 SHOT INFORMATION ONLY LIST FILE 9 AND FILE 12 SHOT INFORMATION (default) DUMP FILE 9 BLASTHOLES ALONG WITH THE LIST
IOP6
IOP7 IOP8 IOP9 IOP10 IOP11 IOP12
Optional MINIMUM SHOT# Optional MAXIMUM SHOT# Optional MINIMUM PUSHBACK# Optional MAXIMUM PUSHBACK# Optional MINIMUM AUXILLIARY# Optional MAXIMUM AUXILLIARY# Optional MINIMUM DATE, YEARMODA Optional MAXIMUM DATE Page 503BH-3
IOP13 = IOP14 =
Revised: 25-September-97
PAR1 PAR2 PAR3 PAR4
= = = =
Optional EASTING ORIGIN FOR DUMP Optional NORTHING ORIGIN FOR DUMP Optional MINIMUM ELEV. FOR RUN Optional MAXAMUM ELEV. FOR RUN Labels of file #9 ITEMS to be listed
GET09 =
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 label-09 label-09 RANGE OMIT TABLE min-value min-value min-value max-value max-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.

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 IOP1 IOP3 = = = ABC 10 -1 / STARTING LOCS TO ACCESS BHS / USE BHS REGARDLESS OF COORDS
GET09 = END
EAST NORTH ELEV. TOTCU ASCU MOLY ORE /
Page 503BH-4

MEDS-503BH 10=METL10.BHS MEDS-503BH 19=SELECT.BHS ** B L A S T H O L E D U M P E X A M P L E USR IOP1 IOP3 SIOP6 IOP7 = = = = = ABC 1 -1 -1 7690 / FILE #9 LOCS TO ACCESS BH DATA / USE BHS REGARDLESS OF COORD / 1=LIST SHOTS ONLY; 1=DUMP & LIST 7700 / SHOT# LIMITS 0 12=METL12.BHS 3=RPT503.LB 9=METL09.BHS;
GET09= EAST NORTH ELEV. TOTCU ASCU MOLY / END

MEDS-503BH 10=METL10.BHS MEDS-503BH 3=RPT503.LC ** B L A S T H O L E S H O T I N F O ** USR IOP1 IOP3 IOP6 = = = = ABC 1 -1 1 00 / FILE #12 LOCS TO ACCESS BH DATA / USE BHS REGARDLESS OF COORD / 1=LIST SHOTS ONLY; -1=DUMP & LIST 12=METL12.BHS 9=METL09.BHS;
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.
Page 503BH-5
Page 503BH-6
MineSight Proprietary Software: Mintec, Inc.
M507BHSDUMP BLASTHOLE FILE 9 TO ASCII
M507BHS DUMP BLASTHOLE FILE 9 TO ASCII DATA FILE

PROGRAM SUMMARY
M507BHS creates a sequential ASCII file from the blasthole files 9 and 12

Blasthole data that has already been stored into File 9 may 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. M507BHS will dump existing blasthole data from M ineSight File 9 under control of File 12. You can specify the output format to the ASCII file with a FMT1 line, but the program will generate a default format. The first two data fields output from M507BHS include the blasthole number and the pushback number. The blasthole number should be given an alphanumeric format of A4, and the pushback number should be given an integer format specification of I5. 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.

RUN FILE: - Optional selection - Output format
INPUT: - PCF - File 9 - File 12
CALCS: - Select data - Create ASCII file
OUTPUT: - ASCII output file - Printer Output File
The ASCII output file contains a header line before the actual blasthole data. This is the standard blasthole format that is generated during the merge function of blasthole 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 commands. 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
M507BHS - DUMP BLASTHOLE FILE 9 TO ASCII DATA FILE

RUN FILE OPERATION
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 IOP1 IOP2 IOP3 = = = = = = = = = = = = = = = = USER INITIALS (e.g. ABC) M12 N12 -1 0 first location of file #12 to be dumped. last location of file #12 to be dumped. USE ALL BHS REGARDLESS OF LOCATION LIST BHS WITHIN PROJECT LIMITS
IOP7 IOP8 IOP9 IOP10 IOP11
Optional MINIMUM SHOT# Optional MAXIMUM SHOT# Optional MINIMUM PUSHBACK# Optional MAXIMUM PUSHBACK# 0 BHS DUMP FORMAT 1 SRV DUMP FORMAT 2 ASY DUMP FORMAT Optional EASTING ORIGIN FOR DUMP Optional NORTHING ORIGIN FOR DUMP Optional MINIMUM ELEV. FOR RUN Optional MAXIMUM ELEV. FOR RUN 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.
PAR1 PAR2 PAR3 PAR4
GET09 =
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)
Page 507BHS-3
Optional data selection by RANGE, OMIT, TABLE ITMn = = = label-09 label-09 label-09 RANGE OMIT TABLE min-value min-value min-value max-value max-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.

MEDS-507BH 10=MBHS10.DAT 9=MBHS09.DAT MEDS-507BH 19=BHDUMP.BHS 3=RPT507.LB ** MBHS09.DAT BLASTHOLE DUMP, ALL SHOTS ** USR = COM IOP1 IOP3 =0 = -1 0 / RECORD #S FOR FILE 12 DHS TO BE LISTED / -1=LIST ALL BHS; 0=WITHIN PROJ COORD LIMITS 12=MBHS12.DAT;
COM GET09 =
BLASTHOLE ITEMS ORDER FOR OUTPUT REPORT. ELEV. EAST NORTH AU AU1 AU2 2350. / MIN-MAX ELEV.
PAR3 = 2300. END
SAMPLE OUTPUT FILE FROM M507BHS

Shot 901 901 1 147 1 148 1 149 1 . . . . . 257 1 258 1 259 1 0 19890701 2320.0 8835.1 2320.0 8836.1 2320.0 8835.0 . . . 2320.0 8933.0 2320.0 8933.0 2320.0 8933.0
1154.0 0.008 1139.0 0.006 1125.0 0.003 1194.1 0.017 1209.1 0.010 1223.0 0.015
0.008 0.005 0.003 0.017 0.010 0.015
0.008 0.007 0.003 0.017 0.011 0.015
Page 507BHS-4
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
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
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.
Page TEC500-3
In addition to other system common blocks, the following common block data is available: /BUF/B12(1024), B09(1024) 1. 2. 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. 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. 2. 3. 4. 5. 6. 7. 8. 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). L09GET is the subscript for the last File 9 GET item. K09PAK is the subscript for the first File 9 PAK item. 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. LOC09 is the base subscript of the current interval data unit and is addressed by B09 (LOC09 + 1). J09 is the current File 9 data unit number. K09 is the first data unit number of interval data for the current survey data unit. 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

M500Bhs - Load Blasthole Assay Data To BH File 9: Program Summary

Uploaded by

Document Information

Original Description:

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

M500Bhs - Load Blasthole Assay Data To BH File 9: Program Summary

Uploaded by

Copyright:

Available Formats

MineSight Proprietary Software: Mintec, inc.

M500BHS - LOAD BH ASSAY DATA TO FILES