Sunteți pe pagina 1din 41

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

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

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

<<<
<<<

If the &DICT file does not exist and decoding has been requested using the interactive
commands, then the process terminates with the message:
>>> CANNOT FIND FILE DICT
>>> &DICT
file missing

<<<
<<<

If an &REMARKS file is not specified then a warning is issued:


>>> CANNOT FIND FILE REMARKS
>>> &REMARKS
file missing

<<<
<<<

This is for information only as the file is optional.


>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>

INVALID MARGINS SET <<<


INVALID HEADING IDENTIFICATION <<<
INVALID HEADING INPUT INFORMATION <<<
INVALID FOOTING IDENTIFICATION <<<
INVALID FOOTING INPUT INFORMATION <<<
FIELD fieldname NOT IN FILE <<<
INVALID FORMAT - format
OUTPUT nnn CHARACTERS - MAX ALLOWED mmm <<<
FORTRAN ERROR NUMBER = nnn WRITING TO PRINTER

Notes
If @PRECD ENT=1 and the field has a non-blank precedent, then the precedent text
starts on a new line.
When a field has a non-blank antecedent, then the current line of text is terminated after
the antecedent is output.

ENGLOG

1.5

DATAMINE

GENERAL EXTENSIONS

When a field has an antecedent, but the field value cannot be matched in
then the antecedent is not output.

the &DICT file,

Text strings (precedents, antecedents and decoded English fields) are stripped of
trailing blanks before being reported.
If the text from an &REMARKS file exceeds the specified width of the translated text
part of the output report then the text is split between lines at a word boundary (a
space).
Both BHID and FROM values in the &REMARKS file must match exactly with the BHID
and FROM values in the &IN file for the remark to be transposed to the output report.
Any non-matching remarks are ignored.
Although the process can be run interactively, it is mo st suited for running from a macro
or menu. The interactive prompts are not displayed on the screen when running from
a macro or menu.
Substitution strings (e.g. $DATE#) may be included in header and footer lines. The
expression ^page^ will print the incremental page number in the header or footer.
Special DATAMINE characters -, +, tr (TR) are honoured in the printed report. Any
numeric out of format range is printed as a '*'. Any character strings exceeding the
format range are truncated to the right.

Example
An example of the use of ENGLOG process is given over the next six pages:
ENGLOG 1.7
ENGLOG 1.8
ENGLOG 1.9
ENGLOG 1.10
ENGLOG 1.11
ENGLOG 1.12
ENGLOG 1.13

Listing of the &IN file.


Listing of the &DICT file.
Listing of the &REMARKS file.
Interactive use of ENGLOG
Interactive use of ENGLOG
Macro for running ENGLOG
Output report

ENGLOG

1.6

DATAMINE

GENERAL EXTENSIONS

The only difference between the interactive and macro examples is tha t a system output
file is used when running from a macro.
======================================================================
FILENAME
DATA1
ENGLOGIR
Test data
---------------------------------------------------------------------FILE CONTAINS
5 RECORDS EACH OF LENGTH
10
---------------------------------------------------------------------FIELD
TYPE WORD.NO STORED START
DEFAULT
---------------------------------------------------------------------BHID
A
1
Y
1
Hole
BHID
A
2
Y
2
_id
FROM
N
1
Y
3
0.0
TO
N
1
Y
4
0.0
RECOVER
N
1
Y
5
0.0
ROCKTYPE A
1
Y
6
rock
STRAT1
A
1
Y
7
stra
STRAT2
A
1
Y
8
stra
COLOUR1
A
1
Y
9
col1
BCA_ANG
N
1
Y
10
0.0
======================================================================
===================================================================================
BHID
FROM
TO
RECOVER
ROCKTYPESTRAT1 STRAT2 COLOUR1 BCA_ANG
===================================================================================
A100
2.1
4.2
90.0
BAS
A
MF
R
50.5
A100
4.2
6.6
50.0
CAR
NB
A
B
27.3
A100
6.6
10.2
65.0
CNG
GR
B
44.4
A100
10.2
12.9
50.0
CNG
K
A100
12.9
14.4
0.0
LIM
P
H1
G
12.1
5 RECORDS LISTED

ENGLOG

1.7

DATAMINE

GENERAL EXTENSIONS

======================================================================
FILENAME
CODES1
ENGLOGIR
codes
---------------------------------------------------------------------FILE CONTAINS
16 RECORDS EACH OF LENGTH
8
---------------------------------------------------------------------FIELD
TYPE WORD.NO STORED START
DEFAULT
---------------------------------------------------------------------TYPE
A
1
Y
1
type
TYPE
A
2
Y
2
CODE
A
1
Y
3
code
TEXT
A
1
Y
4
text
TEXT
A
2
Y
5
TEXT
A
3
Y
6
TEXT
A
4
Y
7
TEXT
A
5
Y
8
======================================================================
>>> LISTING
COLOUR A
COLOUR B
COLOUR C
COLOUR G
COLOUR R
ROCK
BAS
ROCK
CAR
ROCK
CNG
ROCK
DOL
ROCK
LIM
STRAT
A
STRAT
GR
STRAT
K
STRAT
NB
STRAT
MF
STRAT
H1

FROM FILE CODES1


Grey
Blue
Cream
Green
Red
Basalt
Carbonate
Conglomerate
Dolomite
Limestone
Fault A
Granite
Shear K
North Bassett
Mip Fault
No.1 Horizon

<<<

16 RECORDS LISTED

ENGLOG

1.8

DATAMINE

GENERAL EXTENSIONS

======================================================================
FILENAME
REMARKS1 ENGLOGIR
remarks
---------------------------------------------------------------------FILE CONTAINS
3 RECORDS EACH OF LENGTH
14
---------------------------------------------------------------------FIELD
TYPE WORD.NO STORED START
DEFAULT
---------------------------------------------------------------------BHID
A
1
Y
1
Hole
BHID
A
2
Y
2
-id
FROM
N
1
Y
3
0.0
TO
N
1
Y
4
0.0
TEXT
A
1
Y
5
text
TEXT
A
2
Y
6
TEXT
A
3
Y
7
TEXT
A
5
Y
8
TEXT
A
6
Y
9
TEXT
A
7
Y
10
TEXT
A
8
Y
11
TEXT
A
9
Y
12
TEXT
A
10
Y
13
======================================================================
================================================================================
BHID
FROM
TO
TEXT
================================================================================
A100
2.0
3.0
Very fine grained
A100
6.6
7.0
Strong brecciation
A100
12.9
50.0
Poor recovery. Fault found in near holes
3 RECORDS LISTED

ENGLOG

1.9

DATAMINE

GENERAL EXTENSIONS

EXAMPLE OF INTERACTIVE USE OF ENGLOG


-----------------------------------!ENGLOG &IN(DATA1), &DICT(CODES1),&REMARKS(REMARKS1),
@ENG_MARG=50,@ENG_LENG=40,@LHMARGIN=1,@RHMARGIN=120,
@LINES=60,@DOUBLE=0,@NOFF=0,@SYSFILE=0,@PRECDENT=0
>>> GENERAL TABULATION PROGRAM <<<
>>> PLEASE SUPPLY PAGE HEADINGS IN THE FORM:
>>> HDn[,COL=ccc|,JL|,JC|,JR];HEADING TEXT :
>>> where n=heading number.
HEADING>HD1;
BELGRAVIA MINING
HEADING>HD1; - Downhole log for hole A100
HEADING>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 <<<
FIELD >FROM
FORMAT>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 <<<


ENGLISH_FIELD =

ENGLISH_FIELD >ROCKTYPE
ENGLISH_TYPE
>ROCK
PRECEDENT
>Major Rock Type:
ANTECEDENT >.
>>> ALPHA FIELD 4 CHARACTERS WIDE
FORMAT >
ENGLISH_FIELD =

ENGLISH_FIELD >STRAT1
ENGLISH_TYPE
>STRAT
PRECEDENT
>Stratigraphies:
ANTECEDENT >
>>> ALPHA FIELD 4 CHARACTERS WIDE
FORMAT >
ENGLISH_FIELD =

ENGLISH_FIELD >STRAT2
ENGLISH_TYPE
>STRAT
PRECEDENT
>
ANTECEDENT >.
>>> ALPHA FIELD 4 CHARACTERS WIDE
FORMAT >
ENGLISH_FIELD =

ENGLISH_FIELD >COLOUR1
ENGLISH_TYPE
>COLOUR
PRECEDENT
>
ANTECEDENT >in colour.
>>> ALPHA FIELD 4 CHARACTERS WIDE
FORMAT >
ENGLISH_FIELD =

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: >, >=,
<, <=, =, <>, /

*VALUE1

an alpha field of up to 20 characters to which the conditional operation TEST1


applies.

*TEST2

a four character alpha field, containing one of the conditional operators: >, >=,
<, <=, =, <>, /

*VALUE2

an alpha field of up to 20 characters to which the conditional operation TEST2


applies.

If the value of FIELD is repeated within the same ZONE and SUBZONE classification then the
condition is treated as a logical 'OR'. If different values of FIELD are specified within the same
ZONE and SUBZONE classification then they are treated as a logical 'AND'.
The optional SUBZONE field is used to make alternative definitions for the same ZONE code. The
SUBZONE does not form part of the output file.
The / operator represents a BREAK field. If the value of *FIELD changes then the zone is
terminated. It does not require a *VALUE1 or *VALUE2 field.
The <> operator represents 'not equals'.
Example:

ZONE
SUBZONE
FIELD
TEST1
-----------------A
1
FE
>=
A
1
ROCK
=
A
2
FE
>
A
2
ROCK
=
A
2
ROCK
=
A
2
STRAT
/

VALUE1
-----50
R1
52
R4
R6

TEST2
----<=

VALUE2
-----55

Zone A is defined as:


FE >= 50

and FE <= 55

and ROCK=R1

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<MPROP<0.5
0<MPROP<0.5
0<MPROP<0.5

FE
-<50
<50
<50

ROCKTYPE
-------R3
R2
-

BREAK1
-----STRAT
STRAT
STRAT

BREAK2
-----LITHO

MINZON

1.4

DATAMINE

GENERAL EXTENSIONS

Fields MPROP, FE and ROCKTYPE exist in the in put model file. The zone field ZONE
will be created in the output model according to the above definitions.
The BREAK fields show wh en changes in a field value cause a zone to be terminated.
In the above example zone D is terminated when there is a change in the value of the
field STRAT, where STRAT must be one of the fields in the input model file. This
termination will occur even if the adjacent zone is also D. Zone E will be terminated
when either of the fields STRAT or LITHO change. Up to 5 BREAK fi elds are permitted.
It can be s een from the usage of these BREAK fields that they will usually reference
alpha model fields which have discrete values rather than numeric fields which will
normally be continuous.
The sign - indicates that the valu e of that field is not important. It can be seen from the
above example that the order in which zones are defined is significant. If the definition
for zone E is placed first, th en zone D will never be assigned. the above example also
illustrates that the same zone code can apply to more than one combination of field
values.
A volume w hich does not meet any of the zone definitions will be assigned the default
zone code. this is taken from the default value of the *ZONE field in the &ZONEDEF
file. Alternatively, the user m ay use the last record in the &ZONEDEF file to define the
default value, by supplying no criteria with that zone code.
Zone Assignment
Figure 1 shows a plan through the sub-cell structure of an orebody model. The direction
of advance is the negative X direction. A model slice is defined as a rectangular volume
with dimensions:
-

X:
Z:
Y:

@MINADV the mining advance distance


@MINBHT the mining bench height
the dimension in Y is the maximum possible distance subject t o the constraints
that the zone type, and other specified fields, remain constant.

The dimension in Y is calculated as follows. The zone and BREAK values of crosssection XZ are calculated by applying the zone rules to the material intersected by a
plane defined by P1Q1 in plan and extending by the face height in a vertical direction.
This plane is then pushed backwards (in the positive) Y direction in Figure 1) until it

MINZON

1.5

DATAMINE

GENERAL EXTENSIONS

crosses a sub-cell boundary (P2Q2). The zone and BREAK values of this new plane
are calculated. If any of these values have changed th en the current slice is terminated
and a new slice started. If none of the values have changed the XZ plane is pushed
back to the next sub-cell boundary (P3Q3) and the process is repeated until the total
model has been di vided into slices with constant zone and BREAK values within each
slice.
When a slice is terminated the average value of all numeric fields within the slice is
calculated. For alpha fields , the major value is calculated. This is the value which has
the largest tonnage within the slice. Alpha fields which are blank (absent data) are not
included in the calculation of the major field value.
It should be not ed that the example in Figure 1 is in two dimensions, whereas sub-cell
boundaries for slice termination will usually be in three dimensions.
Minimum Mining Width
The slices defined by zone and BREAK represent potential mining slices. However,
some of the s lices may be narrow in the Y dimension, and therefore not selectively
mineable as a sin gle unit. Parameter @MINWID is used to specify a Minimum Mining
Width. The next stage of the process is therefore to compare the width (W) of each
slice with @MINWID, and to combine slices where W<@MINWID. The rules for
combining slices are described below.
Rules for Combining Slices
Two successive slices m ay be combined into a single slice according to a set of rules.
These rules are defined by the user by specifying a set of target and adjacent zones,
and a sequence of field priorities. The set of zones which can be considered for
combining is specified using input file &RULES. This has two fields *TARGET and
*ADJACENT. The order of the records in the &RULES file is the order in which the
rules are applied.
An example of an &RULES file is shown in Figure 3. This shows that the first priority
is to combine two neighbouring C zones. Second in priority is to combine two D zones;
then a C and an O zone; and so on.
Each rule is applied to each of the slices in sequence. As a rule is a pplied to a slice that

MINZON

1.6

DATAMINE

GENERAL EXTENSIONS

slice becomes the target slice. The target zone is the zone of the target slice. The
adjacent slice is the slice wh ich is being considered for combining with the target slice.
The rules are applied in sequence:
rule1 is applied to slice 1, then to slice 2, ..., then to slice n;
rule2 is applied to slice 1, then to slice 2, ..., then to slice n;
The rules are only applied if the width (W) of the target slice is less than the Minimum
Mining Width (@MINWID). If this is true then the values of the target slice are
compare d with the values of the slices either side of it to see whether it can be
combined with either of them.
A set of field priorities are used to decide which of the two adjacent slices should be
combined. They are specified using the optional fields *PRIORTY1, *PRIORTY2, .....,
*PRIORTY5. For example:
*PRIORTY1(STRAT),*PRIORTY2(MATERIAL)
This defines the field STRAT to have the highes t priority, and then the MATERIAL field.
The adjacent slice which is the nearest match to the target slice is selected for
combining. If both adjacent slices p rovide an equal match then the mining width rule is
used as described below.
Two examples of these rules are shown below where T is the target slice and A and B
and the adjacent slices either side:
-

if T, A and B have the same STRAT, but only B has the same MATERIAL then T
and B are combined.

if only A has the same STRAT as T then A an d T are combined, irrespective of the
MATERIAL values of T, A and B.

If both adjacent slices are equally matched then the slice that creates the smallest
combined width (CW) is selected, provided that CW is greater than or equal to the
minimum mining width (@MINWID). If CW<@MINWID for both adjacent slices, then
the one that maximises CW is selected.

MINZON

1.7

DATAMINE

GENERAL EXTENSIONS

After slices have been combined according to the above rules, the zone and all other
field values of the combined slice will be recalculated. It should be noted that the
resulting zone may not be the same as either of the individual components.
Threshold Values
Threshold values are sometimes used to allow grade criteria to be applied after slices
have been combined using the above rules. the threshold values are independent of
any grade values used in zone definition. The values may be used to reset the zone,
or to attemp t to 'shrink' the width of the zone so that the grade of the critical field
exceeds the threshold.
The &THRESH file contains the threshold values for each zone/grade combination. An
example of an &THRESH file is given below:
Zone
C
C

MATERIAL
LGS
HG

Grade
FE
AL2O3

Threshold
50
-3

Shrink
1
2

Fail Zone
X
ALU

A positive threshold value implies that the slice should be greater than the threshold.
A negative value indicates that the grade should be less than the threshold (e.g. for a
contaminant).
The shrink value determines the required action as follows.
Shrink = 1
If the zone of a slice is defined according to the rules as C, and if the value of the
MATERIAL field is LGS, but its calculated FE grade is less than 50%, then it will be
redefined as zone X.
Shrink = 2
If a zone is defined as C, and the value of MATERIAL is HG, and its calculated AL2O3
grade is greater than 3% then shrinking will be attempted. First the AL2O3 grade for
the slice either side will be checked. If ne ither is below the threshold then shrinking will
be abandoned. If one of the slices is below the threshold, then shrinking will be
attempted in that direction as shown in Figure 4.

MINZON

1.8

DATAMINE

GENERAL EXTENSIONS

The boundar y will be moved in increments of @INCRMENT and after each increment
the AL2O3 gra de will be recalculated. When the value falls below the threshold, the
width (W) of the new zone is checked against @MIN WID. If W=>@MINWID, then both
zones either side of the new boundary line are recalculated and rezoned.
Output Model
After slices have been combined and the threshold values have been applied the
resulting model is written to the output file &OUT. The output model contains the zone
field, and average or majority values for all other fields that are in the input model.
The output model prototype is the same as the input model prototype. The boundaries
of each zone slice will not therefore align with original cell boundaries. In the output
model, each zone slice will be split into sub-cells at the original cell boundary.
Progress Reports
The parameter @PRINT can be use d to control the amount of information displayed to
the screen and print file. The default 0 gives just a summary of the input parameters,
and a progress report as each mining bench is processed. A value o f @PRINT=1 gives
a summary of tonnes by b ench and zone. A value of @PRINT=2 gives details of slice
combination according to the specified rules. For example:
Bench
315

315
.
.

X
Y
1234.5 23456.7
1234.5 23460.7
1234.5 23456.7
1456.7

23566.6

Slice
Zone
Target
C
Adjacent O
Combined O
Target

Width
3.8
2.4
6.2

STRAT
DG1
DG2
DG1

2.4

MCS

MATERIAL
BIF
LGA
BIF
BIF

etc.
Process Summary
MINZON

Determ ines mining zones of consistent material within mining


advances. For an input model and mining parameters, the zone and
geometry of mining slices is determined. The slices may then be
combined to satisfy a minimum width requirement, or split to satisfy
a maximum width requirement, or shrunk to meet grade cut-off

MINZON

1.9

DATAMINE

GENERAL EXTENSIONS

specifications.

&IN

Input model. Must contain at least the fields XC, YC, ZC, XINC,
YINC, ZINC, XMORIG, YMORIG, ZMORIG, NX, NY, NZ, IJK. May
contain cells and sub-cells.

&ZONEDEF

Zone definition file. Must contain the fields SEQNO, ZONE, FIELD,
TEST1, VALUE1, TEST2, and VALUE2. May also contain
SUBZONE field. Must be sorted by SEQNO, SUBZONE.

&RULES

Rules file. Must contain the fields TARGET and ADJACENT.

&OUT

Output model. Will contain all fields of &IN input model plus ZONE,
and optionally *SLICENO and *SLICEWID.

&SCRATCH

Working file.

&THRESH*

Threshold file. Must contain the fields ZONE, GRA DE and THRESH.

&RESERVES*

Output reserves file. Will contain the fields BENCH, ZONE and
TONNES.

*PRIORTY1*

First field in model to be used in slice combination. Printed if


@PRINT=2.

*PRIORTY2*

Second field in model to be used in slice combination. Printed if


@PRINT=2.

*PRIORTY3*

Third field in model to be used in slice combination. Printed if


@PRINT=2.

*PRIORTY4*

Fourth field in model to be used in slice combination. Printed if


@PRINT=2.

*PRIORTY5*

Fifth field in model to be used in slice combination. Printed if


@PRINT=2.

MINZON

1.10

DATAMINE

GENERAL EXTENSIONS

*PRINT1*

First field to be printed (@PRINT=2) after any *PRIORTY1..5 fields;


up to maximum of 5 fields.

*PRINT2*

Second field to be printed (@PRINT=2) after any *PRIORTY1..5


fields; up to maximum of 5 fields.

*PRINT3*

Third field to be printed (@ PRINT=2) after any *PRIORTY1..5 fields;


up to maximum of 5 fields.

*PRINT4*

Fourth field to be printed (@PRINT=2) after any *PRIORTY1..5


fields; up to maximum of 5 fields.

*PRINT5*

Fifth field to be printed (@PRINT=2) after any *PRIORTY1..5 fields;


up to maximum of 5 fields.

*SLICENO*

Field name to hold slice number if @SLICEFLD=1.


SLICENO.

Default is

*SLICEWID*

Field name to hold slice width if @SLICEFLD=1.


SLICEWID.

Default is

@MINADV

Mining advance distance.

@ZXORIG*

X co-ordinate of origin for zon e modelling. Default is the input model


X origin.

@ZYORIG*

Y co-ordinate of origin for zon e modelling. Default is the input model


Y origin.

@ZZORIG*

Z co-ordinate of origin for zone modelling. Default is the input model


Z origin.

@MINWID*

Minimum mining width, measured perpendicular to the mining


advance. Default (0) ensures no minimum mining width is applied.

@MAXWID*

Maximum mining width, measured perpendicular to the mining


advance. Default (0) ensures no maximum mining width is applied.

MINZON

1.11

DATAMINE

@MINBHT*

GENERAL EXTENSIONS

Mining bench height. Default is the input model parent cell Z


dimension.

@DIRECTN*
1
2
3
4

Direction of mining advance. Default (1).


positive X (West to East)
negative X (East to West)
positive Y (South to North)
negative Y (North to South)

@INCRMENT*

Increment distance for shrinking. Default (1).

@EXZONE*

A value of the ZONE field - 4 character alpha - which will be excluded


from the output model. Cells or sub-cells with this ZONE value will
not be written to the &OUT file. Must be enclosed in quotes e.g.
@EXZONE='HG'. Default is to write all ZONE values.

@ONLYRULE*

Flag to always combine narrow slices. Default (0).


0 Slices less than @MINWID will always be co mbined with an
adjacent slice.
1 Slices less than @MINWID will be combined with an
adjacent slice if one satisfies criteria in &RULES file or
*PRIORTY1-5 fields, only.

@TRUEVOL*
0
1

@DENSITY*

Volume flag in output model. Default (0).


all
slices
will
have
the
full
volume
of
@MINADV*@MINBHT*slice thickness.
slices containing missing cells or subcells will have their Z
dimension reduced so that they have the true volume.

Density value to be used in calculations. If a DENSITY field exists in


the input model the @DENSITY parameter will be ignored. Default
(1).

@SLICEFLD*
0
1

Write slice width and number to &OUT file. Default (1).


Slice width and number are not written to &OUT file.
&OUT file will contain fields hold ing slice width and number.
Field names are defined by *SLICENO and *SLICEWID.

MINZON

1.12

DATAMINE

GENERAL EXTENSIONS

@PRINT*

Print flag. Default (0).


0 minimum output.
1 summary of tonnes per zone per bench.
2 details of combination of slices including values of first five
fields specified as *PRIORTY1..5, *PRINT1..5.

@ECHO*

Echo to printer. Default (0).


0 No copy.
1 copy of output to printer or print file.

Error and Warning Messages


>>> Warning: Minimum mining width = zero <<<
>>> Fatal Error:
MINWID must be 0 or a positive number <<<
The @MINWID parameter is negative. Fatal; the process is exited.
>>> Fatal Error:
MINADV must be a positive number <<<
The @MINADV parameter is negative. Fatal; the process is exited.
>>> Fatal Error: in IN file <<<
An error has occurred on opening the &IN file. Fatal; the process is exited.
>>> Fatal Error: in a field in IN file <<<
There is an error in a field in the &IN file. Fatal; the process is exited.
>>> Fatal Error: in ZONEDEF file <<<
An error has occurred on opening the &ZONEDEF file. Fatal; the pro cess is exited.

MINZON

1.13

DATAMINE

GENERAL EXTENSIONS

>>> Fatal Error: in a field in ZONEDEF file <<<


There is an error in a field in the &ZONEDEF file. Fatal; the process is exited.
>>> Fatal Error:
ZONEDEF VALUEn field must be alpha <= 20 chars <<<
The VALUE1 and VALUE2 fields in the &ZONEDEF file m ust be alphanumeric and
20 or less characters in length. Fatal; the process is exited.
>>> Fatal Error:
VALUEn field in ZONEDEF is missing <<<
The VALUE1 or VALUE2 field in the &ZONEDEF file is missing.
is exited.

Fatal; the process

>>> Fatal Error:


ZONEDEF file must be sorted by SEQNO and SUBZONE <<<
Fatal; the process is exited.
>>> Fatal Error: in RULES file <<<
An error has occurred on opening the &RULES file. Fatal; the process is exited.
>>> Fatal Error: in a field in RULES file <<<
There is an error in a field in the &RULES file. Fatal; the process is exited.
>>> Fatal Error: in OUT file <<<
An error has occurred on opening &OUT file. Fatal; the process is exited.
>>> Fatal Error: in a field in OUT file <<<
There is an error in a field in the &OUT file. Fatal; the process is exited.

MINZON

1.14

DATAMINE

GENERAL EXTENSIONS

>>> Fatal Error: in SCRATCH file <<<


An error has occurred on opening &SCRATCH file. Fatal; the process is exited.
>>> Fatal Error: in a field in SCRATCH file <<<
There is an error in a field in the &SCRATCH file. Fatal; the process is exited.
>>> Fatal Error: in a field in THRESH file <<<
There is an error in a field in the &THRESH file. Fatal; the process is exited.
>>> Fatal Error: in a field in RESERVES file <<<
There is an error in a field in the &RESERVES file. Fatal; the process is exited.
>>> Fatal Error:
Please use valid coordinate numbers <<<
There is an error in @XMORIG, @YMORIG or @ZMORIG. Fatal; the process is
exited.
>>> Fatal Error:
Maximum coordinate must be greater than minimum <<<
Fatal; the process is exited.

Notes
Proportions:
The definition of a zone may require a certain proportion of a rocktype or group of
rocktypes or stratigraphic unit to be present in the zone. This can be achieved by
defining a 0/1 variable in the input model file dependent on the non-existence/existence
of the selected at tribute. This variable can then be used as part of the zone definition.

MINZON

1.15

DATAMINE

GENERAL EXTENSIONS

For example, suppose there is a field MATERIAL i n the input model file and that certain
of the MATERIAL values are contaminants. A new field, CPROP (contaminant
proportion), can be cre ated in the input model with a value of 1 if the MATERIAL is the
contaminant or 0 if it is not a contaminant. This can be achieved most easily by using
the DECODE process. When the zone definition is applied to a slice of sub-cells, the
value of CPROP will give the proportion of the slice which is contaminant. the zone
definition can therefore include criteria such as CPROP<0.3, so that the zone must
have less than 30% contaminant.
Grouping Field Values:
There may be several alternative definitions for a si ngle zone code. For example, there
may be 30 possible values of field ROCK, of which 12 are possible for zone A. Each
of the 12 options can be specified individually as previously illustrated. Alternatively,
a new field could be defined in the input model which has a value of 1 if ROCK is one
of the 12 permitted values, or a value of 0 otherwise. Zone d efinition can then be based
on this new field, and then only one entry in the &ZONEDEF file is required. This is
similar to the method described in the previous note for defining proportions.

Example
!MINZON &IN(model), &ZONEDEF(zones), &RULES(must), &OUT(newmod),
&SCRATCH(temp),&THRESH(thold),&RESERVES(resvs) ,
*PRIORITY1(rock), @MINADV=50, @MINWID=20, @DIRECTN=3

MINZON

1.16

DATAMINE

GENERAL EXTENSIONS

Figure 1 Plan through Input Model showing Sub-cell Structure

MINZON

1.17

DATAMINE

A1B1
A2B2
etc.

GENERAL EXTENSIONS

face position 1
face position 2
Figure 2 Direction of Mining Advance

MINZON

1.18

DATAMINE

GENERAL EXTENSIONS

Rule
Target
Number
Zone
----------1
C
2
D
3
C
4
D
5
C
6
D
7
C
8
D
9
O
10
O
11
O
12
O
13
O
14
P
15
P
16
P
17
P
18
P
19
M
20
M
21
M
22
M
23
M
Note:

Adjacent
Zone
-------C
D
O
O
P
P
M
M
O
D
C
P
M
P
O
D
C
M
M
P
C
D
O

The rule number does not have to be included in the &RULES file. Rules are
applied in order.

Figure 3 Rules for Combining Slices

MINZON

1.19

DATAMINE

GENERAL EXTENSIONS

Figure 4 Shrinking Parameters


MINZON

1.20