Datamine EXTRA
April 14, 2017 | Author: capelfernando | Category: N/A
Short Description
Download Datamine EXTRA...
Description
DATAMINE
GENERAL EXTENSIONS
COPMOD
Transforms a cell/sub-cell model into ASCII files, suitable for the COPOR floating-cone pit optimisation system.
EDDIE
Enhanced Drillhole Data Interactive Edit process.
ENGLOG
Translates coded downhole logs in an input file, using a dictionary file, and outputs a report in English.
MINZON
Determines mining zones of consistent material within mining advances.
PROCESSES
1
DATAMINE
GENERAL EXTENSIONS
LIST OF FIGURES PROCESS
PAGE
DESCRIPTION
MINZON
1.17
Plan through Input Model Showing Subcell Structure
MINZON
1.18
Direction of Mining Advance
MINZON
1.19
Rules for Combining Slices
MINZON
1.20
Shrinking Parameters
FIGURES
1
DATAMINE
GENERAL EXTENSIONS
COPMOD Introduction Transforms a cell/sub-cell model into the ASCII files needed for input to the stand-alone COPOR floating-cone pit optimisation system.
Process Summary COPMOD
Transform a cell/sub-cell model into ASCII COPOR files. The two ASCII files produced may be read by the COPBM program within COPOR. These files are the Flag file and the partial waste (PWASTE) file. The DATAMINE model file must contain the usual model definition fields. It must also contain a LAYER code field and between 1 and 6 grade fields. The LAYER field must contain an integer between 0 and 99 which represents the rocktype, oretype etc. This must exist for each record in the model file. The model must extend at least to the limits of the COPOR model (as defined in &IN1) in the X and Y directions and downwards from topography to the base of the COPOR model. There should be no undefined cells below defined material. The model should contain no air cells/sub-cells below topography.
&IN1
Input COPOR model prototype file, defining the COPOR model origin, number of cells and cell sizes. This is typically set up by process PROTOM. The fields required are XMORIG, YMORIG, ZMORIG, NX, NY, NZ, XINC, YINC, ZINC (all implicit) and IJK, XC, YC, and ZC (all explicit).
&IN2
Input model file for conversion. This must have the fields XMORIG, YMORIG, ZMORIG, NX, NY, NZ (implicit) and IJK, XC, YC and ZC (explicit). XINC, YINC and ZINC must exist as either explicit (sub-cells permitted) or implicit (no sub-cells). There must also be at least one explicit numeric data field, to be specified as *F1. The records may be in any order, but speed is increased if they are in IJK order. There must also be a LAYER field, defining the rocktype, oretype etc. as integers from 0 (air) to 99.
COPMOD
1.1
DATAMINE
GENERAL EXTENSIONS
*LAYER
Name of the numeric field containing the rocktype or oretype integer numeric field in the range 0-99. This field must be explicit. LAYER=0 means air.
*F1
First explicit numeric field to be averaged.
*F2*
Second explicit numeric field to be averaged.
*F3*
Third explicit numeric field to be averaged.
*F4*
Fourth explicit numeric field to be averaged.
*F5*
Fifth explicit numeric field to be averaged.
*F6*
Sixth explicit numeric field to be averaged.
@PRINT*
>=2 display for each input cell or sub-cell that intersects with an output model cell; IJK1, IJK, NUMMET, XC, YC, ZC, VOLP, VOLT, F1 [IJK of input and output cell, sub-cell no., input cell centre, volume intersected, total volume to date in output cell, *F1 value] (0).
@ECHO*
= 1; Echo screen output to print file (0).
Enter system file of COPOR Flag file to be written. This name may include a full path name. >SYSFILE> Enter required file name. Enter system file name of COPOR PWASTE file to be written. This name may include a full path name. >SYSFILE> Enter required file name.
Error and Warning Messages
Field ffffffff missing from COPOR Prototype Model file. One of the compulsory COPOR prototype model fields is missing. Fatal; the process is exited. Field ffffffff missing from DATAMINE Model file. One of the compulsory DATAMINE model fields is missing. Fatal; the process is exited.
COPMOD
1.2
DATAMINE
GENERAL EXTENSIONS
>>> No *LAYER field in file. The *LAYER field specified is not present in the DATAMINE model file. Fatal; the process is exited.
>>> Grade Field ffffffff is not on file - Fatal Error. The grade field specified does not exist in the DATAMINE model file. Fatal; the process is exited.
>>> Grade Field ffffffff is alphanumeric - Fatal Error. The grade field specified in the DATAMINE model file is alphanumeric. Fatal; the process is exited.
>>> Error - unable to open file aaa.... An error has occurred on trying to open one of the system files. Fatal; the process is exited.
COPOR Block (Row iii Column jjj Bench kkk) lies outside DATAMINE model - Fatal Error. Fatal; the process is exited.
CELL WITH CENTER AT x y z HAS LAYER CODE = ccccccc.cccc WHICH INTEGERIZES TO nnnnn ILLEGAL FOR COPOR Fatal; the process is exited.
>>> Warning - value of field ffffffff too large >>> on record number nnnnnnn - ignored FOR COPOR ROW,COL,BEN a b c THE VOLUME FOUND IN DATAMINE MODEL IS MAXIM PERMITTED IS CHECK FOR DUPLICATE CELLS
UM
FOR COPOR ROW,COL,BEN a b c THERE ARE mm LAYERS. THERE ARE ONLY nn PERMITTED No numeric grade variables. there are numeric grade fields in the DATAMINE model file. Fatal; the process is exited.
COPMOD
1.3
DATAMINE
GENERAL EXTENSIONS
Example
!COPMOD &IN1(COPRPRO T),&IN2(MODEL1),*LAYER(ROCK),*F1(CU),*F2(MO) Enter system file of COPOR Flag file to be written. This name may include a full path name. >SYSFILE>MDL1FLAG Enter system file name of COPOR PWASTE file to be written. This name may include a full path name. >SYSFILE>MDL1WSTE
COPMOD
1.4
DATAMINE
GENERAL EXTENSIONS
EDDIE Introduction Enhanced process for the interactive entry and editing of drillhole data.
Process Summary EDDIE
Enhanced Drill/Data Interactive Edit process. EDDIE is a flexible, multi-file interactive editor for direct data entry and editing of DATAMINE database files. EDDIE is customisable for a large range of data input applications from simple key punch style drill hole data entry, to fully formatted data input screens with validation. Two styles of data entry are allowed, SPREADSHEET and FORM. In SPREADSHEET mode the user is presented with the data formatted as a table with fields across the columns and data records down the rows. In FORM mode, a single record can be edited laid out across the screen using a format stored in the &DEFAULT file.
&KEYDEF*
Key definition file. Controls how records are accessed and displayed. Also permits the records to be accessed on a KEY FIELD (e.g Bore Hole ID or ZONE etc)
&DEFAULT*
Defaults file. Controls the default values and the screen format of data files.
&VALIDA*
Validation file. Controls the validation of data files.
&MESSAGE*
Message file. Contains expanded text used in error messages and prompts.
&HEADER*
Drill hole header (collar information) file.
&ASSAY*
Assay data file.
&SURVEY*
Down-hole survey data file.
&LITHO*
Lithology data file.
EDDIE
1.1
DATAMINE
GENERAL EXTENSIONS
&DRILL*
Drilling data file. Typically contains the following values for various down-hole intervals :- Core recovery, core diameter, drilling fluid used, casing used.
&GEOTECH*
Geotechnical data file.
Error and Warning Messages
>>> EDDIE ONLY WORKS WITH NATIVE-FILE DATABASES Fatal; the process is exited.
Example !EDDIE
&HEADER(HEADER), &SURVEY(SURVEY), &ASSAY(ASSAY), &LITHO(LITHO),&DRILL(DRILL),&VALIDA(VALIDA) &DEFAULT(DEFAULT), &MESSAGE(MESSAGE)
EDDIE
,
1.2
DATAMINE
GENERAL EXTENSIONS
ENGLOG Introduction Translates coded downhole logs in an input file, using a dictionary file, and outputs a report in English. The input file (&IN) contains at a minimum the borehole identifier field (BHID) together with a downhole distance FROM. It also contains any coded information describing for example rocktype, subrocks, recovery, stratigraphy, texture, mineralogy, colour, faults and so on. These are referred to as English fields. The dictionary file (&DICT) includes the codes used in the &IN file together with a decoded description, and also the name of the field to which the code applies. The optional remarks file (&REMARKS) is keyed on BHID and FROM, and contains text which is simply copied to the output report at the appropriate downhole distance. The user can define headings and footings for the output report in a similar manner to that used in the REPORT and FORMAT processes. The processing of the coded data consists of three stages: -
Any of the fields in the &IN file can be copied directly to the output report without being decoded. This is done in a similar way to REPORT and FORMAT using a Fortran-type format specification.
-
Selected coded fields are translated via the dictionary into English text or transposed directly to the English log part of the output report. Consecutive fields may be concatenated and separated by a comma, so that the resultant output forms part of an English sentence, although it will not necessarily be grammatically correct. Each field may have a precedent, which is an array of text which will precede the decoded description. Similarly a field may have an antecedent which will follow the decoded description.
-
The remarks file contains any additional text which is included in the output report immediately following the decoded description.
Process Summary ENGLOG
The process takes as input a file containing coded downhole logs, and translates them through a dictionary file into readable English equivalents in a report format. It can also take input from a second file containing remarks, and join this information at the appropriate downhole distance to the output report. The report can be sent to the printer, to a system file, and to the screen.
ENGLOG
1.1
DATAMINE
GENERAL EXTENSIONS
&IN
The input data file containing the coded log. This must contain at least the BHID and FROM fields. All fields which are to be decoded [the English fields] must be of the same type [alpha or numeric] and the same length [if alpha].
&DICT*
The dictionary file containing the translated codes. It must contain the 3 fields TYPE, CODE and TEXT.
&REMARKS*
The remarks file contains the three fields BHID, FROM and TEXT, and should be sorted on BHID and FROM. The TEXT field is multi-character alpha.
@LHMARGIN*
Start column for printing (1).
@RHMARGIN*
End column for printing (79).
@LINES*
Number of lines per page of output (0). 0 - no paging.
@NOFF*
If set to 1, suppresses form feeds (0).
@DOUBLE*
(0) 1
@SYSFILE*
=1
@ENG_MAR*
The number of spaces left as a margin on the left-hand side of the output report before the decoded text is written. Default is (0).
@ENG_LEN*
The number of characters per line for the translated text part of the output report. This does not include the spaces defined by @ENG_MAR.(79)
@PRECDENT*
This parameter controls the output of the precedent. The precedent itself is defined interactively. =0 if there is no code in the &IN file [ie if it is blank for an alpha field or '-' for numeric] then the precedent is not included in the report (0). =1 the precedent [if it has been defined] will always appear in the output report, even if the coded field to which it applies is absent data.
@PRINT* @ECHO*
=-1 will stop screen output. If >= (0) output will appear on the screen. If = 1 output will also be sent to the print file.
-
single spacing [default]; double spacing. to send report to a system file rather than the print file (0). The file name is requested interactively.
Interaction is divided into five parts: -
system file prompt
ENGLOG
1.2
DATAMINE
GENERAL EXTENSIONS
-
heading footing formatted output English fields
>SYSFILE>
Name of system file for output report. This prompt is only given if @SYSFILE=1.
>HEADING >
Prompts for heading lines. Format of heading line input: HDn[,COL=ccc|,JL|,JC|,JR];heading text : where
n ccc JL,JC,JR :
= = = =
heading number (1 to 9); start column; justify left, centre and right, respectively. heading text terminator. If not present, last non blank character used as terminator inclusively.
Heading lines must be entered sequentially starting at 1. Partial heading lines (i.e two lines with the same hea ding number) should be entered from left to right. Unless overriding opti ons are used, heading text for partial heading lines will be concatenated. Heading input must be terminated with a blank line. A blank line is required even if there are no heading lines. >FOOTING >
Prompts for footing lines. Format of footing line input: HDn[,COL=ccc][,JL|JC|JR];footing text : where
n ccc JL,JC,JR
= = =
footing number (1 to 9); start column; justify left, centre and right, respectively.
ENGLOG
1.3
DATAMINE
GENERAL EXTENSIONS
:
=
footing text terminator. If not present, last non blank character used as terminator inclusively.
Footing lines must be entered sequentially starting at 1. Partial footing lines (i.e t wo lines with the same footing number) should be entered from left to rig ht. Unless overriding options are used, footing text for partial footing lines will be concatenated. Footing input must be terminated with a blank line. A blank line is required even if there are no footing lines. >FIELD>
Name of the field to be printed. Enter blank line to terminate entry of field names.
>FORMAT>
FORTR AN format specification for the field, including any leading or trailing blanks.
>ENGLISH_FIELD
Enter the name of the first English field [as defined in the &IN file DD] which is to be decoded through the &DICT file or transposed directly to the output report. Terminate with a blank line.
>ENGLISH_TYPE
Enter the value of the TYPE field in the &DICT file which matches the ENGLISH_FIELD. If this is left blank then the field value will be transposed directly to the output report.
>PRECEDENT
Enter a string of text of up to 30 characters which will precede the English field. This may be left blank.
>ANTECEDENT
Enter a string of text of up to 30 characters which will follow the English field. This may be left blank.
>FORMAT
If the English fie ld is to be transposed rather than decoded then the format for the output report must be defined. This should be an A format for alpha fields or F or I for numerics.
ENGLOG
1.4
DATAMINE
GENERAL EXTENSIONS
Error and Warning Messages If the &IN file does not exist then this is a fatal error and the process terminates with the message: >>> CANNOT FIND FILE IN >>> &IN file missing
>> &DICT file missing
>> &REMARKS file missing
>> >>> >>> >>> >>> >>> >>> >>>
INVALID MARGINS SET HD2; ---------------HEADING>HD2;------------------------------HEADING>HD3; HEADING>HD4; FROM TO RECOVERY HEADING>HD5; -----------HEADING>
STRAT CODE ----------
>>> GENERAL TABULATION PROGRAM > PLEASE SUPPLY PAGE FOOTINGS IN THE FORM: >>> HDn[,COL=ccc|,JL|,JC|,JR];FOOTING TEXT : >>> where n=footing number. FOOTING> >>> DEFINE FIELDS AND OUTPUT FORMATS F10.2 FIELD >TO FORMAT>F10.2 FIELD >RECOVER FORMAT>5X,F10.2 FIELD >STRAT1 FORMAT>10X,A4 FIELD >
ENGLOG
1.10
DATAMINE
GENERAL EXTENSIONS
>>> DEFINE ENGLISH FIELDS ROCK PRECEDENT >Major Rock Type: ANTECEDENT >. >>> ALPHA FIELD 4 CHARACTERS WIDE FORMAT > ENGLISH_FIELD =
2
ENGLISH_FIELD >STRAT1 ENGLISH_TYPE >STRAT PRECEDENT >Stratigraphies: ANTECEDENT > >>> ALPHA FIELD 4 CHARACTERS WIDE FORMAT > ENGLISH_FIELD =
3
ENGLISH_FIELD >STRAT2 ENGLISH_TYPE >STRAT PRECEDENT > ANTECEDENT >. >>> ALPHA FIELD 4 CHARACTERS WIDE FORMAT > ENGLISH_FIELD =
4
ENGLISH_FIELD >COLOUR1 ENGLISH_TYPE >COLOUR PRECEDENT > ANTECEDENT >in colour. >>> ALPHA FIELD 4 CHARACTERS WIDE FORMAT > ENGLISH_FIELD =
5
ENGLISH_FIELD >BCA_ANG ENGLISH_TYPE > PRECEDENT >Bedding angle: ANTECEDENT >degrees. >>> NUMERIC FIELD. PLEASE GIVE FMT (REAL OR INTEGER) FORMAT >F5.1 ENGLISH_FIELD = ENGLISH_FIELD
6 >
ENGLOG
1.11
DATAMINE
GENERAL EXTENSIONS
!START MAC1 !ENGLOG &IN(DATA1), &DICT(CODES1),&REMARKS(REMARKS1),@ENG_MARG=50,@ENG_LENG=40, @LHMARGIN=1,@RHMARGIN=120,@LINES=60,@DOUBLE=0,@NOFF=0,@SYSFILE=1,@PRECDENT=0 englog.sys HD1; BELGRAVIA MINING HD1; - Downhole log for hole A100 HD2; ---------------HD2;------------------------------HD3; HD4; FROM TO RECOVERY STRAT CODE HD5; --------------------FROM F10.2 TO F10.2 RECOVER 5X,F10.2 STRAT1 10X,A4 ROCKTYPE ROCK Major Rock Type: . STRAT1 STRAT Stratigraphies: STRAT2 STRAT . COLOUR1 COLOUR in colour. BCA_ANG Bedding angle: degrees. F5.1 !END
ENGLOG
1.12
DATAMINE
GENERAL EXTENSIONS
BELGRAVIA MINING - Downhole log for hole A100 --------------------------------------------FROM ---2.10
TO -4.20
RECOVERY -------90.00
STRAT CODE ---------A Major Rock Type: Basalt . Stratigraphies: Fault A, Mip Fault. Red in colour. Bedding angle: 50.5 degrees.
4.20
6.60
50.00
NB Major Rock Type: Carbonate . Stratigraphies: North Bassett, Fault A. Blue in colour. Bedding angle: 27.3 degrees.
6.60
10.20
65.00
GR Major Rock Type: Conglomerate . Stratigraphies: Granite . Blue in colour. Bedding angle: 44.4 degrees. REMARKS: Strong brecciation
10.20
12.90
50.00 Major Rock Type: Conglomerate . Bedding angle: - degrees.
12.90
14.40
0.00
P Major Rock Type: Limestone . Stratigraphies: No.1 Horizon . Green in colour. Bedding angle: 12.1 degrees. REMARKS: Poor recovery. Fault found in near holes.
ENGLOG
1.13
DATAMINE
GENERAL EXTENSIONS
MINZON Introduction The process allows the user to investigate the relationship between mining parameters (bench height, minimum advance distance, minimum mining width) and the composition of each mining volume or zone. The definition of a zone is user definable, and can take account of any modelled attribute such as rocktype, material type, stratigraphy, grade etc. For example, zone Z1 could be defined as having a mixture of rocktypes R1 and R2, where the proportion of R1 is greater than 50%, where the major stratigraphy is S3, and the grade of the element E1 is greater than 3.5 g/t. If a zone does not meet the minimum mining width requirement then it may be combined with an adjacent zone according to a set of user definable rules. An additional option allows the width of a zone to be shrunk in order to achieve grade criteria. The process requires as input a geological model, a set of zone definitions, and the mining parameters. Two output files may be created; a model and a reserves file. The output model contains all the fields of the input model plus the zone field. Numeric fields are averaged over the zone, and alpha fields in the output model show the major value calculated on a tonnage basis. The output reserves file contains the tonnage and grade of each zone on each bench. File Handling The following are the major files used by the MINZON process: &IN
-
the input model
The input model file contains the standard 13 model fields plus a minimum of one additional field (e.g. grade, rocktype, etc). If it contains a field DENSITY, then this will be used for tonnage calculations. &ZONEDEF
-
zone definitions
This file contains the definitions of each zone using conditional criteria on fields in the input model file. It contains six compulsory fields and has one optional field: *ZONE
-
a four character alpha zone code.
*SUBZONE*
-
a secondary classification within the primary ZONE field. This is an optional field, and may be either alpha or numeric.
*FIELD
-
the field in the input model file to which the criteria apply.
MINZON
1.1
DATAMINE
GENERAL EXTENSIONS
*TEST1
-
a four character alpha field, containing one of the conditional operators: >, >=, =, A 2 ROCK = A 2 ROCK = A 2 STRAT /
VALUE1 -----50 R1 52 R4 R6
TEST2 ----= 50
and FE 52
and ROCK=R4, terminated with a change of STRAT
FE > 52
and ROCK=R6, terminated with a change of STRAT
or or
MINZON
1.2
DATAMINE
&RULES
GENERAL EXTENSIONS
-
rules for slice combination
This file defines pairs of zones which may be combined and the order in which they are to be considered for combining. The order in which zones are compared is simply the order of the records in the file. *TARGET
-
the main zone which is to be combined. This is a 4 character alpha field. Possible values are as defined in the *ZONE field of the &ZONEDEF file.
*ADJACENT
-
the zone to be combined with the *TARGET zone field. this is a 4 character alpha field. Possible values are as defined in the *ZONE field of the &ZONEDEF file.
&THRESH
-
threshold values
This file defines values for threshold calculations. It is an optional file; if it is not specified then threshold calculations will not be used. The following five fields are compulsory: *ZONE
-
zone type' a 4 character alpha field
*GRADE
-
the name of a grade field in the &IN file to be used in determining whether the zone is above or below the threshold value. This is an 8 character alpha field.
*THRESH
-
the threshold grade value corresponding to the *GRADE field. A positive value indicates a lower limit, and a negative value indicates an upper limit.
*SHRINK
-
a flag to indicate if shrinking is required: =0 =1 =2
*FAILZONE
-
do not apply shrinking or thresholds; if the grade of the zone does not pass the threshold, then redefine the zone field to be as given in *FAILZONE; apply shrinking.
the new zone type which applies if threshold criteria fail. This is a 4 character alpha field.
The &THRESH file may also contain any field from the input model file. The values of this field are used as criteria in addition to the *ZONE field. A value of - indicates that the field should be ignored.
ZONE C D
MATERIAL LGS -
GRADE FE AL2O3
THRESH 50 -3
SHRINK 1 2
FAILZONE X Y
MINZON
1.3
DATAMINE
GENERAL EXTENSIONS
MATERIAL is a field in the input model file. If the zone of a slice is C and the value of MATERIAL in the slice is LGS, and the grade of FE is less than 50, then redefine the zone as X. If the zone is D and the grade of AL2O3 exceeds 3, then shrinking will be attempted, irrespective of the value of MATERIAL. &OUT
-
the output model
The output model file will contain all the fields from the input file plus the ZONE field. Numeric fields will contain the average value over the zone, and alpha fields will contain the majority alpha value. The majority alpha value is calculated on a tonnage weighted basis, excluding any blank (absent data) values. &RESERVES -
reserves by zone
The optional &RESERVES file contains tonnage classified by bench and zone: *BENCH
-
Base of bench RL.
*ZONE
-
Zone code.
*TONNES
-
The tonnage for the bench and zone.
Mining Parameters Seven parameters are required to define mining dimensions. These are illustrated in Figure 1. @ZXORIG, @ZYORIG, @ZZORIG define the starting point for zone modelling, and @DIRECTN defines the direction of mining advance. The direction must be parallel to either increasing X or Y direction. this is illustrated in Figure 2. @ZZORIG is the elevation of the base of the lowest bench for which zoning is required. The parameters @MINWID, @MINADV and @MINBHT define the minimum mining width, the mining advance distance, and the mining bench height respectively. Zone Definition A zone is defined by the values of the individual cells and subcells which make up the zone volume. For example: Number -----1 2 3
ZONE ---D D E
MPROP ----0 Fatal Error: ZONEDEF VALUEn field must be alpha Fatal Error: VALUEn field in ZONEDEF is missing > Fatal Error: ZONEDEF file must be sorted by SEQNO and SUBZONE > Fatal Error: in RULES file > Fatal Error: in a field in RULES file > Fatal Error: in OUT file > Fatal Error: in a field in OUT file > Fatal Error: in SCRATCH file > Fatal Error: in a field in SCRATCH file > Fatal Error: in a field in THRESH file > Fatal Error: in a field in RESERVES file > Fatal Error: Please use valid coordinate numbers > Fatal Error: Maximum coordinate must be greater than minimum
View more...
Comments
