Data Mine Tutorial

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

Geological Modeling

Creating a New Project: - File/ New/ Project Wizard/ Name: “Geomodeling”, Location: “C:\ Database\ DMTutorial\ Projects folder”, select “Automatically add files . . .”/ Project Settings / select: “Detect new files . . .”, “Detect files added”, “Automatically update project”/ OK/ Next/ Add Files/ browse to: “C:\ . . . \VBOP\ Datamine, CAD, Text, ODBC folders”/ Next/ Finish; >>> File/ Save Displaying Geological Modeling Toolbars: - View/ Customization/ Toolbars/ select: Boolean Operation, Data Filter, Drillhole Processing, DTM Creation, Format, Modeling, Point and String (Standard & Advanced), Snapping, View Control, Visualizer, Wireframe Linking - View/ Toolbars/ Holes, Hole Data, Log - View/ Customization State/ Save/ browse to project folder/ Name: “profile”; >>> File/ Save - View/ Customization State/ Load Defining Project Setting for Geological Modeling: - File/ Setting/ Project Setting dialog/ Data Display: symbol size: 0.2mm/ Desurvey Setting: Desurvey method: Radious Curvature, Desurvey Control: select Include direction . . . , Drillhole trace . . ./ Digital Train Model: General Option: select ‘use boundary strings’, ‘minimize flat triangles’, ‘breakline tolerance: 0.001’, DTM Plane: plan, Attributes: use first point-string/ Legend: select all options/ Mine Design: Evaluation Control: select ‘evaluate block model’, uncheck ‘use display legend’, select legend for evaluation (make later)/ Wireframes: ‘Tolerance: 0.001’, selection method: ‘always use default . . .’, default method: select by field/ wireframe linking: linking method: equi-angular shape, String Linking Control: select all options except ‘optimal linking’/ Apply/ OK. >>> File/ Save Importing CAD Format (*.dwg 2000): - File/ Add to project/ Imported from data source/ Data Import dialog/ driver category: CAD, data type: Auto CAD (string)/ OK/ Open source file dialog/ browse to file/ read drawing file dialog/ select ‘load all layer’/ OK/ Import file dialog/ define a name: ‘stopoi’, uncheck ‘points file’ and ‘table file’ options/ browse to project folder/ Import fields tab/ color field: color, select ‘use legend to resolve . . . ‘/ OK. >>> check this file in ‘File window’: it has 10 fileds: xp, yp, zp, ptn, pvalue, color, thickness, angle, Layer, Ltype. >>> File/ Save. - To see a quick preview: project file control bar/ right click/ preview - To Re-Import the file: right click on ‘stopoi’ in project files control bar/ select Re-Import Conditioning Strings: - Checking for Duplicate Points and Strings: Application/ utility processes/ check string data/ CHECKIT dialog/ IN: ‘stopoi’, OUT: ‘stopo1’ / OK. >>> In command control bar check that ‘no duplicate points & strings identified’ - Reducing Points and Setting a Minimum String Chord Length: Command toolbar/ find command/ Find Command dialog/ select ‘ proper’/ Run/ PROPER dialog/ Files tab/ PERIMIN: ‘stopo1’, PERIMOUT: ‘stopo2’/ Parameters tab/ Mode: 1, Tol: 0.01, Reduce: 1/ OK. In command control bar check that the output file contains 1819 records. Mode: 1, is to open all closed strings; boundary string to limit DTM creation can be reclosed later

1

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

Changing String Color (table editor): -Colour filed values range from 1 to 64 - Project file control bar/ right click on ‘stopoi’/ copy/ right clock on string folder/ paste/ right click on ‘copy of stopoi’/ rename/ Rename project file dialog/ select ‘show full file path’/ browse/ Rename file as . . dialog/ browse to your project folder/ define name: ‘stopo.dm’/ save/ OK - Project files control bar/ double click on ‘stopo’/ Table Editor window/ select column Colour/ Find/ Find and Replace dialog/ Replace tab/ Find: ‘1’, Replace: ‘10’, search option: by records, select ‘match entire filed contents’/ Replace all/ OK/ close/ save/ Exit. Importing Drillhole Data Tables (*.txt & *.xls) - File/ Add to project/ Imported from data source/ Data Import dialog/ Driver category: Text, data type: table/ OK/ Open source file dialog/ browse to . . . \VBOP\Text\_vb_collars_space.txt /Open/ Text Wizard dialog/ Data type: delimited, starts at line: 1, Header row: 1/ Next/ Delimiters: space, select ‘treat consecutive . .’/ Next/ check format setting for each column/ Finish/ Import file dialog/ Files tab/ name: ‘dhcollar’/ Fields tab/ select all nine fields/ OK; check this file in project files list and review in Table Editor and Files windows. - File/ Add to project/ Imported from data source/ Data Import dialog/ Driver category: ODBC v2, data type: table v2/ OK/ Select Data Source dialog/ Machine Data Source tab/ Excel Files data source/ OK/ Select Workbook dialog/ browse to ‘C:\ . . . \VBOP\ODBC\_vb_drillhole_data.xls’/ OK/ select sheet ‘Zones$’/ OK/ select the [BHID], [FROM], [TO] and [ZONE] fields/ OK/ warning dialog/ OK/ Table file name: ‘dhzones’/ select the [BHID], [FROM], [TO] and [ZONE] fields/ OK; check this file in project files list and review in Table Editor and Files windows. - All drillhole tables (*.txt or *.xls) including collars, survey, assay, lithology can be imported like this. Creating Static Drillholes: - Design Window/ Drillhole Processing tollbar/ Desurvey Drillholes/ HOLES3D dialog/ File tab/ Collar: ‘collars’, Survey: ‘survey’, Sample1: ‘lithology’, sample2: “zones’, Out: ‘dholes’/ Fields tab/ BHID, X, Y, Z, FROM, TO, AT, BRG, DIP/ Parameters tab/ Survsmth:0, Endpoint:0, Dipmeth:1/ OK. In Command control bar check to see results. Endpint:1, will include coordinates for both starts/end of each sample in the desurveyed output file; these coordinates can be extracted to a point table and used for DTM generating like water level, oxidation level, . . . Validating Static Drillholes: - To check for absent, incomplete, missing, overlaps, duplicate samples - Re-run desurvey process/ HOLES3D dialog/ Out: ‘dholes’, Holesmry: ‘dhsumry’, Errors: ‘dherrs’; open output files in Table Editor window to check the problems; correct the data in data source file and re-import and re-run desurvey process. Calculating Summary Statistics: - Design Window/ Application/ Statistic process/ Compute Statistic/ STATS dialog/ Files tab/ In: ‘collar’, Out: ‘dhstats’/ Fields tab/ F1:Xcollar, F2:Ycollar, F3:Zcollar/ OK; press Enter three times in Command tollbar; check in command bar and review output file. Visually Validating Static Drillholes: - To add label, color, Au histogram, section view, query - Design Window/ load ‘stopo’, ‘collars’, ‘holes’ files (drag and drop from project files list into design window; - Sheet control bar/ overlay tree/ double click on ‘collars’/ Format display/ format display dialog/ Label tab/ Reset/ Label to include: BHID/ OK; check BHID label is added in contents tab/ Style tab/ BHID/ Format for BHID dialog/ Text tab/ set font size and color/ back in Label tab/ Position/ Position relative to points: up-right/ OK 2

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

- Sheet control bar/ overlay tree/ double click on ‘holes’/ Format display/ format display dialog/ Drillholes tab/ Format/ Drillhole traces dialog/ Static drillhole tab/ Color tab/ On section: color using legend, Off section: color using legend/ Legend group/ Column: NLith/ click button ‘use default legend for this column/ Apply/ OK - Sheet control bar/ ‘holes’/ Format display dialog/ Drillholes tab/ Display downhole column group/ Insert/ select: Au/ OK/ Format for Au dialog/ Style template tab/ select: Filled histogram/ OK - Design Window/ View control toolbar/ View setting/ section: North-South, Width: 25m, Apply Clipping/ OK - Design Window/ Query/ Point/ Snap (left click) on a portion of a hole/ check information in ‘Data Properties control bar’ or in ‘Output Control bar’ Compositing Static Drillholes (COMPDH) - Drillhole Processing tollbar/ Composite Down Drillholes/ COMPDH dialog/ Files tab/ In: ‘holes’, Out: ‘holesc’/Fields tab/ BHID, FROM, TO, ZONE: NLith/ Parameters tab/ Interval: 1000 (longest hole length to be composited to), Mingap:0.05, Maxgap:0, Mincomp:0.001, Start:0, Mode:0, Print:0/ OK; - Check output results and records number - The combination of setting the ZONE: NLITH (rock type) and INTERVAL: 1000, will combine adjacent sample intervals of same ‘NLITH’ to generate composites of single rock type; can be done for same grade values, zone, by assigning another field as ‘ZONE’ - Retrieval tab is to filter the data by special criteria like: CU>0.2 to composite ‘holes’ at cut-off 0.2 Creating Dynamic Drillholes (Data Load Wizard): - Data/ Load/ Wizard/ Data Load Wizard (Import Data Type) dialog/ select: Drillholes Tables, Hole, Collar, Survey, Assay, Lithology, Interval log/ Next/ Import Hole Collar table/ Add/ Driver Category: Text, Data Type: Tables/ Open Source File dialog/ browse to C:\ . . .\VBOP\Text\_vb_collars_space.txt/ Open/ Text Wizard dialog/ Data Type: Delimited/ Next/ Delimiters: Space/ Next/ Absent data:-; Repeat the same procedure for other tables:/ Survey, Delimiters: comma, fields: BHID, AT, BRG, DIP, Positive Dip: down, Angular values: Degree/ Assays, Delimiters: comma, fields: BHID, FROM, TO, AU, CU, absent, . . . , DENSITY/ Lithology, Delimiters: comma, fields: BHID, FROM, TO, NLITH, LITH (description)/ Zones, fields: BHID, FROM, TO, absent, . . . , Zone:ZONE/ Load Complete/ 3D hole trace: yes, intersection table: yes/ Finish; check in loaded data control bar; File/ Save. Validating Dynamic Drillholes: - To check for missing, incomplete, gaps, overlaps, duplicate samples - In Desurvey Report control bar, check errors and warnings Visually Validating Dynamic Drillholes - To see relative location of holes in topography, hole trace, stratigraphic sequence, mineralized zones - Sheet Control bar/ Overlay branch/ show ‘dynamic drillholes’ and ‘stopo’ - View Cntrol bar/ toggle off clipping/ zoom all data/ view setting/ plan view, Z:77.5m - Sheet control bar/ Dynamic holes/ Format Display dialog/ Drillholes tab/ Format/ Drillhole trace dialog/ label tab/ select collar:BHID/ OK/ back in Format display dialog/ Display downhole column/ select NLITH/ Format/ Style Template tab/ select ‘Trace’/ Apply/ Trace tab/ select color using legend/ select NLith for color column legend/ Apply/ OK/ Apply/ OK. - Querying Drillholes: Compositor Control bar/ select (left click) below one collar of one hole. Linked Plots/ Tables - Plot Window/ Sheet control bar/ Plots/ Section 6012.50E/ Set of 2 Projections/ South North Projection Section 6012.5E overlay branch/ show ‘dynamic drillholes’ and ‘stopo (string)’ - Scale View toolbars/ Scale Fit/ Plot Scale: [1:2,500] - Section toolbar/ Define Section/ Section orientation: North-South, Width:50m, use clipping, X:6100, Y:5100, Z:75 3

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

- Dynamic Drillhole/ Format Display dialog/ Drillholes tab/ Format/ Drillhole trace dialog/ Labels tab/ select collar:BHID/ back in Format Display/ Display downhole column/ select NLith/ Format/ Format for NLith dialog/ Style template tab/ select ‘Trace’/ Apply; Repeat all the same format display settings for Rotated Plan Projection Section 6100E. - View/ Window/ Tables/ select _vb_collars_tab (txt) tab - Table Window/ select record ‘BHID VB2675’/select survey tab, check the highlighted records/ select Plot window, check the highlighted drillhole; - Plot Window/ select a part of a hole/ Table Window/ select various tabs, check highlighted records; Loading CAD drawing (*.dgn: microstation file) - Design Window/ Data/ Load/ Data Source Driver/ other . . ./ Data Import dialog/ Driver category: CAD, Data type: DGN/ OK/ Open Source file dialog/ browse to C:\ . . .\VBOP\CAD\ _vb_ltopo.dgn/ Open/ Read drawing file dialog/ select all levels and all objects/ Unit Scale 1: 10000/ OK; check that _vb_ltopodgn string object is listed in the Loaded Data Control bar; >>> File/ Save - Load ‘stopo.dm’; View Control/ toggle off clipping/ zoom all data/ view setting/ Az:0, Dip:0/ update visualizer; compare two contour string files. Creating Legend for Geological Modeling: - Load ‘holes’ by dragging and dropping from project files list into design window; - Format/ Format legend/ legend manager dialog/ New Legend/ Legend Wizard/ select ‘Use object field’ option/ select ‘holes’ in object list/ select ‘NLith’ from field list/ Next/ select current project file/ Next/ define legend name ‘holes-Nlith1’/select unique value/ Next/ Data range dialog/ Next/ Rainbow blue>Red/ Preview/ Finish; - Legend manager dialog/ select ‘holes-Nlith1’/ select legend item [0]/ Edit/ Description: soil, Fill color: yellow/ [1]:sandstone, red/ [2]:siltstone, Bgreen/ [3]:breccia, magneta/ [4]:basalt, bright blue/ right click on ‘holes-Nlith1’ legend/ Save Legend/ browse to project folder/ save; >>> File/ Save

Modifying a Legend to Use Fill Patterns - Legend Manager dialog/ make a copy of ‘holes-Nlith1’ into User legends folder and change the name to ‘holes-Nlith2’/ select ‘holes-Nlith2’/ select the legend item [soil]/ Edit/ Fill style: Texture, Texture file name: p-soilB.bmp, color: black, Line color: black/ Repeat for all legend items with Texture file names: [p-Sandstone W.bmp], [p-Siltstone N.bmp], [p-Breccia.bmp], and [p-Basalt.bmp] with black color and line color; - Save this legend in your project folder; this legend is used for log sheet and sections. Display Wireframe as Intersection - Sheet control bar/ Wireframe file: ‘topotr’, ‘oretr’/ Format display dialog/ Style tab/ Display as: Intersection/ OK Creating Viewplanes - View Control bar/ Plane by 1 point/ click inside window/ select ‘Plan’/ zoom to extent/ use clipping toggle/ clipping limit/ set clipping dialog/ Primary Clipping group: select front and behind Infinite check boxes/ OK/ Save view/ Section Definition dialog/ define a name in Description: ‘Plan’/ OK; check that new ViewDefs table object is added in loaded data list; this file will save the rest of views - Inclined View: set Azi:345, Dip:-42 in view setting or click and drag the view by holding shift inside design window to find a view/ save view/ Name: Inclined view - Section View: by 2 points or by 1 point and select NS or EW direction/ toggle on Use clipping/ clipping limits/ primary clipping/ fron:10, behind:10 - In Loaded data control bar/ right click on ‘ViewDefs’/ Data/ save as/ project file - View Control bar/ Get view/ in Command Control bar/ select a number from list/ type in command toolbar/ Enter - To edit the ViewDefs.dm (section) file use Table Editor Window/ Save after modified 4

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

Filtering Static Drillhole Data Using Legend - Format/ format legend/ new legend/ Legend Wizard dialog/ use object field/ select ‘holes’/ select ‘Zone’ from field list/ user legend storage/ Next/ Name: ‘hole-zone’/ unique value/ tick the “convert to filter expression” option/ Next/ Data range dialog/ Next/ Rainbow B>R/ Preview: there are 3 zones (,1,2)/ Finish - Legend manager/ delete legend items: [-] and [1]/ there is only one item now: [2] - In sheet control bar/ ‘holes’/ format display/ apply new legend/ now only segments of zone:2 are visible (???) - loaded data control bar/ right click on ‘holes’/ Data object manager/ clear Filter Expression/ Apply Filtering Orebody Strings Using Data Object Manager - Loaded Data Control bar/ right click on minst (string)/ Data Object Manager/ Expression Builder/ Expression Builder dialog/ Variable selection: ‘Colour’, click “select variable”, operator: =, column data: 5, click “check expression validity”/ OK/ Apply/ Close data object manager; this can be done by typing a filter like: ZONE=1 or COLOUR=5 - To remove a filter: Data Object Manager dialog/ clear Filter Expression/ Apply/ close Creating/ Viewing Log Sheet (Dynamic Drillholes) - Load dynamic drillholes and intersections - In Log Window/ Insert/ Sheet/ Log; or simply right click inside log window/ new log sheet; zoom fit - right click/ Log View Properties dialog/ Hole tab/ Extent: Custom, from:100 to:200, Scale: custom, 1:1000, locked, Initial extents when hole changes: same as previous hole/ Apply; current hole name can be changed to see other holes log sheet. - Log toolbar/ Hole Next, Hole previous/ move between holes - Selection toolbar/ select hole name Creating Rectangular Modeling Boundary (Extent of Block Model Prototype) - Load ‘holes’ and ‘stopo.dm’; View control/ Zoom all data/ view setting/Az:0, Dip:0, Z:220 - Current object toolbar/ object type: string/ create new object applying default templates; check that the “new string” object is added in loaded data list - Format/ Grid/ Options tab/ Line formatting/ select fixed intervals: X:10, Y:10, Z:10 - Snapping toolbar/ Snap mod grid - Point and string editing standard toolbar/ New String/ color palette/ select red:2/ right click close to the xy coordinates 5880,5250, go on for more 3 points to draw a rectangle around drillholes/ click cancel/ close string - View setting/ Az:345, Dip:-42/ zoom all data - Point and string editing standard toolbar/ New String/ color palette/ red:2 - View/ Mouse position/ select ‘locked’ for all coordinates and type the first point coordinates (5880,5250,-80)/ click anywhere within display limit/ repeat for rest of points/ clear ‘locked’ tick boxes/ close the dialog/ cancel/ close string - Loaded data control bar/ right click on “New String” object/ Data/ Save as/ Save New 3D object dialog/ single precision datamine (.dm) file/ browse to project folder/ define a name: “modbound”/ save; this file can be edited visually or by table editor to correct coordinates. Create Geological Interpretation Using Background Image - Load ‘stopotr (wireframe)’ and ‘viewdefs (section)’ - Format display dialog/ stopotr/ style tab/ intersection - View control bar/ get view/ 5/ enter - Format/ background/ Open image file/ Image number: 1.0/ select file dialog/ browse to C:\ . . .\ VBOP\ Pics\_vb_Seismic_Section_NS_5985.bmp/ Open/ Image World Location dialog/ XTopLeft:5985, YTopLeft:5270, ZTopLeft:220, XTopRight:5985, YTopRight:4760, ZTopRight:220, XBotLeft:5985, YBotLeft:5270, ZBotLeft:-130, 5

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

- Creating Section String From Topography Wireframe: Wireframe/ Plane Operation/ Section/ Section dialog/ Use view plane/ OK; check that new string file “Section 0: . . .” is listed in Loaded data control bar - Sheet control bar/ turn off display of wireframe and show only section string in red color using format display dialog - Current object toolbar/ Object type: string/ create new object applying default templates - Snapping toolbar/ Snap mode lines - Point and string editing standard toolbar/ New String/ Color palette/ orange:3/ snap (right click) to the topography section string at top left/ move down to bottom of the fault/ left click for second point/ New String command again/ snap (right click) to top section string at top right/ move down to bottom of the fault/ left click for second point/ cancel - Digitize First Ore Body String: New String command/ Color palette/ green:5/ move to top left end of ore body (thick, dark red, black reflectors)/ left click for first point at left side of fault string/ digitize the top contact toward right using left click/ left click for last point just at right side of fault line/ cancel string command/ repeat for second and third ore string with cyan (6) and magenta (7) colors - Point and string standard toolbar/ trim to string/ select (left click) left fault string/ select (left click) each of the 3 ore strings in turn at their start point to left/ cancel the command/ repeat for right side - Loaded data control bar/ right click on “new string” object/ Data/ save as/ single precision file/ browse to project folder/ define name: “seisinterp_NS5985” - To unload image file: Format/ Background/ close Image file Digitizing Vertical Section String - Load ‘faulttr’, ‘holesc’, ‘stopotr’, ‘viewdefs’ - Sheet control bar/ format display dialog/ display both wireframes as intersection - Format Display dialog/ ‘holesc’/ Drillholes tab/ format/ color tab/ select legend: holesc-Zone, column: Zone/ label tab/ Collar: BHID/ Apply/ OK - View control bar/ get view/ 3/ enter/ primary clipping: 10m (front and behind) - Upper Ore zone (blue): Zone 1, lower ore zone (red): Zone 2 - Current Object toolbar/ Object type: string/ Create new object applying default template - Snapping toolbar/ snap mode point/ toggle on snap to drillhole data - Digitizing upper zone ore body: Point and string standard toolbar/ New String/ color: green (5)/ move to first point at top left corner of ore body and left click/ move to top contact of ore in drillholes and right click (snap)/ move to next point using arrow keys/ at top right corner, extrapolate and left click then move down to bottom contact of upper ore zone and and go on/ close string - Smoothing string: select the string inside design window/ point and string toolbar/ smooth string; check that one point between each points is added now/ click delete points/ select points which are not needed - Digitizing lower zone ore body: snapping toolbar/ toggle on snap to drillhole data and string data/ click snap mode - Point and string toolbar/ new string command/ color: cyan (6)/ snap to existing upper zone string points without gap or overlap - Point and string toolbar/ insert point/ left click to insert 4 points along bottom contact of lower ore corresponding to upper contact - Saving the ore body string: Loaded data control bar/ right click on “New String”/ Data/ save as/ single precision (.dm) file/ project folder/ name: “min1st” - Repeat the same for other sections using the same file (min1st.dm) Translation Both Ending Strings (Extension) - View control bar/ Inclined view: Az:340, Dip:-40/ select one side ending string inside design window - Point and string toolbar/ Translate string/ Translate String dialog/ X Translation distance:25m, Y TD:0, Z TD:0, Keep original string: Y/ OK; repeat for other side ending string; be noticed that +: increasing values (eastward or northward), -: decreasing values (westward or southward) 6

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

- Point and string toolbar/ delete points/ select a few points at both ends of the new strings to minimize the area; - Loaded data control bar/ right click on “min1st.dm”/ save Adding Tag Strings - Wireframe linking toolbar/ Tag String color/ color:2 (red)/ OK - Snapping toolbar/ toggle on snap mode point/ snap to string data - Wireframes/ linking/ Create tag string/ snap (right click) to first set of points wish to connect in modeling/ cancel/ repeat for other set of consequence points by running “Create tag string” command for each run - Loaded data control bar/ right click on “min1st.dm”/ save; check in table editor window to see new field “TAG(N)” has been added to data table including values for these tag strings Conditioning Section Strings - Select string (s) inside design window/ point and string toolbar/ remove crossovers; can be done through: Design/ condition/ Trim crossovers - Select string (s) inside design window/ point and string advanced toolbar/ condition string; can be done through: Design/ condition/ condition string/ max chord length:100, min chord length:0, min angle:45/ OK Adding Zone Attribute Field to String Model (Design Window Tools) - Zone 1 for upper green strings and Zone 2 for lower cyan strings - Point and string advanced toolbar/ Add attribute; or Format/ Add new attribute/ Add Column dialog/ Object:min1st.dm (string), Name: ZONE, Type: Numeric/ OK - Loaded data control bar/ right click on “min1st.dm”/ Data object manager/ Filter: COLOUR=5/ Apply; inside design window right click/ select all strings - Point and string editing advanced toolbar/ Edit attributes/ type in “1” for ‘ZONE’ field/ Enter/ Confirmation dialog/ Yes/ deselect all strings; repeat for other ore strings with Filter: COLOUR=6 and ZONE:2; at end remover filter in Data object manager dialog - Loaded data control bar/ save “min1st.dm”; check the file in Data table tab in data object manager dialog Adding Zone Attribute Field to String Model (EXTRA) - copy string file: Application/ file manipulation process/ copy/ COPY dialog/ files tab/ In:”min1st”, Out:”min2st”/ OK; in retrieval tab can set a criteria for output file like a filter - Edit/ transform/ general/ EXTRA dialog/ files tab/ In:”min1st.dm”, Out:”min2st.dm”/ OK/ Expression translator dialog/ Expression: “ZONE=absent() if(COLOUR==5) ZONE=1 elseif(COLOUR==6) ZONE=2 end”/ Test/ if OK/ Execute - EXTRA, SETVAL, DECODE, COPYNR, GENTRA can be used to add/ edit fields Adding Zone Attribute Field to String Model (Table Editor) - Table Editor Window/ open “min1st.dm”/ add/ column/ Add Column dialog/ name: ZONE, type: numeric, default value: -, implicit: No- different value for each record/ OK - Select field “ZONE(N)”/ Tools/ Run formula/ column: ZONE/ formula wizard button/ Edit Formula dialog/ formula: “if(COLOUR==5,1,if(COLOUR==6,2,#absent))”/ Test/ if OK/ OK Extracting Parts of the String Model - Loaded data control bar/ right click on “minst.dm”/ Data object manager dialog/ Extract from object/ Extract using filter/ filter wizard/ Expression builder dialog/ Expression: “COLOUR=5”/ check validity/ if OK/ OK - Loaded data control bar/ right click on new file “minst-split(colour=5).dm”/ Data object manager dialog/ data table tab/ field “COLOUR” contains only “5” values 7

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

Combining Different String Models - Load all string files wish to combine - Data object manager dialog/ combine objects/ combine data objects dialog/ New object name: “GeolMod”/ select loaded object from left pane and move to right pane in combine list/ object group filed: GROUP/ OK Creating Surface DTM Wireframe - Load “stopo.dm (string)” - Current object toolbar/ Object type : wireframe/ create new object applying default template - Wireframe/ Intractive DTM creation/ Make DTM/ make DTM - general options dialog/ output: current object (“new wireframe” object must be selected in loaded data control bar), general option: uncheck “use boundary string”, DTM plane: plan, attributes: use first point string/ Next/ select DTM points and strings dialog/ tick the checkbox of “stopo.dm”/ finish - DTM creation toolbar/ undo DTM/ Erase wireframe dialog/ OK/ delete confirmation: Yes/ unloading confirmation: No Creating DTM wireframe Using Boundary Limit - Unload all data/ Load “stopo.dm (string)” and “modlim.dm (string limit)” - DTM creation toolbar/ create DTM/ general options dialog/ output: current object, general option: tick “use boundary string” option, DTM plane: plan, attributes: use first point string/ Next/ select DTM points and strings dialog/ tick the checkbox of “stopo.dm”/ Next/ select boundary string dialog/ tick the checkbox of “modlim.dm”/ finish - Loaded data control bar/ right click on “new wireframe”/ save as/ single precision file/ project folder, name: “stopotr” Creating DTM Surface from Grid Points (Smoother & Regular Spaced) - Unload all data/ Load “stopotr/stopopt.dm” - Wireframe/ Grid DTMs/ Grid DTMs dialog/ output: new object (grid points), grid increment: 25, combine elevations: average, object: “stopotr/pt (wireframe)”/ OK; check that the “grid points” is added in loaded data list - DTM creation toolbar/ Create DTM/ make DTM - general options dialog/ output: new object (new DTM), uncheck “use boundary string”/ Next/ select DTM points and strings dialog/ tick the checkbox of “grid points”/ finish; check that “new DTM” is added in loaded data list Creating Closed Volume Using String Linking - Unload all data/ Load “minst.dm” - Current object toolbar/ Object type: wireframe/ create new object applying default templates - Filtering upper ore strings plus tag strings: Format/ filter all objects/ strings/ object expression builder/ expression: “COLOUR=2 OR COLOUR=5”/ OK; check that only upper ore and tag strings are visible - Wireframe linking toolbar/ toggle on “use tags”/ End link/ select (left click) western ending section string/ select (left click) eastern ending section string/ cancel; check that the ending surfaces are created - Wireframe/ linking/ link string/ start from one end of string set and select (left click) all sections in turn to other end of the section set/ cancel - Unloading malformed wireframe: wireframe linking toolbar/ Erase wireframe; there are 3 ways: 1) to erase whole wireframe: wireframe/ erase wireframe; 2) erase by group or by link: toggle on the “Data picker” from erase dialog to select wireframe data part to be erased; wireframe selection method can be set under File/ Setting/ Wireframe/ Selection Creating Closed Wireframe Using Link Multiple by Attribute - This method relies on a numeric Attribute field to guide the automatic string linking order; In this case the Attribute “SECTION” is used; the section strings are numbered 1 to 10 from west to east - Unload all data/ Load “minst.dm”/ set inclined view 8

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

- Filtering lower ore strings plus tag strings: Format/ filter all objects/ strings/ object expression builder/ expression: “COLOUR=2 OR COLOUR=6”/ OK; check that only lower ore and tag strings are visible - Wireframe/ linking/ toggle on “End Link when multiple linking” and “use tags” options/ click and drag inside design window to select all 10 section strings (not tag strings) - Wireframe/ linking/ link multiple by attribute/ Auto Linking dialog/ Attribute to define sequence: “SECTION”/ OK/ number of strings: “10”/ OK - Removing filters: Format/ filter all objects/ erase all filters - save “New Wireframe” in project folder as “mintr.dm” Verifying DTM Wireframe Model - Unload all data/ Load “stopotr.dm (DTM surface)” - Boolean operation toolbar/ verify wireframe/ verify wireframe dialog/ name: stopotr/pt(wireframe), key field: none, uncheck all “store”, “remove”, and “write” options and check (tick) all “check” options including check for open edges, shared edges, and crossovers/ OK; check the reported results; the verified open edges define the outer rim of the DTM and do not indicate any potential problems Verifying Closed Wireframe Model - Unload all data/ Load “mintr.dm (ore wireframe)” - Loaded data control bar/ right click on “mintr.dm”/ Verify/ verify wireframe dialog/ name: minetr/pt, key field: ZONE, uncheck all “store”, “remove”, and “write” options and check (tick) all “check” options including check for open edges, shared edges, and crossovers/ OK; - The “1 Intersections Found” message indicates that wireframe triangle faces intersect. The string objects are generated and added in loaded data list; these objects can be used to indicate areas in the source string objects that may need editing and subsequent regeneration of the wireframe object. The crossover is an overlap between the upper and lower mineralization zone wireframes - this is an unwanted effect and would typically be corrected before using the wireframe for further volume calculations or block modeling commands. Calculating Wireframe Model Volume - Wireframe/ calculate volume/ calculate volume dialog/ Object: “mintr/pt (wireframe)”, object type: closed volume, uncheck “verify” option, density:1/ OK; TRIVOL command (wireframe/ wireframe process/ calculate wireframe volume) also performs the same process - To calculate volume of upper ore body (Zone 1): Wireframe/ wireframe setting/ selection method: select by filter “ZONE=1” >>> wireframe/ calculate volume/ toggle on “select object” button/ select (left click) on the upper ore body object/ object is changed to “mintr/pt - Split (ZONE=1)”/ OK Defining Block Model limits - Prototype volume must contain both ore body and surrounding waste materials; the extents of the volume to be modeled must be adequately covered and model cell sizes must be large enough for the job at hand but not too small i.e. very small blocks = very large file size! - Load “faulttr.dm (wireframe)”, “stopotr.dm (DTM)” and “mintr.dm (ore body closed wireframe)”; display in plan view - Design/ query/ points/ select (left click) a point to the southwest (down-left) of ore body limit; check in output window: this is minimum X,Y coordinates >>> select a point to the northeast (up-right) of ore body limit; this is maximum X,Y coordinates - To find out minimum and maximum Z values display in section view without clipping and do the same using query/ points Creating Block Model Prototype (Table Editor) - Tools/ Datamine products/ Table Editor/ File/ New Table/ Block Model/ Block model parameters dialog/ XYZMORIG: minimum xyz, XYZINC: parent cell dimension along xyz axes, NXYZ: number of parent cells along xyz axes/ OK; save this table as “modprot.dm” in project folder; this file can be edited 9

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

Creating Block Model Prototype (PROTOM) - Modeling toolbar/ define prototype model/ PROTOM dialog/ Out: “modprot”/ parameters tab/ Rotmod: “0” (“1” is for rotated models)/ OK/ answer questions in command toolbar to input data/ Is a Mined out field required? “N”, Are Subcells to be used? “Y”, XYZ (Model Origin): “5880, 4780, -80”, XYZ (Cell Dimension): “10, 10, 10”, XYZ (No of Cells): “29, 47, 30”; now the process is completed and the “modprot” is listed in “Block Models” folder in project files list Creating Waste Block Model Using Surface Wireframe (WIREFILL) - Load “modbound (limit string)”, “stopotr (DTM)” - Modeling toolbar/ Fill wireframe with cells/ WIREFILL dialog/ Files tab/ Proto: “modprot”, Wiretr: “stopotr”, Wirept: “stopopt”, Model: “modwst”/ Fields tab/ ZONE: ZONE (if still there is no ZONE field in wireframe, a new field will be created in output block model)/ Parameters tab/ ZCODE: “0” (the block model with contain numeric field ZONE with default value set to “0” as waste materials), Wiretype: “2” (1: Solid - create cells inside; 2: Surface - create cells below; 3: Surface - create cells above; 4: Surface - create cells to the south; 5: Surface - create cells to the north; 6: Surface - create cells to the west; 7: Surface - create cells to the east), Cell XYZ MIN: “2.5 , 2.5, 2.5” (minimum cell size), Cell XYZ MAX: “10 , 10, 10” (maximum cell size)/ OK; check that “modwst” contains 51,104 records (cells and sub-cells) and the ZONE field values are set to “0” Creating Ore Body Block Model (Closed Wireframe) - Load “modbound (limit string)”, “mintr (ore body wireframe)” - Modeling toolbar/ Fill wireframe with cells/ WIREFILL dialog/ Files tab/ Proto: “modprot”, Wiretr: “mintr”, Wirept: “minpt”, Model: “modore”/ Fields tab/ ZONE: ZONE/ Parameters tab/ ZCODE: leave blank (so the ZONE field and its own values will be transferred from wireframe file to block model), Wiretype: “1” (1: Solid - create cells inside), Cell XYZ MIN: “2.5 , 2.5, 2.5” (minimum cell size), Cell XYZ MAX: “10 , 10, 10” (maximum cell size)/ OK; check that “modore” contains 54,856 records (cells and sub-cells) and the ZONE field values are set to “1” and “2” (upper and lower ore bodies) Visually Checking Ore Body Block Model against Wireframe Model - Load “mintr.dm (ore body wireframe) and “modore.dm (ore block model)”/ display in section view - Format display dialog/ both files/ style tab/ display as: intersection - Design/ Query/ Points/ select (left click) a point within a model cell/ check the information in the output control bar - View/ Customization/ Control Bars/ Data Properties; Data properties control bar also shows list of tabulated cell data Checking Ore Body Block Model Using Summary Statistic (STATS) - Application/ Statistical Processes/ Compute Statistics/ STATS dialog/ Files tab/ In: “modore”, Out: “sumryoremod”/ Fields tab/ F1 to 20: all fields to be summarized statistically like “XC, YINC”, Key1 to 10: to apply key fields, Weight: is to calculate weighted summary by selecting a weighting field/ Retrieval tab/ retrieval criteria can be defined to additionally filter records/ OK; In command toolbar press enter inside “run command field” as many times as number of fields selected to be summarized times to number of key fields until the message “STATS complete” is displayed - A combination of the processes SORT and SELCOP should be used to generate a list of unique values for any numeric flag in order to check that only the expected values are present in block model, especially after optimization or manipulation Combining Waste and Ore Block Models (ADDMOD) - Both block models must have same prototype (can be done by SLIMOD) and block models must be sorted on the field “IJK” (if not, use process MGSORT to sort blocks by setting the field “Key1: IJK”); if block model can’t be displayed in design window, it is not sorted 10

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

- Model/ Manipulation processes/ Add two block models/ ADDMOD dialog/ Files tab/ In1: “modwst” (first block model or host), In2: “modore”, Out: “modwo”/ Parameters tab/ Tolerance: “0.01” (0.01x10m cell size= 0.1m, it means output model will contain cells with dimensions less than 0.1m)/ OK; check that output file “modwo” contains 147,423 records - Load “modwo.dm”/ display in section view/ display as intersection style/ color by “ZONE” field - Design/ Query/ points/ select points in defferent zones to check corresponding data in output bar or in Data properties control bar Optimizing Combined Block Model (PROMOD) - To reduce the number of sub-cells in block model controlled by ZONE field; the optimization will average out numeric field values when adjacent sub-cells are combined; this is not suitable for numeric rock type field like “NLITH” which contain discrete values; if required these averaged numeric field in the optimized block model can be processed after optimization using “EXTRA” to correct this - Models/ Manipulation Processes/ Optimize Block Model/ PROMOD dialog/ Files tab/ In: “modwo”, Out: “modopt”/ Fields tab/ Key1: “ZONE” (adjacent sub-cells within same parent cell and with same Zone value will be combined)/ Parameters tab/ Density: “1”, Overlap: “2”, Optimize: “2” (0: no combination of sub-cells; 1: combination of sub-cells only if they form a complete parent cell and if the values of the key field(s) in each are consistent; 2: combine sub-cells to form a minimum number of subcells), Tol: “0.001”, Accuracy: “0.001”, Print: “0” (no summary list of process)/ OK; check that the output file “modopt” contains 67,278 records - Load both files “modwo” and “modopt” and display in section view, as intersection style and color by ZONE field; zoom in to see where sub-cells have been combined to create new cells; these new cells fall within the limits defined by parent cells - Design/ Query/ Points/ select points within cells to see data

11

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

Grade Estimation

Creating a New Project: File/ New/ Project Wizard dialog/ Name: “GrdEst”, Location: “C:\ Database\ DMTutorial\ Projects\ S3GrdEstTut\ ProjFiles\ MyProj1 folder”, check “Automatically add files . . .”/ Project Settings / tick check boxes for: “Detect new files . . .”, “Detect files added”, “Automatically update project”/ OK/ Next/ Add Files/ browse to: “C:\ . . . \VBOP\ Datamine”, select these 21 files: “2delp1pt.dm, 2delp1tr.dm, depar1.dm, depar2.dm, depar3.dm, depar4.dm, dgmod1.dm, dgmod2.dm, dgmod3.dm, dgmod4.dm, dpanel.dm, dpmod1.dm, dres1.dm, dspar1.dm, dvpar1.dm, dvpar2.dm, dxvs1.dm, dzmod1.dm, ostopo.dm, srflim.dm, srfsamp.dm”/ Open/ again “Add Files”/ browse to: “C:\ . . . \VBUG\ Datamine”, select these 20 files: “3depar1.dm, 3dspar1.dm, caf5so.dm, geres2.dm, geres3.dm, geres4.dm, qqouAU.dm, qqplAU.dm, ubm5cat.dm, ubm5g.dm, ubm5z.dm, bmlim.dm, ubmm.dm, udhz5c.dm, udhz.dm, uepe.dm, ueps.dm, uepv.dm, uorept.dm, uoretr.dm”/ Open/ Next/ Finish >>> File/ Save - Project Setting can be done later using: Tools/ Options/ Project tab/ automatic updating/ Detect changes group/ tick check boxes for all options Displaying Grade Estimation toolbars: - View/ Customization/ Toolbars/ select: Modeling, Mine Design, Point and String Editing (Standard & Advanced), Snapping, View Control, Visualizer - Tools/ Customize/ Commands tab/ categories: “Models”/ drag and drop two commands “Interpolate grades from menu” and “Create wireframe ellipse” from Commands pane (right pane) into Modeling toolbar - View/ Customization State/ Save/ browse to project folder/ Name: “profile”; >>> File/ Save - View/ Customization State/ Load Defining Project Setting for Grade Estimation: - File/ Setting/ Project Setting dialog/ Data Display: symbol size: “0.2mm”/ Design: tick check boxes for “enable automatic redraw”, and “use white fill background” options, background color: “white”/ Mine design: select “Evaluate block model”, clear check boxes for “fast evaluation”, “full cell evaluation”, and “use display legend” (evaluation legend will be defined later) - Format/ Gradient convention/ Gradient In: “degrees”, Direction: “+ve up”/ OK; >>> File/ Save Defining 2D Search Parameters (Table Editor) - Elliptical search method is used; first search ellipse axes lengths and orientations is based on variogram model (i.e. variogram model ranges as ellipse search distances; variogram rotation angles as search ellipse rotation angles); octant search is not used, second search volume with multiplying factor of 2 is used; separate search volume is defined for each grade field for each geological zone; search volume parameters is stored in a single search parameters file and define a unique search reference number for each set - Table Editor Window/ File/ New Table/ from more definitions/ Insert Definition dialog/ select “search volume standard”/ OK - Add/ Record/ set all parameters as following: SDesc: “1” (description)/ SRefnum: “1” (ref. number)/ SMethod: “2” (2=elliptical)/ SDist1,2,3: “240,100,10” (search distance along 1:X, 2:Y, 3:Z axes)/ 12

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

SAngle1,2,3: “-10,0,0” (rotation angles about axes 1,2,3)/ SAxis1,2,3: “3,1,3” (rotation axes: 1:X, 2:Y, 3:Z)/ OctMeth: “2” (use octant search: 1:yes, 2:no)/ MinOct: “2” (number of octants to contain samples if OctMeth: “1”)/ MinPerOct: “1” (required minimum number per octant)/ MaxPerOct: “4” (maximum number per octant)/ MinNum1,2,3: “3,3,1” (minimum number of samples in 1st, 2nd, 3rd search volume)/ MaxNum1,2,3: “20,20,20” (maximum number of samples in 1st, 2nd, 3rd search volume)/ SVolFac2,3: “2,0” (multiplying factor for 2nd, 3rd search volume)/ MaxKey: “0” (maximum number of samples with same key field value); - Table Editor Window/ File/ Save/ Name: “2dspar1.dm” - For 2D search ellipse, assume that the SDist3 (search distance along 3:Z axis) is perpendicular to the plane of 2D sample set and must be set to “1” or greater (#0); SAngle1 and SAxis1 set to axis 3 (Z) are used to define the direction of the major search axis; SAngle2,3 are set to “0” (horizontal search volume) Defining 2D Variogram Parameters (Table Editor) - Define two variogram models, the first is a single structure spherical model and the second is a two structure spherical model, using the variogram model parameters (from VARFIT process) - Table Editor Window/ File/ New table/ Variogram model/ select and delete fields “ST3 to ST4Par4” - Tools/ Definition Editor/ Definition editor dialog/ columns group/ check that the table contains only 19 fields/ Close - Add/ Record (click twice to create two records for two variograms)/ set all parameters as following: - First Record: VDesc: “Au1structure” (description)/ VRefNum: “1” (ref. number)/ VAngle1,2,3: “-10,0,0” (rotation angles about axes 1,2,3)/ VAxis1,2,3: “3,1,3” (rotation axes: 1:X, 2:Y, 3:Z)/ Nugget: “0” (nugget variance:C0 value)/ ST1: “1” (variogram model type for 1st structure including: 1=Spherical, 2=power, 3=exponential, 4=Gaussian, 5=Dewijsian)/ ST1Par1,2,3: “240,80,80” (range in x,y,z directions for 1st structure)/ ST1Par4: “90000” (Spatial variance for 1st structure: C1 value)/ ST2: “0” (variogram model type for 2nd structure)/ ST1Par1,2,3: “0,0,0” (range in x,y,z directions for 2nd structure)/ ST1Par4: “0” (Spatial variance for 2nd structure: C2 value) - Second Record: VDesc: “Au2structure”/ VRefNum: “2” / VAngle1,2,3: “-10,0,0”/ VAxis1,2,3: “3,1,3”/ Nugget: “0”/ ST1: “1”/ ST1Par1,2,3: “40,40,80”/ ST1Par4: “30000”/ ST2: “1”/ ST1Par1,2,3: “240,100,80”/ ST1Par4: “60000” - Table Editor Window/ File/ Save/ Name: “2dvpar1.dm” - For 2D variogram, STPar3 (range in Z direction) is usually set to an arbitrary value greater than “0” - VGRAM process is used to generate experimental semi-variograms for all grade fields and all zones in many directions and then using VARFIT process the best three perpendicular semi-variograms are selected and modeled and saved as veriogram model file Defining 2D Estimation Parameters (Table Editor) - Define 3 sets of estimation parameters for Au grade filed using 3 methods including Nearest Neighbor (NN), Inverse Power Distance (IPD), and Ordinary Kriging (OK); output grade fields are Au-NN, AuIPD, Au-OK; no zonal control is used; search volume is used to control anisotropy; 1st variogram model (VRefNum:1) is used - Table Editor Window/ File/ New Table/ from more definition/ Estimation Parameters-standard/ OK - Add/ Column/ Name: “KRIGVARS”, type: “Numeric”, default value: “1”, Implicit: “No”/ OK - Add/ Record (press 3 times, one record for each set)/ set all parameters as following: 13

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

- First Record: EDesc: “Au-NN”/ Value-In: “AU” (input grade field name)/ Value-Out: “Au_NN” (output grade field name)/ NumSam-F: “-” (output field name to contain number of samples used, optional)/ SVol-F: “-” (output field name to contain search volume number, optional)/ Var-F: “VAR_NN” (output field name to contain estimation variance, optional)/ MinDist-F: “-” (output field name to contain transformed distance to nearest, optional)/ SRefNum: “1” (search volume reference number)/ IMethod: “1” (estimation method: 1=NN, 2=IPD, 3=OK, 4=SK, 5=ST)/ Power: “2” (power of distance for IPD method)/ AddCon: “0” (constant added to distance in IPD method or additive constant for lognormal in ST method)/ VRefNum: “0” (variogram reference number for kriging methods)/ KrigNegW: “0” (Treatment of negative kriging weights: 0=keep & use, 1=ignore negative weighted samples)/ KrigVars: “0” (Treatment of negative kriging variance >sill: 0=keep KV>sill, 1=set KV equal to sill; only applicable if LOG=0) - Second Record: EDesc: “Au-IPD”/ Value-In: “AU”/ Value-Out: “Au_IPD”/ NumSam-F: “-”/ SVol-F: “-”/ Var-F: “VAR_IPD”/ MinDist-F: “-”/ SRefNum: “1”/ IMethod: “2”/ Power: “2”/ AddCon: “0”/ VRefNum: “0”/ KrigNegW: “0”/ KrigVars: “0” - Third Record: EDesc: “Au-OK”/ Value-In: “AU”/ Value-Out: “Au_OK”/ NumSam-F: “-”/ SVol-F: “-”/ Var-F: “VAR_OK”/ MinDist-F: “-”/ SRefNum: “1”/ IMethod: “3”/ Power: “2”/ AddCon: “0”/ VRefNum: “1”/ KrigNegW: “0”/ KrigVars: “1” - Table Editor Window/ File/ Save/ Name: “2depar1.dm” Defining 3D Search Parameters (ESTIMATE) - Elliptical search is used; first search ellipse axes lengths and orientations is based on variogram model (i.e. variogram model ranges as ellipse search distances; variogram rotation angles as search ellipse rotation angles); no octant search is used; second search volume with a multiplying factor 2 is used; separate search volume is defined for each grade field for each zone; - Models/ Interpolation processes/ Interpolate grades from menu/ ESTIMATE dialog/ Next/ Search volume tab/ Index group/ Add/ search volume list/ select “search volume 1”/ Shape sub-tab/ shape: “ellipsoidal”, X,Y,Z axis: “150,90,30”, Rotation angle first,second,third: “123,42,0”, Axis for rotation first,second,third: “Z,X,Z”/ Category sub-tab/ primary search volume: min “5”, max “20”, second search volume: expansion factor “2”, min “5”, max “20”, third search volume: expansion factor “0” (not used)/ Decluster sub-tab/ uncheck “use octant” - Repeat for two more search volumes with following parameters: - “Search volume 2”: X,Y,Z axis: “120,115,15”, Rotation angle first,second,third: “45,40,0”, Axis for rotation first,second,third: “Z,X,Z”/ Category sub-tab/ primary search volume: min “1”, max “20”, second search volume: expansion factor “2”, min “1”, max “20”, third search volume: expansion factor “0” (not used)/ Decluster sub-tab/ uncheck “use octant” - “Search volume 3”: X,Y,Z axis: “60,50,15”, Rotation angle first,second,third: “123,42,0”, Axis for rotation first,second,third: “Z,X,Z”/ Category sub-tab/ primary search volume: min “1”, max “20”, second search volume: expansion factor “2”, min “1”, max “20”, third search volume: expansion factor “0” (not used)/ Decluster sub-tab/ uncheck “use octant” - Index group/ Export/ Name: “3dspar1”/ OK - The SDIST1, SDIST2 and SDIST3 parameters need to be set; the search ellipsoid typically has a dip direction and a dip defined by rotations about two axes; First rotation SANGLE1 about SAXIS1 (typically 3=Z), Second rotation SANGLE2 about SAXIS2 (typically 1=X), a 3D search ellipsoid may require a third rotation SANGLE3 about another axis. 14

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

- Define axes and rotations as dip direction, dip, cross dip: use SDIST1, SANGLE1 about SAXIS1 (=3) to define the Dip Direction/Plunge axis; use SDIST2, SANGLE2 about SAXIS2 (=2) to define the Strike axis; if required, then use SDIST3, SANGLE3 about SAXIS3 to define the rotation for a more complex orientation Defining 3D Variogram Parameters (ESTIMATE) - 12 set of variogram model parameters (one for each grade fields Cu, Au, Ag, Co and each zones 1, 2, 3) have been output from VARFIT with 1 or 2 structure spherical models (models are based on experimental semi-variograms generated from VGRAM process using sample/drillhole data); all are omni-directional (same in all direction); record 5 (Cu zone 2) contains a set of dummy parameters; parameters include Variogram axes and angles of rotation, ranges, Nugget (C0), Sill, and Spatial Variance (=Sill - Nugget) - Models/ Interpolation processes/ Interpolate grades from menu/ ESTIMATE dialog/ Next (twice)/ Variogram model tab/ Index group/ Import/ browse to “uepv”/ 12 models are listed now/ check all models individually in all sub-tab/ close the dialog Defining 3D Estimation Parameters (ESTIMATE) - 2 sets of estimation parameters for Cu and Au in Zone 1; search volume 1 is used; ordinary kriging method is used; variogram 1 for Cu and 2 for Au are used - Parameters in 2 sets include: EDesc: “est.para.1, est.para.2”/ ERefNum: “1, 2”/ ValueIn: “Cu, Au”/ ValuOut: “Cu, Au”/ SRefNum: “1, 1”/ Zone: “1, 1”/ NumSam: “NCU, NAU”/ SVol: “SCU, SAU”/ VarF: “VCU, VAU”/ IMethod: “3, 3”/ Aniso: “1, 1”/ VRefNum: “1, 2”/ Tol: “0.01, 0.01”/ KrigNeg: “0, 0”/ KrigVar: “1, 1” - Models/ Interpolation processes/ Interpolate grades from menu/ ESTIMATE dialog/ Input tab/ Input model: “ubmz”, Sample file: “udhz”, coordinate fields: “x,y,z”, Zone1: “ZONE”, uncheck “sample key field” option/ Output sub-tab/ clear the checkbox of “use default”, search volume file: “ueps”, estimation parameters: “3depar1”, variogram model file: “uepv”/ Next/ search volume tab/ check that 3 search volumes are listed/ Next/ variogram model tab/ check that 12 models are listed/ Next/ Estimation type tab/ Index group/ Add/ select “Estimation Par.1”/ Attributes sub-tab/ method: “O.Kriging”, Data field: “CU, CU”, model fields: “NCU, VCU, SCU”, search volume: “1”, variogram model: “1” (Cu, Zone 1), Zone: “1”/ Option sub-tab/ uncheck “negative kriging weights” and “macro kriging group” options/ Indicator estimation sub-tab/ leave all options grayed out/ Repeat all for Est.par.2 for Au field/ Index group/ Export/ name: “3depar1”/OK/ Cancel Checking Search Parameters Using a Wireframe Ellipsoid (ELLIPSE) - To check orientation and distances of the axes and sample coverage of search volume - Models/ Interpolation Processes/ Create Wireframe ellipse/ ELLIPSE dialog/ Files tab/ Input files: “2dspar1”, output wiretr: “2delp1tr”, wirept: “2delp1pt”/ Parameters tab/ SRefNum: “1” (set no. 1), x,y,z centre: “6250,5350,280.1” (optional point inside sample data)/ OK - Load “srfsamp.dm” and “2delp1tr”/ view in plan and section views/ color the sample (point) data by field Au (0.2~1.5g/t)/ define symbol as fixed: “filled circle”, “2.0mm”/ Apply/ display ellipse as intersection/ OK; change “x,y,z centre” parameters in ELLIPSE process to place the wireframe in different location - Check orientation of major axis of ellipse and orientation of high value zones; number of samples falling within ellipse, min and max samples to be met in search ellipse; potential octant search parameters Optimizing Estimation parameters, Cross Validation (XVALID) - To compare different variogram and search volumes; compare a single vs. a double spherical model; non-octant vs. octant search - It removes each sample point in turn from data file and estimates its value from remaining data; a table of actual and estimated values is created; statistic analysis runs comparing the actual and estimates; 15

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

estimation parameters can then be changed and process rerun to see if it improves; several run is required to establish the best set of parameters - Design Window/ Application/ variogram/ cross validation/ XVALID dialog/ files tab/ In: “srfsamp”, SrcParm: “2dspar1”, EstParm: “2depar1”, VModParm: “2dvpar1”, XVStats: “2dxvs1”, leave other two output blank/ fields tab/ x,y,z: “xpt,ypt,zpt”, leave other blank/ parameters tab/ SMinFac: “0.0001”, print: “0”/ OK - Output Window/ record the key parameters of input (estimation, search and variogram parameters) and output data in a table including: no. of samples, mean difference (% of actual), mean absolute difference, correlation coefficient, kriging variance (mean of squared difference), kriging variance (ratio), regression equation slope - Output Window/ displayed cross validation menu options/ there are 9 options (0~8)/ type in “2” in command toolbar (edit estimation parameters)/ Enter/ Screen Window/ datamine editor dialog (AED)/ use arrow keys to move to record “3” and “VRefNum” field/ type in “2” (variogram model is changed)/ Enter/ in command toolbar type in “8” (re-run validation)/ Enter/ the results are saved in “2dxvs1” - The following guidelines should be used when using Cross-Validation statistics to compare different runs. The statistics are listed in order of decreasing importance: ・ means of the Estimates and Actuals should ideally be equal ・ mean difference (as % of actual): aim is to make the statistic as close as possible to “0”. It should be < 5% and hopefully < 2%. ・ kriging variance ratio: it should lie in the range between 0.8 and 1.2, and be as close as possible to 1. ・ correlation coefficient: always lies between “-1” and “+1” (a value of “+1” shows perfect positive correlation). Aim to make the correlation coefficient as large as possible. ・ mean absolute difference: aim to make it as close as possible to “0” ・ regression line slope (constant b): slope of the line should ideally be equal to “1” ・ A change in one of the input parameters (variogram, estimation, or search parameters) will often result in some of the statistics improving and others getting worse. The end result is likely to be a compromise. - Command toolbar/ type in “0” (exit cross validation)/ Enter Estimation Using GRADE - GRADE process is used for single grade field, single search volume with NN, IPD or OK methods - To estimate Au grades into 2D block model using IPD method; no zonal control; no octant - Modeling/ Basic grade interpolation/ GRADE dialog/ files tab/ Proto: “2dpmod1”, In: “srfsamp”, Model: “2dgmod1”/ fields tab/ x,y,z: “xpt,ypt,zpt, Value: “AU”, leave the rest unchecked/ parameters tab/ SDist1,2,3: “240,100,10”, SAngle1,2,3: “-10,0,0”, SAxis1,2,3: “3,1,3”, Min: “1”, Max: “20”, IMethod: “2”, Power: “2”, x,y,zPoints: “3,3,3” (number of discretisation points in the x,y,z direction)/ OK; in command control bar check that process is complete and 780 records in “2dgmod1” Estimation Using ESTIMATE - ESTIMATE process is used for multiple grade fields, estimation methods (NN, IPD, OK, SK, IK), dynamic search volume with advanced estimation options - To estimate Au grades into 2D block model using IPD, ID, and OK methods; search volume 1 and variogram model 2 and zonal control “Anom field” are used; no octant - Models/ Interpolation Processes/ Interpolate grade from menu/ ESTIMATE dialog/ Input model: “2dzmod1”, Sample file: “srfsamp”, coordinate fields x,y,z: “xpt,ypt,zpt”, Zone1: “Anom” (Zone field need to be present in both model and sample files for zonal control)/ Output sub-tab/ Grade model: “2dgmod2”, clear “use default” checkbox, search volume: “2dspar1”, estimation para.:”2depar1”, var. model: “2dvpar1”/ Next/ search volume tab/ summary sub-tab/ check single set of parameters/ Next/ variogram model tab/ summary sub-tab/ check two sets “AU1st, AU2st”/ Next/ estimation type tab/ summary sub-tab/ check that 6 sets are listed (3 methods, 2 zones), AU-OK use 2nd variogram model (VRefNum: “2”)/ Next/ control tab/ parameters sub-tab/ parent cell estimation: “seb-cells estimation”, cell discretisation: “number of points”, number of points in x,y,z: “3,3,3”/ Next/ Preview tab/ summary sub-tab/ check files, fields, parameters groups/ Run; check the output model in project files list 16

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

OK and SK Estimation Using ESTIMATE - To estimate Au grades into 2D block model using OK and SK methods; search volume 1 and variogram model 2 and zonal control “Anom field” are used; LocalMNP: “2” (local mean is calculated automatically, only for SK method); no octant; - For Ordinary Kriging (OK) a weight is calculated for each sample, and the sum of these weights is 1; for Simple Kriging (SK) a weight Wi is calculated for each sample and a weight of (1-ΣWi) is assigned to the mean grade. Simple Kriging is not as responsive as Ordinary Kriging to local trends in the data, since it depends partially on the mean grade, which is assumed to be known, and constant throughout the area; the local mean value required by Simple Kriging can be defined in one of the following two ways: 1) The local mean is obtained from a 'local mean' field in the input block model; set estimation parameter LOCALMNP: “1”; define the name of the local mean field in the block model using the estimation parameter LOCALM_F 2) The local mean is calculated as the arithmetic mean of all samples lying in the search volume; set estimation parameter LOCALMNP: “2” - Use Simple Kriging when: requiring the local mean to play a role in the grade estimate, wanting to reduce the effects of clustered data, wanting to produce a result that is "smoother" and more aesthetically pleasing - Models/ Interpolation Processes/ Interpolate grade from menu/ ESTIMATE dialog/ Input model: “2dzmod1”, Sample file: “srfsamp”, coordinate fields x,y,z: “xpt,ypt,zpt”, Zone1: “Anom”/ Output subtab/ Grade model: “2dgmod3”, clear “use default” checkbox, search volume: “2dspar1”, estimation para.:”2depar2”, var. model: “2dvpar1”/ Next/ search volume tab/ summary sub-tab/ check parameters/ Next/ variogram model tab/ summary sub-tab/ check two sets “AU1, AU2”/ Next/ estimation type tab/ check that 6 sets are listed in Index pane/ Add/ select “Est. para. 7”/ method: “simple kriging”, uncheck “indicator estimation”, sample grade: “AU”, model grade: “AU-SK”, search volume: “seach vol.1”, variogram model: “AU2-structure”, Anom: “1”/ Option sub-tab/ uncheck “reset negative weights to zero” option, local mean value: “ calculate mean”/ Indicator Estimation sub-tab/ leave all options grayed out/ repeat all for new “Est. para. 8” for zone “Anome:2”/ Export/ name: “2depar3”/ OK/ Next/ control tab/ parameters sub-tab/ parent cell estimation: “seb-cells estimation”, cell discretisation: “number of points”, number of points in x,y,z: “3,3,3”/ Next/ Preview tab/ check files, fields, parameters groups/ Run; check the output model in project files list Indicator Estimation Using ESTIMATE - To estimate Au grades into 2D block model using IK method; search volume 1 and variogram model 1,2 and zonal control “Anom field: 1,2” are used; median indicator values: AU:267 (for zone 1) and AU:752 (for zone 2); cutoff grades for zone 1: AU=104, 266, 431, 570 (these are the grades at the 25%, 50%, 75% and 95% quantiles); cutoff grades for zone 2: AU=652, 746, 874, 1083 (these are the grades at the 25%, 50%, 75% and 95% quantiles); this will be done by defining a total of eight Indicator Kriging runs, one for each of the four cutoffs (listed above) for each of the zones; these estimation parameters will then be saved to a new estimation parameter file “2depar4” - Indicator Estimation: is a non parametric estimation method and so does not depend on the statistical distribution of the data as in standard (i.e. non-indicator estimation) Ordinary and Simple Kriging methods. The estimation method used with indicator estimation is typically ordinary kriging although other estimation methods can also be used e.g. inverse power distance, simple kriging. - Advantages: in general the indicator variograms are better behaved i.e. smoother; outliers do not cause a problem; the sill of the variogram can be calculated theoretically; gives recovered grade and tonnes by cutoff; non parametric i.e. it does not depend on the grade distribution (histogram) of the samples - Disadvantages: it can take longer to set up as in theory you need to calculate a variogram for each cutoff, although median IK can be used to avoid this; indicator variograms can be affected by clustering of samples; the recovered grades and tonnes cannot be related to a specific size of SMU; there can be order relation problems; there is no theoretical kriged variance; the Indicator Estimation method cannot be combined with non indicator estimation methods in the Datamine estimation parameter file; only one 17

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

set of indicators (per Zonal Control zone) can be defined in a set of estimation parameters in the Datamine estimation parameter file - Indicator Kriging is typically used for: automatically defining boundaries between different zones in a block model e.g. low/high grade ore zones or rock types; estimating grades for complex (and inseparable) mixed data populations; estimating grades for highly skewed grade distributions; as an alternative to log normal kriging - ESTIMATE dialog/ Input model: “2dzmod1”, sample file: “srfsamp”, Zone1: “Anom”/ output sub-tab/ grade model: “2dgmod4”, search: “2dspar1”, estimation: “2depar4”, variogram: “2dvpar2”/ search volumes tab/ there is a single sets of parameters (when using multiple indicator kriging, a single search volume must be used for the set of multiple indicators)/ variogram model tab/ there are two sets, one for each zone: VRefNum: “1”-“2”, VAngle1,2,3: “0,0,0”-“0,0,0”, nugget: “0.1”-“0.1”, St1Par1,2,3,4: “85,85,85,0.08”-“42.7,42.7,42.7,0.09”, St2Par1,2,3,4: “162,162,162,0.074”-“140,140,140,0.06”/ estimation type tab/ index group/ reset/ yes/ remove all parameters/ add/ select “estim.para.1”/ method: “OK”, check “indicator estimation” option, grade: “AU”, model grade: “same as sample”, search volume: “1”, variogram: “1”, Anom: “1”/ option sub-tab/ uncheck “reset negative w to 0” option/ indicator estimation sub-tab/ mean grade method: “average from sample file, median value for samples”, order relation correction: “average of downwards and upwards”, upper cutoff: “104”/ repeat all from adding new “Estima Param” in index group for all other cutoffs in Anom1 and Anom2 separately (total of 8 IK runs for Au grade), use variogram “2” for Anom “2”/ Export/ name: “2depar4”/ Run - Selecting cutoffs for multiple indicator kriging: use the maximum quartile (25%, 50%, 75%) and the maximum 95% quantile grade values; use the maximum decile (10%, 20%, ... 90%) and the maximum 95% quantile grade values; base cutoffs on values related to mineralization zones or grade control categories; the 95% quantile (or another more suitable top end quantile) is typically used, in addition to the quartiles or deciles, to cater for the 'upper tails' i.e. the high grade values in high positively skewed data distributions. - Statistical parameters: 1) Median is middle value in a ascending sorted list (50% value); if there is an even number of values, so there is no single middle value then the mean of two middle values is defined as median; 2) Arithmetic mean (average): adding the numbers and dividing the sum by the number of numbers in the list; 3) Geometric mean: multiplying all values in a list and taking root of that product equal to the number of values; 4) Mode: most frequently occurring value in a list Estimation Using Drillhole Data and ESTIMATE Process (3D) - Use Drillhole sample data when: estimating grades into a 3D block model; estimating grades into a pseudo 3D block model i.e. Z coordinate has been set to a constant reference elevation e.g. flat dipping tabular ore bodies; using sample length as a weighting factor for estimation - The block model cells are colored according to the three separate mineralization zones (cyan: zone1, green: zone2, red: zone3); the fold axis of the ore body plunges at 35 degrees towards the east, the tabular to massive shaped limbs have a dip of 40 degrees, a maximum down dip length of 240m and a thickness (perpendicular to the bottom contact) of 5~45m; the drillholes are set in fans which are parallel with the dip direction of each limb and are spaced 50m apart. - To estimate a variety of grades (and Density) into a 3D block model using drillhole sample data and the following parameters: input block model is 5m regular celled (no sub-cells) and zone flagged; sample data file is drillholes; input Grade fields include AU(g/t), CU(%), AG(g/t), CO(%); output Grade fields are same as input field names; estimation methods are Inverse Power Distance, Ordinary Kriging; three search Volumes, one for each of the three mineralization zones “ueps”; 12 variogram models, one for each of the 4 grades for each of the three mineralization zones “uepv”; zonal control (field ZONE:1,2,3); set negative kriging weights to zero - ESTIMATE dialog/ files tab/ input model: “ubm5z”, sample file: “udhz”, Zone1: “ZONE”/ output subtab/ grade model: “3dbm5g”, search volume file: “ueps”, estimation parameter file: “uepe”, variogram model file: “uepv”/ Next/ search volume tab/ there are 3 sets, one for each zone (based on the orientation of the axes and the ranges of the Au grade variograms)/ Next/ variogram model tab/ there are 12 sets, one for each grade and each zone (each model consists of two spherical structures, models 1-3 and 5-8 are anisotropic, models 4 and 9-12 are isotropic)/ estimation type tab/ there are 15 sets/ check all of them 18

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

individually, additional output model fields NCU, VCU and SCU are used to record the number of samples, estimation variance and search volume respectively (the other grade fields have corresponding field names), resetting negative kriging weights to zero prevents the calculation of negative grade estimates/ Next/ Run; check the output model in project file list Panel Estimation (PANELEST) - Use PANELEST to estimate grades when estimating: panel grades directly without first creating a block model; a single grade field at a time; into 2D or 3D panels; using the estimation method NN, IPD, OK, IK or Sichel's T estimation - Panel: 2D or 3D open or closed strings can be used to define panels; panel strings must be coplanar and orthogonal to the X, Y or Z axis; panels can also be defined by sets of 2D or 3D discretisation points; drillholes or suitable point data can be used as Sample Data files. - Parameters: input grade field: AU; estimation method: Ordinary Kriging; search volume: all samples within the panel are used for the estimate; variogram model: variogram model 2 (VREFNUM=2); vertical thickness for volume calculation: 10m (DIST=5, DIST=5); the panel string is a closed area of 1.248 km2 - Models/ Interpolation processes/ estimate grade of panels/ PANELEST dialog/ files tab/ In: “srfsamp”, VModParm: “2dvpar1”, Perim: “srflim”, Out: “2dpanel”/ fields tab/ x,y,z: “xpt,ypt,zpt”, Value: “AU”, Panel: “PValue” (panel identifier)/ parameters tab/ Min: “1”, Max: “480” (greater than total number of samples), Inside: “1” (sample lie inside panel), x,y,zDSpace: “10,10,0” (distance between discretisation points, typically set to half the sample spacing), MinDisc: “50” (minimum number of discretisation points), DPlus,DMinus: “5,5” (panel projection distance in ±direction of the perpendicular axis), IMethod: “3” (OK), VModNum: “1” (variogram model reference number)/ OK; check that the file “2dpanel” is created with 1 record Visual Validation of the Block Model (comparing model cell grades to the drillhole grades) - To check that the wireframe or string boundary is filled with block cells; block cells are zone flagged; grade estimates in cells are according to grades in drillholes - Load “udhz5c” (5m composite drillhole) and “ubm5g” (5m celled block) in design window/ display in WE section view with ±5m clipping distances/ display BHID labels in end of holes/ color drillhole by “AU” field/ display block model as intersection/ color block model by “AU” field (same as drillhole); check the grades in block model cells and drillhole samples - Design/ query/ points/ select (left click) on a model cell/ check the information in output control bar/ right click on a drillhole segment near that cell to compare the data in output control bar/ repeat for more points Statistical Validation of the Block Model Cell Grades (STATS) - To check presence of missing grade values; summary statistics for each grade field per zone; for regular celled block model; for composited or declustered sample data - Application/ statistical processes/ compute statistics/ STATS dialog/ files tab/ In: “ubm5g”, out: “???” (optional name)/ fields tab/ F1,2,3,4,5: “Cu,Ag,Au,Co,Density”/ retrieval tab/ click new button/ type in: “ZONE=1”/ OK/ press Enter 5 times for 5 input fields; check summary in command control bar or in output file - STATS dialog/ repeat all for Input file “udhz5c” (composite drillhole) with same fields and retrieval definition; check summary in command control bar or in output file - Compare the mean value and shape of the distributions of the model cells and drillhole samples (better to generate histograms by CHART) Graphical validation (Q-Q Plots) - QQ plot is to check for bias in the estimates; it is a plot of the quantiles (of a particular grade field) of one data set against the quantiles of another data set; if the two sets come from a population with the same distribution, the points should fall approximately along the 45 degree reference line. A quantile is 19

DataMine Studio v.3 Tutorial – By: Seyed Masoud Ahmadi Rouein, Islamic Republic of Iran

defined as the fraction or percent of the number of data points below the given value; for example, the 20% quantile is the point at which 20% percent of the data fall below and 80% fall above that value. - PP plot is a cumulative probability plot of two data sets from same distribution - Design Window/ Command toolbar/ type in “ppqqplot”/ Enter/ PPQQPLOT dialog/ files tab/ In1: “udhz5c”, In2: “ubm5g”, QQout: “qqAu”, QQplot: “qqplAu”/ fields tab/ Value1: “AU”, Value2: “AU”, Key: “ZONE”/ parameters tab/ PlotType: “1” (scatter plot), Diagonal: “1” (include diagonal line, 45o line), Display: “1” (to display plot file)/ OK - Graphic Window/ Y axis: model cells, X axis: drillhole quantiles, [+]: zone1, [×]: zone2, [^]: zone3/ points should not deviate much from 1:1 line; deviation away indicates bias in distribution/estimation - Project files control bar/ plot files folder/ right click on “qqplAu”/ display; file is displayed in graphic window - Design Window/ Format/ view plots/ superimpose plots/ select “qqplAu”/ zoom all data Informal Classification of Block Model into Confidence Categories (Using Kriging Variance) - To calculate a category field in the block model using EXTRA, based on a set of kriging variance ranges for the Au grade estimates; kriging variance field: VAU; category ranges: CAT=1 (VAU≤3), CAT=2 (3