Introductory Tr aini ng C ours e Manual
Table of Contents Introduction
1
Objectives
1
Prerequisites
1
Acronyms and Abbreviations
1
Using This Training Manual
1
More information
2
Datamine Background
3
Software
3
Training
4
Consulting
4
Chapter 1
5
Getting Started
5
Principles
5
The Project File
5
Extended precision versus Single precision files
6
Files versus Objects
7
Working with Data Objects
7
Loading data
9
Saving changes to objects
9
Working with files in a project Summary Exercises
9 10 10
Exercise 1: Create a new project
10
Exercise 2: Add existing Datamine files to a project
11
Exercise 3: Load existing external Datamine files into memory
11
Exercise 4: Load text files and CAD files to a project
12
Exercise 5: Remove files from a project
12
Exercise 6: Save a project
12
Additional Exercises
12
Additional Exercise 1: Save a project with loaded objects
13
Additional Exercise 2: Automatically detect files added to or removed from the project folder
13
Additional Exercise 3: Rename file in a project
13
Additional Exercise 4: Describe the purpose of a project file
13
Table of Contents
i
Additional Exercise 5: Describe differences between loaded objects and files
13
Additional Exercise 6: Questions about loaded objects and files
13
Chapter 2
14
The Studio RM Interface
14
Principles
14
Windows
15
Project menu
16
Ribbons
17
Quick Access toolbar
20
Current Object toolbar
21
Navigation toolbar
22
Command toolbar
22
Commands and Processes
23
Control bars
24
Command control bar
27
Status Bar
28
Context menus
28
Help menu
29
Exercises
29
Exercise 1: Setup the Quick Access toolbar
29
Exercise 2: Working with windows and control bars
29
Additional Exercises
30
Additional Exercise 1: Setup a custom Quick Access toolbar
30
Additional Exercise 2: Change the look and feel of Studio RM
30
Additional Exercise 3: Working with the Sheets control bar
30
Additional Exercise 4: Working with the Holes, Loaded Data and Compositor control bars
30
Additional Exercise 5: Questions about commands and processes
31
Additional Exercise 6: Questions about the Studio RM interface
31
Chapter 3
32
Data Management
32
Principles
32
Data Types
32
Standard Datamine file types
34
Data Capture
34
Exporting Data
40
Table of Contents
ii
Creating and editing Datamine files using the Datamine Table Editor
40
Exercises
41
Exercise 1: Importing Topography Contours from a CAD File
41
Exercise 2: Re-importing CAD data
43
Additional Exercises
44
Additional Exercise 1: Questions about data management in Studio RM
44
Chapter 4
45
Data Visualization
45
Principles
45
Viewing Data Objects
45
3D Visualization Window
47
Understanding 3D Data
47
The 3D Environment
48
Navigational Controls SectionWhat vs. View is the– Difference?
48 52
Changing the View of an Unlocked Section
53
A Closer Look at the View Ribbon
54
Creating 3D Grids
56
Displaying block model data in 3D
58
Block Models Overview
59
Viewing Options
59
Block Model Sequencing Animations
63
Working with Section Widgets
63
Working with Section Definition Files
64
Exercises
65
Exercise 1: Loading Data into the 3D Window
65
Exercise 2: Adding and Configuring 3D Hull Grids
66
Exercise 3: Creating a Grid of finite size
69
Exercise 4: Modifying Sections with Widgets
70
Exercise 5: Adding a Second Section to your Scene
73
Exercise 6: Loading an existing Section Definition File
76
Exercise 7: Creating a Section Definition File using the 3D window
80
Additional Exercises Additional Exercise 1: Questions relating to data visualization in Studio RM
85 85
Chapter 5
86
Table of Contents
iii
Data Formatting Principles
86
86
The Visual Hierarchy
86
Objects
87
Display templates in the 3D window
87
Overlays and Display Templates in the Plots window
88
Legends
89
Displaying different data types using legends Format Display Dialog
90 90
Exercises
91
Exercise 1: Creating a Unique Values Legend for Rock Type Codes
91
Exercise 2: Editing the new NLITH Legend colours
93
Exercise 3: Creating a view template in the 3D window
94
Additional Exercises Additional Exercise 1: Modifying a Legend to Use Fill Patterns
95 95
Chapter 6
96
Data Filtering
96
Principles
96
Interactive Filtering
96
Numeric Filters
97
Alphanumeric Filters:
98
File Based Filtering Exercises
98 102
Exercise 1: PICREC and JOIN and EXTRA to filter drillholes
102
Exercise 2: EXTRA, PICREC, JOIN and COPY to update wireframes with information
103
Additional Exercises Additional Exercise 1: Use SUBJOI to create a drillhole file with specific holes only
105 105
Chapter 7
106
Working with Drillholes
106
Principles
106
Required data for creating drillholes in Studio RM
106
An Overview of Desurveying
107
What are 'Static' Drillholes?
107
What are 'Dynamic' Drillholes?
109
Subdividing Samples
110
Table of Contents
iv
Dynamic or static holes?
110
What difference does it make?
111
Validating drillhole data
111
Compositing drillhole data
112
Creating Isoshells
113
Exercises
116
Exercise 1: Create static drillholes
116
Exercise 2: Composite down drillholes Exercise 3: Create a dynamic drillhole data object
118 120
Exercise 4: Create categorical Isoshells from static drillhole data
126
Specifying Estimation Parameters
129
Additional Exercises
130
Additional Exercise 1: Create continuous isoshells for AU grades from drillhole data
130
Additional Exercise 2: Create a static drillhole file from a dynamic drillhole object
131
Additional Exercise 3: Create planned drillholes on a regularly spaced grid
132
Chapter 8
139
Working with points and strings
139
Principles
139
String Characteristics
139
Point Characteristics
141
String Manipulation Tools
144
Exercises
150
Exercise 1: Creating New Strings and Editing Points
150
Exercise 2: Saving Strings to a File and Erasing Strings
155
Exercise 3: Opening and Closing Strings
157
Exercise 4: Undo Last Edit and Combining Strings
158
Exercise 5: Extending, Reversing and Connecting Strings
160
Exercise 6: Clipping Strings and Generating Outlines
161
Exercise 7: Copying, Moving, Expanding, Rotating and Mirroring Strings
166
Exercise 8: Projecting Strings
172
Exercise 9: Translating Strings
175
Exercise 10: Extending to a String
178
Exercise 11: Conditioning Strings
180
Exercise 12: Trimming Crossovers and Corners
182
Exercise 13: Smoothing Strings and Reducing String Points
183
Exercise 14: Breaking Strings with Strings
185
Table of Contents
v
Chapter 9 Wireframe Constructing Modeling Surfaces –
187 187
Principles
187
Definition of a wireframe
187
Using wireframes to accomplish mining objectives
188
Displaying wireframe objects
188
Saving wireframe objects to a file
188
DTM surfaces
189
Creating DTM surfaces in Studio RM
189
General Options
190
Select DTM Points and Strings
192
Select Boundary Strings
192
Edit Attributes
193
Editing wireframe triangles
193
Exercises
194
Exercise 1: Creating the DTM without Limits
194
Exercise 2: Creating the DTM with Limits
195
Exercise 3: Saving the New Wireframe
196
Exercise 4: Displaying Wireframe Slices
196
Exercise 5: Generating Strings from Wireframe Slices
197
Additional Exercises
198
Additional Exercise 1: Load the topography contour strings and create the DTM surface.
198
Additional Exercise 2: Digitize an outer limit and recreate the DTM surface
199
Additional Exercise 3: Write the DTM Object to wireframe files.
199
Additional Exercise 4: Wireframe Intersection
199
Chapter 10 WireframeConstructing Modeling – Closed Volumes
Principles
200 200
200
Linking Methods
200
Tag Strings
202
Creating Wireframe Links
202
Erasing Wireframe Links
202
Terminology
203
Exercises Exercise 1: Creating a Basic 3D Volume
Table of Contents
203 203
vi
Exercise 2: Linking a Perimeter to an Open String
207
Exercise 3: Creating a Wireframe with Multiple Splits
208
Exercise 4: Creating Tag Strings
211
Exercise 5: Creating the upper mineralized zone wireframe using tag strings
213
Exercise 6: Creating the lower mineralized zone wireframe.
216
Additional Exercises
217
Additional Exercise 1: Wireframing towards an open string.
217
Additional Exercise 2: Create Bifurcated Wireframes
217
Chapter 11 Wireframe Manipulating Modeling Wireframes –
218 218
Principles
218
When should I use wireframe manipulation?
218
How do I select wireframes for manipulation or editing?
218
Why do I need to verify my wireframes?
219
Exercises
221
Exercise 1: Verifying Wireframe Objects
221
Exercise 2: Calculating the Volume of a Wireframe Object
223
Exercise 3: Using the Boolean operations: Extract Separate
224
Exercise 4: Using the Boolean operations: Intersections
224
Additional Exercises Additional Exercise 1: PlaneMultiple Operations Sections – Additional Exercise 2: Extract wireframes and Add wireframes
225 225 226
Chapter 12
229
Introduction to Macros and Scripts
229
Principles
229
The use of macros in Studio RM
229
The use of scripts in Studio RM
229
The difference between scripts and macros
230
Recording macros in Studio RM Editing Studio RM macros
230 231
Exercises
232
Exercise 1: Recording a macro to calculate statistics on a field
232
Exercise 2: Editing and Replaying the Macro
233
Exercise 3: User Interaction with a Macro
235
Additional Exercises
Table of Contents
236
vii
Additional Exercise 1: Record the same actions as Exercise 1 in a script.
236
Chapter 13
237
Block Modeling
237
Principles
237
Wizards used for block modelling
238
Batch processes used for block modelling
238
Controlling cell sizes in the model
238
What is subcelling and why is it necessary?
238
How to start creating a model
239
Viewing a prototype model or block in the 3D window
241
How to fill ore zones with model cells
242
Other ways to create a block model
244
How many subcells should I used?
245
Seam filling
245
The Resol parameter
246
What if I don’t want any subcelling?
246
Combining block models
247
Exercises
247
Exercise 1: Determining suitable prototype model parameters
248
Exercise 2: Defining the Model Prototype - Method 2
250
Exercise 4: Building the Ore Model
250
Exercise 5: Viewing the Model
251
Exercise 6: Creating a Waste Model
254
Exercise 7: Adding the Two Models Together
255
Exercise 8: Optimizing the Model
256
Exercise 9: Using the Fill Wireframe wizard to create block model
257
Exercise 10: Reblock a model to new cell sizes
257
Chapter 14
258
Grade Estimation
258
Principles
258
Background
258
The ESTIMATE wizard
259
Search Volume File
259
The Estimation Parameter File
261
Matching estimation runs with the relevant search ellipsoids
262
Table of Contents
viii
Search Parameter File
262
Estimation Parameter File
262
How is the grade estimation done?
262
How do I ensure certain samples are only used to estimate grades in cells?
262
Exercises
264
Exercise 1: Generating a Search Ellipse
264
Exercise 2: Estimating Gold Grade into the Model
265
Exercise 3: Estimating AU and CU using Different Methods.
273
Chapter 15
275
Data Presentation - Plotting
275
Principles
275
Plots Window
275
Displaying the Plots Window
275
Plots Window Context Menus
275
Controlling the Display of Data
276
Formatting Data
278
Section Definitions
279
View Settings
281
Section Definition Files
282
View Definitions
283
Plot Items
285
Sheet Templates
286
Reloading Files and Importing New Data
289
Managing Multiple Templates
290
Exercises
290
Exercise 1: Exploring the Menus for Plots
290
Exercise 2: Creating, Renaming, Copying and Deleting Sheets
293
Exercise 3: Modifying the Paper Size and Grid Settings
296
Exercise 4: Changing the scale and zoom
298
Exercise 5: Changing the section definition
300
Exercise 6: Modifying the Data Format Settings
301
Exercise 7: Inserting Plot Items
304
Exercise 8: Creating a Section Definition File and using it in the Plots window
309
Exercise 9: Editing the Section Definition File using the Table Editor
312
Exercise 10: Applying the Section Definition File in the Plots window
314
Additional Exercises
Table of Contents
314
ix
Additional Exercise 1: Create a Section Definition File
314
Additional Exercise 2: Generate a series of plots
314
Chapter 16 StripData LogsPresentation –
315 315
Principles
315
Exercises
316
Exercise 1: Loading Dynamic Drillholes
316
Exercise 2: Opening the Log window and inserting a new log sheet
323
Exercise 3: Formatting the strip logs
324
Additional Exercises
327
Additional Exercise 1: Generate a series of log sheet plots with different column data displayed and different header information.
327
Chapter 17
328
Data Presentation – Animations and 3D PDF’s
328
Principles
328
Understanding Virtual Reality data
329
The VR Environment
330
Perspective and Orthogonal 3D Views What is meant by 'Perspective' and 'Orthogonal'?
330 330
Selecting a View Type
330
Zooming
331
Panning
332
Recommendations
332
Navigational Control
332
View Modes and Controls
335
Navigating in an Orthogonal Projection
335
Using a Mouse Wheel
335
Changing the View during Simulation Playback
336
Setting Auto-Spin and Auto-Roll
336
Draping Textures
336
Viewing Block Model Data
337
Viewing Block Models as Points
338
Viewing Block Models as Lines
338
Viewing Block Models as Blocks
338
Viewing Block Models as ‘Quick Sections’
339
Table of Contents
x
Viewing Block Models as Intersections
340
Creating, Importing and Manipulating Section Planes
340
Adding Objects
343
Animations and Simulations
344
Exercises
344
Exercise 1: Displaying windows
344
Example 2: Modifying Surface Properties
346
Exercise 3: Navigational Control Exercise 4: Viewing Block Models with Sections
346 348
Exercise 5: Viewing Block Models as blocks
350
Exercise 6: Draping Textures
350
Exercise 6: Manual Alignment
351
Exercise 7: Adding Objects
353
Appendix 1
357
Studio RM Training Courses
357
Course overview
357
Who should attend
357
Course duration
357
Uniform Conditioning
357
Course overview
357
Who should attend
357
Course duration
357
Conditional Simulation
357
Course overview
357
Who should attend
357
Course duration
357
Ore body unfolding
358
Course overview
358
Who should attend
358
Course duration
358
Macros in Studio RM
358
Course overview
358
Who should attend
358
Course duration
358
Appendix 2
Table of Contents
359
xi
Datamine File Types
359
Block Model File
359
Wireframe Triangle File
359
Wireframe Points File
359
String File
360
Desurveyed Drillhole File
360
Drillhole Collars File
360
Downhole Survey File
360
Downhole Sample File
361
Point Data File
361
Plot File Prototype
361
Plot File
361
Variogram File - Experimental
362
Variogram Model File
362
Dependency File
363
Section File
363
Results File
364
Search Volume Parameters File
364
Estimation Parameters File
365
Attribute Validation File
366
Planes File
367
Table of Contents
xii
INTRODUCTION Objectives Your day-to-day activities are geared to maximizing the resource and profit of your operation. This training course has been designed with the specific goal of teaching you how Studio RM can be used to assist you in achieving these business objectives.
Prerequisites It is not essential to have prior experience with Datamine software. However it is expected that you are familiar with standard exploration and/or mining practices and have experience with computers on a Windows™ operating system. The training exercises can be completed using either your own data or a specific set of data that is distributed with the software.
Acronyms and Abbreviations The following table includes acronyms and abbreviations used in this document. Abbreviation
Description
DTM
Digital Terrain Model
VR
Virtual Reality
DSD
Data Source Drivers
CAD
Computer Aided Drawing
RL
Reduced Level
.dm file
A Datamine format file
Using This Training Manual To make information as accessible and as easy to understand as possible each module is divided into standard sections with each module comprising the following:
Principles – This section contains background information and outlines the underlying principles pertaining to the module. Exercises – This section contains a number of step-by-step guided exercises using the tutorial data set supplied with the Studio RM installation. Additional exercises – This section contains a number of additional course exercises that your course instructor may ask you to perform during the course or on your own time.
The following boxes appear throughout the manual:
Notes Notes provide supplementary information to the topic and give you a broader understanding of the item being discussed.
Introduction
1
Tips Tips are used to provide hints and suggestions about how best to achieve an end result. Tips will be used to provide alternative methods, or shortcuts that may be useful.
Warnings Warnings are used to highlight potentially destructive actions and raise awareness of how not to use the application.
More information Studio RM includes a wide range of online information available from the Help menu. Further information on Datamine software and services can be obtained from the web site at www.dataminesoftware.com.
Introduction
2
DATAMINE BACKGROUND Datamine is a world leading provider of the technology and services required to seamlessly plan and manage mining operations. With operations in thirteen countries, Datamine provides solutions ranging from exploration data management and orebody modelling to mine planning and operations to over 1,400 companies worldwide. Our software solutions integrate with our consulting and training services to ensure that we provide our clients with industry-leading support and expertise. Established in 1981, Datamine revolutionised the industry as a pioneer of 3D computerised resource modelling and estimation tools. Over a period of almost 30 years of continued investment and growth, Datamine became a leading global supplier of geology and mine planning software. In 2010, CAE Inc purchased the Datamine business and made significant investments to create an end-to-end portfolio of products, acquiring Century Systems Technologies and developing several new products including the innovative Summit cloud-based technical mining platform. In July 2015, Datamine was acquired by Constellation Software Inc., Canada’s largest software company. Building on Datamine’s history of domain expertise, coupled with Constellation Software’s deep capabilities in the software industry, Datamine continues to develop the mining industry’s most advanced range of technical software and complementary services.
Software Datamine provides the world’s leading range of integrated mining solutions across the e ntire value chain from exploration field work, database storage, resource modelling and all levels of mine planning from strategic optimisation to detailed design and short term decision-making.
Figure 1: Datamine software
We work collaboratively with customers and leading research groups to ensure that we continue to advance our products to solve industry problems, improve productivity and help our customers maximise the value of their mining assets.
Datamine Background
3
Training Datamine conducts regular training programs that enable users to build proficiency in the use of our mining engineering and geological software products.
Figure 2: Training
These programs are designed to provide users with technical familiarity of the Datamine software suite and the applied knowledge and skills to effectively incorporate the use of the available tools into daily mining activities.
Consulting Datamine provides a comprehensive range of consulting services for the mining industry with a team of over 100 industry recognised experts. Our consultants have the experience and depth of knowledge to provide practical advice for extracting the optimal value from existing operations, potential projects and mine expansions. Areas of expertise include geology, resource modelling, mine planning and financial analysis.
Datamine Background
4
C HAPTER
1
GETTING STARTED In this chapter, you will learn to:
Work with Studio RM projects
Organize data files in a logical manner so that information can be accessed quickly
Create and save StudioRM projects
Open and close Studio RM projects
Add and remove data files to a Studio RM project
Save and delete data files in aStudio RM project
Principles The Project File When you first start Studio RM a project file is created which stores all the settings that define and control the access, appearance, views and data relevant to your project. The file is created in the project folder when you start a new project. The project file has the ability to link a range of different data categories (e.g. Text, CAD, databases, other mining and exploration applications) as well as link in data from various locations (project folder or data external to the project folder).
Figure 3: The Studio RM project file is a container
The project file indexes all Datamine binary format files and details for imported files. The project file controls how and when data is refreshed from their data source as well as retaining all the information necessary to load and display data as it was when the project was last saved. The project file embodies the idea that Studio RM can be used to perform different types of work, and that different user-groups will require access to different data to perform different tasks. Depending on the circumstances of the implementation, specific users will have control over more or fewer aspects of the Studio RM project. A consultant doing a feasibility study, for instance, will probably wish to work in a data environment that gives greater control and flexibility than a technician producing weekly plans and sections for an operation. All the settings that define and control the
Getting Started
5
access, appearance and views of data relevant to any Studio RM project are stored in a project file. Studio RM project files have a .dmproj extension. You will not be able to load a Studio RM project file in Studio 3. Datamine products do not support backwards-compatibility for previous versions, even between the same products.
Data files created in Studio RM can be opened and used in a Studio 3 project.
You can load other project files from the Studio family (e.g. Studio 3, Studio OP, Studio EM, etc.) into Studio RM, but if they are single-precision, they will be automatically converted to extendedprecision.
Studio RM enables access to data from a wide variety of sources according to the task in hand and the extent to which the data need to be manipulated. The project file may contain the following main categories of information:
Links to data sources (external data) Links to physical .dm files (internal data) Archived data for records and auditing
Settings for the various application views
Legends specific to the project
The project file also maintains the concept of a current working folder, or project folder. This is used for the batch processes which require file storage and it also defines the default location for the creation of new file based data. Extended precision versus Single precision files Studio RM creates and supports only extended precision project files (sometimes referred to as 'double' precision'). Single-precision and extended-precision data files (files with .dm extension) continue to be supported and can be both created and loaded in Studio RM. It is the project file itself (the file with a .dmproj extension) that will be saved as extended-precision or automatically converted to extended precision. This is a departure from the model supported by Studio 3, where it supported the creation of both single precision and extended precision projects. This resulted in conflicts, because extended precision Datamine data files (*.dm) could not be used in single precision Studio 3 projects. This problem does not exist in Studio RM.
In a single precision Datamine data file (*.dm), numeric data is stored as real numbers to a precision of 7 significant digits whereas in an extended precision file it is 16 significant digits.
Being more specific; the difference between single precision and extended precision is in the way numeric values are stored. Both store numbers as floating point values, but in single precision files, this is restricted to 24 bits of precision, representing 6/7 significant digits, whilst in extended precision files, this is extended to 53 bits, representing 16 significant digits. To put this into context consider that 16 significant figures is sufficient in metres to compare the circumference of the earth (4e 7 metres) to a human hair (1e-4 metres), and still have a few significant figures left over. Single precision files permit a maximum of 64 data columns, whereas extended precision files extend this to 256 possible columns.
Getting Started
6
Files versus Objects Studio RM deals with data loaded into memory as “data objects”. A "file" refers to data that is stored on a physical device, such as a disk, that can be accessed and manipulated as a single-named unit. Files that form part of a Studio RM project are listed in the Project Files control bar. When a files is loaded into memory in Studio RM, it becomes an object. This can be either be a "table" or "3D object". A table is a collection of data in rows and columns which has no spatial context. A 3D object can also be viewed as a table but additionally has a spatial context (X, Y, Z coordinates). Examples of 3D objects are: points, strings, drillholes, wireframes and block models. When a file is loaded into memory in Studio RM, the data remains separate from any other loaded data (or data objects), and can be formatted, filtered and selected independently. Data objects can be merged and split on attribute fields or by using a filter expression to either combine or create new objects. A restriction of earlier versions of Studio, was that data could only be separated within the application by type, e.g. points, strings, wireframes, drillholes and block models. If two files containing string data were loaded into Studio 2 they were effectively appended to each other within the application whereas in later Datamine products, they are separate objects which can be formatted, snapped to, and manipulated independently.
Working with Data Objects Studio RM has the very powerful capacity to create and modify data. All data loaded into Studio RM are regarded as objects whether it represents tables, drillholes, points, wireframes or anything else. More than one instance of a single data object type can be loaded at any time and any one of these instances can be added to or edited. Data objects can be merged and split on attribute values stored in attribute fields or by using a filter expression to either combine or create new objects. Studio RM has the concept of “Current Objects”. These are the objects that are currently being created or edited. The concept of current object is to cater for the fact that more than one object of a specific type (e.g. two string objects) can be loaded in memory at the same time. It is the current object that will be modified when a save command is executed. There will be a current object for each object type that has been loaded or created as a new object. If strings are being linked, for instance, the triangles will be added to the current wireframe object. There are three ways in which the current object for any data type can be identified:
The Sheets control bar, where a current object is displayed in bold text.
The Loaded Data control bar, where a current object is displayed in bold text.
The Current Object toolbar, where the current object of each type is named.
The current object can be changed using the Current Object toolbar, the Sheets control bar or the Loaded Data control bar. In the Sheets control bar or the Loaded Data control bar, the current object can be changed by right-clicking an object and selecting Make Current. In the Current Object toolbar the same can be achieved by selecting the desired Object Type and object from the Object Name field (see Figure 4).
Figure 4: The Current Object toolbar
Getting Started
7
In terms of current objects, the following should be considered:
Every data type (wireframe, string, drillhole, block model, points, planes), if it exists in memory, will have a current object associated with it. If current objects are unloaded from memory (and this action is confirmed), the next object in the list (of the same data type) will automatically be assigned as the current object. Overlays of current objects can be rendered invisible (using the Format Display dialog, or by disabling their view in the Sheets control bar). If you try to add data to a 'hidden' current object, data will be added in the form of a new independent data object, which will also be set to the new current data. If an object is hidden, it cannot be set as the current object. If no current object is set, one will automatically be created if subsequent operations require one. Digitizing a string in a new project, for example, will automatically create a " New Strings" object and default overlay (sheet). Similarly, creating a DTM will create a new wireframe object if none is currently set. You can create a new current object at any time using the Current Object toolbar or using the relevant Create Object button
The Current Object toolbar has four drop-down lists (see Figure 4). The first allows you to select the object type: points, string, wireframe etc. The second lets you choose which of the objects of the selected type you wish to modify (using the name of the loaded object). In addition to these boxes there are buttons for creating a new object saving to the current object and deleting the current object. To change the current object using the Loaded Data control bar double click on the object name to change its status to "current object".
Figure 5: The Data Object Manager window
The Data Object Manager utility (as shown in Figure 5) is accessed either by right-clicking on an object in the Sheets (or Loaded Data) control bar and selecting Data Object Manager from the drop down list or alternatively using the Data ribbon, select Objects | Manage Objects. The utility contains a host of functions that relate to the control and analysis of loaded object data. The screen is divided into 3 main areas.
Command buttons: o
Import Data: brings data into Studio RM, using the selected Data Source Driver .
o
Refresh Data: refreshes (redraws) the currently selected object.
o
Refresh All Data: refreshes all currently listed objects.
o
Reload Data: reloads the selected object.
o
Getting Started
Unload Data: remove the selected object from memory. Note that this does not remove the file from the project.
8
o
o
o
Export Data: allows you to export the selected file to a variety of different formats. Combine Objects: displays the Combine Data Objects dialog. This dialog is used to join two or more loaded objects together. Extract From Object: select a property or properties of an object to extract.
Loaded Data Objects list: displays all currently loaded objects, and is used to add a data column to the selected object. Object Details panes: two tabs exist: Data Object - shows a summary of the currently selected object's statistics and functions relating to object filtering, and Data Table - which shows a view of the contents of the selected object's database table.
Loading data Studio RM will load any data stored in the native .dm file format or data from files that are supported by the Studio RM data source drivers. Once in memory, data is regarded by the program as objects. Studio RM supports numerous methods for loading data into memory. All methods, except the creation of a new object, support filtering of the data as it is loaded. Previous versions of Studio only permitted the loading of Datamine native format file (.dm files) into memory. Studio RM will load data directly from any files supported by the Studio RM data source drivers.
Saving changes to objects It is important to remember to save changes to objects before unloading the data objects from memory. When an object is saved in Studio RM, it is saved as a physical file (a .dm file that belongs to the project). Objects that have been modified, but not yet saved to a new or existing file, are listed in the Loaded Data control bar in Italics. As soon as the objects have been saved to file, the Italics are removed.
If an object is unloaded or deleted before the changes are saved as a physical file, those changes will be lost.
Objects can be saved in the Studio RM project file without saving them out as physical files first. This is not best practice, but it can be done. If the project is closed while there are objects loaded in memory, the user will be prompted to save the changes to the project file and the user is also prompted to either Save or Auto Reload the individual loaded objects.
Working with files in a project Files that are created during the course of working in a Studio RM project are stored in the project folder and are automatically added to the Project File browser. The links to these files are stored in the project. Other files (also files stored in other folders) can be manually added to the project by
Getting Started
9
using on the Home ribbon the Project | Add Files button. Working with files and data in a Studio RM project is discussed in more detail in Data Management (Chapter 3). Summary
A file is a term used to refer to data that is associated with a project file, and is listed in the Project Files control bar. An object is a term applied to a file when it is loaded into memory using one of the various data loading methods. Objects in memory can be edited and manipulated. The current object is the loaded data that is active, and currently being edited or created.
Exercises Exercise 1: Create a new project Follow the steps in this exercise to create a new Studio RM project called ‘Training’. 1. Open the Studio RM application by launching it from either the Windows Desktop or the Windows Start menu. 2. Create new project is created by selecting the New Project option in the Studio RM Start window (upper left part of the Start page).
Figure 6: New Project in the Studio RM Start window
An alternative way to create a new project is to select New Project on the Project menu.
Figure 7: Studio Project Wizard dialog box
3. In the Studio Project Wizard (Project Properties) dialog, define the settings as shown in Figure 7. 4. You are given the option to add any existing files to the project. You can do this by clicking on the Add File(s) button in the Project Files dialog. Browse to the folder C:\Database\DMTutorials\Data\VBOP\Datamine , select all Datamine files (files with a .dm extension) and then click Open. 5. You can review the list of added files and remove any that are not required before proceeding to the next dialog. 6. The final dialog allows you to review the Project Summary details. Click the Finish button to exit the Studio Project Wizard. Congratulations! You have created your first Datamine Studio project!
Getting Started
10
To configure general system-wide properties for Studio RM select the Project Settings button. The general settings are used to manage project updates and scripting files. The options are:
Detect new files in the project folder when the project is opened : Ensures that any files added to the project directory outside of Studio RM (for example, using Windows), since the project was last run, are added to the project.
Detect files added to or removed from the project folder while the project is open : Ensures that all files located in the project folder are automatically added to the project file.
Automatically update project (no prompts) : The project file will be updated according to the settings above without user prompts.
Automatically Compress Files: This option allows you to compress tables when saving to conserve disk space.
File Exclusions: Allows you to exclude certain files from triggering the project update process. The list shows all currently excluded file types.
Scripting (optional): Allows you to display a script file each time a project is opened.
For more information on any of these options refer to the online Help.
Exercise 2: Add existing Datamine files to a project The following exercise show the procedure for adding links to existing Datamine format files (.dm files) to a project. Once a file has been added to the project, the file will appear in the file list in the Project Files control bar. 1. In the Home ribbon select Project | Add files. 2. Browse to the folder C:\Database\DMTutorials\Data\VBOP\Datamine , select the files in this folder. Click the Open button. 3. Open the Project Files control bar to view the files you have added to the project. Files can be added to the project at any time after the project has been created. stored in other folders (other than the project folder).
The files can be
Exercise 3: Load existing external Datamine files into memory The following exercise show the procedure for loading existing external Datamine format files (.dm files) into memory. Once a file has been loaded into memory in the project, the file will appear in the file list in the Project Files control bar. 1. In the Data ribbon select Load | Datamine | Wireframes. 2. Browse to the folder C:\Database\DMTutorials\Data\ VBOP\DMDist, select the file _vb_faulttr.dm and click Open. 3. You will then be asked to identify the wireframe points file. In the case of this example select the _vb_faultpt.dm and click Open. 4. You can then select which data fields to load and define the coordinate fields. A Datamine wireframe consist of two files, a triangle file (normally ending in tr.dm suffix) and a points file (normally ending in pt.dm suffix). More about this in Data Management (Chapter 3).
Getting Started
11
Exercise 4: Load text files and CAD files to a project The following exercise show the procedure for adding other format files (in this case Text and CAD files) to a project. Once a file has been added to the project, it is possible to list it from within the Project Files control bar. 1. In the Home ribbon select Project | Add files to add the text files. 2. Browse to C:\Database\DMTutorials\Data\VBOP\Text , set the Files of Type dropdown option to "All Files (*.*)". 3. Select all of the listed files and then click Open. 4. The files can be viewed in the Project Files control bar under the All Files folder. 5. In the Home ribbon select Project | Add files to add the CAD files. 6. Browse to C:\Database\DMTutorials\Data\VBOP\CAD , set the Files of Type dropdown option to "All Files (*.*)". 7. Select all of the listed files and then click Open. Exercise 5: Remove files from a project The following exercise shows you how to remove files from a project. This procedure just removes the links to a file in a Studio RM project.
Removing a file from a project does not delete the file. It still exists as a physical file on the storage drive and can be added to another project if necessary.
1. In the Project Files control bar, select the _vb_faulttr.dm and _vb_faultpt.dm files. 2. Right-click and select Remove from Project in the context menu. If you select Delete in the context menu, the physical file will be permanently delete from the storage drive. A Confirm File Delete message box will warn the user of the consequences of this action.
Exercise 6: Save a project Follow the steps in this exercise to save changes to the Studio RM project called ‘Training’. 1. In the Project menu, select Save. 2. All changes to the project in terms of the files that have been added and removed have been saved in the project file. The next time you open the project, you will see the same list of files in the Project Files control bar. It is good practice to regularly save changes to a project. When you exit Studio RM without saving the project first, you will be prompted to save the project before exiting.
Additional Exercises Please complete the following additional exercises as instructed by the course instructor.
Getting Started
12
Additional Exercise 1: Save a project with loaded objects Check the size of the project file (Training.dmproj) in Windows Explorer. Open the project. Load a block model in the 3D window. Save the project. Close the project. Check the size of the project file again in Windows Explorer. Can you explain the change in the size of the project file? Additional Exercise 2: Automatically detect files added to or removed from the project folder Activate the setting to automatically detect files added to or removed from the project folder. Remove all files that are currently in the project. Copy Datamine files from the folder C:\Database\DMTutorials\Data\VBOP\ to the project folder. Additional Exercise 3: Rename file in a project Rename files in the project folder using the Studio RM file renaming functionality. Additional Exercise 4: Describe the purpose of a project file Describe the purpose of a Studio RM project file. What is stored in a project file? Additional Exercise 5: Describe differences between loaded objects and files Name and describe three differences between loaded objects and physical files. Additional Exercise 6: Questions about loaded objects and files Please answer the following questions: 1. How can a file become an object in Studio RM? 2. How can a Studio RM object become a file? 3. What are the differences between these Studio RM objects: tables and 3D objects? 4. Describe two ways in which the current object can be set in Studio RM. 5. How can one tell, when changes have been made to an object?
Getting Started
13
C HAPTER
2
THE STUDIO RM INTERFACE In this chapter, you will learn to:
Navigate around quickly in the Studio RM interface
Use the various control elements in the Studio RM interface
Configure the Studio RM interface
Principles Studio RM has a sophisticated interface that allows the user to utilize the powerful capability of the software optimally. It is essential for the user to understand the various elements of the interface in order to access the full power of the software. This chapter provides an overview of the various elements that make up the user interface.
Figure 8: Studio RM user interface elements
The following user interface elements are discussed in this chapter.
Windows Project Menu Ribbons Quick Access toolbar
Navigation toolbar
Control bars
Status Bar
Popup Menus
The Studio RM Interface
14
Windows In Studio RM there are several view windows that can be activated by clicking on the tabs as shown in Figure 9.
Figure 9: Windows that are displayed by default
General notes about working with windows in Studio RM: •
By default the different windows are in a tab view format.
•
To view multiple windows, on the Home ribbon select Window | Arrange | Cascade . This allow you to maximise and close windows to suit your preferred set up.
•
You can also tile the different windows using Window | Arrange | Tile Vertically on the Home ribbon or using Window | Arrange | Tile Horizontally. To return to the srcinal tabbed view simply maximise any of the open windows.
•
Windows provide different views of loaded data as summarized below: 3D window
The 3D Window is the primary design window and is used to render realistic, simulated worlds using your core data as building blocks. It is also a functional design area allowing you to create and modify your 3D data directly within a richly-detailed visualization environment, using one, two or four linked viewing windows. This visualization environment allows for an immersive view of data including draping of aerial photos, simulations etc. For more information about working in this window, please see Data Visualization (Chapter 4). Plots window
The Plots window provides the tools required to create high quality plots in plan section and 3D views. The Plots window with its comprehensive suite of data source drivers, can use data from a huge variety of sources and bring it all together into a single model showing all the characteristics and properties you choose, and in whatever format you select to maximize the presentational impact. For more information about working in this window, please see Data Presentation - Plotting (Chapter 15). Logs window
The Logs window provides the tools required to create high quality strip logs. The Logs window is used to configure the contents of the log sheet using a host of formatting functions. Similar in behaviour to the Plots window, a log sheet can be enhanced using a selection of Plot Items, from a
The Studio RM Interface
15
library, to ensure that data presentation is effective and informative. For more information about working in this window, please see Data Presentation – Strip Logs (Chapter 16). Tables window
The Tables window displays loaded data as columns and rows. The Tables window provides another way to view data that is loaded in memory. The content of a table is completely definable by the user and, as such, does not necessarily represent the entire contents of any source data file. Fields may be duplicated, displayed as text or graphs or fields from more than one table source can be viewed in the same table view including composited and system fields. An alternative table view can be found using the Table Editor facility.
Reports window
The Reports window displays various reports including drillhole summary and data validation reports. External 3D window
The External 3D window displays a 3D visualization window outside the Studio RM window. This is ideal for working on multiple display monitors. There can be more than one External 3D window open. One of the great improvements made with the advent of Studio RM is the ability to create a standalone, floating 3D window that is dynamically linked to all other views, including locked sections. All of these windows are 'live' in that they can be used for digitizing, editing and other purposes. Once set up, you can digitize in true 3D by using multiple windows to create data points, even within the same command Start window
The Start window is a web browser window that displays useful information about the software and it also shows recent projects. This is the window that is active when Studio RM is first opened. The Start Page window can be set to update information with a live link to the internet. This allows the user to always get the latest news. This option can be activated in the Home ribbon using Project | Options.
Project Files window
The Project Files window displays the list of files that belong to the project. The Design, Graphics and Screen windows are legacy functionality in Studio RM and have been deprecated to the background in the Studio RM interface. If you need to activate these legacy windows you can on the Home tab click on Window | Show and select them from the list. The use of legacy functionality is not covered in this training course.
Project menu The Project menu contains all the functionality to manage Studio RM projects, i.e. create new projects, open existing projects, close projects and save projects. The printing functionality (for plots and reports) are also accessed in this menu. The Datamine License Manager and Plugins can also be accessed from this menu. Figure 10 shows the Project menu.
The Studio RM Interface
16
Figure 10: The Project menu
Ribbons Studio RM uses a ribbon interface to provide access to the majority of its core functionality. This is in line with many other commonly used Windows® applications, like Microsoft Word®, Microsoft Excel®, etc. The basic concept of ribbons as a user interface element is graphical buttons, grouped by functionality on tabbed toolbars. Studio RM also makes use of contextual ribbons, meaning that contextual tabs are tabs that only appear when the user needs them. Tab information is listed in a left-to-right order, by command group. On the ribbons are large and small buttons with text labels and some buttons open up in expanding menus providing access to more functionality. Buttons linked to expanding menus have down arrows associated with them to indicate that there are more options available. In terms of its user interface, Studio RM represents a major departure from previous version of Studio, by replacing menus and customizable toolbars with a so called “ Fluent User Interface”. The Fluent User Interface consist of the following major elements: a single Project menu, a miniature toolbar known as a Quick Access toolbar and tabbed ribbons. Another big change in Studio RM is the grouping of functionality (on the ribbons) according to task domains rather than grouping according to functional domains as was the case in the menu system of previous versions of Studio.
In the following section each ribbon is described briefly. For more information, please consult the online Help. The Home ribbon
The Home ribbon contains general commands that are useful throughout the system. From here, the user can manage data behaviour (snapping, selection etc.), query data in memory and access an automation interface for running scripts and macros. Figure 11 shows the groups and buttons that appear on the ribbon.
Figure 11: The Home ribbon
Some of the buttons and groups on the Home ribbon may be greyed-out depending on the window that is open, e.g. when the Start window is open, only a few of the buttons on the Home ribbon are available.
The Studio RM Interface
17
The Sample Analysis ribbon
The Sample Analysis ribbon contains commands related to the investigation of sample data; a wealth of statistical and geochemical analysis functions, charting options, drillhole data building and compositing plus a range of drillhole data editing commands. Figure 12 shows the groups and buttons that appear on the ribbon.
Figure 12: The Sample Analysis ribbon
Some of the buttons and groups on the Sample Analysis ribbon may be greyed-out depending on the window that is open, e.g. when the Start window is open, none of the buttons on the Sample Analysis ribbon are available. The Structure ribbon
The Structure ribbon is a useful place to be when you're interpreting, creating and/or editing structural data such as strings, points and wireframes. Studio RM's powerful Boolean commands are here, plus a wide range of string editing commands. Figure 13 shows the groups and buttons that appear on the ribbon.
Figure 13: The Structure ribbon
Some of the buttons and groups on the Structure ribbon may be greyed-out depending on the window that is open, e.g. when the Start window is open, none of the buttons on the Structure ribbon are available. The Model ribbon
The Model ribbon contains commands related to the definition, preparation and creation of a block model file, from prototype to estimated orebody model. Figure 14 shows the groups and buttons that appear on the ribbon.
Figure 14: The Model ribbon
Some of the buttons and groups on the Model ribbon may be greyed-out depending on the window that is open, e.g. when the Start window is open, none of the buttons on the Model ribbon are available. The Estimate ribbon
The Estimate ribbon focuses on the operation of estimating resources/reserves using a wide range of estimation techniques from simple Inverse Power of Distance estimation to more advanced techniques like Conditional Simulation, Dynamic Anisotropy and many more tools to provide reliable, pragmatic estimation results. Figure 15 shows the groups and buttons that appear on the ribbon.
Figure 15: The Estimate ribbon
The Studio RM Interface
18
Some of the buttons and groups on the Estimate ribbon may be greyed-out depending on the window that is open, e.g. when the Start window is open, none of the buttons on the Estimate ribbon are available. The Report ribbon
The Report ribbon contains functions related to the evaluation of reserves and analysis through detailed reporting and visualization. Figure 16 shows the groups and buttons that appear on the ribbon.
Figure 16: The Report ribbon
Some of the buttons and groups on the Report ribbon may be greyed-out depending on the window that is open, e.g. when the Start window is open, none of the buttons on the Report ribbon are available. The Format ribbon
The Format ribbon contains commands relating to the visual formatting of the current display and loaded data objects, including filtering and legends configuration. Figure 17 shows the groups and buttons that appear on the ribbon.
Figure 17: The Format ribbon
Some of the buttons and groups on the Form ribbon may be greyed-out depending on the window that is open, e.g. when the Start window is open, only some of the buttons on the Format ribbon are available. The Data ribbon
The Data ribbon focuses on all commands related to the input and output of data objects and files, and complements the commands found in the Project menu. Figure 18 shows the groups and buttons that appear on the ribbon.
Figure 18: The Data ribbon
Some of the buttons and groups on the Data ribbon may be greyed-out depending on the window that is open, e.g. when the Start window is open, only some of the buttons on the Data ribbon are available. The Edit ribbon
The Edit ribbon contains many commonly-used point and string CAD-type editing commands, including modification of point and string objects in memory. Figure 19 shows the groups and buttons that appear on the ribbon.
Figure 19: The Edit ribbon
Some of the buttons and groups on the Edit ribbon may be greyed-out depending on the window that is open, e.g. when the Start window is open, none of the buttons on the Edit ribbon are available.
The Studio RM Interface
19
The View ribbon
The View ribbon is a contextual ribbon and its display and contents will vary depending on which window is the active window. When the 3D window is the active window, the contextual View ribbon contains a variety of commands related to the formatting of the 3D viewing window, including definition of views, sections, window arrangements and clipping. Figure 20 shows the groups and buttons that appear on the ribbon.
Figure 20: The View contextual ribbon associated with the 3D window
When the Plots or the Logs window is the active window, the View ribbon contains all the tools you need to format the view of your plot sheet, log or table display, including tools to define your sectional view, scale, zoom and pan settings. Figure 21 shows the groups and buttons that appear on the ribbon.
Figure 21: The View contextual ribbon associated with the Plots window
In Studio RM the Design window is part of the legacy functionality that is deprecated to the background. It is worthwhile to note the contextual View ribbon in the Design window provides access to functions associated with the legacy Design window, including overlay management, view settings and control over clipping.
The Manage ribbon
The Manage ribbon is a contextual ribbon that is specific to the Plots and Logs windows, and will only appear when one of these windows is the active window. The Manage ribbon contains functions to allow the user to construct a report-ready plot, including projections, sheets and plot items. It also allows the user to insert table views into your project. Figure 22 shows the groups and buttons that appear on the ribbon.
Figure 22: The Manage contextual ribbon associated with the Plots window
Quick Access toolbar The Quick Access toolbar can be used to create your own group of favourite commands. The toolbar is always visible regardless of which ribbon or window is active and it is therefore easier to get access to commands on this toolbar. It is a good practice to add commands that are regularly used to this toolbar.
The Studio RM Interface
20
Figure 23: Customize the Quick Access toolbar
The Customize Quick Access Toolbar menu can also be activated by right-clicking on any of the ribbons.
Current Object toolbar The Current Objects toolbar is located at the bottom of the Studio RM window (see Figure 8). The Current Objects toolbar is used to set the current object, set attributes and values for the current objects when digitizing new data; create, save and delete current objects. For more information about current objects, please see Data Management (Chapter 3).
Figure 24: The Current Object toolbar
The Current Object toolbar have the following controls:
Object Type: select an object type from the drop-down. The following object types are available: Block Model, Drillholes, Planes, Points, Strings, Wireframe . Current Object: select an object name from the drop-down; only those objects which are currently displayed and which belong to the object type selected in Object Type will be listed. Attribute Field: select an attribute field from the drop-down; this field and the Attribute Value field below are used to set attributes when digitizing new data. Attribute Value: type in a value or select a value from the drop-down list or palette. The drop-down list's values are controlled by the data legend associated with the column. When an object is loaded or created in memory, each column is automatically assigned a default legend. This
•
can be changed. Right-clicking in this field displays a context menu with the following menu items: Show Fill - this option only applies if a non-system legend has been selected; select this option to show a preview of the fill type associated with the value/legend combination.
•
Show Line - this option only applies if a non-system legend has been selected; select this option to show a preview of the line style associated with the value/legend combination.
•
Show Symbol - this option only applies if a non-system legend has been selected; select this option to show a preview of the symbol associated with the value/legend combination.
•
Change Legend - click this display the Default Legend dialog, for changing or creating a new data legend.
The Studio RM Interface
21
Navigation toolbar The Navigation toolbar is one of Studio RM's three static toolbars, and its default position is on the right of the screen (see Figure 8). The functions on this toolbar allows the user to orientate the user view or a section.
Figure 25: The Navigation toolbar
The Navigation toolbar is always visible, regardless of the active window. However some tools may be greyed-out depending on the active window, e.g. the Interactive Section Editor is only available in the 3D window and is greyed-out when the Plots window is active. Figure 25 shows the layout of the Navigation toolbar. The Navigation toolbar can be moved, floated, customized or docked. Command toolbar The Command toolbar is used to run, cancel and search for commands and processes. In a default system setup, this toolbar is docked at the bottom left of the main application window (see Figure 8). The Command toolbar is used in conjunction with the Command control bar (see Figure 29) which displays the progress of a command and also supplies additional prompts when running certain processes e.g. PROTOM.
The Studio RM Interface
22
The Find Command button, on the far right of the Command toolbar, can be used to display the Find Command dialog. This dialog is used to search for, select and run a process.
To get access to the required command quickly, type in the first letter of the command, page down or use the slider bar on the right.
Figure 26: The Find Command window.
The Find Command functionality in Studio RM has been enhanced significantly. The Quick Key of each command as well as a full description of what the command does is also shown.
Quick keys are what most advanced users use in Studio RM use to work quickly and efficiently. In order to get the full value out of quick keys, the user has to memorize the quick keys. The user can
find the quick keys for a command or process in the Find Command window or the Status Bar.
Commands and processes can be run using one of the following methods:
Typing in the name of the command or process in the Run Command field clicking Run Command button.
Selecting a previously run command or process from the drop-down list.
Using the Find Command dialog and running the command from the list. If a process or command requires additional user input, the Command control bar will display a text message prompt, and the Command Line will be highlighted in yellow. This indicates that the information required must be entered before the next step is accessed. Each time a process is run, its progress is reported in the Command control bar.
Whenever you run a process, check the Command control bar for: additional process input prompts (this does notrun happen for all processes), or error messages, or a message indicating that the process has to completion and that anwarning output file has been generated.
Commands and Processes Commands and processes underpin the core functionality of Studio RM. It is important to understand the role of commands and processes and how these could be accessed via the Studio RM interface. The functionality available within Studio RM (including all the commands and processes) can be accessed using ribbons, shortcut keys, command syntax and process syntax. In essence, commands are used for loaded objects and processes are used for data files (not objects).
The Studio RM Interface
23
There are three main categories of commands and processes:
Commands Processes Macro Commands
Understanding “Commands”
Commands, such as make-the-dtm, link-single-outline, circle-from-edge-to-edge are all accessible from the ribbons and the command line i.e. the Run Command box in the Command toolbar. In addition, most commands can also be run via the toolbar or via quick keys (where relevant) theadditional 3D window. These commands typically act dialogs. on currently loaded (into memory) data, optionallyinwith parameters supplied using further Understanding “Processes”
Processes, such as HOLES3D, ESTIMA, PERFIL are similar to commands, in that they can also be accessed via the ribbon or command line, but instead of activating a function directly, they provide an interface to allow you to specify the files, fields and parameters required to run the process. These dialogs all have a standard layout, and differ only in the contents of each tab. A number of processes are what are termed 'Superprocesses'. Each is made up of a specific group of processes, grouped together in a specific order in a single file, like in a macro, which make use of input file(s), associated fields and also parameters in order to process data and generate an output file(s). These superprocesses are run just like any other process, use the same interface and also have the maximum 8 character name format. Superprocesses create temporary Datamine (*.dm) files which all start with the 3 characters ' _SP' or '_SQ'. At the end of every superprocess all of these temporary files are deleted. Examples of superprocesses include: APTOTRUE, BHCOUNT, CHECKIT, COGTRI, DECILE, DECLUST, ELLIPSE and HOLES3D.
Macro Commands
Macro Commands is a special category of commands. These commands are used to enhance macros by providing simple programming functionality such as looping, conditional statements and data entry prompts. The macro commands cannot be accessed from the interface. These macro commands do not have any file output, but are instead used in conjunction with other processes within a macro. They function only within a macro. Please see more about macros in Introduction to Macros and Scripts (Chapter 12). Macro commands include the following commands: LOADCF, MACEND, MACST, MDEBUG, MENU, NOMENU, NOXRUN, OPSYS and XRUN. Please consult the online Help for more information.
Control bars Control bars provide context-sensitive information relating to the selected object or component. They are used to control and view the state and display of loaded data. There are a number of control bars which contain application controls. They can be floated, docked, auto-hidden or hidden.
The Studio RM Interface
24
Control bars can be positioned anywhere in the main Studio RM window. They can be grouped, they can be docked and they can be made to hide and reveal themselves automatically. When a control bar has been selected and dragged away from a docked position, it can either be docked on the edges of the Studio RM window or it can be made a floating toolbar. As the control bar is dragged over one of the edges of the window, the position where it would be dropped is highlighted. If no docking location is selected the control bar will float. Once docked, the automatic hiding and showing can be toggled on or off using the pin icons.
The control bars include: Project Files control bar
The Project Files control bar is used to manage the files in the project folder. It categorizes them in folders according to a file type, e.g. points, strings, block models, macros, etc. This is the tool for adding or removing files from the project, previewing or opening a Datamine file in the Datamine Table Editor, loading files into memory, copying and exporting files. This works in conjunction with the Project Files window and allows the user to see the files contained within the project. Sheets control bar
The Sheets control bar is used to manage the various data window's sheets, projections, views and overlays. Only 3D data objects are listed in this control bar. Making extensive use of the right-click (context) menu system, the Sheets control bar can be used to access commands and functions related to both individual items, and groups of items, depending at which point in the data hierarchy a menu is selected. The window to which the selected item(s) relate (3D, Plots etc.) will also determine the functions that are available in a given menu. For example, you can access the Strings Properties dialog by right-clicking a string object (in the Strings sub-folder of the main 3D folder) and selecting Properties.
Figure 27: The Sheets control bar
It also allows you to manage the data objects from which the selected overlay is derived; you can save, load, unload, reload and refresh data objects as well as assign the " current object" (see the context menu in Figure 28 for an example).
The Studio RM Interface
25
In Studio RM all of the functionality in the Loaded Data control bar for 3D data objects are available in the Sheets control bar. Only data table objects (non-visual objects) cannot be managed using the Sheets control bar.
Figure 28: The context menu for drillhole object in Sheets control bar
With regards to object overlays, the Sheets control bar manages displaying and hiding items, formatting overlays and editing the associated overlay visual settings. An overlay is just one representation of a data object, and possibly one of many in memory
Loaded Data control bar
The Loaded Data control bar is hidden by default. It is used to manage the data objects that are currently loaded in memory. This includes loading, unloading and refreshing objects; editing object definitions; accessing the Data Object Manager and performing object operations. In Studio RM all of the functionality in the Loaded Data control bar for 3D data objects are available in the Sheets control bar. Only data table objects (non-visual objects) cannot be managed using the Sheets control bar. The Loaded Data control bar is rarely needed and therefore hidden by default.
Holes Control Bar
The Holes control bar displays a list of currently loaded drillholes. The Holes control bar reports on dynamic drillhole data, containing a series of X,Y, Z sample centre points, lengths and directions representing hole traces. The Holes control bar shows all currently loaded dynamic drillhole objects, and a list of the borehole identifiers. The list displayed represents the drillhole data that is currently in-memory. For more information on working with drillholes, see Working with Drillholes (Chapter 7). Customization control bar
The Customization control bar is an HTML browser through which scripts can be run. It is a very powerful feature of Studio RM that can be used to deliver fit-for-purpose scripted systems. See Introduction to Macros and Scripts (Chapter 12). Data Properties control bar
The Data Properties control bar can be used to identify objects and display the values of properties associated with objects loaded in memory. Values shown in this view are displayed when an object is
The Studio RM Interface
26
selected in the 3D window – note that selection of multiple objects is not supported. It is therefore a useful tool when, for instance checking attribute values in strings after the attribute has been edited or identifying which loaded object a particular string belongs to. The window displays a number of object properties, including the object name, object type, X, Y and Z values at the start of the object, the values of any attributes, the length of the object (strings and drillholes) and the coordinate values of all points in the object. In addition, for string objects, the Data Properties control bar displays whether the string is planar and the dip and dip direction of the string. Properties control bar
The Properties control bar is a context sensitive settings table, updated on selection of data in the 3D, Plots, Tables, Logs and Reports windows. This control bar offers methods of formatting the selected property, using an object-browser style interface. The menu displayed depends on the type of object selected and in which window it has been selected. Compositor control bar
The Compositor control bar is used to interactively query static or dynamic drillhole segments or composites. The Compositor control bar is a powerful tool for analysing drillhole data. It provides the following functionality:
Works with dynamic and static drillhole data. Use the compositor in conjunction with drillholes in any Table, Plots, 3D window or Log view. Works in the 3D window after the composite-drillholes command has been run.
Displays additional information such as horizontal and vertical thickness
Select intervals interactively and display composite results.
Slide composite or composite limits up and down the hole and observe composite values.
Select intervals by BHID and FROM - TO depth and display composite results. Locate any interval on any hole on any section by synchronizing views from the compositor. Save composited intervals to the intersections table with any selection of composite result fields.
Composite samples over lithological domains.
Composite drillholes over fixed downhole lengths.
Command control bar The Command control bar is used to record and display the progress of processes, and supply prompts for additional user input. Its default position in the Studio RM window is below the main windows area (see Figure 29). The Command control bar displays information that is relevant to the process being run and as such is used in connection with the Command toolbar when running processes.
Figure 29: The Command control bar
The Studio RM Interface
27
If a process or command requires additional user input, the Command control bar will display a text message prompt, and the Command Line will be highlighted in yellow. This indicates that the information required must be entered before the next step is accessed. Each time a process is run, its progress is reported in the Command control bar.
Whenever you run a process, check the Command control bar for: additional process input prompts (this does not happen for all processes), warning or error messages, or a message indicating that the process has run to completion and that an output file has been generated.
Status Bar
Figure 30: The Status bar
The Status bar is situated at the bottom of the Studio RM window and is used for the following
To display brief information relating to a specific icon or menu item.
To show the progress of commands.
To display or set the position of the mouse in XYZ space.
To show if a command is currently running.
To show the read status of the currently open file. To see or set numlock, scroll lock and caps lock statuses.
Context menus There are context sensitive menus available within each window, activated with a right-click of the mouse button. These context menus provide quick access to specific functions.
Figure 31: Context menus in Studio RM
The Studio RM Interface
28
Help menu The Help menu provide access to various online information and training resources. It is located in the top right hand corner of the Studio RM main application window (see Figure 8). If you click on the Help button, it will open the online Help. If you click on the down arrow next to the Help button, the Help menu is displayed which provides access to various online tutorials.
Figure 32: The Help menu provides access to various online tutorials
An additional Help feature in Studio RM is the new optional Cursor Messaging System that can be enabled to provide status information on-screen at the appropriate place, e.g. close to the active cursor.
Studio RM makes use of context-sensitive tooltips to get a new user up-and-running with the ribbons quickly. These are much more than the tooltips of old. All ribbon commands in Studio RM are introduced by a short overview of the command and pointers on how to use it, e.g.:
Exercises Exercise 1: Setup the Quick Access toolbar 1. In the View ribbon right-click the Sections | 1 Point button. 2. On the context menu select Add to Quick Access Toolbar. 3. Do the same for the following commands: a. In the Edit ribbon, the Edit | New Object | New Strings button. b. In the Edit ribbon, the Edit | New Object | New Points button. Exercise 2: Working with windows and control bars 1. In the Home select Show | Logs. 2. In the Home select Show | Reports. 3. In the Home select Show | Loaded Data bar. 4. Move the Properties and Data Properties control bars and group it together with the other control bars on the left side of the Studio RM application window.
The Studio RM Interface
29
Additional Exercises Please complete additional exercises according to the instructions of the course instructor. Additional Exercise 1: Setup a custom Quick Access toolbar Setup a custom Quick Access toolbar with buttons for all the tools that you think you might use often. Additional Exercise 2: Change the look and feel of Studio RM Change the look and feel of Studio RM. Change the display to the Carbon theme (or any theme that you like). Change the display of the windows tabs. Additional Exercise 3: Working with the Sheets control bar Please do the following tasks: 1. In the Sheets control bar, use the Load Drillholes button to load the _vb_holes.dm file. 2. In the Sheets control bar, use the Load Block Models button to load the _vb_mod1.dm file. 3. In the Sheets control bar, use the Load Strings button to load the _vb_stopo.dm file 4. In the Sheets control bar, right click on _vb_mod1 to display the context menu. Select Quick Section Controls. In the Section Control move the slider to move the quick section through the block model. Change the plane and move the slider to get a different section. Close the Section Control. 5. In the Sheets control bar, right click on _vb_mod1 to display the context menu. Select _vb_mod1 Properties. In the General tab of the Block Model properties dialog, change the Display Type to Blocks. Click the OK button. 6. In the same way, open the Drillholes properties. On the Lines & Symbols tab, change the Display Options to Default Cylinder. 7. Switch off the display of the vb_mod1 block model in the Sheets control bar. 8. In the Sheets control bar, unload the vb_stopo strings object. 9. In the Sheets control bar, use the Unload All Objects to unload the remaining objects. Additional Exercise 4: Working with the Holes, Loaded Data and Compositor control bars Please do the following tasks: 1. Use the Hole Wizard to build a dynamic drillholes object using the following text files: _vb_collars.txt, _vb_surveys.txt, _vb_lithology.txt and _vb_assays.txt (in the folder C:\Database\DMTutorials\Data\VBOP\Text ). The Hole Wizard can be accessed in Sample Analysis ribbon Prepare Sample | Hole Wizzard .
When you setup the field mappings of the files, make sure the fields are mapped correctly. In the files used in this exercise, please check especially the mappings for the collar file.
2. View the Desurvey Report in the Desurvey Report window. 3. Check the Summary and Validation report in the Desurvey Report window. In the Sample Analysis tab select Prepare Samples | Build Dynamic | Validate and Prepare Samples | Build Dynamic | Summary to run the reports.
The Studio RM Interface
30
4. Use the Interactive Compositor tool to dynamically change the composite length (and values) of any of the holes in the 3D window. Notice how the values change in the Compositor control bar. The Interactive Compositor can be accessed in Sample Analysis ribbon Edit Drillholes | Interactive Compositor.
Notice the behaviour of the Interactive Compositor tool in the 3D window. Dragging the edges change the size of the composite. Dragging the middle change the position of the composite.
5. In the Compositor control bar right-click and select Save Selection on some of the dynamic composites to save some of the composites to the Intersection table object. The Intersections object is a data table object (not a 3D data object). It can therefore only be accessed in the Loaded Data control bar (not in the Sheets control bar as with 3D data objects). In the Loaded Data control bar, right-click on the Intersections object. Select Data | To Excel from the context menu. View the saved composite values in the Microsoft Excel ® file.
6. In the Holes control bar, right-click and delete holes VB2675, VB2737 and VB2812. 7. Save the Dynamic Drillholes object as a holes file. Additional Exercise 5: Questions about commands and processes Please answer the following questions relating to commands and processes: 1. How can you access commands and processes in Studio RM? Please describe more than one way. 2. Where can you find a short description and a quick key for commands and processes? 3. What is the major difference between commands and processes in Studio RM? 4. What do we record in a macro? Commands or processes? Additional Exercise 6: Questions about the Studio RM interface Please answer the following questions relating to the Studio RM interface: 1. Describe how you would activate the Loaded Data control bar. 2. What type of objects are not displayed in the Sheets control bar? How would you unload these objects? 3. Where in the application will you find tools to navigate around in the 3D window?
The Studio RM Interface
31
C HAPTER
3
DATA MANAGEMENT In this chapter, you will learn to:
Manage data files in a Studio RMproject
Add data files to anexisting project
Import data using the Data Source Drivers
Import data using Studio RM batch commands
Export data to Excel
Export data using theData Source Drivers
Reload/refresh data from external data sources
Edit and view data tables
Principles Studio RM uses several types of data and it is important to understand the nature of each and how it is accessed. Studio RM also integrates with other system and data can be imported and exported to these other systems. The subject of data management, in the context of Studio RM, deals with all aspects relating to data exchange, data capture and data processing.
Figure 33: The Data ribbon in Studio RM
Once data has been loaded into the project, it is available for viewing, interpretation, modeling and plotting in all windows (see section on The Interface). The tasks involved with managing data within Studio RM are:
Data capture
Importing data using the Data Source Drivers
Importing data using Datamine batch commands
Digitizing from hardcopy plots, plans or sections Exporting data Reloading/refreshing data from external sources Editing and viewing data tables
Data Types Studio RM uses several types of data and it is important to understand the nature of each and how it is accessed:
Data Management
32
Data type A: Datamine file in the project folder
In general, these are working files such as strings and wireframes, which do not need to be stored in a central database. Your application can run using only this type of data. To improve performance, temporary files created during batch processing, or data manipulation, may also fall into this category. Data type B: Distributed Datamine file
These are external Datamine files containing data which can be shared between two or more users. Having a single reference point avoids the need to manage multiple copies of a key file and ensures all users are always working with the same data. For example, a resource model has been created, and is being updated, by geologists also it also needs to be accessed by the mine engineers for planning purposes. Data type C: Imported Data cached as a Datamine file
Cached files are used to access data from a third party source and store it in the project folder, as a Datamine file, for further processing. The key characteristic of this data type is that a link is maintained to the external source so that the Datamine file can be refreshed easily whenever a latest version of the source data is required. This data type is used for mine data stored in a third party format but which needs to be processed using a Datamine application. For example, a large geological block model (many megabytes) is stored in a corporate geological modeling system. Your application will recognize that the data are stored externally, in the corporate database, but it will optimize its performance by accessing the data using its own formats. Another example is drilling data (Collars, Surveys , and Samples files) are usually stored in an external database such as Microsoft SQL Server© or Microsoft Access©. The data are often imported into Studio RM for further validation, processing and modeling. As with geological block models it is not always desirable to get the very latest data if it is changing frequently and represents work in progress. Data type D: Automatically Imported Data
This memory-based data type is used to access data from a third party source and load it into the data Window. In other words, the data are loaded into memory but are not stored as a Datamine file. A link to the external source is maintained so that the data can be reloaded easily into the data Window when needed. This is for data that are not processed directly but are needed for display or reference purposes when working with other data. For example, when surveyed underground development wireframes (drives and cross-cuts) are imported for use in a ring design, they are only needed as a reference. The wireframes themselves will not be changed. Data type E: Archived Data
These data are actually stored within the project file rather than in a linked external source. The archived data type is useful for saving a snapshot of the data (and any settings) used at a particular time. For example, a set of plots can be be saved as archived data to be printed-out at a later date. Data type F: Other
Other data includes file-based data which are not stored in the Datamine format such as fields and records. The most common examples would be macros and scripts which are used to record and run user-defined sequences of commands. Both macros and scripts are stored as lists of commands with associated settings in text files. For example, Bitmap files, representing Company logos, to be added to title boxes on plotted plans and sections would also fall into this category. A bitmap file representing seismic survey data could be loaded as geo-referenced data into the 3D window. Data Type G: In Memory data
Data created in memory that has not yet been saved either within the project or to a file.
Data Management
33
Standard Datamine file types Studio RM makes use of a number of standard Datamine file types, in terms of the types of objects that are represented by the files and the standard fields that exist in the files. For a full list of file types, please refer to Appendix 2. The most common standard Datamine file types that are used in this training course are:
String files
Point files
Desurveyed drillholes files Block model files Wireframe triangle and point data files
A full description of the standard fields for each of these file types can be found in Appendix 2. The Datamine relational database: •
The way Studio RM stores data in different files can be compared to a primitive database. Although all the Studio RM data files are Datamine (*.dm) files, there are different file types that are recognized by the Studio RM (see Appendix 2 for a description of the various file types).
•
In addition to the fact that there are standard fields (with standard fields names) used in these various Datamine file types, it is also important to note that the concept of key fields are also used (similar to key fields in any other database). For instance, in a drillhole file the combination of the BHID with the FROM and TO fields should be unique for every record. In a block model the IJK field can be viewed as a key field and every parent cell in a block model will have a unique IJK value.
•
To work with these files (or data tables in the database context), Datamine provide several database processes in the Data ribbon in the Data Tools group.
•
Most of these database processes have their equivalent commands in SQL, like JOIN, SUBJOI, SORT, etc. If you understand relational databases, you will understand the basic concepts for working with Studio RM data tables (Datamine files).
Data Capture Data available for input into Studio RM are usually available in a number of forms. These include:
Data Management
34
Data tables stored in databases;
Output from CAD software or other graphics packages; ASCII format files from various packages;
Hardcopy plots, plans or sections i.e. paper based information;
Any combination of the above.
Importing of files into Studio RM can either be done via the Data Source Drivers which allows connectivity between the Datamine product range and other software applications or by using batch processes. Importing files using Data Source Drivers
Studio RM utilize data source drivers that can be used to link to external data sources including other general mining packages, CAD packages, Microsoft Excel® spreadsheets, Microsoft Access®, Microsoft SQL Server® databases and text files. One of the most frequently used Data Source Drivers is the ODBC driver. The term ODBC stands for Open Database Connectivity and allows the seamless transfer of information from a data source to the software product. In order to connect to an Excel® spreadsheet or Access® database table, it is necessary to use the ODBC data source drivers. The following procedure outlines the steps that are necessary to create a system ODBC data source for a Microsoft Access® database or a Microsoft SQL Server® database. When files are imported using the Data Source Drivers, the path, field mapping and other information of how the files were imported is stored in the Project File. This allows the imported data to be re-imported when required, from within the Project Files control bar. The data import process generates a new Datamine format file from the external data source. This new Datamine file is automatically added to the project. The Data Source Drivers include the following Driver Categories: Driver
File Types
CAD
*.dwg, *.dgn, *.dxf
Generic Data Tables
Data Provider, Datashed, ODBC (databases, spreadsheets)
Exploration & Mining Software
Earthworks, GDM, Medsystem, Micromine, Surpac, Vulcan, Wavefront, Wescom
GIS
ESRI
Text
ASCII ( comma, tab and other delimited formats)
These driver categories allow the import and export of the following import data types:
General data tables Drillholes Points Block Models Strings Wireframe volumes and surfaces
Data Management
35
Figure 34: The Load and Export groups in the Data ribbon
In the Data ribbon in Studio RM the commands relating to import of data are as follows: Command
Description
Load | External
Import data to, or export from, a program. The drivers support a variety of data types including CAD files, RDBMS tables, spreadsheets and a selection of third party data formats.
Load | Database
Imports from any data source with a defined ODBC connection, including Datamine Fusion , Acquire®or Datashed.
Load | DHLogger
Imports drillhole data from a Datamine Fusiondatabase using the Fusion Connexdrivers.
Load | Hole Wizard
Runs a generic drillhole data load wizard.
Once a data file from another source has been imported into the current project, the following commands can reload, unload, refresh and export the data: Load | Reload
Refresh a selected object from the data source using different import options. A second option is to reload all data.
Load | Refresh
Refresh a selected object from the data source. A second option is to refresh all data.
Data Management
36
Load | Unload
Remove one or more selected objects from memory.
Importing Files using Batch Commands
As an alternative to importing data via the Data Source Drivers, Studio RM offers a number of batch processes for importing data in fixed or comma delimited format. These allow file manipulation with no integrated graphics.
Figure 35: Data conversion processes
These commands can be found in the Data tab in Transfer | Text. The two most commonly used commands are:
Input DD and CSV Data (INPFIL ): creates an empty file (Data Definition with no records) and loads data into this empty file, from a comma delimited text file. Input DD and Fixed Format Data (INPFML): Creates an empty file and loads data into it from a fixed format text file. For more information on these batch commands refer to the Studio RM online help. Under Help | Contents you will be able to search the help file for “command table” this will list the available commands and processes available in Studio RM.
Digitizing directly in the 3D Window
Digitizing allows for the capture of vector information contained on paper, along with associated attribute information.
Data Management
37
It is generally necessary to add one or more fields to record information about data being generated. These additional fields (called attribute fields) allow you to filter your data when required. The names you choose to give these “User Defined” or “Attribute” fields are entirely up to you the only requirement being that they must not clash with any of the standard Datamine field names (see Appendix 3).
There are occasions where geological mapping or other mapped data have to be captured into Studio RM. With Studio RM, the mapped data can be digitized directly in the 3D Window. To achieve this, the map have to be scanned as an image file and can be imported into Studio RM as a .jpeg or .tiff or .bmp file. Once scanned, the image is imported into the 3D Window in the following manner: By using the Data ribbon and Load | External | 3D Data | Image , select the sectional, plan or data plan that has to be imported. Select the required image and press the Open button.
The Image Registration dialog box will appear.
o
Figure 36: The Image Registration dialog box
This dialog box can be manipulated and made larger of small simply by using the interactive controls at the side of the image box. To zoom in, use the roller on the mouse to zoom or out. Manipulate the view so that all relevant data can be seen, like co-ordinates etc. When the cursor is moved across the image, you will notice that is in the form of cross-hairs. On the image, select the first reference point and select (left click). It will be observed that a new line will be added in the bottom part of the Image Registration dialog box. In this new line the respective X,Y and Z co-ordinates will be inserted.
Data Management
38
Figure 37: The coordinates of the georeferenced image positions
It is recommended that the coordinates for at least four reference points should be inserted.
On completion, select the OK button. The image will then appear in the 3D Window in geographic space.
Figure 38: The image appears in the correct position in the 3D window
It will be observed that in the working directory there will be two files now: the srcinal .tif file and now a .tifx file. In the case of the image being unloaded from the 3D window, the next time this image is required, simply drop and drag the image into the 3D window and it will automatically be georeferenced. The file that is automatically created with the same name as the srcinal file (except for the x suffix to the extension) is a world file that contains the registration details of the georeferenced image.
To draw (digitize) directly on this image, create a section by two points (View | Sections | 2 Points), then right click at both end of the image in the 3D window The user can then proceed to use the string tools to draw the required geological information as strings and points in Studio RM.
Figure 39: Draw on the georeferenced image in the 3D window
Data Management
39
Exporting Data Exporting data is effectively the reverse of importing. It reads a Datamine format file, and using the appropriate Data Source Driver, it creates and saves an external format file. You can export data in a variety of formats, and as with the Import facility you can access the Export function using one of several methods, including:
On the Data ribbon select Export | External and choose the correct option from the list. Right-click a file in the Project Files control bar and select Export from the context menu. In the Data Object Manager dialog select an object to export from the list and click the Export Object button. In the Sheets control bar, right-click on an object and select Data | Export from the context menu. A loaded object can be exported straight to Microsoft Excel® by right clicking on the object in the Sheets control bar and selecting Data | To Excel from the context menu.
Creating and editing Datamine files using the Data mine Table Editor The Datamine Table Editor is a powerful, intuitive tool for viewing, creating and editing Datamine files. The Table Editor contains templates which define the data and set default values for all the main Datamine file types including:
Points
Strings
Wireframe points and triangles
Block models The Datamine Table Editor is very similar in appearance to a spreadsheet and allows you to perform all the standard operations available within spreadsheets including:
Creating new data tables
Adding data columns and /or records
Using formulae to populate fields
Editing data
Data Management
40
Figure 40: The Datamine Table Editor
Exercises Exercise 1: Importing Topography Contours from a CAD File In this exercise you will import topography contours data from the file _vb_stopo.dwg (AutoCAD DWG 2000 format), and generate the Datamine format (.dm) strings file stopoi.dm. The CAD drawing file has the following data characteristics:
Polylines: represent topography contours and a bounding perimeter
Contour interval: 10m
Elevation range: 60 - 250m
X-coordinate range: 5,610 - 6,780m
Y-coordinate range: 4,600 - 5,779m
1. Display the Project Files control bar and select the Import External Data into the Project toolbar icon. 2. In the Data Import dialog, select the Driver Category [CAD], and select the Data Type [AutoCAD(strings)]. 3. In the Data Import dialog, click OK. 4. In the Open Source File (CAD AutoCAD ) dialog, browse to . C:\Database\MyTutorials\GeolMod , and select _vb_stopo.dwg 5.
In the Open Source File (CAD AutoCAD) dialog, click Open.
6. In the Read Drawing File dialog, select Load All Layers, and click OK. 7. In the Import Files dialog, Files tab, clear the Points File and Table File check boxes. 8. Define the Strings File name as " stopoi". 9. In the Import Fields tab, define the Datamine Colour Field as [COLOUR] (which should be set by default anyway)
Data Management
41
10. Select Use legends to resolve Datamine color values, and click OK. 11. In the Project Files control bar, Strings folder, confirm that the file stopoi is listed. 12. Display the Files window using the Home ribbon's Show menu. 13. In the Project Files control bar, left-click the file stopoi. 14. In the Files window, confirm that the file's field Name, Type, Precision and Size parameters are as shown in Figure 41.
Figure 41: The file parameters in the File window
15. Save the project file using the Project button and Save. Your imported and saved topography contour strings table stopoi can be checked against the example file _ostopoi.
The number of records in the string table can be checked using the following steps: •
In the Project Files control bar, selecting the Strings folder
• In the Files window, selecting stopoi and checking the value listed under Rows (the value should be 1828).
16. In the Project Files control bar, select the Strings folder. 17. Right-click the stopoi file, select Preview. 18. In the Preview dialog, check that your contours are as shown in Figure 42.
Data Management
42
Figure 42: The Preview window
19. Rotate the 3D preview using the left mouse button. 20. Close the dialog when you have finished previewing the topography contour data. The Preview option can be used to preview any Datamine-format files (only 3D objects). It provides a quick view of the 3D object before it is loaded in the Design window for modeling purposes, or used for data processing. In addition Datamine files can also be previewed (right-click, and select Preview) in the Explorer Widow before adding files to the project.
Exercise 2: Re-importing CAD data In this exercise you will re-import the topography contours data from the file _vb_stopo.dwg (AutoCAD DWG 2000 format) to regenerate the Datamine-format (.dm) String file stopoi.dm.In this lesson, you will re-import the topography contours data from the file _vb_stopo.dwg (AutoCAD DWG 2000 format) to regenerate the Datamine-format (.dm) String file stopoi.dm.
Please note the following: •
The file is re-imported using the import parameters that are stored in the project file as defaults. These parameters were generated and saved to the project file when the file was first imported.
•
This feature can be used to simply and quickly re-import a data file that has been updated with new information, e.g. a CAD topography drawing which is updated on a monthly basis with the latest survey measurements.
•
As an alternative, the CAD file could also be loaded directly into Studio RM without generating a *.dm file. This is done via the Data ribbon's External | Other menu option which also makes use of the Data Source Drivers. One advantage of loading (rather than importing) the CAD file is that every time the project is opened, the loaded CAD reference data is refreshed; new records that have been added to the CAD file will then automatically be displayed. The loaded CAD data can be refreshed at any time using the Refresh context menu option in the Loaded Data control bar.
Data Management
43
When to import and when to load: •
Import a CAD file when you wish to process or manipulate the data.
•
Load a CAD file when you only wish to use it as unmodified reference data for modeling or visualization purposes.
1. In the Project Files control bar, select the Strings folder. 2. Right-click the stopoi file, and select Re-Import. 3. Check the progress of the re-import process, using the progress bar.
Additional Exercises Additional Exercise 1: Questions about data management in Studio RM Please answer the following questions: 1. Explain the difference between single precision and extended precision Datamine files. 2. Explain in terms of the file structure, how a Datamine wireframe triangle file relates to a Datamine wireframe points file. 3. What data is stored in the A0 and B0 fields in a Datamine drillhole file? 4. Mention more than one way to add a new field to a Datamine file. 5. How can you import a CSV file as a Datamine file without using the Data Source Drivers?
Data Management
44
C HAPTER
4
DATA VISUALIZATION In this chapter, you will learn to:
Navigate in the 3D visualization window in Studio RM
Load and update objects in the3D window
Define and change view sections in the 3D indow w
Work with section definition files
Synchronize views between viewingwindows
Principles Once data has been loaded in your Studio RM project, these objects are now available for viewing, interpretation, modeling and plotting in all relevant windows (see Chapter 2 for an overview of the Studio RM interface): This chapter deals with the tools available for managing the data views in the 3D visualization window. The 3D window is the main window used for string and wireframe modeling, interpretation of drillhole data and mine design. Viewing Data Objects The following data objects are treated as 3D data by Studio RM and can be viewed in the 3D and Plots windows:
Static drillhole traces
Dynamic drillhole traces
Points (survey points, mapping and sample points) Strings (topography contours, geological strings, pit design crests and toes, survey measures) Wireframes (topography surface, geological surfaces and volumes, pit surfaces and underground workings) Block Models (geological and mining models)
Figure 43: Example of various data t ypes displayed in the 3D window
Data Visualization
45
The common theme in the above file types is that they represent data having X, Y and Z coordinates which allow them to be displayed in a 3D environment. Other data types such as geology logs cannot be loaded and viewed in the 3D window. A dedicated Logs window exists for this purpose. If a file has not been loaded into memory in Studio RM, it cannot be viewed in the 3D window. In other words, only loaded objects can be viewed in the 3D window.
Studio RM has the very powerful capability to create, modify and view specific items. Each data file loaded into Studio RM is regarded as an object whether it represents tables, points, wireframes or anything else. A single object (e.g. an orebody block model) can be loaded multiple times. With each instance of the object being formatted, edited and added to independently. Once data has been loaded into memory it is listed in the following locations:
Loaded Data control bar: A number of functions can be carried out on objects listed in the Loaded Data control bar including unloading, refreshing, saving and exporting. These functions can be accessed by right-clicking on the relevant object (see Figure 44).
Figure 44: Object reflected on the Loaded Data control bar
Sheets control bar: The Sheets control bar is used to control the display (i.e. visible/hidden) and format of all objects loaded into memory. This includes all projections, views and overlays related to a particular data window (see Figure 45).
Figure 45 - 3D and Plots Data Windows
The Sheets control bar is situated on the left of the data window area on a default system. It can be docked or floated, shown or hidden as any other control bar (refer to the Studio RM Interface module). Making extensive use of the right-click (context) menu system, the Sheets control bar can be used to access commands and functions related to both individual items,
Data Visualization
46
and groups of items, depending at which point in the data hierarchy a menu is selected. To hide particular objects simply uncheck the tick box next to the filename. 3D Visualization Window When a new Studio RM project is initially created, or an existing RM project is opened which does not reload data on start-up, the 3D window will automatically be set to a horizontal (“ XY”) plane centred on the srcin ( X, Y, Z = 0, 0, 0). Both a Default Grid and Default Section are created. The Default Grid is set to be displayed automatically. The window represents plane whose orientation, dimensions, and location can be easily changed to suit the current needs ofayour project. To change the colour of the 3D window background, double click on the open space within the 3D window. An Environmental Settings dialog box will appear. More will be covered later in this Chapter on the Environmental Settings. Don’t forget that changing your background colour may require you to change the grid colouring as well depending on the colour you have chosen.
In addition, data objects can be ‘Previewed’ prior to loading them into memory. This option is accessed from the Project Files control bar
Multiple objects can be previewed at the same time. Each window is independent and can be sized. Data canonbeeach rotated, zoomed etc. Some formatting options do exist and can be accessed by right clicking window. Also note that as long as you have Studio RM installed on your machine, the option to preview also exists in Windows Explorer.
Understanding 3D Data 3D data is categorized into distinct data type categories, and although all share the same core functionality, each data type is supported by its own range of specific tools; for example:
Data Visualization
47
Wireframes surfaces have an option for adding texturing (i.e. in the form of an aerial photograph). Block Models have an option for dynamic section view controls. Drillholes have an option to display the collar and end position of each hole with different symbols.
Once a file has been imported – there are no sacrifices that need to be made due to the srcinal format of the file. If a DXF topography file was imported, for instance, and a separate aerial survey image needed to be applied according to the georeferenced data held within the image file, it could be applied to the surface model using the 3D window in an identical manner to if the srcinal topography file was in a native Datamine format. The 3D Window organizes its data into the following categories:
Points
Planes
Strings
Drillholes
Wireframes Block Models
Sections
VR Objects
VR Object Types
GVPs
Grids
The interrelation of these components is a key aspect of the 3D visualization system. Strings not only act as a visual aid or enhancement, they are also capable of acting as simulation control strings, guiding the route of a mobile VR Object along a predetermined path, according to the specified object settings (maximum acceleration, maximum turning angle etc.). Similarly, objects can be ‘dropped’ onto a surface and instructed to follow the topographical angles of the virtual scene during animation, if required. All of these data types sit within your virtual scene – the environment, which is also controllable. The 3D Environment Despite being part of a simulation, the level of control over how your scene is rendered permits many different effects. You can change the lighting (ambience, direction, strength, colour), if and how data is clipped (to focus on a particular section of the scene, for example) and whether any environment ‘fog’ is to be used (and if so; what color? How thick? Getting the idea?). Lighting can also be applied to individual objects, and these objec ts can be mobile. Animated sky ‘maps’ are also supported,
adding even more layers of realism to your virtual world. Once your objects are loaded and the environment set, you can then opt to create dynamic fly-throughs and simulations. Please refer to the online Help for more information. Navigational Controls The actions of the Navigation Controls (panning, zooming, rotating and taking sections) in the 3D window are dictated by the type of view mode that is operational at the time. This topic outlines the various options and methods for viewing data. Viewing options are controlled by a combination of modes and controls ;
Data Visualization
48
View Mode is a particular viewing state or setting that is applied to the 3D window view; all subsequent view controls will honor the currently active mode. For example, if in Look At mode, the Spin View control can be used to rotate the view around a particular point; whereas in Floating View mode, the view cannot be spun in this way. View Control is a command that will perform an action, such as setting or interactively changing the view direction. For example, the Perspective View toggle will automatically switch between a vanishing-point perspective and isometric view of the data.
There are various options to enable you to move around the workspace in the 3D window. Floating view
Allows you to navigate anywhere in the world. The current view point is the focus around which the data is rotated.
Look At mode
Allows you to fix the focus on a particular point. Movement is restricted so that you zoom, rotate and pitch around the selected point
Plan view
Data Visualization
Adjust the display so that the data is viewed in a plane projection, no matter what section you have taken
49
Look North, South, East or West
Adjust the view to show data looking towards the North, South, East or West
Looking North
Looking South
Looking East
Data Visualization
50
Looking West
Using a Wheel Mouse
If you have a wheel mouse, the wheel can be used in certain viewing modes to access the following functions:
Zoom In - rotate wheel forward
Zoom Out - rotate wheel backwards
Zooming with the Mouse Wheel will zoom around the cursor position.
In the Perspective view
, the view zooms by moving the camera.
If a Look Atpoint has been defined, then the speed of moving is based on the distance to the viewpoint. If the cursor is away from the view centre, then the Look At point is moved horizontally or vertically (relative to the viewport) to keep it in the new view centre.
The Look At mode can be activated by either:
Selecting the icon from the Viewribbon 3D window.
, the selecting your point of interest on the
Selecting a point on the 3D window, by clicking down on the m ouse wheel will centre that point in the 3D window, and toggle the Look At mode to active Also remember the following useful hints:
•
If you get disoriented, activate the View ribbon and select Align View or Lock View to return to a view that is orthogonal to the current section, then, if you are still lost, choose an object or viewpoint from the Viewpoint list to get you back to familiar territory.
•
When navigating around an immersive world, use the Look At command to move towards and around an object of interest. Once active, you can rotate the entire 3D scene quickly around the selected point, using the Rotate View command.
•
Use the Viewpoint list on the View ribbon to quickly move from one object or view position to another.
•
Use multiple windows (either split and/or external views) to allow you to retain each view at a particular point of interest. You can even lock one of these views to prevent any inadvertent movement during
•
•
visualization or digitizing. You can select data in any window, even External 3D windows. Similarly, you can digitize into any view, or orient it independently of other views. There is no theoretical limit to the number of views you can have, although a large number of views on a low-power system may cause some performance slowdown, particularly with large or numerous data objects in memory. When saving viewpoints, use a descriptive name to help you select the right viewpoint while navigating.
Data Visualization
51
Changing the View during Simulation Playback
Different view modes and controls can be accessed even during play back of a simulation, for example, you can:
change the Inside View in a vehicle to find a better driving position keep your view fixed on a moving object by choosing the Look At command and click on a moving object when inside a simulation object, keep your view fixed on another object, using a similar approach to above. The Look At object may also be moving in the simulation.
Setting Auto-Spin and Auto-Roll
An automatic spin animation can be activated in the following way:
Anchor your rotation point using the Look At icon. Hold down the < Shift> key and use the left or right arrows to start an automatic rotation of the contents of the 3D window. Subsequent presses of the relevant direction key can be used to speed up/slow down the rotation, or stop it and reverse direction. Similarly, you can use the up and down arrows to instigate an automatic roll.
Section vs. View – What is the Difference? Sections are working planes in 3D space which have user-definable location, orientation and extents parameters. They can be used for digitizing, slicing objects and viewing data within the 3D window. All sections are listed in the Sheets control bar, under the Sections folder, where their display can be controlled and managed using the context menus (by right-clicking on the folder or a listed section).
Figure 46: Difference between section and view
The distinction between section and view is important in the 3D window as they are independently managed. Figure 46 shows the difference between a section and view graphically. The red plane represents the section and the view is from the viewpoint of the observer (you!).
Data Visualization
52
Section
View
A flat 3D object, the position of which is determined by a central reference point, an azimuth and an inclination value.
An entity that governs from which position you view your data. It is the same as a 'camera' position and is defined by an X, Y, Z position, yaw, pitch and roll.
A section has a definable height and width, and can be visualized in 3D alongside your loaded data.
Although it is not a 3D object as such, you can display the position of all viewpoint names in their correct locations in the 3D window.
Sections are defined as 'Section Definitions'. One or more sections can be created within the same 3D window. What is a section used for?
as a way of creating a section through your data
View definitions are stored as 'Viewpoints'. One view can be assigned per data window (both fixed/split and external 3D views can support their own unique view). What is a viewpoint used for?
as a way of setting clipping limits in 3D as a plane upon which to design/snap/modify data as a way of fixing the camera to a position orthogonal to your current design plane (e.g. by locking a section).
Displaying your data from the most informative angle(s). As a container to store useful view orientations. As a way of focussing attention on particular aspects of your data.
Changing the View of an Unlocked Section In the 3D window, you can change the orientation of the view of an unlocked section by:
Setting a standard (default) view such as those found in the View | Zoom Fit button on the View ribbon.
Figure 47 - Zoom East and fit data extents
Saving a fixed viewpoint and using it later. Importing a table containing a collection of section definitions, and automatically aligning the view to one of them Moving the position of a section in an unlocked view, whereupon a locked view display will update accordingly Freeform mouse movement in Floating mode, using the
key: o
Rotate - key + left mouse button
o
Pan - key + right mouse button
o
Zoom - key +left & right mouse buttons
Data Visualization
53
Using any of the View ribbon's Pan, Zoom and Spin options, followed by interactive mouse movement.
Locking any view to the currently active section.
Selecting a 3D object and electing to 'look at' it.
Navigating in a parallel projection can feel counter-intuitive. The main reason for this is that as the 'camera' moves forwards, objects in the view do not appear to get closer, as they do not get any bigger. The only indication of forward motion is usually when objects start getting clipped by the view’s
front clipping plane. This can be a problem if you are trying to use the free-flight tools (i.e. floating), as any subsequent rotations around the camera may be confusing. It is recommended, therefore, that you turn on the Perspective mode when in Floating mode. Using a variety of the methods above, you will find it easy to locate the correct aspect for your 3D scene. Remember that these tools are useful not only in static scenes, but can also be selected prior to and during simulation playbacks. A Closer Look at the View Ribbon The View ribbon consists of five main categories used to control your current working plane (section) and the direction from which you view your data (view):
Figure 48 - View Ribbon
View
View – Commands used to change/control the view direction when looking at data in the 3D window.
Figure 49: View controls
Data Visualization
54
Sections
Sections – Commands used to change the orientation and position of the active working plane (the default plane on which all your design work will be done).
Figure 50 - Sections Ribbon
Clip
Clip – Commands used to control the width and type of clipping applied to the active section.
Figure 51 - Clip Ribbon
Viewpoints
Viewpoints – Commands used to store the current view point, or reset the view using a previously saved viewpoint.
Figure 52 - Viewpoints Ribbon
Data Visualization
55
Split
Split - Option to split the 3D screen into multiple screens – vertically or horizontally. Allows you to double the amount of views in the current tab, each of which can be navigated separately.
Figure 53 - Split Ribbon
Creating 3D Grids Grids allow the overall dimensions of data objects along the X, Y and Z axes to be effectively displayed in the 3D window. Whereas 2D grids make it difficult to interpret the extents of a 3D data object in a direction that is not orthogonal to the view, 3D grids provide more visually-informative feedback of the dimensions of the object using either 3D hulls, or flat grids applied to sections. 3D Grids are created in the Sheets control bar by expanding the 3D section object, and right-clicking the Grids folder. They can then be configured, and applied to the loaded data in the 3D window, or to a selected section. Any grids that you create are listed in the Grids folder. Right-clicking a grid in the Grids folder allows you to rename, copy or delete it, as well as access the Grid Properties dialog.
Grid Types
The Grid Type drop-down list in the Grid Properties dialog allows you to select a different type of grid. This is applied to the loaded object in the 3D window, or the selected section, when you click Apply. The available options are described in more detail below:
3D Hull: allows the grid axes to be visualized as planar regions, creating a 3D grid that encompasses the extents of the object in the 3D window. The grid can then be configured using the tabs in the Grid Properties dialog, and the Display Mode drop-down list.
Figure 54 - Grid Type - 3D Hull
Data Visualization
56
Active Section: creates a flat grid in the plane of the active section. The active section is displayed in the drop-down list in the Sections toolbar, in the main menu. By default, an infinite grid is created, and displayed over the active section. In the following image, the active section has been deselected in the Sections folder in the Sheets control bar, allowing the grid to be displayed more clearly.
Figure 55 - Grid Type - Active Section
Grid Display Mode
Within the Grid Properties dialog, the Display Mode drop-down list allows you to control the way the grid interacts with the loaded object (in this case, the wireframe) in the 3D window.
Figure 56 - Default Grid Properties - Display Mode
The following options are available:
Normal: displays only the areas of the grid which should be visible in the 3D world (see Figure 57).
Data Visualization
57
Figure 57 - Display Mode - Normal
Show Hidden Lines: displays all areas of the grid - areas which should not be visible in the 3D world are shown using a broken line style (see Figure 58).
Figure 58 - Display Mode - Show Hidden Lines
Always on Top: displays all areas of the grid using the same line style, regardless of whether they should be visible in the 3D world (see Figure 59).
Figure 59 - Display Mode - Always on Top
Displaying block model data in 3D Block model objects are probably the best objects to illustrate in detail the steps for creating sections and applying the Edit Interactively option for the on screen interactive widgets. Keep in mind that
Data Visualization
58
each data type (points, strings, wireframes, drillholes etc) all have their own unique set of formatting and display options. The 3D window is capable of displaying all standard Datamine block model data. The main viewing functionality includes being able to:
Import block model data from a wide variety of sources, using Studio RM's Data Source Drivers functionality. Display block model data as blocks, lines, points, quick sections or intersection sections. Animate block model data by building up a model set according to a nominated field held within the object's underlying database. You can set any existing object field as a sequencing
field for the purposes of animation. Interactively and dynamically view cross-sectional data, with graphical output displayed according to whichever legend you require.
Exaggerate block model cell sizes.
Access object information using the Information Mode function.
Block Models Overview In the mining environment, block models represent 3D shapes, volumes, tonnages and grades of solids such as ore zones, waste zones and other volumes of geological or mineralogical interest. Models are usually designed and made to be manipulated or processed in such a way as to enhance the understanding of the modelled situation/orebody. Block models consist of blocks, which are cubes or cuboids, packed together to fill the defined volume as closely as the block sizing criteria will allow. Viewing Options Several display types are available to you when displaying 3D representations of block models. You can choose to display your block model as any of the options shown in Figure 60.
Figure 60 - Display Type options for Block Models
Once the block model is loaded into memory, display options are set using an object-sensitive Block Model Properties dialog. The Block Model Properties dialog box can be accessed in one of the following ways:
Block Models sub-folder – by right-clicking on the relevant object and selecting the objects properties, e.g _vb_modore (block model) Properties.
Data Visualization
59
Figure 61: Loaded Block Model object listed in the Sheets | Block Models category
On the 3D window double-clicking on the displayed object. This will automatically open up that objects properties dialog box.
Figure 62 – Selecting to object to access the properties dialog box
Quick Sections
By default the block model is displayed as a single Quick Section through the data, as shown in Figure 63.
Figure 63: Quick Section through Block Model
You can adjust the position and orientation of this section by right-clicking the block model object in the Sheets control bar and selecting the Quick Section Controls option (note that this option is only available when an object is currently viewed as a quick section).
Figure 64: Accessing the Quick Section Controls
Data Visualization
60
This displays the Section Control dialog, which will allow you to reposition and reorient the section plane (see Figure 65).
Figure 65: Section Control for the Quick Sections
Intersection Sections
This display type uses the default or custom defined section to create an intersection section for the block model with the defined section's plane. By loading the block model into memory for a second time, you can define multiple intersection sections which can be displayed with different locations and orientations as shown in Figure 66.
Figure 66 - Multiple Quick Sections
You cannot view block model section data in conjunction with a sequencing animation.
Blocks
You can also view your block m odel as block model cells, with each block representing the total volume of a block model cell.
Figure 67 - Block Model displayed as blocks
Each block model cell can be coloured according to a legend key, as with all other block model view formats. Block views can also be animated according to a sequencing field (see the section on 'Block Model Sequencing Animations' below, for more information). Important - This is the most memory-intensive option, which may affect system performance adversely when viewing high-density block model data in conjunction with a restricted system hardware specification
Data Visualization
61
Points
It is also possible to view block model data as a cloud of points. These points, as with all viewing formats, are subject to colouring via an applied legend (or fixed colour). See Figure 68 for an example.
Figure 68: Block Model displayed as a point cloud
Point views of block model data can also be animated according to a sequencing field (see the section on 'Block Model Sequencing Animations' below, for more information). Lines
Another viewing option is to view your block model as a set of independent lines. Viewing a block model as lines helps to portray more of the geometry of a block model data set with less effect on system resources.
Figure 69 - Block Model displayed as lines
Line views of block model data can also be animated according to a sequencing field (see the section on 'Block Model Sequencing Animations' below, for more information). Displaying a Mixture of Formats
It has already been described how to show more than one section of the same block model on screen simultaneously. You can extend this functionality to show each loaded instance of a data object in a different way. To do this: 1. Load a block model file and view it in format A (e.g as a section view). 2. Load the same block model file again and view it in format B (e.g as filled blocks).
Data Visualization
62
Figure 70 - Block Model loaded twice a nd displayed differently in each overlay
As each object is independent, you could even filter one object to show a particular type of data only (for example, areas where grade values are above a certain cutoff), and superimpose, say, a points view to give an indication of the full orebody geometry. Block Model Sequencing Animations When viewed as blocks, points or strings, it is possible to apply a sequence animation. This animation can be configured and played back entirely from within Studio RM. You can even record the results to an AVI or WMV video file using the standard simulation recording functions. The Block Model Properties dialog for a data set viewed in this way allows you to select any numeric field in the block model file that can be used to define how the view of the model is configured on screen. For example, if you were to select the IJK field to represent the sequencing Control Projectif a order,control you could use the (right-click block model in the Files Sequence Controldialog bar then and select theSequence option - note thatthe this option is only available sequencing field has already been defined for the selected object ). This dialog is used to set up the start and end points of the animation, and to control playback on screen. Once an animation is setup, you can record the final screen activity to an external AVI or WMV file using the Simulation toolbar controls (for more information, refer to your online Help). It is not possible to define more than one sequencing field for each loaded object.
Working with Section Widgets Studio RM introduces an interactive approach to editing and positioning display sections in the 3D window. By default, sections are displayed without on-screen interactive widget controls. When the Edit Interactively mode is turned on, the widgets controls will surround the currently active section in the 3D window as shown in Figure 71.
Data Visualization
63
Figure 71 - Edit Interactively - Widgets Displayed
The Edit Interactively mode is a temporary mode; if you enter another command in your application (or even click outside of the application) you will automatically disable the widget display. There are three types of widgets available, and all are used to reposition the active section in realtime, honoring any existing clipping settings that are associated with the section.
Adjusts the reference point of the section in the direction of the normal of the section plane.
Changes the azimuth of the active section.
Changes the dip/inclination of the active section.
Working with Section Definition Files A S ection Definition is a numerical representation of the current section/view of your data. A section definition fileviews is a table containing references one or more section/view a variety of of a multi-pit wireframe withtoassociated drillhole data. arrangements (for example, The 3D window supports the import of section definition tables and will automatically detect if one is found in memory - allowing you to select any of the stored section definitions and apply them to the current 3D section. Note that you can only have one section definition file loaded at any one time. Attempts to load another file will result in the current one being closed.
Data Visualization
64
Exercises Exercise 1: Loading Data into the 3D Window In this exercise you will load data into the 3D Window. There are several ways in which data can be loaded into the 3D Window, namely:
From the dropdown menu, select Data. The Data ribbon will be displayed. In the Load group select the relevant data type from the drop down menu.
Figure 72 - Data | Load Ribbon
Locate the required file in the Project Files control bar and click and drag it into the 3D window. It is possible to select and load several files at once by holding down the or key whilst selecting each file in turn. Holding down the Ctrl button while dragging the selected file onto the 3D window, will allow you the option to apply a filter to the data on loading
Locate the required file in the Project Files control bar, right-click on it and select Load from the drop down menu.
Figure 73 - Project Files drag and drop
1. Using any one of the options explained to you above, load both the composited drillhole file (_vb_holesc) and the topography contours file (_vb_ltopo). Don’t apply any filters on loading the data.
Data Visualization
65
The 3D window is automatically zoomed to fit the very first data file being loaded. In this case the drillhole file. The view remains focused on the drillhole data even though the contour file has been loaded. In order to see the complete extents of all the data that has been loaded, select the option to Zoom Fit.
2. All available sections are displayed in the Grid Type drop-down list. Select a section, and click Apply in the Grid Properties dialog. The grid is applied to the relevant section. Exercise 2: Adding and Configuring 3D Hull Grids In this exercise, you will create a 3D Hull grid, and configure it using the [Grid Name] Properties dialog. 1. In the 3D window, type the keyboard shortcut " ua" to unload any loaded objects. 2. In the Project Files control bar, expand the Wireframes Triangles folder, and drag the _vb_qpitmergetr file into the 3D window using the mouse. 3. In the 3D window, confirm that the open pit design is displayed:
Data Visualization
66
Figure 74: _vb_qpitmergetr with default section
4. In the Sheets control bar, right-click the Grids folder, and select New | 3D Hull. 5. In the Grids folder, confirm that an object named "Grid" has been created - and a new grid is shown in the 3D window, wrapped around the pit data:
Figure 75: vb_qpitmergetr with 3D Hull
6. In the Grids folder, right-click Grid, and select Rename. 7. In the Rename 3D Object Overlay dialog, type "3D Hull" in the Name text box, and click OK.
Figure 76: Sheets | Grids | Rename 3D Object Overlay
8. In the Grids folder, double-click 3D Hull. 9. In the 3D Hull Properties dialog, confirm the following options are selected:
Grid Type: drop-down list, confirm that [3D Hull] is selected. In the Display Mode drop-down list, confirm that [Normal] is selected. In the Options tab, Line Formatting group, Line type: drop-down list, confirm that [Lines] is selected. In the Line Formatting group, select Fixed Intervals.
Data Visualization
67
In each Fixed Intervals box below the X, Y and Z check-boxes, specify a value of '20'.
In the Major line every N: box, specify a value of '10'.
In the Annotation group, confirm that Major lines only is selected.
Figure 77: Grid Properties dialog box
On the Advanced Options tab, Constraints group, confirm that Snap to hull is selected, click Apply.
Figure 78: 3D Hull properties box – Advanced Options tab
In the More Line Formatting tab, Minor line intensity % row, specify a value of '30' in each of the X, Y, Z and Border boxes, click Apply.
Data Visualization
68
Figure 79: Sheets | [Grid Name] properties box – More Line Formatting
10. Back on the 3D Hull Properties dialog, click Apply. 11. In the 3D window, confirm that the 3D Hull grid has been applied to the loaded object. 12. In the 3D Hull Properties dialog, click OK. The hull grid should be updated as shown in Figure 80.
Figure 80 - 3D Hull properties formatted
Exercise 3: Creating a Grid of finite size To create a grid of finite size, specify its dimensions as follows: 1. Unload all the data from the 3D window. 2. Load the vb_mintr file into memory (as an object). 3. In the Sheets control bar, expand the Sections folder. 4. Right-click the active section, and select [Section Name] Properties. 5. In the Section Properties dialog, Plane Dimensions group, select Use dimensions.
Data Visualization
69
Figure 81: Sheets | Default Properties dialog box – Plane Dimensions
6. In the Plane Dimensions group, specify the dimensions of the section plane in the Width: and Height: windows. 7. In the Section Properties dialog, click OK. The finite grid is displayed in the 3D window, in the plane of the active section.
Figure 82: Default Section of finite size
Try changing the section orientation using the Plan Section, North-South Section and East-West Section icons.
Exercise 4: Modifying Sections with Widgets In this exercise, you're going to load a demonstration block model and clip data in front of the active section. Following that, you will modify the section position, azimuth and dip using on-screen widgets. You also get to play with the widgets in subsequent exercises as they are an efficient way of moving the section in relation to loaded data. 1. Unload any data that may be loaded from previous exercises.
Data Visualization
70
2. Load the file _vb_mod1.dm into the 3D window using one of the methods demonstrated earlier. 3. Format the block model as blocks, with an 80% Exaggeration (leave the Show Fill and Show Edges properties as they are). 4. Use the Block Model Properties dialog to display a default legend for the [CU] data column. 5. Zoom in and fill the screen with the Copper grade model.
Figure 83: _vb_mod1 loaded in the 3D window
6. Change the 3D window screen to white ( a good option for screen captures for presentations and documentation) following these steps: a. Double click on the empty space of the 3D window. b. The Environmental Settings dialog box will appear. c.
Change the Background Color to Single – White. Click OK.
Figure 84: 3D Window Environmental Settings
7. Using the Sheets control bar, turn on the display of the Default Section. 8. Double-click the Default Section item to display the Section Properties dialog. 9. Click the East-West button and Apply to change the orientation of the section automatically to an inclination of -90 degrees. 10. Ensure the Use Dimensions check box is disabled. 11. Set the Clipping to Front and click Apply. 12. In the Section Plane group, disable the Fill check box and enable the Lines option. Click OK - one clipped model:
Data Visualization
71
Figure 85 - Section and front clipping a pplied
13. Using the View ribbon toggle ON the Edit Interactively button - widgets are added.
Depending on your zoom factor, some (or even all) of the widgets may be hidden as the section limit may extend beyond the edges of the screen, e.g.:
14. You can change the extents of the section by going back into the Section Properties dialog and enabling the Use Dimensions check box. The default 500x500 dimensions will be fine for this exercise. Click OK and the section limits will update:
Figure 86: Section extents limited by Use Dimensions
15. Click Edit Interactively again - now you should be able to see at least one widget of each colour:
Data Visualization
72
Figure 87: Widgets activated
16. Hover your mouse over the visible widgets (don't click yet). Each widget will expand as the mouse hovers over it, to show that it is selectable. 17. Widgets are available in the three colours indicated at the start of this topic; hover your mouse over one of the green widgets, left-click and hold the mouse button down. Now drag the section backwards/forwards - the section and clipped data will update in real time. 18. Reset the position, and this time move the Red widget to alter the azimuth of the section. 19. Finally, try the Blue widget to alter the dip. 20. Go back into the Section Properties dialog and reset the section to an East-West alignment. Click OK. Exercise 5: Adding a Second Section to your Scene In this exercise you will add a second section to the 3D window. 1. You should be looking at data from the completion of the previous exercise.
Figure 88: _vb_mod1 in the 3D w indow
2. After following the instructions of the previous exercise, the model data should be clipped in an East-West plane. You are going to add another section, this time in a North - South alignment. 3. Right-click the 3D | Sections folder and select New.
Data Visualization
73
Figure 89 - Sheets | Sections - New
4. As you move your cursor over the 3D window a new cursor type will appear which will be labelled ‘Select the first section reference point’ 5. Left click roughly at the position as indicated in the screen grab below.
Figure 90 - Selecting the position about which your new section will be drawn
6. Select the Orientation North - South option in the dialog that is shown, then click OK. 7. Right-click the 'Section' item that has just appeared in the Sheets control bar and rename it to 'North-South' 8. In the Sheets control bar, double click on the North-South section to display the properties dialog. 9. Select the Use Dimensions field to apply a 500x500 size to the section.
Figure 91 - Plane dimensions to restrict section to a finite size
10. Select the Back clipping option 11. In the Section Plane group, disable the Fill check box and enable the Lines option.
Data Visualization
74
12. Click OK to display the two sections in an 'X' alignment. Note how the data is now clipped in two directions. You may also have noticed that the second section does not have a grid overlay - this is because the current Default Grid item is only associated with the Default Section, not the one that you have just created (you'll learn more about section grids later in this tutorial).
Figure 92 - Data clipped in two directions
13. All available sections will be listed on the Sections ribbon under the Sections | Section dropdown.
Figure 93 - All available sections
14. Whichever section is selected, becomes the active s ection for the Edit Interactively option. 15. Select the North-South section from the dropdown list.
Figure 94: Selecting Edit Interactively to be applied to the Active Section (North-South)
16. The widgets will appear on the section display. Select the various widgets and drag them to new positions - you will find that the Default Section position and clipping remains static, whereas the second section applies additional clipping dynamically.
Data Visualization
75
Figure 95: Widgets appear on Active Section
Alternatively, the same can be achieved by using the Sheets control bar. Right-click on the NorthSouth section and select Edit Interactively.
Exercise 6: Loading an existing Section Definition File In this exercise, you will load an existing section definition file and use it to dynamically update the view of data in a locked data window. 1. Unload any data that may be loaded from a previous exercise. 2. A section definition file is just like any other table in Studio RM. For this exercise, drag the following items into the 3D window from the Project Files control bar: _vb_itsurfacetr.dm _vb_itholes.dm
3. From the Project Files control bar drag and drop the _vb_viewdefs file from the Section Definition folder into the 3D window. 4. Use the View ribbon to select Split | Vertically.
Figure 96: Split window vertically into two panes
5. With the left-hand window selected (highlighted), open the Sheets control bar. 6. Expand the 3D | Sheets | Sections folder - you will see that the _vb_viewdefs item has been created automatically - this is the 3D object containing all of the loaded section definitions.
Figure 97: New section definition object created
7. Right-click the _vb_viewdefs item to rename it to "Section Table" - this will rename the overlay and not the underlying data file.
Data Visualization
76
Figure 98: Available sections within the Section Table
8. Ensure the Section Table is the active section.
Figure 99: Select active Section Table
9. On the 3D | Clip ribbon, select the option to clip Outside. Only data lying within the predefined clipping srcinally setup when the section was saved will be displayed.
Figure 100: Apply clipping to the active section
10. On the 3D | Sections ribbon, click on the Next and Previous icons and watch both views update to show the new position of the section each time - each new position represents a unique definition held within the external file. The Section Properties dialog will also update dynamically to show the values associated with each section that is defined therein.
Figure 101: Moving through the sections using Next and Previous
Data Visualization
77
11. Keep clicking the Next / Previous icons until you have selected the flat horizontal section as shown below. Select None for the clipping so that all the data is visible.
Figure 102: Deactivating the clipping to display all data
12. With the left-hand window still selected, use the View ribbon to enable the Lockicon. The view will automatically update to show a plan view (that is - orthogonal to the selection section within the loaded section file). You should now be looking at something like the following:
Figure 103: Split screen (left) Locked to align view with section
13. Set the clipping back to Outside. 14. On the Sheets | Wireframes double click on the loaded wireframe file so that the Wireframe Properties dialog box appears. 15. Select the Shading option – Intersection. The wireframe will be represented on the 3D windows as a line of intersection between the active section and the wireframe.
Data Visualization
78
Figure 104: Wireframe Properties, Shading set to Intersection
16. Use the Next and Previous icons to select different sections within the loaded table - this time, the left-hand window will automatically update to show a view that is orthogonal to each section.
Figure 105: Split screen - moving through sections
Data Visualization
79
Figure 106: Split screen - moving through sections
17. Left-click inside either of the two data windows and use the Data ribbon to select Load | Unload | Unload All. Or use the shortcut key ‘ua’. The Section Definition file (Section Table) and the associated overlay (" Default Section") is unloaded along with all other visual data, and the Default Section is reinstated. 18. To remove the split windows, deactivate Split | Vertical. Exercise 7: Creating a Section Definition File using the 3D window In this exercise the user will learn how to create a section definition file. 1. Load the composited drillhole file _vb_holesc into memory. 2. By default the drillholes will be loaded onto the 3D window in a Plan view. 3. Activate the Default Section on the Sheets control bar.
Figure 107: _vb_holesc in the 3D window
4. You will notice that the drillholes are orientated along a fairly evenly spaced North-South grid (each row about 25m from the next). In this instance it would be wise to create each of our section lines along each line of drillholes moving from left to right, along a North-South orientation. 5. At this point you can deactivate the Default Section. 6. On the Sheets control bar, right-click on the Sections category and select New. By default the created section will also be a Plan section.
Data Visualization
80
Alternatively the same can be achieved by selecting the Section dropdown on the View |Sections ribbon.
The moment you move your cursor onto the window you will be presented with a cursor 7. and a dialog box asking you to ‘Select the first 3Dsection reference point’ . 8. Take your cursor and snap (using your right hand mouse button) onto the collar of any one of the drillholes on the very left hand side (the first line of holes).
Figure 108: Select the point around which the North-South Section will be anchored
9. An Orientation dialog box will appear. Select your desired orientation. Note that if you select By 2 Points, you will need to define that section line. For this exercise we are going to create true North-South sections. Select North-South and click OK. 10. If your newly created ‘Section’ is activated you will see the section and clipping extents appear on the 3D window.
Figure 109: New North-South section orientation
Data Visualization
81
11. In the Sheets control bar, right click on the newly created Section and select Rename. The Rename 3D Object Overlay will open. Rename the section as indicated below.
Figure 110: Rename 3D Object Overlay
12. In the Sheets control bar, right click on the section ‘ Section Definition’ and select Add Section.
Figure 111: Add additional sections
13. A new section will be created under the new Section Definition. The section will have the orientation information as described in the steps above, and will be labelled accordingly.
Figure 112: New section
14. Repeat Step 12 above to add another section to the new Section Definition. The new section added will have the same name as the section created in Step 12 above.
Figure 113: New section created as a copy of the previous, prior to further editing
15. Highlight the new section in the Sheets control bar. Right-click on the section in the Sheets control bar. In the context menu select, then select Set Plane | Plane by 1 Point .
Figure 114: Set section using 1 point
16. You will be presented with a cursor and a dialog box asking you to ‘Select the first section reference point’. Snap onto the collar of one of the drillholes on the second row of holes. Select a North-South orientation. Click OK.
Data Visualization
82
Figure 115: Use the cursor to select the new section position
17. You will notice that your active section line has moved to the second row of holes.
Figure 116: New section orientation
18. You now need to save the setting for this second section you have created. Since this section was a duplicate of the first (prior to changing the orientation and positioning), you have to select the option to Overwrite from the context menu. 19. Right click on the newly created sub-section and select Overwrite.
Figure 117: Use Overwrite to save new orientation to the highlighted section details
Data Visualization
83
20. The sub-section will be renamed to reflect the position of the section.
Figure 118: Section will be renamed automatically according to the section details
21. Repeat Steps 12 to 19 until sections have been created over the entire drilled area. In total you should have 8 sections.
Figure 119: List of sections created within the Section Definition object
22. Move to the Loaded Data control bar. Notice an object named ‘sectiondef’ was created. Right-click on it and select Data | Save as on the context menu. Save the files as ‘Extended Precision Datamine (.dm) File’. Save it to your projects folder.
Figure 120: Save Section Definition file to the hard drive
It is very important to note that this file is purely in memory until such time as it is saved. Had you unloaded the file, you would have lost all the work you had done until now.
23. Create a new 3D Hull Grid. Turn off the ‘Default Grid. 24. Make the new saved ‘sectiondef’ file the active section. This can be done by right clicking on the file in the Sheets control bar and selecting Make Active Section on the context menu.
Figure 121: Set as Make Active Section
25. It is important to note that tools for clipping and moving sections are all tied to the ‘ Active Section’. In this case our sectiondef file.
Figure 122 - Active Section
Data Visualization
84
You can now….
Apply an Outside clipping (the width of which will be dictated by what was srcinally set during the creation of your section). Use the options Wider
and Narrower
to interactively change the
section width. Or type in a section width into the option
.
You will have noticed that as you move from section to section, the currently active section within the sectiondef file is highlighted in the sheets window. If you are happy with your new section width, right click on the section in the Sheets control bar, and select Overwrite.
Figure 123: Saving any changes made to section
If you double click on the section now in the Sheets control bar, the section properties dialog box will be displayed. You will notice that the new saved section width has been saved. By default our selected Width of 25m is comprised of a front clipping of 12.5m and a back clipping of 12.5m. This can be edited on this interface. Remember to select Overwrite to save the new settings, and don’t forget to save the file in the Loaded Data or the Sheets control bar.
Additional Exercises Additional Exercise 1: Questions relating to data visualization in Studio RM Please answer the following questions: 1. Explain the difference between view and section. 2. Mention more than one way to change the position of a section. 3. How many sections can you have loaded simultaneously in the 3D window? 4. How can you set vertical exaggeration in the 3D window? 5. Explain what happens to the view orientation when you apply the section lock? 6. Can you move the view when a section is locked? Explain.
Data Visualization
85
C HAPTER
5
DATA FORMATTING In this chapter, you will learn to:
Use the various elements in the display hierarchy to control the displayobjects of
Work with legends to control the display of data
Work with overlays and templates to control the display of objects
Format the display ofdrillholes
Principles The Visual Hierarchy Studio RM windows (3D, Plots, Reports, Tables, Logs, etc.) represent data objects in memory according to both the structure and content of the underlying data in conjunction with specific views of this data (known as ‘overlays’). This chapter deals with the presentation of the objects across the various windows. Loaded data can be formatted so as to facilitate or enhance working with data in the viewing, interpretation, modeling and plotting processes. Formatting typically involves defining the following formatting settings:
Colours
Symbol styles
Line styles
Labels (annotation)
Attributes
And other display settings
The following formatting functions are available: Grid
define X, Y and Z grid spacing, line styles and annotation formats
Filters
filter objects by their attributes
Legends
define legends for formatting table data and data objects
Attributes
add and edit numeric and alphanumeric object attributes
Display format drillhole traces, drillhole columns, grids and objects using format settings Any or all of these tools can be used to present data in the most effective way. To fully understand how to use the various data formatting options, it is necessary to see how each object can be viewed in various ways without affecting the underlying data integrity. Studio RM makes it easy to format data in a variety of different ways, specific to each window (if required), and even to transform data from one format into another. This concept is handled by the provision of objects, overlays and legends.
Data Formatting
86
Objects Objects represent data in memory. Data objects contain the essential underlying string or numeric data that defines the ‘code’ for an object. This applies to both its geometry (if relevant) and other tabular data that can be presented according to sets of rules. In the 3D window every object’s display properties can be set using the Object Properties dialog (which can be accessed by right-clicking on the object in the Sheets control bar). In the Plots window, you can define how each object is represented by associating it with an overlay. You can also represent the same data in more than one way by creating multiple overlays. Overlays are created and formatted using the Format Display dialog. Display templates in the 3D window The 3D window display templates allow you to capture and restore an object's visual formatting settings in a convenient way. You can save one or more templates for each object type, and templates can be applied to any loaded data object of the same type (drillholes, points, strings, wireframes, etc.). Display templates for controlling the visual formatting settings of objects in the 3D window is new functionality in Studio RM.
Templates are stored alongside your project file, but can optionally be exported to an external file (.3dtpl) that can be transferred between projects and systems. Each of the respective 3D properties dialog for points, strings, drillholes, block models, wireframes and planes contain the same functions but you are restricted to applying templates only to the object type from which the template was srcinally created. You can also specify which template is to be the " default" for each object type; this will represent the formatting that will be applied each time a new object of that type is created/loaded. The basic procedure for creating a display template for an object in the 3D window is: 1. Load a data object of the required type in the 3D window. 2. Double-click on the object in the 3D window to display its properties. Or right-click on the object in the Sheets control bar to display the context menu. Select Properties.
3. Use the object properties dialog to apply the various formatting options (color, symbols, labels etc.) and visually check the results. 4. When you're happy with the visual formatting, open the Templates tab. 5. Select New. 6. Enter a name for the template and press - the new template will capture all of the current formatting of the overlay relevant to the displayed properties dialog. The basic procedure for applying a template to an object in the 3D window is: 1. Create a template using the procedure above. 2. Load an object of the same type in the 3D window. 3. Open the object properties dialog and select the Templates tab. 4. Select a Template from the main list and click Apply Template. 5. Click OK in the properties dialog and the template will be applied to the loaded object. To set a Default Display Template for a type of object in the 3D window, do the following:
Data Formatting
87
1. Create a template using the procedure above. 2. Open the object properties dialog and select the Templates tab. 3. Select the required default template from the Default template drop-down list. 4. Click OK. Overlays and Display Templates in the Plots window An overlay is, quite simply, a set of rules determining how an object is to be displayed in the Plots or Logs windows (or the Design window). The complexity of rules is up to you, for example, you could set up an overlay that displays a topographical wireframe as a red mesh, or you could use an overlay in conjunction with a legend to highlight visual characteristics such as ore grade classification (or even grade itself). Overlays are, in summary, the fundamental rule sets determining how an object is presented in the Plots or Logs windows (or the Design window). Overlays can be stored in data display templates which can be applied to more than one object, and can be used to create overlays automatically when an object of a certain type is loaded. Templates can also be created as external files, transferable to other projects. A data display template can contain a variety of information. In a simple form, a template could be used to, say, colour a wireframe red. This type of display template is relatively generic and can easily be transferred to other object overlays of the same object type (it is not possible to apply, say, a wireframe display template to a block model, for example). Data display templates can be used to:
Apply the same display format to multiple objects in memory.
Apply the same display format to objects in different projects.
Automatically create an overlay or overlays each time data of a particular type is loaded into memory.
Figure 124: Display templates can be used to apply overlays to multiple objects
Data Formatting
88
You need to be aware of the data type referenced in the display template for example, if a block model display template is set up so that a particular legend is used to display the presence of AU and the template was applied to a block model file, with no AU data column, data would not be drawn as expected. In this case the default display method would be used as it is not possible to match the information I the template with the contents of the file.
Legends Legends are optional formatting options that permit complex display of either numerical or string data according to more detailed rules about how data is to be interpreted. They can be seen as a ‘key’ to which the ‘code’ of a data object is matched, and subsequently displayed. Legends can be set up to interpret either ranges of data (e.g. AU grade values from 0.21 to 0.31 g/t to be shown filled with a
specific coloured bitmap tile, or can provide instructions on how to interpret individual values (e.g. show all ore grade categories stored as ‘WASTE’ in green). Legends can also be formed from conditional expressions (e.g. show all values above 10 but below 20 in transparent pink). An overlay can be associated with a single legend only, if legends are required. A legend is a convenient way of assigning a consistent but unique appearance to a predefined value or range of values. Creating and using legends makes the representation of data both distinctive and consistent between documents. The systematic use of legends can make the interpretation of data much more intuitive. Legends provide the tools for both editing existing legends and creating new legends. Filters, ranges, colors and display styles can all be set to facilitate the interpretation and presentation of drillhole and other data. Creation and editing of legends is controlled by the Legend Manager dialog which is available under Format | Legends. Four types of legends are available:
Legend Type
System
Description
These are necessary for the software to work properly. They cannot be edited or deleted, but they can, be copied and pasted to the other legend categories where the copies may be edited. They are not saved with the project; they are saved in the Legends folder (under ...Program Files/Common Files/Earthworks/Legends ). If the are not displayed by default display is enabled by a checkbox in the Legends Manager.
User
These are frequently used legends which are saved independently from the project. This category is to enable users to group commonly used legends together for easier selection and consistency of application. They can be edited and will be saved, as " User.elg" in the "C:\Documents and Settings\\Application Data\Datamine\Legends " folder. Note: If a project is sent to another user, any user legends, used by the project, will not be available to the new user.
Project
These are saved as part of the project. If a project is sent to another user, its project legends are available to that user. They can be edited easily.
Driver
Created automatically when data is imported to the host program using Data Source Drivers. Not displayed by default - Display is enabled by checking a box in the Legends Manager . Driver legends are listed as PROJECT legends but contain a prefix identifying the driver used to import the data.
Data Formatting
89
Displaying different data types using legends Many different types of alphanumeric and numeric data can be displayed distinctively using legends. A "value" is a specific numeric or string value to which a particular appearance (colour, linestyle, fill, symbol etc.) can be assigned. Values are often used to apply legends to coded data such as rock types, structure types and intensity groupings. Ranges are defined by an upper and a lower limit, and a colour and/or texture is assigned to the values that fall within the range. Filters are used to handle more complicated situations where simple values or ranges will not work. Filters are logical statements which define the conditions under which a specific legend appearance applies. Complex filters can be developed to map the variation of more than one variable. Once defined, a legend is available to all relevant data in all windows. Any changes made to a legend are applied to all data objects which are using that legend. So, in summary, each overlay can be represented by a single legend, but each legend can be associated with any number of overlays (why? Well, you might wish to view several different topographical meshes showing a gradient of colors according to the extent of the Z axis. In this situation, you set up a legend encompassing the minimum and maximum of all relevant objects, and apply the same legend to more than one object. It is for this reason that Studio 3 not only permits the sharing of single legend across multiple objects; it also allows you to save legend data as an external file and apply it to data objects in different projects. This is important if more than one project is to be compared. Format Display Dialog The Format Display dialog is used to define the display properties for currently loaded data in the Plots window. The options are set within tabs along the top of the dialog, with additional sub-tabs available. The Format Display dialog can also be used to format the display of objects in the Design window.
Figure 125
The Overlays tab used to specify object specific settings that will affect the way it is displayed in Studio RM. Selecting an object in the Overlays list will show the current format settings for that particular object. The sub-tabs displayed under the Overlay Format section of the dialog will change
Data Formatting
90
depending on the object selected. For example if the selected object is a drillhole file the tabs available are Style and Drillholes, however, if the selected object is a wireframe then the tabs available are Style and Color. The following table summarizes the various tabs available and what display settings they contain. Tab
Objects
Settings
Style
Strings, Points, Drillholes, Wireframes, Block Models
Determines the way in which data is displayed. For example if you select the Intersection radio button for a wireframe then it will be displayed as an intersection profile rather than triangle faces.
Color
Strings, Points, Wireframes, Block Models
Determines the colour in which the selected object will be displayed. You can colour objects using a legend or a fixed colour.
Symbols
Strings, Points
Symbols are used to highlight the terminal points of strings data. Symbols can be varied with regards to size, rotation and/or shape according to a particular field value. For example, it is possible to add a symbol representing the specific grade at key positions along a drillhole.
Labels
Strings, Points, Block Models
Labels are used to annotate objects in the Designwindow.
Drillholes
Drillholes
Allows you to control the way in which drillhole data is displayed. This includes the hole name annotation, trace color, line style, line thickness and market symbols for collars, entry and exit points and end of hole. Downhole data can be displayed in a number of styles including text, line graph, histograms and color or pattern filled bars.
Advanced
Strings, Points
This tab is used to control the display of objects within the primary and secondary clipping regions.
Exercises Exercise 1: Creating a Unique Values Legend for Rock Type Codes In this exercise you are going to create a unique values legend for the set of rock type codes (field NLITH) found in the static drillholes file _vb_holes.
It is best practice: •
When starting a new project, define custom legends for data that will be regularly used for modeling, mine design and presentation purposes.
•
Define new color/texture/image standards for you various data columns (or use existing standards if they already exist) e.g. rock types, ore zones, grade categories, mine design elements, mine planning time periods.
1. In the Format toolbar, click Format Legends. 2. In the Legends Manager dialog, click New Legend. 3. In the Legend Wizard: Data Table Column dialog, select the Use Object Field option. 4. Select the Object [_vb_holes (drillholes)], select the Field [NLITH], click Next>. 5. In the Legend Wizard: Legend Storage dialog, select the Current Project File option, click Next>.
Data Formatting
91
Legends can be stored in three ways: •
Current Project File - these legends are stored in the current project file and are not available for use in other Studio projects.
•
User Legends Storage - these legends are stored in the external legend file user.elg , in the following locations, and are available to other Studio projects opened by the current user:
C:\Users\[Username]\AppData\Roaming\Datamine\Legends •
External Legend File - a single legend is saved to a user defined legend file (. elg), in any location, which can be loaded into any Studio RM project.
6. In the Legend Wizard: General dialog, define the legend Name as 'vb_holes_NLITH1'. The Type has been automatically set to [ Numeric] as the field NLITH is defined as a numeric field in the _vb_holes(drillholes) table.
7. Select the Unique Values option, clear the Convert to Filter Expressions check box, click Next>. 8. In the Legend Wizard: Data Range dialog, click Next>. 9. In the Legend Wizard: Coloring dialog, select the color range [Rainbow blue->red], click Preview Legend.... 10. In the Legend preview dialog, check that your legend is as shown below, click Close:
Figure 126
11. Back in the Legend Wizard: Coloring dialog, click Finish. 12. In the Legends Manager dialog, Available Legends group, check that the new legend vb_holes_NLITH1 is listed (expanded) at the bottom of the project legends folder, as shown below (do not close the dialog):
Figure 127
Data Formatting
92
Exercise 2: Editing the new NLITH Legend colours In this exercise you are going to define custom colours for the set of rock type codes legend created in the previous exercise. 1. In the Legends Manager dialog, Available Legends group, select vb_holes_NLITH1, if it is not already expanded, click the "+" symbol next to the legend name. 2. Select the legend item [0], move across to the details (right) side of the dialog. 3. In the Legend Item Description group, clear the Automatically generate description check box, define the Description as 'Soil'. 4. In the Legend Item Format group, select the Fill Color [Yellow 3], check that Line Color is also [Yellow]. If the Use fill for line colour checkbox is ticked (default), then the Line Color is automatically set when the Fill Color is defined. Clear this checkbox to set line colors independent of fill colors.
5. Select the legend item [1]. 6. In the Legend Item Description group, clear the Automatically generate description check box, define the Description as 'Sandstone'. 7. In the Legend Item Format group, select the Fill Color [Red], select the Line Color [Red]. 8. Select the legend item [2]. 9. In the Legend Item Description group, clear the Automatically generate description check box, define the Description as 'Siltstone'. 10. In the Legend Item Format group, select the Fill Color [Bright Green], select the Line Color [Bright Green]. 11. Select the legend item [3]. 12. In the Legend Item Description group, clear the Automatically generate description check box, define the Description as 'Breccia'. 13. In the Legend Item Format group, select the Fill Color [Magenta 1], select the Line Color [Magenta]. 14. Select the legend item [4]. 15. In the Legend Item Description group, clear the Automatically generate description check box, define the Description as 'Basalt'. 16. In the Legend Item Format group, select the Fill Color [Bright Blue], select the Line Color [Bright Blue]. 17. In the Legends Manager dialog, click Preview Legend. 18. In the Legend preview dialog, check that your legend is as shown below, click Close.
Data Formatting
93
Figure 128: The legend
19. Back in the Legends Manager dialog, click Close. Exercise 3: Creating a view template in the 3D window In this exercise you will create a view template for a loaded drillhole object in the 3D window.
1. Load the _vb_holes file in the 3D window. 2. Double click on the _vb_holes object in the 3D window to open its properties. 3. In the Lines & Symbols tab of the Drillholes Properties dialog box, apply the _vh_holes_NLITH1 legend to the NLITH column. Also change some of the other properties to match the properties in Figure 129.
Figure 129: Drillholes Properties dialog box
4. When you're happy with the visual formatting, open the object properties dialog and select the Templates tab.
Data Formatting
94
5. Select New. 6. Enter the name Holes1 for the template and press . The new template will capture all of the current formatting of the overlay relevant to the displayed properties dialog. 7. Select the Holes1 from the main list and click Apply Template. 8. Click OK in the properties dialog and the template will be applied. 9. Select the Holes1 template from the Default template drop-down list. 10. Click OK. 11. Unload the _vb_holes object from the 3D window. 12. Load the _vb_holes file in the 3D window. The new default template should automatically be applied to the _vb_holes object in the 3D window.
Additional Exercises Additional Exercise 1: Modifying a Legend to Use Fill Patterns In this exercise you are going to copy the legend vb_holes_NLITH1, created in the above exercise, then change the fill style from solid color to fill patterns.
Create a copy of the legend vb_holes_NLITH1.
Figure 130: The copied legend name
For the vb_holes_NLITH2 legend change the Fill Style for all the legend items to Texture and choose appropriate Texture File Names for each rock type in the list.
Figure 131: Texture Fill Style
Figure 132: The rock types with texture fills
Data Formatting
95
C HAPTER
6
DATA FILTERING In this chapter, you will learn to:
Use Studio RM’s Expression Wizard to selectively load data
Manage filters to applychanges selectively to objects in memory
Filter data file contents using processes like PICREC, JOIN and EXTRA
Use Retrieval Criteria to filterdata
Principles A filter is a mechanism for separating a subset of information from the whole data set, such that only the data you wish to load, display or process, is available; the rest is ignored. In Studio RM, filtering can be used in two main ways:
Interactive filtering. This will define a subset of data from objects loaded in memory and is being visualised in either the 3D or Plots windows. File Based filtering using Studio RM processes. These are processes are carried out on Datamine files which will create a new file containing the subset of data based on the input filter.
Filters use different syntax depending on whether the data is numeric, consisting only of numbers or alphanumeric, where the data can contain characters. This chapter will give a brief summary of the most common filtering techniques and how to access them. Interactive Filtering Interactive filters operate at several levels in Studio RM. The most commonly used are:
Filtering multiple objects based on data type on data that is loaded in memory. Filters can be accessed in the Filter group in the Format ribbon (see Figure 133).
Figure 133: The Filter group in the Format ribbon
The following quick keys can be used to filter objects in the 3D window: Filter Points
fp
Filter Strings
fs
Filter Drillholes
fdh
Filter Models
fm
Filter Wireframes
fwt
Filter Planes
fln
Data Filtering
96
An individual object can be filtered independently using the Data Object Manager.
To access the Data Object Manager dialog box use on of the following methods: • •
In the Data ribbon select Objects | Manage Objects. Right-Click on an object in the Sheets control bar and select Data Object Manager from the context menu.
For each of the methods, accessing the filter will bring up the Expression Builder dialog. This is where the filter can be set using the tools within the dialog.
Figure 134: The Expression Builder dialog box
The expression is built in the main area of the dialog and variables from the file can be selected in the variable selection by double clicking, else they can be typed manually. Note that all filters can be checked for their validity by clicking to see if the expression is correct.
Numeric Filters The standard numeric filter Operators (<, >, =, ! , =, >=, etc.) can either be written or selected from the buttons in the operator area. For example, the filter:
A U>1 This would return drillhole samples where AU was above 1. More complex filters can be used integrating the Logical Operators, (A ND , OR , etc). For example:
A U>1 AND ZONE = 1
Data Filtering
97
This would return all samples with AU above 1 and only those samples within Zone 1. Alphanumeric Filters: In the context of drillholes, filters are commonly used to restrict on the borehole ID. Alphanumeric filters require that the variable queried is placed between quote marks (“”). Alphanumeric filters require that the alphanumeric variable queried is placed between quote marks (“”).
Examples of some common alphanumeric filters are listed below:
BHID M ATCHES "VS *" This will retrieve all drill holes in the BHID field which start with the prefix “VS”
BHID MATCHES “VS05*”
This will retrieve a set of drill holes starting which contain VS05 as the root.
BHID MATCHES “VS05?”
To retrieve drill holes between VS050 and VS059 the syntax above can be used. The ? symbol represents any single character after the 5.
BHID> "VS 050" AND BHID< " VS06 5" To retrieve drill holes between VS050 and VS065 the syntax above can be used.
BHID="VS103"
BHID= "VS 080" OR B HID= "VS 095" OR B HID= " VS097 " OR B HID= " VS10 3"
To retrieve one drill hole simply add the entire BHID value within the quote marks.
To multiple drill holes in an area, the Logical Operator ‘OR’ can be used to combine the retrieve individual drillhole filters.
BHI D REGEXPR "J" Another function not commonly used but maybe useful in some operations is the Regular Expression function. Regular expression can be used to find any drill hole containing an alphanumeric.
The example above uses BHID as this is a common alphanumeric field, though of course these can be used for all alphanumeric fields such as Lithology, Texture or other descriptive fields. File Based Filtering File based filters work on the basis of running a process with a defined input file and an output file that will be created which contains the filtered subset of data. There are several command processes that can incorporate filtering; the most common are listed below. Command processes can be accessed by typing the name of the command in the command toolbar and then pressing to bring up the dialog:
Figure 135: The Command toolbar
PICREC command
The PICREC command enables the user to carr y out multiple filters in the interactive command window as described below.
Data Filtering
98
The command will need an input file entered. This is a file in your database which you need to filter. The output file is the area where you type the name of a file which will be created containing the subset of data.
Figure 136: The PICREC command dialog
After adding the input and output files, press, OK to active the command. The command toolbar will then turn yellow. This means that it is expecting a response. Enter your filter expression in the Command line.
Figure 137: The Command line highlighted in yellow
The same expressions can be used in the PICREC command that are used in the filtering expression above. In this example we can write; BHID MATCHES “VS10*” END
It is necessary to type E ND after your filter to tell the PICREC process that you have completed your filter.
In the Command window the filter summary results are written as shown in Figure 138.
Figure 138: The Command window shows the results
Filters can be combined using the logical operators. For example:
BHID MATCHES “VS05*” AND
A U>1 END In the case above, after typing the first filter, finish with an ‘ AND’ and then press enter. You will then
be prompted for another filter. Type END, when your filter is completed. When trying to filter drill holes on a certain area (underground or open pit) the PICREC command can be used. To use the PICREC command with coordinates follow the procedure below. Type PICREC into the command line and enter the Input and Output drillhole files, then push OK. (Do not change any of the settings in the Field, Parameters or Retrieval tabs).
Data Filtering
99
Enter into the command line the following statement based on your coordinates.
X>5903 A ND X<6300 A ND Y>4000 AND Y <4250 AND Z<20 E ND
Figure 139: The Command line showing the coordinates
Figure 140: The Command window showing the summary results
Once the PICREC command has run, a drillhole file is created. Note that if no records are written to the file try using OR instead of A ND .
COPY command
It is possible to create subsets of data by using the command COPY. The COPY command has a more basic means of filtering using what are known as Retrieval Criteria. This can be useful to quickly create a file using a simple filter. To use the COPY command with Retrieval Criteria, type COPY into the command line and the following box appears. Again you must define the input and output file in the File tab.
Figure 141: The COPY command dialog
Now open the retrieval Criteria tab. This is where you can add a simple filter. For example to create a new file based on ZONE, simply double click in the white area and type, ZONE = 1. Once the criteria has been defined, press OK. You will then see in the Output control bar, that the new file has been created based on the supplied filter.
Data Filtering
100
Figure 142: The summary results in the Command window
For more examples of COPY see the online HELP JOIN command
The JOIN command can be activated in the Data ribbon under Data Tools | Relational | Join . The JOIN command requires two sorted files and a designated key field to create one file. The JOIN command is commonly used on subsets data (i.e. drillholes). For example;
!JOIN
&IN1(XX1),&IN2(XX2),&OUT(XX3), *KEY1(BHID),*KEY2(FROM),*KEY3(TO), @SUBSETR=0.0,@SUBSETF=0.0,@CARTJOIN=0.0
EXTRA command
The EXTRA command can be activated in the Data ribbon under Data Tools | Expressions. EXTRA is a general purpose EXpression TRAnslator that allows you to transform the contents of files by modifying fields and creating new ones based on the values of existing fields. Again it is accessed from the command toolbar and expects an input and output file defined. Once the files have been defined, press OK to access the Expression Translator dialog. The filters defined in EXTRA are used in a different way than the previous methods described. The previous methods describe creating a subset of data based on a filter, though EXTRA is used to create and manipulate existing data using a variety of filters or functions. In the example below, a new field ‘DENSITY’ is going to be created based on the existing data.
Figure 143: The Expression Translator dialog
In the expression below, the first line is going to create a new column in the file named DENSITY where each record is assigned a value of 2.5
DE NS ITY = 2.5 The next line applies a condition stating that if the existing field ZONE = 1, then the value for the new field DENSITY will be assigned 2.6
IF (ZON E == 1) DE NS ITY = 2.6 END
Data Filtering
101
The next line applies a condition stating that if the existing field ZONE = 2, then the value for the new field DENSITY will be assigned 3.1
IF (ZON E == 2) DE NS ITY = 3.1 END You will notice that in the syntax for the IF statements, there is a single = and also a double ==. This is not a mistake! When using IF statements, the condition must firstly be in (brackets). Also to set a condition you must use a double ==. You must then set the assignment. That is to say, IF the condition ZONE ==1 is met, then DE NSITY = 2.6 . When assigning values, a single = is used. To complete the IF statement, it must finish with E ND .
It is necessary to type E ND after your filter to tell the PICREC process that you have completed your filter.
The statements above describing density can also be stated as one statement;
IF (ZONE == 1) DE NS ITY = 2.5 EL S EIF (ZONE == 2) DENS ITY = 3 .1 END Further commands from the Functions and Procedures can be used Further commands from the Functions and Procedures can be used but they must relate to the specific data types mentioned; Numeric Functions; String Functions; Procedures and Record Selection.
You will find that the EXTRA process contains some very advance functionality to enable you to manipulate and interrogate your data. Note that under the Functions and Procedures menu these apply to different data types. Please use the help files for further information.
Exercises Exercise 1: PICREC and JOIN and EXTRA to filter drillholes
It will be necessary to add the following files to the project you are working in. C:\Database\DMTutorials\Data\VBUG\Datamine\_vsdhz.dm (Drill hole file)
1. Use the PICREC function and select the input file as _vsdhz.dm, then enter the Output file as filename xx1. Leave all other Fields, Parameters and Retrieval criteria the same. Then press the OK button.
Data Filtering
102
Figure 144: The PICREC dialog box
2. Via the commands prompt window enter the following statement and select the tick button (Run Command).
BHID = "VS 001" E ND In the Output window the results are shown displaying 20 records in file xx1.dm. 3. Repeat the process by changing the Output file name to xx2.dm and select the drill hole file _vsdhz.dm as the drillhole file.
BHID = "VS 002" E ND 4. Via the commands prompt window enter the above statement and select the tick button (Run Command). In the Output window the results are shown displaying 35 records in file xx2.dm. 5. Use the command JOIN to link both files together, both files should be already sorted. Set the Output name to 2holes.dm. 6. Run the function called EXTRA and select the Input file called 2holes.dm. Exercise 2: EXTRA, PICREC, JOIN and COPY to update wireframes with information In this exercise we will use the EXTRA, PICREC, JOIN and COPY commands to write back grade and volume data to the wireframes so that when the information mode is active, different wireframe information is given.
It will be necessary to add the following files to the project you are working in: C:\Database\DMTutorials\Data\VBUG\Datamine\ •
_vsoretr.dm (Wireframe Triangle File)
•
_vsorepr.dm (Wireframe Points File)
•
_vsbmgrd.dm (Block Model File)
1. Unload all data from the 3D window. 2. Load the files _vsoretr.dm and _vsbmgrd.dm in the 3D window.
Data Filtering
103
3. In the Report ribbon select Evaluate Dynamic | Wireframes. Use the settings as shown in Figure 145. Please change the Block Identifier and the Grade Columns values as seen in the Figure 145. Press OK.
Figure 145: Evaluate Wireframe Properties
4. The Table view then appears with the grade categories for each of the wireframes. Press the Save Results button which saves the results to the Loaded Data command bar after a file name is given. Name the file res_ore in the Save Evaluation Results and press OK. 5. In the Loaded Data command bar, right-click on the res_ore file and select Data | Save As | Extended Precision Datamine | Save . The file has now been saved to the Project Folder. 6. Run the EXTRA process and select the Input file res_ore via the window which appears, enter the Output file name as res_ore1. Leave all other Fields, Parameters and Retrieval criteria the same. Then press the OK button. The Expression Translator window then appears, in the Expression dialog box type the following statement; S UR FA CE = B LOC K ID and then press the Test button to check the criteria. Next press the Execute button. 7. Run the PICREC process and select the Input file res_ore1.dm, then enter the Output file the name as res_ore2. Leave all other Fields, Parameters and Retrieval criteria the same. Then press the OK button. 8. Via the commands prompt window enter the following statement and select the tick button (Run Command):
S UR FA C E < 4 END 9. In the Output Window the results are shown displaying 3 records in file res_ore2.dm 10. Run the JOIN function and join the srcinal file to the results file. In the JOIN function select the Input file 1 name as vsoretr and Input file 2 as ore_res3. Enter the Output file name as called vsore2_tr. In Field tab select the KEY1 to read SURFACE. Then press OK, in the Command window it should report that 2114 records are stored in vsore2_tr.dm . 11. Run the COPY function and select the Input file vsorept and enter the Output file name vsore2_pt. Then press the OK button. 12. Load the wireframe called vsore2_tr into the 3D viewer window and double click on the wireframes and in the Wireframe Properties window select the Info Mode List. Select the Tonnes, Volume and grade (AU and AG) fields into the Info Mode List. 13. Interrogate the wireframes by selecting on the key board +?, then click on each of the available wireframes. The information dialog should appear with the relevant information.
Data Filtering
104
Additional Exercises Additional Exercise 1: Use SUBJOI to create a drillhole file with specific holes only In this exercise you will use a Studio RM process to create a drillhole file with only selected holes in it.
In the Datamine Table Editor create a new file (called list.dm) with only one field (BHID - A8) and add the following records to the file: o
VB2813
o
VB4270
o
o
VB4282 VB4287
o
VB4291
Use the SUBJOI process (Data | Data Tools | Relational | Subset Join ) to filter the above list of holes from the _vb_holes.dm file. The ouput file is filholes.
Figure 146: The Files tab in the SUBJOI process
Figure 147: The Fields tab in the SUBJOI process
Load the filholes files in the 3D window to view the filtered holes.
Data Filtering
105
C HAPTER
7
WORKING WITH DRILLHOLES In this chapter, you will learn to:
Understand the difference between static and dynamic drillholes
Validate drillhole data and buildstatic drillholes using HOLES3D
Composite drillhole data using COMPDH
Generate dynamic drillholes from an external database
Convert static drillholes todynamic drillholes
Produce isosurfaces from drillholes
Principles Drillhole data are often used as a basis for creating geological models. Studio RM has extensive specialised functionality to work with drillhole data. The functionality include creating desurveyed drillholes, compositing drillholes and displaying drillholes. Studio RM supports two mechanisms for creating and displaying drillholes. The first is the static method which uses the HOLES3D process and the second is the dynamic method which creates drillholes from data 'on-the-fly'. The principal difference between static and dynamic drillholes is that static drillholes are created as a desurveyed drillhole file, using a process, from Datamine format files; whereas dynamic drillholes use data in memory (from any data source) to create drillholes in memory. You can load many drillhole data tables into memory and combine them intelligently into a single Dynamic Drillholes object in memory, without altering the component data. It can calculate composite values "on-the-fly" and make changes to sample values automatically, immediately reflecting them in all composite values. Required data for creating drillholes in Studio RM The format of the source data is not important provided there is a driver available to load the data into memory. The desurveying algorithm requires certain data as a minimum before it can create drillhole trace and sample composites. The following drillhole tables are used to generate holes:
Collars - required; contains drillhole XYZ collar coordinate, coordinate system, coordination
and drilled date data
Surveys - required; contains drillhole survey depth, survey bearing and dip data
Assays - required; sample interval start and end depth, mineral grade or quality data; rock
density data
Lithology - required; sample interval start and end depth, lithology codes, short and long
descriptions; rock density data
Interval log(s) - interval start and end depth; interval data e.g. mineralized zone identifiers,
rock mass rating values
Depth log(s) - depth; point measurement data e.g. geophysical survey data, other download
log data.
Working with Drillholes
106
An Overview of Desurveying Desurveying a drillhole is the process of determining the actual X, Y, Z coordinates down a drillhole given the collar location and survey data. It is customary to survey a hole to obtain known values of the azimuth and dip at regular downhole distances along its length. From the collar location and survey measurements the actual X, Y, Z coordinates along the hole are then calculated. Studio RM represents drillholes according to the way that underlying program data has been created, based on the real-world location of definition points. Whichever method is used, it is important to understand that the data represented on the screen is an emulation of the actual drillhole position, shape and direction. There are two distinct types of data interpretation, based on the source of the data used to define drillhole strings; static drillholes and dynamic drillholes. The simplest method of calculating the coordinates down a hole is the straight-line method. In this method, the hole direction at each survey point is projected to the depth of the next survey point. This has the advantage of being very easy to compute. Coordinates at each survey point are computed directly by simple trigonometry from the position and orientation of the previous survey point. Unfortunately, this method leads to large errors which increase with depth through ignoring the fact that a drillhole is in fact continuously curved, and does not bend abruptly and only at points where survey readings happen to have been taken. In addition, there is a systematic bias in the interpreted coordinates, in that each surveyed direction is taken to apply for a length of hole below - but not above - the position of the measurement. A centred straight-line method avoids the bias problem, by assigning a given direction to a length of hole both above and below each measurement, half-way to the next higher or lower measurement. Unfortunately this method still does not account for the real curvature of the hole. What are 'Static' Drillholes? A Static drillhole is a single Datamine file which contains a set of X, Y, Z sample centre points, lengths and directions which represent the hole traces. The desurveyed file maintains the sample lengths and centre points as specified in the raw drillhole data. Static drillholes are created from physical Datamine files using the HOLES3D super-process. Please refer to Appendix 2 for the standard field names in a static Datamine drillhole file. As a minimum the following Datamine files are required as input for the HOLES3D process: •
COLLAR: Data file of drillhole collar locations. Expects fields BHID, XCOLLAR, YCOLLAR and ZCOLLAR.
•
SURVEY: Optional survey data file. Expects fields BHID, AT, BRG, DIP. If a borehole has Survey Data, then it must include a record for the collar location, i.e. AT=0. If a survey file is not specified it is assumed that all holes are vertical. If the survey file only includes a subset of the total number of holes, then it is assumed that all holes which are not included in the survey file are vertical.
•
SAMPLE: One or more sample data files (including the lithology file). At least one file is compulsory and must include fields BHID, FROM, and TO. It will probably also include at least one sample attribute field, such as grade or lithology.
Static drillholes are also known by the term "desurveyed drillholes" as they are desurveyed during the HOLES3D super-process.
Working with Drillholes
107
Figure 148: The commands and processes to create drillholes in the Sample Analysis ribbon
HOLES3D is known as a super-process, because it is a combination of Studio RM processes, including DESURV, HOLMER and JOIN. To display each individual process that is run by HOLES3D, you can change the V parameter to 1, when running the process.
The DESURV process produces a curved-hole interpretation using spherical arcs. The survey measurements are treated as unit vectors in 3D space in order that the dip and azimuth of each measurement is not treated independently. Between any two orientations, for a given (and known) downhole length, there is exactly one spherical arc between them. Knowing the coordinates of the first point, the coordinates of the second are uniquely fixed, as are the positions of every point between. Furthermore, since the spherical arc is tangential to the orientation at each survey point, curvature along the entire hole is guaranteed to be continuous, with no sharp angles as in any straight-line method. Starting from the known surveyed collar location the X, Y, Z coordinates are progressively calculated down the hole. The following default bearing and dip conventions are used when working with drillhole data in Studio RM: •
Bearings (or dip directions) are measured in degrees, zero at the North position, and measured clockwise (range 0 to 180 degrees)
•
Dips are measured in degrees, zero horizontal, positive down (range -90 to 90 degrees).
•
X coordinates increase towards the East
•
Y coordinates increase towards the North
•
Z coordinates (elevation) increase upwards
Figure 149 shows a highly exaggerated example of the deviation of a screen-based drillhole line segment from a real-world drillhole location. Note how the sample positions (shown as crosses) lie on the actual plane of the drillhole raw data, but the projected strings deviated both above and below this point. Also note the position of the interpreted collar position, offset from the real-world collar coordinates due the projection of the first line segment above the initial sample point (a deviation of this magnitude in reality is, however, highly unlikely to exist).
Working with Drillholes
108
Figure 149: Static hole trace with exaggerated sample lengths
Finally, it is important to note that the length of the sample along the real-world curvature of the drillhole is maintained in the flat-line segment, thus a 'gap' is created to compensate. Preserving segment lengths for flat-line segments is essential to preserve ore grade locations along the segment, so this issue is unavoidable. In addition to survey data the input data to the desurveying process is typically defined by a set of samples of known lengths and distances down the hole. For grade estimation it is best to retain the exact lengths of these samples, for length weighting, and to produce a set of (sample centre) points that lie on the calculated curved hole trace. However, it is not mathematically possible to do this and to also have the end points of adjacent sample segments exactly meet or have their end points also lie on the curved trace. Therefore, there will be instances whereby aspects of the known-length samples, comprised of vectors do not match raw X, Y, Z drillhole location points. However, for grade interpolation purposes, this is the most accurate method, even though the screen representation of the drillhole (a simulation, not an exact replication) may not match raw data in some points, including the collar location. The differences between real-world and interpreted screen data can be minimized by compositing or dividing samples into smaller segments before running the DESURV process. What are 'Dynamic' Drillholes? A dynamic drillhole (sometimes referred to as a drillhole trace, trace or drillhole string) is a set of X, Y, Z points that represent the location of the hole in space. Drillhole traces are calculated 'on-the-fly' by desurveying. Drillhole strings are calculated from drillhole data, which consists of collar coordinates, survey information and assay sample information etc. The traces are used in conjunction with formatting options to create a holes overlay for display purposes. This process differs from the way in which static drillholes are managed in that the in-memory coordinate data ensures that hole segments are drawn that meet exactly at their ends, and that the hole starts at exactly the collar position. It should be noted, however, that this is at the expense of retaining precise sample lengths, and the centre points of each sample are not maintained as being on the calculated hole trace as calculated from the spherical arcs interpretation. Figure 150 shows an exaggerated example of dynamic drillhole string projections.
Working with Drillholes
109
Figure 150: Dynamic hole trace with exaggerated sample lengths
Note that in this situation, sample lengths have been compromised, but the collar position is in the correct place. Also, the middle point of each string segment does not lie at the same position as the raw drillhole data. For this reason it is not recommended that this type of drillhole data be used for interpolation purposes. Subdividing Samples Figure 149 and Figure 150 show an extreme view of the data deviations that occur with both desurveying methods. Studio RM provides functions to enable this deviation to have minimal impact by creating smaller (and subsequently a larger number of) drillhole segments. This 'sample subdivision' is one of the Project Options available for handling drillhole data. When a static drillhole traces is calculated using the HOLES3D process, the survey data (azimuth and dip) of the sample is used to locate the sample centre point in space. A desurveyed drillhole file contains a set of samples each with a calculated centre point in XYZ world space. Sometimes raw drillhole data tables to be desurveyed may contain more than one survey record within one sample, each with different azimuth and dips. Since a sample is by definition a straight line its location in space cannot be calculated using more than one survey record. The SURVSMTH parameter is used to automatically divide up samples where more than one survey records lie within a sample. The samples are split in half until only one survey record lies within each sample. Therefore many samples may be created. The default value of SURVSMTH is 1 which will cause extra samples to be created so that no sample contains more than one survey record within its FROM and TO interval. For no extra samples to be created the SURVSMTH parameter should be set to zero. If the SURVSMTH parameter is set to zero and a sample does contain more than one survey record not all survey records will be taken into account. Traditionally this has been resolved by first compositing the samples to reduce their lengths. The SURVSMTH parameter avoids this requirement. It is often the case that the first one or two samples in exploration holes contain more than one survey record because they are relatively long. This is because sample divisions have not had to have been created through assay and lithological identification near the surface.
Dynamic or static holes? For the reasons explained above, drillhole representations have both advantages and disadvantages, and your choice of which one to use will be based on what you want to use the drillhole data for:
If you intend to use current drillhole data for the purposes of interpolating grades, a static drillhole will provide a more accurate result, but the displayed screen image will not match the raw drillhole coordinates along the full length of the drillhole if any curvature is present.
Working with Drillholes
110
If you wish to display your drillhole more accurately, particularly with regard to the collar positions, but aren't concerned with subsequent grade interpolation, a dynamic drillhole will provide the visual accuracy at the expense of less accurate sample positions.
What difference does it make? In reality it makes very little difference. The effects of differences between data and real-world coordinates, although increasing in line with the curvature of a drillhole along its overall length, can be minimized by a combination of the following actions:
Compositing prior to desurveying. Dividing samples into smaller segments before desurveying. Selecting the appropriate data type for the function you are going to perform (display or grade interpolation).
Validating drillhole data Data validation is an important step in the creation of both static and dynamic drillholes. Studio RM is tolerant of sampling gaps, overlapping samples and duplicated samples, which may be unintentional data errors. These are all detected and reported in an errors file (using HOLES3D) or reported to the appropriate sheet in the Reports window (using the Dynamic Drillhole comm ands). The following validation checks are performed on the data: When running HOLES3D to create static drillholes, you are encouraged to output the optional HOLESMRY and ERRORS files. You should also take careful note of the output display to see whether any warnings have been issued. If there are any warnings it is strongly recommended that you fix the data problems before using the desurveyed file for subsequent processing.
Gaps
Where there are gaps between samples, the values of all data fields within the gap interval will be treated as absent data when calculating composite values. Overlapping and duplicated samples
Studio RM's compositing algorithms handle overlaps and duplicate samples correctly without calculating biased results.
For duplicate records Studio RM uses the arithmetic average for grade values. For overlapping records, it uses a length weighted average value. There is no limit on the number of overlaps or duplicates for an interval.
Absent Data
Studio deals with absent data values encountered in a composite by ignoring them when calculating the weighted or dominant text value of the composite. If all samples in the composite have absent values, the composite value will be absent. If the Specific Gravity Weighting method is being used but there is no S.G. value then the weighting method will revert to standard length weighting. Weighting Method
The weighting of composite sample values may be by either Length or by weight (Length x Specific Gravity, assuming a uniform sample cross-section). Compositing Text Values
The dominant text value in a composite is determined by calculating the total length of each text value e.g. lithology codes, and assigning the value with the maximum length to the composite.
Working with Drillholes
111
Compositing drillhole data Compositing drillhole traces involves the splitting up or combining of consecutive drillhole segments into segments of either fixed or variable length, typically within a defined compositing ZONE control field. Compositing where drillhole intervals are split into standard lengths could be for geostatistics or grade estimation purposes. Compositing where drillhole segments are combined could be for modeling rock type or mineralization zone contacts or for visual validation. Studio RM has extensive drillhole compositing functionality to cater for a variety of options.
Figure 151: Compositing options in the Prepare Samples group of the Sample Analysis ribbon
The COMPDH process for compositing
The COMPDH process composites drillhole data down each drillhole in a static drillhole file. By use of retrieval criteria and a very large compositing interval, COMPDH can also composite over different rock types or seams. The input file must be in standard drillhole data file (as output by process HOLES3D). The output file of COMPDH is in an identical format. Up to a maximum of 20 explicit numeric data fields may be composited. These do not have to be specified; they are identified by the process as those fields which are not the standard ones (BHID, X, Y, Z, LENGTH, A0, B0, C0, RADIUS, FROM, TO ). Each drillhole is split exactly into fixed length composites for a length equal to the parameter @INTERVAL, starting normally from the collar; if the optional parameter @START is set, this is the
distance down the drillhole at which compositing will begin. If there is a gap between samples of less than or equal to a specified distance (parameter @MINGAP) it will be ignored; that is, the missing part will be assigned the grades of the whole composite. Any gap greater than this, but less than or equal to the parameter @MAXGAP , will be replaced by a dummy sample with the default values specified in the file. A gap larger than @MAXGAP will be taken to terminate the composite. If the total length of samples with non-absent grade values within a composite is greater than @MINCOMP, then the average grade of those samples is assigned to that grade field for the entire composite. If the total length of samples with non-absent grade values within a composite is less than @MINCOMP, then that grade field is assigned an absent data value for the entire composite. Weighting can be according to density and can also account for core recovery. Please refer to the online Help for more information. The COMPSE process for compositing
The COMPSE process composites a static drillhole data file by optimizing the composite interval using ore and waste criteria. The input file must be in standard drilhole data file (as output by the HOLES3D process). The output file of the COMPSE process is in a similar identical format, with the VALUE field positioned first in the file. The compositing depends on whether a specified numeric field in the input file is above or below a specified cutoff. Up to 20 explicit numeric fields may be composited at the same time, but they have no influence on which intervals are grouped together. These extra fields do not have to be specified; they are identified by the process as those fields which are not the standard ones. Standard field names are: BHID,X,Y,Z,LENGTH,A0,B0, C0,RADIUS,FROM,TO.
Working with Drillholes
112
The optimized compositing method works by applying a number of rules in turn. Please refer to the online Help for more information. The COMPBE process for compositing
The COMPBE process composites a static drillhole data file over horizontal benches. The input file must be in standard drillhole format (as output by process HOLES3D). The output file of the COMPBE process is in an identical format. Up to a maximum of 20 explicit numeric data fields may be composited. These do not have to be specified; they are identified by the process as those fields which are not the standard ones ( BHID, X, Y, Z, LENGTH, A0, B0, C0, RADIUS, FROM, TO ). The compositing method is shown in Figure 1. The drillholes are split exactly on horizontal bench elevations, unless the hole ends within a boundary, or the composite becomes longer than a specified length (by default twice the bench height). In the latter case, composites are split into the units of the maximum permitted length. Composites less than a specified minimum length (by default half the bench height) are ignored. A reference elevation is given by parameter @ ELEV and a bench height by parameter @INTERVAL . If there is a gap between samples of less than or equal to a specified distance (parameter @ MINGAP) it will be ignored; that is, the missing part will be assigned the grades of the whole composite. Any gap greater than this, but less than or equal to the parameter @MAXGAP, will be replaced by a dummy sample with the default values specified in the file. A gap larger than @MAXGAP will be taken to terminate the composite. If the total length of samples with non-absent grade values within a composite is greater than @ MINCOMP, then the average grade of those samples is assigned to that grade field for the entire composite. If the total length of samples with non-absent grade values within a composite is less than @ MINCOMP, then that grade field is assigned an absent data value for the entire composite. Please refer to the online Help for more information.
The COMPBR process composites drillhole data over horizontal benches, with additional computation of a recovered grade and recovered fraction for a specified field at a given cut-off.
Interactive compositor
The Interactive Compositor mode allows the user to interactively composite either dynamic or static drillhole segments in the 3D or Log windows. The selected composites can then be saved and analysed in the Compositor control bar. Creating Isoshells Previously, geological and grade interpretation could be challenging and highly subjective, with wireframe interpretations of geological data requiring section lines to be digitized manually. This process had to be restarted with each arrival of new data, and could take days to complete. The Create Isoshells (Structure | Create | Create Isoshells) process automates this procedure, allowing you to create complex shells directly from point sample data in drillholes ore chip samples in a matter of minutes.
Figure 152: The Create group in the Structure ribbon
Creating a resource model is an iterative process with greater understanding of the geology and grade distribution being achieved as the study proceeds, and more data becomes available. Isoshell wireframes can assist in this process: surrounding an area in 3D space, they allow boundaries
Working with Drillholes
113
between rock types to be delineated, and allow you to model the spatial distribution of grades by representing different cutoffs. Where controls on mineralization are unclear, Isoshell wireframes allow different levels of a lower cutoff to be investigated - providing a suitable domain for grade estimation.
Figure 153: Isoshells in Studio RM
The Create Isoshells process allows isoshells to be created from any point sample input, such as drillholes or chip samples, and is accessed as follows:
Using the Structure ribbon's Create Isoshells command (see Figure 152). Running the create-shells command in the Command line. (shortcut key "csh").
Figure 154: The Input tab in the Create Isoshells dialog box
The Create Isoshells dialog, Input tab allows you to select a sample file (usually a drillhole or points file), and associated coordinate fields. The field of interest can be defined, as well as isolevel values and the type of isoshells to be generated. The isoshells you produce can contain either Continuous or Categorical values – the type you select determines several subsequent options:
Working with Drillholes
114
Continuous - values vary continuously between samples and are assumed to have an infinite number of possible values - for example, grade. In isoshells created using continuous values, interpolated values between sample data are created. This type of value is numeric. Categorical - a specific set of values with no numerical relationship - for example, zone or rock type, as illustrated below. This type of value is numeric or alphanumeric. Samples with a specific target value are used rather than interpolated values.
The field which contains the values being interpreted must be selected, and an optional weighting field can be specified for the interpolation of Continuous isolevels values. Values can be added singly, or as part of a range, and are displayed in the right-hand side of the dialog. The Condition tab allows you to condition the input data before it is passed to the interpolator, allowing upper and lower limits to be imposed on the input samples. For Continuous isoshells, it allows you to transform data to a different distribution - converting it to the log of the input data, or mapping it to fit a normal distribution. If the input sample distribution is approximately lognormal, then the normal and log transformations will usually reduce the effect of high sample values. To produce a realistic estimated value of a point in 3D space, at least three srcinal sample points must fall within the search ellipse which is centered on that estimation point. A maximum of 10 samples is permitted - if there are more than 10 samples, then the nearest 10 samples to the point being estimated are selected. In order to achieve anisotropy for both Continuous and Categorical isolevel types, different radii and orientations can be specified for each axis. Orientations are defined by specifying rotations in degrees (-360 to 360) for up to 3 axes. The Estimation Parameters tab allows you to specify the parameters in the Estimation Search Ellipsoid for continuous isolevels. It also allows you to select the interpolation algorithm used to estimate values which lie between samples for Continuous isolevel types. Inverse Distance Weighting, or Ordinary Kriging estimation methods can be selected. The Inverse Distance Weighting method estimates values on a regular grid by weighting each sample by the inverse power of its distance from each grid point, and is the faster of the two methods. Ordinary Kriging, however, takes account of the spatial relationship between samples, and has the advantage of adjusting weights to compensate for the clustering of samples. The variogram model used for Ordinary Kriging has a zero nugget variance, with ranges and orientation defined by the search volume. The Volume tab allows you to define a bounding box within which isoshells are calculated. This provides the advantages of restricting the volume to a specific area of interest, and minimizing the effects of extrapolation.
Consider the following in terms of restricting the Isoshells: •
Horizontal extents are defined by the intersection of the Inside perimeter and Inside wireframe hulls, if defined. If these files have not been specified, the horizontal extent of the input sample file is used instead.
•
The maximum vertical extent is defined by the lowest maximum elevations of the Below wireframe or Inside wireframe hulls, if defined. If these files have not been specified, the maximum vertical extent of the input sample file is used instead.
•
The minimum vertical extent is defined by the highest minimum elevation of the Above wireframe or Inside wireframe hulls, if defined. If these files have not been specified, the minimum vertical extent of the input sample file is used instead.
•
If Align with search ellipse is selected in the Alignment group, then the bounding box is extended to enable the values specified for Below wireframe, Above wireframe, and Inside perimeter to be processed in world space. This means that ‘above’ and ‘below’ are always relative to the w orld vertical axis, regardless of any dip in the search ellipse.
Working with Drillholes
115
The Output tab allows you to specify output param eters for isoshells, including defining the Object Base Name, and Triangle Spacing parameters, as well as specifying different objects for each isolevel, and selecting whether to include volume boundaries in the isosurface. Low, medium or high levels of smoothing for Isosurfaces can also be specified. Isoshell wireframes are written into memory for visualization and analysis purposes only - if you require isoshell files, they must be explicitly saved.
Specifying Triangle Spacing allows you to define a value related to the size of the triangles used in generating the output. Larger triangles are processed faster, but produce coarser wireframes which may not show smaller structures. Triangle size can also be set automatically for the size of bounding box specified in the Volume tab by selecting the Calculate from bounding box. By selecting the Include volume boundary in isosurface option, isoshells are automatically closed where they pass through the bounding box boundary – otherwise they remain open.
Since wireframes must be closed to allow volumetric calculations and other wireframe processes to be run, it is recommended to select this option.
Exercises Exercise 1: Create static drillholes In this exercise you will use the process HOLES3D to desurvey a set of drillhole data tables to create the static drillholes file dholes.dm.
The drillhole data tables contain the following information: •
_vb_collars - collar coordinate, coordinate system, coordination and drilled date data
•
_vb_surveys - survey measurement depth, survey bearing and dip data
•
_vb_assays - sample interval start and end depth, Au, Cu and Density assay data
•
_vb_lithology - sample interval start and end depth, lithology data
•
_vb_zones - sample interval start and end depth, mineralized zones data.
Use Static Drillholes for the following: •
Drillhole compositing using COMPDH , COMPBE or COMPBR.
•
String modeling in the reference.
3D window using drillhole segment startpoints/midpoints/endpoints as a
•
Validation and visualization in the 3D window.
•
Grade estimation using GRADE or ESTIMATE.
1. Activate the Sample Analysis ribbon and select the Build Static button, click Desurvey Drillholes. 2. In the HOLES3D dialog, Files tab, define the Input and Output files shown below:
Working with Drillholes
116
Figure 155: The Files tab in HOLES3D
3. In the HOLES3D dialog, Fields tab, ensure that the fields are automatically set as shown below:
Figure 156: The Fields tab in HOLES3D
4. In the HOLES3D dialog, Parameters tab, define the settings shown below, and click OK.
Figure 157: The Parameters tab in HOLES3D
Check the description for each of the above parameters in the Help pane at the bottom of the HOLES3D dialog. Setting the parameter ENDPOINT to '1' will include coordinates for both the start and end of each sample in the desurveyed output file. These start or end coordinates can be extracted to a points table and used as the basis for generating DTMs.
5. In the Command control bar, confirm that all checks were successful, and that desurveying has generated the output file dholes which contains 732 records:
Working with Drillholes
117
Figure 158: The output of the HOLES3D process in the Command control bar
Your static drillholes dholes can be checked against the example file _vb_holes.dm
Exercise 2: Composite down drillholes In this exercise you will use the process COMPDH to composite the drillholes _vb_holes down their lengths, so that each composite contains a single rock type. This is done by using the rock type code field NLITH as well as the compositing "Zone " field, and by setting the INTERVAL parameter to 1000 (a distance greater than the longest continuous rock type interval according to the information in the lithology table _vb_lithology).
Use composited drillholes for the following: •
composited by rock type or domain (by setting a very large interval) to generate individual rock type composites to be used for rock type or domain boundary modeling.
•
composited by a fixed interval (e.g. minimum mining width or block size) for geostatistical analysis, variogram modeling.
1. Select the 3D window. 2. Activate the Sample Analysis ribbon and expand the Composite menu to select Composite Down Drillholes. 3. In the COMPDH dialog, Files tab, define the input and output files shown below:
Figure 159: The Files tab in COMPDH
Working with Drillholes
118
4. In the COMPDH dialog, Fields tab, define the fields shown below (be sure to select NLITH for the ZONE field, not LITH):
Figure 160: The Parameters tab in COMPDH
5. In the COMPDH dialog, Parameters tab, define the settings shown below, and click OK.
Figure 161: The Parameters tab in COMPDH
The combination of setting the ZONE field to NLITH (rock type) and the parameter INTERVAL to '1000', will combine adjacent sample intervals and generate composites which consist of a single rock type. These rock type composited drillholes can be used for modeling rock contacts in the 3D window.
6. In the Command control bar, check that the output file contains 129 records (compared to734 input samples):
Figure 162: The output in the Command control bar
Your output composite drillhole file holesc can be checked against the example fi le _vb_holesc.
Working with Drillholes
119
Exercise 3: Create a dynamic drillhole data object In this exercise you will use the Data Load Wizard to load and desurvey a set of drillhole data tables to create the dynamic drillholes object Holes.
The drillhole data tables contain the following information: •
_vb_collars_space - collar coordinate, coordinate system, coordination and drilled date data
•
_vb_surveys_comma - survey measurement depth, survey bearing and dip data
•
_vb_assays_comma - sample interval start and end depth, Au, Cu and Density assay data
•
_vb_lithology_comma - sample interval start and end depth, lithology data
•
_vb_zones_comma - sample interval start and end depth, mineralized zones data.
Use Dynamic Drillholes for the following: •
Advanced visualization in the 3D window.
•
Generation of drillhole Logs in the Logs window.
•
Plotting from the Plots window.
•
Validation of drillhole data in the Reports sheet.
•
Dynamic query and validation of drillhole data in Linked Views (Tables, Logs, Plots).
1. Unload all data by clicking into the 3D window and typing 'ua', then activate the Data ribbon and select Hole Wizard 2. If the Data Load Wizard dialog is displayed, click Next. 3. In the Data Load Wizard (Import Data Types) dialog, select the following data types, and click Next:
Figure 163: Import Data Types in Data Load Wizard
4. In the Data Load Wizard (Import Hole Collar Coordinate Tables) dialog, click Add. 5. In the Data Import dialog, select the following options, and click OK:
Figure 164: The Data Import dialog
Working with Drillholes
120
6. In the Open Source File (Text) dialog, browse to your project folder C:\Database\MyTutorials\GeolMod, select _vb_collars_space.txt , and click Open. 7. In the Text Wizard (1 of 3) dialog, define the settings shown below, and click Next>.
Figure 165: The Text import wizard
8. In the Text Wizard (2 of 3) dialog, define the settings shown below, confirming that the columns of data in the Preview group are separated by vertical lines, and click Next>:
Figure 166: The Text import wizard
9. In the Text Wizard (3 of 3) dialog, define the absent data setting as follows:
Figure 167
10. In the Text Wizard (3 of 3) dialog, select each data column in turn in the Preview group (use the horizontal slider bar to view the fields hidden to the right), define the column format settings shown below, and click Finish. Name BHID XCOLLAR YCOLLAR ZCOLLAR ENDDEPTH REFSYS
Working with Drillholes
Type Attribute Attribute Attribute Attribute Attribute Attribute
Property Alpha Numeric Numeric Numeric Numeric Alpha
121
REFMETH HOLETYPE ENDDATE Special Values: Absent Data Trace Data
Attribute Attribute Attribute
Alpha Alpha Alpha
-
Leave blank Leave blank
11. In the Define Drillhole Data Table dialog, define all seven of the Field Assignments as shown below, and click OK:
Figure 168: The Define Field Assignment
Define a Field Assignment entry using the following steps: • •
First select a required field item in the left pane Then select the corresponding import table field from the pane on the right.
12. Back in the Data Load Wizard dialog, click Next. 13. Repeat steps 5. to 13. for the surveys table " _vb_surveys_comma.txt" using the settings shown below:
Figure 169: The Text Import wizard
Working with Drillholes
122
Figure 170: The Define Field Assignment
Unless you want your holes to be pointing the air (never a good idea), make sure you ensure the Positive Dip Values Point field is set to Down.
14. Repeat steps 5. to 13. for the assays table "_vb_assays_comma.txt" using the settings shown below:
Figure 171: The Text Import wizard
Working with Drillholes
123
Figure 172: The Define Field Assignment
Figure 173: The Define Field Assignment
Select the Show all field assignments option so that the Specific Gravity field (DENSITY) can be assigned.
15. Repeat steps 5. to 13. for the lithology table "_vb_lithology_comma.txt" using the settings shown below:
Figure 174: The Text Import wizard
Working with Drillholes
124
Figure 175: The Define Field Assignment
16. Repeat steps 5. to 12. for the mineralization zones table (interval log) "_ vb_zones_comma.txt" using the settings shown below:
Figure 176: The Text Import wizard
Figure 177: The Define Field Assignment
Select the Show all field assignments option so that the Zone field ( ZONE) can be assigned.
17. In the Data Load Wizard dialog, click Next.
Working with Drillholes
125
18. In the Data Load Wizard (Load Complete!) dialog , define the settings shown below, and click Finish:
Figure 178: The Data Load wizard complete screen
19. Confirm that the drillhole traces have been loaded into the 3D and Plots windows. 20. In the Sheets control bar, confirm that the Dynamic Drillholes Overlay has been added to 3D and the Plots folders, e.g.:
Figure 179: The Dynamic Drillholes overlay in the Sheets control bar
21. Save the project file using the Project button and Save. 22. In the Save Data/Set Auto Reload dialog, clear all the Save check boxes, select all the Auto Reload check boxes, and click OK. Exercise 4: Create categorical Isoshells from static drillhole data In this tutorial you will create categorical isoshells from drillhole data for various rock values using the Create Isoshells dialog. Before you can create the Isoshells, you first have to create the wireframes used to bound the isoshells. You will use a macro for this. The macro identifies the top and bottom mineralized sample in each drillhole, and then creates upper and lower wireframes to constrain the isoshells.
Categorical values are discrete values, with no numerical relationship - for example, zone or rock type. Samples with a specific target value are used, rather than interpolated values. This type of value is numeric or alphanumeric.
1. In the 3D Window, type 'ua' to unload any loaded data. 2. In the Project Files control bar, drag the COMPS5 drillholes file into the 3D window (the file is located in the folder C:\Database\DMTutorials\Data\VBOP\Datamine ). 3. In the 3D window, confirm that drillholes are displayed (see Figure 180).
Working with Drillholes
126
Figure 180: The drillholes in the 3D window
4. Activate the Home ribbon and select Macro | Run Macro. 5. In the Select File dialog, browse to your project folder and double-click the macro file Start_End_Samples.mac (in the folder: C:\Database\DMTutorials\Data\VBOP\Datamine) 6. In the Command toolbar, type ' M1', and click Run Command. 7. Select Macro | Run Macro. 8. In the Select File dialog, browse to your project folder, and double-click Start_End_Samples.mac . 9. In the Command toolbar, type 'M2', and click Run Command. 10. In the Project Files control bar, Wireframe Triangles folder, confirm that the following wireframes have been created:
lowertr
uppertr
11. In the Project Files control bar, drag both wireframes into the 3D window. In the 3D window, confirm that the wireframes are displayed above and below the drillholes:
Figure 181: The bounding wireframe surfaces in the 3D window
The above wireframe files are also provided here: C:\Database\DMTutorials\Data\VBOP\Datamine.
12. Unload all data from the 3D window. 13. Use the Structure ribbon to select Create Isoshells. 14. In the Create Isoshells dialog, select the Input tab.
Working with Drillholes
127
15. In the Input group, click the Browse button by the Sample File box:
Figure 182: The Sample File browse button
16. In the Project Browser expand the Drillholes folder and double-click COMPS5. 17. In the Create Isoshells dialog, Input tab, confirm that the following fields are selected in the indicated fields:
X Field: [X] Y Field: [Y]
Z Field: [Z]
18. In the Input tab, select the Categorical (e.g. Lithography) option. 19. In the Value Field drop-down list, select [ROCK]. 20. In the Add Values From Range group, click the right-pointing Arrow button:
Figure 183: Add values
21. In the box to the right of the Values group, confirm that '1', '2' and '3' are listed:
Figure 184: Categorical values added
Working with Drillholes
128
Specifying Estimation Parameters 22. In the Create Isoshells dialog, Estimation Parameters tab, Estimation Search Ellipsoid group, enter the following values in the indicated fields:
X : '100'
Y : '100'
Z : '50' The search radii of 100, 100, 50 reflect the stratified nature of the orebody.
23. In the Create Isoshells dialog, Estimation Parameters tab, Rotations group, enter the following values in the Angle boxes for the indicated fields:
Z : '30'
X : '17'
Y : '0' As the orebody has a dip direction of N30ºE and a dip of 17º, the above rotation angles are used to align the estimation search ellipsoid with this structure.
24. In the Create Isoshells dialog, Volume tab, confirm that Align with search ellipse is selected. 25. In the Volume tab, select Below wireframe. 26. In the Project Browser dialog, expand the Wireframe Triangle folder and double-click uppertr. 27. In the Volume tab select Above wireframe. 28. In the Project Browser dialog, expand the Wireframe Triangle folder and double-click lowertr. 29. In the Create Isoshells dialog, Volume tab, confirm that Fit to data and boundaries is selected. Keep the dialog open. 30. In the Create Isoshells dialog, Output tab, Object Base Name box, type "ISO_ROCK". 31. In the Output tab, confirm that the following check-boxes are selected:
Calculate from bounding box
Different object for each isolevel
Include volume boundary in isosurface
32. In the Create Isoshells dialog, click OK. 33. In the Isoshell Report dialog, click Save to Project. 34. In the Project Browser dialog, Filename box, type "categorical isoshell report" and click OK. 35. In the Isoshell Report dialog, click Finish. 36. Isoshell Explorer In Windows browse the location of your project, and confirm that the Categorical Report.dm file, has beentocreated. Double-clicking Categorical Isoshell Report.dm will open the report using Datamine Table Editor.
37. In the 3D window, confirm that the isoshells are displayed:
Working with Drillholes
129
Figure 185: The categorical Isoshells in the 3D window
38. In the Sheets control bar, right-click the 3D folder, and select Hide All. 39. In the Sheets control bar, expand the 3D and Wireframes folders, and select each of the following wireframes individually, viewing the corresponding isoshells in the 3D window:
ISO_ROCK: (ROCK=1)
ISO_ROCK: (ROCK=2)
ISO_ROCK: (ROCK=3)
40. As each of the rock codes are represented by independent wireframes, set the properties for each one to display a single, fixed color:
ROCK=1: show in Red
ROCK=2: show in Blue
ROCK=3: shown in Green
41. You should now see a display clearly identifying the three rock shells:
Figure 186: The three rock type shells coloured in different colours
Additional Exercises Additional Exercise 1: Create continuous isoshells for AU grades from drillhole data In this exercise you can create continuous isoshells for the AU grades in the COMPS5 drillhole files using the following cutoffs: '0', '2' '4', '6', '8' and '10'. Use the same estimation and search parameters as you used in the exercise to create categorical Isoshells from drillhole data (you can use the Restore button to restore the settings you used earlier).
Working with Drillholes
130
Figure 187: The isoshells AU grade envelopes in the 3D window
Additional Exercise 2: Create a static drillhole file from a dynamic drillhole object In this exercise you will create a static drillhole file from the dynamic drillhole object loaded in Exercise 3: Create a dynamic drillhole data object. In this exercise you will use the Define Hole Tables utility to create the static drillhole object (Sample Analysis | Prepare Samples | Define Holes).
Use the Rebuild button in the Define Holes Table to build the static drillholes object (see Figure 188). In the Build Drillholes dialog box make sure that you have the Create Static Drillholes tick box ticked (see Figure 189). When the static drillholes object has been created, you have to save it (you can right click on the object in the Sheets control bar and select Save As from the context menu).
Figure 188: The Define Hole Tables dialog box
Figure 189: The Build Drillholes dialog box
Working with Drillholes
131
Figure 190: The new static drillholes object in the Sheets control bar
Additional Exercise 3: Create planned drillholes on a regularly spaced grid In this exercise you will create planned drillholes (RC holes) on a regular grid of 20m x 20m to increase the ore body knowledge. In general follow these steps: Load the _vb_stopetr/_vb_stopopt wireframe to get the topo surface.
Load the _vb_ugoretr/_vb_ugorepts wireframe to get the extent of the orebody. Use Grid DTMs (Structure | Operations | DTMs | Grid DTMs) to create a regularly spaced grid of points on the topo surface. Use the settings as shown in Figure 191.
Figure 191: The Grid DTMs command dialog box
Figure 192: The 20m x 20m drill grid in the 3D window
Working with Drillholes
132
Save the Drill Grid point object as a Datamine file (drillgrid.dm).
Run the COPYNR process (Data | Data Tools | Set Value | Add Record Number) on the drillgrid.dm file to add a list of numbers that will provide unique hole ID’s for every collar
position.
Figure 193: Data | Data Tools | Set Value | Add Record Number
Figure 194: The Files tab in the COPYNR process
Figure 195: The Parameters tab in the COPYNR process
Run the EXTRA process ( Data | Data Tools | Expressions) to create a collar file (pcollar).
Figure 196: The Files tab in the EXTRA process
Figure 197: The expression
Use the following expressions:
BHID;a8=join("BH",string(RECORDNO,0)) XC OL LA R =XPT YCOLLAR=YPT ZCO LLA R =ZPT
Working with Drillholes
133
erase(XPT) erase(YPT) erase(ZPT) erase(SYMBOL) erase(RECORDNO) erase(COLOUR)
Run the EXTRA process (Data | Data Tools | Expressions) to create a lithology file (plith).
Figure 198: The Files tab in the EXTRA process
Figure 199: The expression
Use the following expressions:
BHID;a8=join("BH",string(RECORDNO,0)) FROM=0 TO=300 LITH=0 erase(XPT) erase(YPT) erase(ZPT) erase(SYMBOL) erase(RECORDNO) erase(COLOUR)
Run the HOLES3D process (Sample Analysis| Prepare Samples | Build Static) to create a planned holes file (pholes).
Working with Drillholes
134
Figure 200: The Files tab in HOLES3D
Load the pholes file in the 3D window.
Select all the holes in the 3D window.
Figure 201: The pholes file loaded in the 3D window
On the Sample Analysis ribbon select Edit Drilloles | Intersect. In the Intersect Drillholes with Wireframes make sure your settings match the settings in Figure 202. Save the Intersections object as intersect.dm.
Working with Drillholes
135
Figure 202: The settings in the Intersect Drillholes and Wireframes dialog box
Run the EXTRA process (Data | Data Tools | Expressions) to create an updated lithology file (plith). Use the intersect file as input.
Figure 203: Files tab in EXTRA
Figure 204: The expressions
Use the following expressions:
if(INTSCT==1) FROM=0 TO=DEPTH
Working with Drillholes
136
ZONE =0 end if(INTSCT==2) FROM=prev(DEPTH) TO=DEPTH end if(INTSCT==3) FROM=prev(DEPTH) TO=DEPTH end if(INTSCT==4) FROM=prev(DEPTH) TO=DEPTH end erase(XPT) erase(YPT) erase(ZPT) erase(SYMBOL) erase(WRFM) erase(BLOCKID) erase(ENTER) erase(GROUP) erase(LINK) erase(SURFACE) erase(COLOUR)
Run HOLES3D again using the previous settings. (Use the Restore button).
Figure 205: The Files tab in HOLES3D
If the previous pholes file is still loaded in the 3D window, unload it first. Then load the updated pholes file. The pholes file now contain the expected intersections of the lithology zones (as updated from the wireframe).
Working with Drillholes
137
Figure 206: The updated pholes file in the 3D window
The steps in this exercise can be automated using a script. A macro will work for only parts of this process (all the processes, but not the commands).
Working with Drillholes
138
C HAPTER
8
WORKING WITH POINTS AND STRINGS In this chapter, you will learn to:
Create and edit pointsand strings
Save and erase point and string data
Accurately and quickly digitize using rapid digitize and snapping modes
Close open strings to create polygons
Combine strings
Extend, reverse and connect strings
Clip strings andgenerate outlines
Copy, move, expand, rotate andmirror strings
Translate strings
Condition strings to remove crossovers and corners
Condition strings to smooth it or toreduce the number of strings nodes
Break strings
Principles String Characteristics Regardless of whether you are a Geologist, Engineer, or Surveyor, the basic medium used for recording orebody interpretation, mine planning, and mine development are strings. Strings are used to define specific regions from which wireframes are generated to calculate volumes and or tonnes plus weighted grades. A string comprises one or more 3D points which are joined by a line. Each string has a start and an end point – in the case of a single point string this is the same point. By default the start of a string is denoted by a slightly larger symbol in the 3D window. A string object may contain a single string or multiple strings.
Figure 207: String PTN values annotated
Studio RM uses the following fields when writing string data to a file:
Working with points and strings
139
Description
Field Name Data Type
PVALUE PTN
Numeric
XP
Numeric
Eastinglocal grid coordinate
YP
Numeric
Northinglocal grid coordinate
ZP
Numeric
RL local grid coordinate
COLOUR
Numeric
Stringcolour
Numeric
Unique identifierfor each string Integer for each point on a string, where first point on string is PTN=1
These numeric fields are compulsory for all Studio RM string files and are used to record the string and point numbers, the coordinates, and the colour information, for each string. All compulsory fields are upper case. If you load a string file into the Design window and the file does not contain a COLOUR field, then the string will be displayed using the default colour of grey.
In addition to this, Studio RM will also support the following two additional fields to allow for varying point symbols and line styles. Field SYMBOL LSTYLE
Description Numericfield set to values between201 and 267 Numeric field set to values between 1001 and 1008
Default 201 (circle) 1001 (solid line)
A list of valid SYMBOL and LSTYLE values along with a description of all the main string file fields is available in Appendix 2 Studio Standard Fields.
You can think of the above field names as“Standard Fields”, these are field names that are reserved for Studio RM use. If you digitize some strings in the 3D window and write them out to a file, the file will contain all of the above fields.
Figure 208 - Example string file in the Table Editor
In addition to the standard Studio RM fields, it will usually be necessary to add one or more additional fields to your file to record information about the strings being generated. These additional fields allow you extra flexibility to filter your data when required. The names you choose to give these “User Defined” or “Attribute” fields are entirely up to you, the only requirement being that they must not clash with any of the standard field names (see section on Attributes for further information).
Working with points and strings
140
Point Characteristics Point files contain a minimum of five fields which define the X, Y and Z coordinates of each point, the symbol shape and the color of the symbol. The standard fields are: TYPE
STORED
XPT
FIELD
N
Y
The X coordinatevalue of the point.
COMMENTS
YPT
N
Y
The Y coordinatevalue of the point.
ZPT COLOUR
N N
Y Y
The Datamine color value to be used when displayingor plottingthe string.
SYMBOL
N
Y
The Datamine symbol type to be used when displayingor plottingthe point.
The Z coordinatevalue of the point.
Point files can optionally contain the following additional fields: TYPE
STORED
SDIP
FIELD
N
Y
Dip
COMMENTS
DIPDIRN
N
Y
Dip Direction
SYMSIZE
N
Y
Symbol Size in millimeters
In addition to these fields, points can have additional attribute fields which describe some property associated with the point such as a sample identification number or project area code. Some examples off point attributes are: FIELD SAMPID
TYPE N
STORED Y
Sample identification number for a soil or a stream sample.
COMMENTS
AREA
A
Y
The name of the project area from which the sample was taken.
Points are edited and manipulated using the same tools as those used for strings. What is the difference between a string and a perimeter? The term perimeter is used to describe strings that are“closed”. A string is closed if the first and last points are identical. You will find that the terms “closed string” and “perimeter” are used interchangeably. Does it matter if strings are clockwise or anti-clockwise?
No, you can digitize strings in any direction. Does the string number field PVALUE have any reserved values or ranges?
No, the only purpose of the PVALUE field is to ensure that each string has a unique identifier. The values themselves carry no significance in the 3D window. What determines the start and end of a string?
The starting point of a string is denoted by an enlarged point symbol. By default this is a circle whose diameter is twice the size of the other string points. The size can be modified usingSheets | 3D | Strings | - [string file name] properties.
Figure 209: Selected string symbol size adjustment
Note that a single string can only have one symbol, one line style and one colour that is consistent for the entire string
Working with points and strings
141
Snap Mode Dialog
The snap mode allows you to set specific conditions for inserting, moving, deleting, modifying data etc. The Snap Mode dialog is used to set how an overlay's data is snapped to when snapping is switched on, i.e. are we moving a point to snap onto a specific point on another string or do we wish to digitise a string ensuring it is snapped onto a wireframe surface.
Figure 210: Snapping ribbon
Five different snap modes exist within Studio RM. Snap To: select the snap mode:
Off: turns all snapping off. Point: snap to the nearest point i.e. including points, string segment mid or end points, wireframe triangle corner or centre point, etc. Lines: snap to the nearest line i.e. including any position along a string, wireframe triangle edge, etc.
Grid: snap to the intersection of the defined grid, whether visible or not
Surface: snap to the indicated position on the wireframe triangle's surface.
You can also set the specific overlays that are to be associated with the current snap mode settings. The current snap mode is clearly listed on the Snapping ribbon
Figure 211 - Currently selected snap mode c learly indicated
Working with points and strings
142
Figure 212 - Right mouse button - Snap mode
To access this dialog:
On the 3D window, activate the Home ribbon and select Snapping | Settings. These data snapping settings apply only to the objects (overlays) for the selected window i.e. these snapping settings are window specific. For example, if this dialog was opened when the Plots window was selected, then the defined settings only apply to the objects in the Plots window and not the 3D window. Note that if you 'snap' to data, you will automatically enforce selection of that data, regardless of what data selection options were previously set in the Overlay Selection dialog.
To select or not to select?
Many of the 3D commands allow you the option to either select a string prior to executing a command, or to activate the command first (with no active string selected) and then select the point on any string to carry out the command on. Should you wish to select multiple strings, for example to change all of their colours at the same time or perhaps deselect them all , hold down your key and left click on each strings you wish to select. Selecting a string the second time, deselects it. This is similar to selectingfiles inWindows Explorer®. The purpose of being able to select one or more strings is to be able to selectively edit those strings without affecting other data. Occasionally this is beneficial and we would say that the majority of the time, this is how you should work. Firstly, it is safer, in that your commands such as delete point or move point are restricted to the selected string only. Secondly, if two strings are lying directly on top of each other, selecting the correct one first, allows you to be sure you have chosen the right string for editing. Selecting data for editing
Different options available:
The settings for selection control are located on the Home ribbon Project | Settings, Points and Strings – Data Selection.
Working with points and strings
143
Figure 213: Project Settings - Data Selection criteria for Points and Strings
Left mouse click + left mouse click allows you to select multiple strings
String Manipulation Tools Many tools exist for the creation and manipulation of both strings and points. All these commands can be found on the 3D | Edit ribbon.
Figure 214 - Edit ribbon for Points and Strings
Undo Last Edit and Combining Strings
The Edit | Undo Edit (ule) command will undo the effect of the last string edit carried out. Note that this command will not work for all commands particularly those that involve the creation or removal of multiple strings. String editing commands that cannot be undone using Undo Edit (ule) include Edit | Erase | All Strings (eal). The Edit | Tools | Combine (com) command can be used to create a union between two overlapping strings. The command works by prompting you to select a segment on each of the two strings that you wish to combine. The strings being processed with this command can be open or closed. T h e r esulting string will contain the attributes from the first string that was selected. Use the Edit | Combine | Keep srcinals command should you not want the srcinal strings to be deleted. It is important to note the segments that are selected will remain; the rest of the string will be erased. Extending, Reversing and Connecting Strings
The Edit | Tools | Extend (ext) command allows you to add additional points to the end of a string. If you wish to add points to the start of a string then you will need toreverse the direction of the string first using the Edit | Condition | Condition | Reverse (rev)command.
Working with points and strings
144
Figure 215: String reversed
It is also possible to extend one string to another, using the Edit | Tools | Extend | Extend to String (ess).By changing the settingHome | Snapping | Snap | Snap Perpendicular (stpe) the extension of the string will be perpendicular to the second string. The Edit | Tools | Connect (conn) option allows you to join two existing strings together. The product is a single string. Unlike extending a string, you can connect two strings “end to end”, “start to start” or “start to end” depending on where you make theselection. The resulting string will contain the attributes from the first string that was selected.
Figure 216: Connecting two separate strings
Clipping Strings and Generating Outlines
The Outlines options generate closed strings using any existing open or closed strings to mark out areas of interest. The Outlines option is used when there is a need to generate two or more tessellated closed strings (i.e. strings that share common segments). Examples of such strings include bench blast outlines and orebody mark-up strings. In all these cases the strings are being used to delineate closed regions, and there should not be any overlaps between the regions. The blast mark-up designs in Figure 217 is a simple example.
Working with points and strings
145
Figure 217: Blast mark-up designs
While the outline strings could be created individually (using snapping where required), in practice this approach is slow and prone to error. It is preferable to digitize “construction strings” as illustrated in Figure 218, and then use the Outlines option to generate the closed regions.
Figure 218: Construction strings
Note that only one string (large rectangle) is actually closed– this is the outer boundary of the area of interest. The strings defining the internal boundaries have been defined using three open strings. Copying and Moving Strings
The Copy and Move commands by default allow you to make changes within the current Default Section. The exception to the rule would be if you chose to snap to an existing point (fixed x, y and z) at a different elevation. We will look at this during one of our exercises below. These commands all work by asking you to select a point on the string you wish to copy or modify and then select a second point to implement the change. All commands are fairly straight forward, you will just need to watch and follow the prompts in the bottom left hand corner of the Status Bar to successfully use these commands. Follow the prompts in the bottom left hand corner of the Status Bar to successfully use these commands.
The following commands allow you to move and copy strings.
Edit | Transform | Move (mo or
Edit | Transform | Move Section (mss or
Working with points and strings
) )
146
Edit | Transform | Copy (cps or
)
Mirroring Strings
The Edit | Transform | Rotate | Mirror String (smm or ) command draws a mirror image of a single existing string, reflected about a defined mirror plane. You will be prompted to select a string (if not already selected) and then define the mirror plane with two mouse clicks as prompted o n screen. The selected string will then be mirrored about the defined plane. The new string will be draw in the current Default Section.
Figure 219: Mirroring a string
The mirror plane must extend beyond the limits of the string being mirrored and the attributes of the srcinal string will NOT be applied to the reflected string.
Expanding and Rotating Strings
view plane. The Expand and Rotate commands will make changes within the current The following commands allow you to Expand and Rotate strings:
Edit | Tools | Expand(exp or
Working with points and strings
)
147
Figure 220: Select the expansion side of the string (above/below)
Figure 221: Specify the expansion distance
Figure 222: New string position
Edit | Transform | Rotate String (rstor strings: o
) command has four options for rotating
Rotate Rotates a string interactively about a fixed anchor point. When you run the command. You will be prompted to "Select anchor point on any string ". Select the anchor point and the willstring change Usingthe your left hand mouse button and the cursor selected will to rotate .about defined anchor point. The drag anglethis of cursor rotation and the azimuth in the view plane from the rotation point to the cursor location is reported in a dialog box adjacent to your cursor position.
o
Rotate By Angle Rotates the selected string(s) in the current view plane about a selected point by a specified angle. When you run the command you will be prompted in both the status bar (bottom left hand corner of the screen) and your cursor position on the screen, to "Select an anchor point on any string " or "Select an anchor point on any selected
Working with points and strings
148
string”. Select a point, and then the Rotate String dialog will open. Set the angle of
rotation as required and click on the OK button. o
Rotate to Azimuth Rotates a string about a selected point in the current view plane to a specified azimuth. When you run the command you will be prompted in both the status bar (bottom left hand corner of the screen) and your cursor position on the screen, to "Select an anchor point on any string" or "Select an anchor point on any selected string”. Select a point, and then the Rotate String to Azimuth dialog will open. Set the new azimuth value as required and click on the OK button.
Be careful of the the current Expanddefault command as the expansion specified is on within current view plane and not section. If you want the distance expansion to remain yourthe current working plane, align your view with that plane by either using the View ribbon View | Align, then use the Expand command.
Translating strings
(tra) command allows you to make a copy of a selected string and The Edit | Translate locate the new string in terms of one or more defined offsets in the X, Y, and Z directions. The newly created string does not have to be located in the current view plane.
Figure 223: Translate string
Projecting Strings
The Edit | Project | Project String (pro)command allows you to make copies of existing strings that are offset from the current view plane.
Working with points and strings
149
Figure 224: Project Strings/Points dropdown options
It differs from the Translate String (tra)command in that the offset is measured perpendicular to the current string at a set angle. This projection angle is set using the Edit | Project | Set Face Angle (fng) option which by default has a value of 60. The command allows you four projection methods as listed below: Method
Description
Up
The projection distance is the required elevationabove the selectedstring.
Down
The projection distance is the required elevationbelow the selectedstring.
Both
Projection Distance is the required elevation. Strings will be projected up or down such that the
Relative
Strings will be projected the specified projectiondistance.
The Project String (pro)command is used extensively in Open Pit and Underground Design and to a lesser degree in Orebody Modeling. Conditioning Strings
A number of commands are available for conditioning strings in the 3D window under the Edit | Condition ribbon. These commands are used to both correct and modify existing strings. Examples of the correction commands include tools for resolving duplicate points and correcting crossovers. Some of the key string conditioning commands are listed in the following table. Command
Edit | Condition | Condition String Edit | Condition | Trim Crossovers Edit | Condition | Trim Corners Edit | Condition | Smooth Edit | Condition | Reduce Points Edit | Condition Smooth | Gradient Edit | Condition | Insert atIntersections
Quick Key cond
Description
Repositionsthe points along a string.
tcr
Resolvescrossoversin strings.
trc
Join string cords (erasing any segments in between).
sms red
Inserts additionalpoints into a string Reduce the number of points on a string.
smg ii
Smooth part of a stringto a consistentgradient. Insert newstring pointswhere a selectedstring crossesother strings
Exercises Exercise 1: Creating New Strings and Editing Points This exercise outlines the procedure for creating new strings.
Working with points and strings
150
Unload anydata from memory. Run the commandEdit | New String (ns or the 3D window, locate theCurrent Objectstoolbar.
). At the bottom of
Figure 225: Insert Current Objects toolbar
By default the colour grey (no.1) is selected. Select the dropdown list to reveal all the available colours.
Figure 226: Colour palette
The coloured boxes represent a palette of available colours numbered 1-64. These represent the standard colour palette. Each box is numbered according to the numeric code that is used when the colour information is written to a string file. 1. Just to the left of the colour selection dropdown, is another dropdown list that allows you to select the active attribute you are modifying.
Figure 227: Dropdown list of string attributes
2. Experiment with these four options by clicking on each in turn. If additional attributes (non standard attributes) have been added to the string object, these attributes will be included on the dropdown for editing.
Figure 228: Available Line Styles
Figure 229: Available symbols
3. Select the colour dropdown to display the colour palette and select a colour. Digitize a couple of lines, remembering to select New String or pick a different colour from the palette between each new string. When finished, click on the ‘ Done’ button in the top left hand corner of the 3D window to exit theNew String mode.
Working with points and strings
151
Figure 230: Digitised strings - 'Done' box indicates 'New String' mode is still active
The New String command is referred to as a modal command. This means that the command will remain active until ‘Done’ is clicked in the top left of the 3D window, the key is selected on the keyboard or another command is run. There are exceptions to commands which will cancel modal commands, e.g. zooming, panning or moving the view plane.
4. You will notice that the last string you digitised will be highlighted yellow. This indicates the current / active / selected string. In order for the string to revert back to its srcinal colour, just click (using the left hand mouse button) away from the string. The string will then be deselected. 5. Without selecting any commands (such as ns, or move point etc.), take your left mouse button and click on a string. The string will change colour to yellow, thus making it the active string and selecting it for editing/modifying. You can then safely run commands such as mpo (move point), dpo (delete point), ipo (insert point) etc, knowing that you are only carrying out those commands on the selected string. 6. With one of your strings selected, select the command Edit | Edit | Move Points (mpo or ).
Using your left hand mouse button, and following the prompts on screen. Click on a point on the selected string then click at a position somewhere else that you would like to move the point to. Try moving a point on another string that is not selected. You will notice that a point on the selected string which is closest to the point you had try to select on the other string was selected and moved. Use ule to undo the move. Click away from all your strings so that none are selected. Now activate the mpo command. Select points on any one of the strings and move them. The mpo command has what is known as a rubber band affect. Instead of clicking on a point and then carrying out a second click to place the point at its new position, just click and hold down the left mouse button while moving the point to its new position.
7. If you have setup your workspace and you would like to keep your Grid layout, Section settings etc, do not use the command ua to unload all the data. If you do this the layout of the 3D window will revert back to the default. 8. Instead, unload just your string file. 9. Now digitise 2 strings that look similar to that illustrated below.
Working with points and strings
152
Figure 231: Strings with common boundary not honoured
10. In this next exercise we are going to practice inserting, moving and deleting points, by editing the green string to share the same boundary with the purple. 11. Select the green string and then the ipo command. Using your right hand mouse button (snap) click on each point in turn as shown below.
Figure 232: Insert points using snap mode and selected string
Working with points and strings
153
Figure 233: Insert points using snap mode and selecte string
12. Continue until you have snapped to each point along the common boundary. This will ensure the new points you created on the green string are snapped directly onto the points of the purple string. Once you deselect the strings, they should look something like the diagram below.
Figure 234: Common boundary honoured (point positions identical)
Working with points and strings
154
Important thing to note is. When you use your left mouse button, where you place your cursor on the screen is where the point will be moved, inserted or created. If you use your right hand mouse button (the snap button), you are forcing the command (whichever you have chosen) to adhere to an existing point (string or grid depending on your snapping selection)
13. Carry out the same exercise now, using the Edit | Edit | Insert Points (ipo). 14. In this instance it is always safer to select the string first prior to selecting the command. 15. Do this same this time, but delete points from both selected strings and non selected string. Use the command Edit | Edit | Delete Points or (dpo ). It is good work practice to select the string you wish to carry out the changes on before you begin deleting points. One case where this is true would be where two strings share the same boundary. Selecting the correct string prior to activating delete point will save you a lot of problems.
16. You can change the size of the symbols displayed by either:
Double clicking on the actual string on the 3D window.
Double clicking on the String object in the Sheets control bar. In both instances, the object properties dialog box will be opened. Select the Symbols tab | Scale. Select OK, to apply the settings and close the dialog box.
Figure 235: Formatting String Properties
Exercise 2: Saving Strings to a File and Erasing Strings Two options exist for saving strings which are currently held in memory:
The Loaded Data control bar – modified and as yet unsaved data is shown in italics
Working with points and strings
155
Figure 236: Saving from the Loaded Data control bar
The Sheets control bar
Figure 237: Saving from the Sheets control bar
1. Open the Loaded Data control bar, right click on the New Strings object and select Data | Save As. In the Save New 3D Object dialog click on Extended Precision Datamine (.dm) file. 2. In the next dialog box, select the location you wish the file to be saved to (if not your current database). Type the filename under Filename and click Save. 3. Check that the file has been created in the Loaded Data control bar.
Working with points and strings
156
4. To erase/unload the strings held in memory, select the Data ribbon Load | Unload | Erase | All Strings (eal) or even easier, right click in the 3D window select Erase | All Strings. Alternatively: •
Select the displayed strings, select the < DELETE> button and on the keyboard.
• Use the Loaded Data or Sheets control bar ‘s Unload Data icon dropdown list the objects you wish to erase / unload from memory.
.
You can then select from a
Exercise 3: Opening and Closing Strings Many Studio RM processes such as Edit | Tools | Clip (ctp) require that a string is closed in order to use it for further processing. A closed string is referred to as a perimeter and is actually just a string file, the only difference being, is that the first and last point of the string share the same identical x, y and z coordinates. Commands exist to close a single string or multiple strings at the same time. Conversely, the same can be achieved to open string/s. 1. Digitize a 4 point string as illustrated below:
Figure 238: New String command
2. Place the cursor close to the first point and click on the right hand mouse button to close the string. Using the right hand mouse button with the new string command forces the new string point to be ‘snapped’ to the nearest existing data point. Click Done (top left corner of the 3D window to exit the New String command.
Working with points and strings
157
Figure 239: Closing the string using the snap to points mode
3. Alternatively, undo last edit by using the command ule. The last point you digitised will be removed. Select the string and type the command clo to close the string. The command ost can be used to ope the string. These commands are located on the Edit | Condition ribbon.
Figure 240: Close string options
The only difference between closing a string by snapping or closing it using Edit | Condition | Close (clo), is that the (clo) command will terminate the new string command after having placed the last point, and the snapping will keep the command new string active until the Done button is clicked or a new command is activated.
Exercise 4: Undo Last Edit and Combining Strings
1. Use Edit | Erase | All strings Strings ) to remove two overlapping closed as(eal illustrated below.all string data from memory and digitize
Working with points and strings
158
Figure 241: Overlapping strings for Combine Strings command
Make sure you click Done when you have finished digitizing the two strings.
2. Deselect all strings with the Home | Deselect | All Strings(das) command and experiment with Edit | String Tools | Combine (com) by selecting the portions of the strings labeled 1 and 2 in the following examples. UseUndo String Edit(ule) after each combine to reverse each change so that you do not need to keep re-digitizing the two srcinal strings.
Figure 242 : Different Combine Strings outcomes
3. If you wish to preserve both the srcinal strings and the combined string in memory, then turn on the Edit | Tools | Combine | Keep Originals(ko) toggle before you use Edit | Tools | Combine (com).
Working with points and strings
159
Alternatively, the same outcomes can be obtained by using the options in the dropdown list Edit | Tools | Combine, to specify the type of combination you require.
Exercise 5: Extending, Reversing and Connecting Strings In order to demonstrate extending, reversing and connecting strings, digitise two separate northsouth trending strings that are roughly parallel to each other. The starting point of both strings is at the top of the page. The command Edit | Tools | Extend (ext or end of each of the two strings.
) can be used to add points to the lower
Remember that you can only extend from the end of a string.
4. Select one of the strings and run the command ext. Automatically a ‘rubber band’ line will appear connected to the last point of the string. Click on the position of your new point. Click Done or hit the button on the keyboard when you have finished extending the string. The background colour was changed in this example just so that you could clearly see the selected string colour
Figure 243: Connecting two separate strings
5. In order to extend your string from the other end, select the string and select the command Condition | Reverse (rev or ). Select to extend the string you have just reversed.
Working with points and strings
160
6. The command Edit | Tools | Connect (conn or two strings to form a ‘U’ shape.
) can be used to combine the
Whichever string is selected first, the second string will take on the first strings attributes.
Figure 244: Connect order - red to green
Figure 245: Connect order - green to red
7. Then use the undo last edit command ule() and combine them again to form an ‘N’. Exercise 6: Clipping Strings and Generating Outlines This exercise will use a circular closed string to illustrate the clipping and outlines commands. A new circular closed string can be created by following these steps:
Working with points and strings
161
1. Remove all strings from memory by holding down your left mouse button and dragging a selection block over the data o y u wish to delete. As long as thestrings turn yellow, they are selected.You can then select on the keyboard and confirm Yes to delete them. The data object those strings belonged to is still a valid object and is still loaded into memory, but the data in that file has been cleared.
2. Run the command Edit | Shapes | Arc | Circle by Radius(cir or ). You are prompted to select a point representing the center of the circle (the prompt will appear on the screen as you move the cursor over the 3D window). 3. Enter a radius of 30 in the dialog box.
Figure 246: Circle radius dialog box
Figure 247: Circle by Radius
There are also commands under Edit | Shapes | Rectangles for creating squares and rectangles interactively by corners, centre’s edges.
Working with points and strings
162
Figure 248: Shapes group
4. Set the snap mode to grid usingHome | Snappingand selectionSnap | Sn ap to Gri d (stg). Check yo ur G rid Snapping Parameters - by default his is set to an Increment of 10 x 10 x 10 and the Origin cantered on 0,0, 0. Accept thisdefault.
Figure 249: Snapping grid dialog box
5. Using your right hand mouse button (snap mode grid), digitize a series of strings crossing the circular string. You can use one string or several strings; the main requirement is that all the start and end points are outside the circle. The Design window should end up looking similar to the image below:
Figure 250 - Strings for Clip to Perimeter
6. Set the snap mode back to points using Home | Snapping | Snap and selection Snap to Points (stpo).
Get into the habit of always returning the snap mode back to Snap to Points after you have carried out any other snapping options such as Grids, Lines etc
7. Deselect any selected strings and run the Edit | Tools | Clip or (ctp – clip to perimeter) command. Running this process will prompt you on screen to select the perimeter that will control the clipping, then to select either inside or outside of that perimeter to indicate what to delete.
Working with points and strings
163
Figure 251: Clip to perimeter - delete strings lying outside the perimeter
All the string data outside the perimeter will be deleted and extra string points are inserted where the srcinal string segments intersect the perimeter. Note that this process will not work unless the string is closed (perimeter). processes where ule (undo last edit) will not work
This is also one of the
8. Experiment with the other two options on the Clip dropdown. Selecting them will automatically restrict you to inside or outside the perimeter
Figure 252: Clip dialog box
9. Delete all the other strings except the perimeter. We are going to use it in a later exercise. Just to the side of the circle digitise two separate strings. 10. Run the Trim to String command located on Edit | Tools | Clip dropdown (this command allows you to cut a string off against another string (no need for a perimeter)
Working with points and strings
164
Figure 253: Trim to string
To generate outlines: 11. Delete all the strings except the circle you drew earlier. 12. Digitise 4 strings crossing over the perimeter, similar to the image below. We would expect than when we run the command to create outlines, that 9 possible outlines would be created.
Figure 254: Perimeter with overlapping strings
13. Open the Outline Settings option located in the Edit | Outlines dropdown menu. Under the String Outline Generation group, toggle on the ‘Generate all possible outlines’ button as illustrated below. Click Apply and OK to close the form.
Working with points and strings
165
Figure 255: String Outline Generation settings box
14. Select the command Edit | Shapes | Generate Outlines (ou). The system will create all the possible closed strings and place them in a new object called ’New Outlines’, which appears in the Loaded Data control bar.
Figure 256: New outlines created
15. Remember that these strings (and this object) are currently only loaded into memory. They need to be saved should you wish to keep them. To save the new outlines to a file right-click on the item New Outlines in the Loaded Data control bar and select Data | Save As. Enter the file name Outlines. Exercise 7: Copying, Moving, Expanding, Rotating and Mirroring Strings 1. Run the command ua (Unload All) to remove all loaded data from memory 2. Digitise a single string on the 3D window 3. Prepare your workspace as follows:
Create a new 3D Grid Deactivate the Default Grid In the Grid properties, set your Grid color to black, then Apply the setting and click OK to exit the dialog box Rotate the view so that the 3D grid is clearly visible – as shown below
Working with points and strings
166
Figure 257: New string
Go back into the Grid properties and on the Advanced Options tab, deactivate the Snap to hull tick box and enter a value of -50 for the minimum Z and 50 for the maximum Z. Select Apply then OK.
Figure 258: 3D Hull Grid Properties – Hull extents modified
Working with points and strings
167
Figure 259: Hull extents adjusted
Activate the Default Section in the Sheets control bar, then open the Section Properties dialog box
4. Set the following parameters, then click Apply then OK
Plane Dimensions – activate Use dimensions
Section Plane – change the colour to light grey and set the Opacity to 30
Section Extents – deactivate the Lines option
Figure 260: Set the Default Section Properties
Working with points and strings
168
Figure 261: Default Section modified for display
5. Play around with your settings for the Default Grid, Grid (3D Hull) and Default Section till you get your desired display. In the example above, the following settings were used: [String File] Properties–
Symbols tab, Style = Fixed (solid filled circle) Scale = 7
Default Grid Properties–
Options tab, Grid Type = Default Section Line Type = Ticks Fixed intervals= 50, 50, 50 Grid color = grey Major line every N= 2 Annotation | Size= 10
6. In order to ensure the Default Section is nicely centred about the data use Set Section using 1 point and snap (right hand mouse click) on a point mid string. Select a Horizontal orientation to remain in plan view.
Working with points and strings
169
Figure 262: Select string to be copied
Figure 263: Define new string position
Notice that the string will remain in the current section / default plane and notice that the string will be copied relative to the point you selected on the srcinal string
Now try the command Edit | Move (moor
. Follow the prompts on the screen.
7. Next we are going to move a string, but this time we are going to use the snap option. 8. Digitise a new point using the command npoor . You will notice that a new object ‘New Points’ has been created in the Loaded Data control bar
Working with points and strings
170
Figure 264: Loaded Data control bar
Figure 265: New Point (npo) digitised on same section
9. This point is sitting on the same section as the string. Select the point and type in the command epc (edit point coordinates. 10. Edit the Z value to -25, then click OK.
Figure 266: Edit Point Coordinate
Working with points and strings
171
Figure 267: New position of standalone point
11. Now copy your srcinal string, but this time when you are asked for the position of the new string, right click / snap onto the red point which is 25m below your current default section.
Figure 268: String copied to new point using the snap to points option
12. The snapping option has allowed you to snap to an existing point of known srcin out of the current default section. The point had to exist there though else it would not have had anything to snap onto.
Exercise 8: Projecting Strings This exercise outlines the procedures for projecting a string using the Up and Relative options. A new string/s will be created which are saved to the srcinal data file 1. On the Loaded Data control bar select the Unload Dataicon the Sheets control bar)
(the same icon exists on
2. On the Data Unload dialog box, select all the loaded data files to remove, then select OK. We do not want to use ‘Unload All’ as we would lose all our Grid and Section parameters. 3. Digitise another circle, but this time using Edit | Shapes | Arc | Circle by Centre and Edge or .
Working with points and strings
172
4. Define the centre point of the circle, by selecting a position near the centre of default section. You will then be prompted to select a point on the edge of the circle. Once you have selected the outside edge of the circle you have the opportunity to resize the circle by holding down the left hand mouse button and dragging your cursor in /out. When you are done resizing the circle, click the Done button.
Figure 269: Resizing the circle while in the ‘Circle by Centre and Edge' command
5. Check the default projection angle is correct by running the command, Edit | Project| Set Face Angle (fng or ). By default this value is set to 60°. Change this to 25°. Select OK to exit. 6. Zoom out slightly so that you will clearly see the new string once it has been projected. 7. Select the digitise d circle and run the command Edit | Project | Project String (proor ) command. When prompted, set the required projectionmethod, in this case U and set the target elevation to50.
Figure 270: Project String parameter prompts
8. On screen you will be asked to ‘Select high side of selected string to project’ 9. The “high side” is the side of the selected string you wish to project the new string to. Answer the question by digitizing a point outside the perimeter. By digitizing outside the perimeter the new projected string will be located at elevation 50m, projected outwards at an angle of 25°.
Working with points and strings
173
Figure 271: Projection Method U (Up
10. Making sure no strings are selected, run the Project String setting the Projection method to R and the Projection Distance to 25. When prompted, click on the screen just outside the inner string (point A on the image below). A new string will be created.
Figure 272: Projection Method R (Relative)
Working with points and strings
174
By not selecting a string prior to running the command, you will be able to project any string multiple times.
Try the other Projection Methods (B – Both) and (D-Down) – remember it is a combination of the following parameters that will yield different outcomes: • •
Selecting the string to project prior running the command or not. Projection Method:
o
U - then you specify the final elevation of the new string).
o
R – you specify a distance to move the new string from the existing string. In this instance a + or – will
o
define if the new string moves up or down. D – final elevation has to be typed as a negative numbe.r
o •
B – Both Defining the High Side – dictated by either clicking inside or outside the string you are wanting to project.
Exercise 9: Translating Strings This exercise will demonstrate the translation of strings to a different location. The process allows you to translate (copy) the strings in the X, Y or Z directions. The option to keep or discard the srcinal strings also exists 1 . Remove all your strings from the screen, by highlighting them and deleting them. 2 . Fix your view direction by selecting View | Align – this will re-orientate your view so that you are looking at your default section from above (perpendicular to your default section) 3 . Digitise all four strings on the section so they resemble something like the figure below. All four of the strings are on the same elevation (default section) 4. Feel free to rotate your view around to confirm this. Return to your plan view by selecting Align.
Working with points and strings
175
Figure 273: Strings drawn on same section
5. Select the three green strings by dragging the selection box over them.
Working with points and strings
176
Figure 274: Selection box to select strings to be translated
6. Once highlighted, run the command Edit | Translate (tra or ). Specify a distance of -30 to translate by. Set the ‘Keep srcinal string(s) Y/N to N. There is no problem with not keeping them, you would just need to go and delete the srcinals once the new strings have been created.
Figure 275: Translate string(s) dialog box
7. Rotate your view so that you can clearly see that the green strings you selected have been copied down 30m below the purple string.
Working with points and strings
177
Figure 276: Translated strings 30m below their srcinal position
Exercise 10: Extending to a String This exercise outlines the procedure for extending a string(s) to intersect another string and uses the strings created in the previous Translate exercise. 1. Ensure noneof your strings areselected. Then run the Edit | Tools | Extend to String (ess) command. If none of your strings are selected prior to running the command ess, the command will remain in a modal state, meaning you will be able to continue to select other strings to extend until you select Done. 2.
When prompted to ‘ Indicate end point TO EXTEND F R OM on any s tr i n g ’, click on the last point on any of the green strings. You will then be prompted toS‘elect string to
EXTEND TO ’ 3. This command extends a string from its end point, using the bearing and dip of the final segment of the string, to a point where it meets another selected string. This is not necessarily an intersection as the string s may be on different planes – as you can see from the final screenshot below.
Working with points and strings
178
Figure 277: Extending strings to intersect another strings - strings at different elevations
4. The purple string is used almost like a barrier or ‘cookie -cutter’ in order to stop the extended string. Select View | Align to re-orientate your view to plan. This will allow you to confirm that the green strings have indeed stopped against the purple.
Figure 278 - Plan view showing extended strings
5. Use the quick keyule to undo the last edit. Do this three times. Remain in plan view. 6. To extend one string to another so that the intersection of the extension is perpendicular first turn on theHome | Snapping | Snap | Snap t o Lines (stl). 7. Select Home | Snapping | Snap: |Snap Perpendicular (stpe)
Working with points and strings
179
8. Run the commandEdit | Tools | Extend (ext) . 9. Select the end point on the string you wish to extend, then digitize (snap) to the string you wish to extend to. You will notice that no matter where you snapped to on the purple string, the new point has been snapped onto the purple string perpendicularly.
Figure 279: String extended perpendicularly to intersect the other string
If you are trying to follow this exercise, depending on the angles at which you have digitized the two strings it may not be possible for the system to extend the string so it is perpendi cular to the second string. If this is the case a message will appear in the bottom left corner Studio of RM.
Exercise 11: Conditioning Strings This exercise outlines the procedure for conditioning strings using the following string. 1. Remove / delete all the strings currently on screen 2. Digitise a string that resembles the one below.
Working with points and strings
180
Figure 280: String to be conditioned
3. Select the string and run the Edit | Condition | Condition String (cond) command. You will be prompted for the minimum and maximum chord lengths and the minimum angle. The minimum and maximum chord length options allow you to adjust the spacing of the points along the string. Points will be inserted and or deleted to satisfy these settings. The minimum angle setting be used to delete adjacent string in chords where the between less than thecan defined value. Change the settings the dialogue boxangle to match those them belowisand press OK.
Figure 281: Condition string parameters
4. Press the Done button to close the command. The zigzag segments of the string should have been rounded out.
Working with points and strings
181
Figure 282: Conditioned string
Exercise 12: Trimming Crossovers and Corners This exercise outlines the procedure for trimming crossovers and corners using the following string. 1. Remove / delete all the strings currently on screen 2. Digitise a string that resembles the one below.
Figure 283: String with crossover and messy corner
3. Make sure the string is selected and run the Edit | Condition | Trim Crossovers (tcr or command). The crossed portion of the string should be deleted.
Working with points and strings
182
Figure 284: Crossover removed and segments selected for Trim Corners command
4. Now run the Edit | Condition | Trim Corners (trc) command and when prompted to ‘ S elect first intersecting segment on any string’ click onto position 1 as shown above. Then select the second point when prompted to do so (labelled 2). The command will extend the two chords selected and delete the excess portion of the string.
Figure 285: Corner has been cleaned
When you use Trim Corners, depending on the projection of the 2 chords selected, the resultant string may not give the expected result. In this case, consider other commands, such as delete points.
The main reason for using these commands is to remove sections from string data which will be difficult to wireframe and or are not practical for mining purposes.
Exercise 13: Smoothing Strings and Reducing String Points This exercise outlines the procedure for smoothing and reducing point on strings using the following string
Working with points and strings
183
1. Remove all existing strings and digitise a new string that resembles the one below.
Figure 286: String ready for smoothing
2. Run the Edit | Condition | Condition | Smooth (sms) command which will smooth a string by inserting additional point between each pair of points. Select the string you wish to smooth. Continue to smooth the string until it contains a large number of points.
Figure 287: Smooth string in modal state allows multiple selections of the string to be smoothed
3. Running the command in this fashion treats it as a modal command. This means the command smooth remains active until you click Cancel or run another command, and each mouse click will insert additional points. Had you selected the string prior to running sms, as soon as you typed the command sms, the string would have been smoothed. In this instance it would only be a once off command.
Working with points and strings
184
4. Reduction of points on a string(s) is controlled by Edit | Condition | Condition | Percentage Reduction (pre). The default for this command is [-] or [absent], a setting which will remove the m aximum number of points possible from the string without destroying its overall shape. If this is reset to ‘50’ then 50% of the points on the selected strings will be removed when Edit | Condition | Condition | Reduce Points (red) is run.
Figure 288: Reducing the number of points on a string using (red)
5. Use the closed string in the 3D window to experiment with the smoothing and reducing commands. Exercise 14: Breaking Strings with Strings This exercise outlines the procedure for breaking strings using the following string 1. diagram Delete allbelow. existing strings from the previous exercise, then digitise 2 strings that resemble the
Figure 289: Strings ready for breaking
2. Deselect all strings and run the Edit | Tools | Break | With String (bks) command. 3. When prompted to ‘ Indicate the control string’ (string used to break all other strings crossing it) select the green string. When prompted to ‘Indicate string to break using FIRST S tring’ select
Working with points and strings
185
the purple string. The first selected string will cut the second at all points of intersection. Click Done to exit the command.
Figure 290: Separate strings created from Break String with String command
Working with points and strings
186
C HAPTER
9
WIREFRAME MODELING – CONSTRUCTING SURFACES In this chapter, you will learn to:
Create a wireframe model ofa topographical surface
To create a wireframe model ofa fault plane
Create a string from the intersection of the wireframe surface with a 3D plane
Principles Definition of a wireframe A wireframe is a geometric model that describes 3D geometry by outlining its edges. In Studio RM, a geometric object is displayed by drawing its edges as lines resembling a model made of wire – hence the term wireframe. Other modeling software may use terms such as surfaces or solids to describe the same concept. Although geometric models may use more complex polygons (e.g. the hexagons/pentagons of a soccer ball), Studio RM wireframes use the simplest polygon – a triangle. These triangles are linked together to form a continuous surface from which block models can be built and volumes calculated. The raw input for building wireframes are string or point data types whose points are used to define the triangles. The example below (Figure 291) is a display of a subset of topography strings and the matching surface wireframe generated from it.
Topogr aphy String s
Topogr aphy W ir eframes
Figure 291: Topography strings and wireframes
In the example above the triangles have been created where each vertex is a point on a string. Also, there is no triangle that crosses a string; each string acts as a break-line. The wireframe forms a continuous surface, in this case with an open edge that defines the boundary of the wireframe surface. In Studio RM wireframes can be generated by one of the following methods:
Digital Terrain Modeling (DTM) using 3D string and/or point objects to create a surface. String Linking techniques on 3D strings to create solid objects.
Wireframing manipulation techniques on existing wireframe objects.
Wireframe Modeling – Constructing Surfaces
187
Using wireframes to accomplish mining objectives Wireframes are either "closed" volumes or "open" surfaces and can be used to represent a wide range of general, geological and mining related features, for example:
topography or infrastructure surfaces geological field mapping e.g. geological structure planes interpreted or modeled geological features e.g. fault surfaces, lithology boundary surfaces, ore body volumes underground and open pit designed or planned mining surfaces or volumes underground and open pit surveyed or actual mining surfaces or volumes
Displaying wireframe objects Wireframe data can be displayed in the 3D and Plots windows whilst held in memory. Initially, wireframes were displayed by using the edges of each triangle. However, it is practical to render the surface of each triangle in the wireframe, adding colour, texture, light, and relative position to the wireframe object. The result is a wireframe object which appears as the intended viewer would see it. To view the edges of each triangle in a wireframe the user can revert to the legacy Design W indow by using the Home ribbon and selecting Show | Design and redrawing the view.
Saving wireframe objects to a file Wireframe data file storage in Studio RM is an example of relational data storage. There are two files created and they use an index field to relate to each other. One file (the point file) stores the coordinates (X, Y, Z ) for each point with an identity number ( PID). The second file (the triangle file) stores the three points – referred to by their PID – for each triangle. The PID becomes the relational field between the two files, with the immediate benefit that each point coordinate need only be stored once as opposed to three times (the number of times the PID must be stored in the second file). The two files are referred to as the points file and the triangle file respectively. To load or store a wireframe object Studio RM must be able to identify these two files, and uses a naming convention to simplify this process. If the naming convention is used, then loading or storing requires only the triangle file to be named. If not used, Studio RM will prompt for the relevant points file. The naming convention applies to the last two letters of the triangle and points file name. If the triangle file ends with the letters TR and the points file ends with the letters PT , and apart from these letters the names are identical, then the naming convention is honoured. When loading a wireframe, Studio RM prompts for the triangle file. If the naming convention is honoured, Studio RM will automatically look for the points file (same name but TR turned to PT ) and if present will load the wireframe. When storing a wireframe, Studio will prompt for the triangle file name and if this name ends in TR , Studio RM will automatically store the points file using the naming convention. If the naming convention is not honoured, then Studio RM will prompt for the name of each file individually. Otherwise, if you wish to change this setting and be prompted for the points file name regardless, using the Home ribbon, select Project | Options | Project | General option from the pull down menus and toggle on the Confirm wireframe point filename in browser option (Figure 292).
Wireframe Modeling – Constructing Surfaces
188
Figure 292: Project Options dialog
DTM surfaces A DTM surface is a surface style wireframe and is by default sub horizontal. It interpolates the surface using the supplied data point coordinates and a viewing direction (by default this is vertical). One effect of the viewing direction (via the interpolation algorithm) is that any point projected through the DTM surface in the direction of view will only cross the surface once. If any two points line up in the direction of view then the algorithm will be unable to generate a surface. In general, the direction of view is vertical and this is adequate for the more common applications of DTM surfaces:
surface topography
geological features (fault surfaces, lithology or mineralization surfaces) open pit designs
open pit survey measurements
Creating DTM surfaces in Studio RM In the Structure ribbon select Operations| DTMs which activates the Make DTM wizard command to guides you through the process of creating a DTM from loaded point or string objects.
Figure 293: The DTMs ribbon Wireframe DTM’s can also be created using the file base processes, SURTRI and WFTREND that can be activated in the Structure ribbon in Process | File Processes .
The process of making a DTM from loaded string or point data hinges on the following criteria:
Which string or point object(s) will be used to create the resulting mesh?
How will the points be linked during DTM creation?
Wireframe Modeling – Constructing Surfaces
189
Will data be cleaned/trimmed?
How will string or point attributes be proliferated?
Will boundary strings be used to define a periphery?
To run the DTM create command at least one string or point object must be loaded into the 3D window. The Make DTM wizard may consist of more than two steps depending on what options are selected. The steps are: 1. General Options. 2. Select DTM Points and Strings. 3. Select Boundary Strings (only appears if the Use Boundary Strings option is selected in the General Options dialog). 4. Edit Attributes (only appears if the User-Defined Attributes option is selected in the General Options dialog). General Options Details of each of each dialog are summarized in Figure 294:
Figure 294: Using the Make DTM dialog
The Output section:
If Current Option is selected then the resultant wireframe is saved to the current (active) wireframe object. If New Object is selected then the resultant wireframe is saved to the new object name specified by the user. If the Use Boundary Strings option is selected, this will introduce a third screen in which you are prompted to specify a string file that defines an area within which the DTM will be created (i.e. an outer boundary limit). All data outside of this closed string will be removed from the resulting DTM. Any number of boundary strings can be specified, with the system using the left-to-right rule to determine whether the string is an outer or inner limit. By default, the first string encountered will be assumed to be an outer limit, then the next, an inner limit and so on. There can be multiple outer limits, and multiple inner limits within an outer limit. Where the first string defines the inner limit (e.g. there is only one string), choosing Invert Results will reverse this left-to-right logic.
Wireframe Modeling – Constructing Surfaces
190
By selecting the Minimize flat triangles option the system will minimize the effects of several wireframe triangles connecting to the same contour line as shown below:
Figure 295: A: Minimize Flat Triangles option is not selected; B: Minimize Flat Triangles option is selected.
The Trimming Options section: In some cases the resultant DTM contains thin ‘sliver’ triangles at the edge. If the trimming option is selected then these triangles are removed from the edge of the wireframe until the specified parameters have been satisfied. The parameters are:
Minimum Angle: remove any triangles which have a vertex angle less than the userspecified minimum. Max. Edge Length: select this option to remove any triangles with an edge longer than a specified amount.
The DTM Plane section: Although most DTM models will be generated relative to the virtual world's XY plane, there may, at times, be a requirement to create a surface in a different orientation (e.g. along a drive). In this case the current view plane, as determined by the viewing direction in the 3D view, can be used to specify a DTM projection plane.
Select Plan for the world XY plane, Select View for the current view plane. The Best Fit option will attempt to calculate a plane which best fits the points being input to the DTM function.
The Spur Options section: Flat zones on a surface triangulation are often undesirable and can occur frequently when a surface triangulation is formed for a contour set that is somewhat sparsely separated. A thin section of contour will often connect to itself, forming a flat bridge that is unrealistic. The spur generation will
Wireframe Modeling – Constructing Surfaces
191
identify and classify each flat zone in the triangulation according to Crest, Valley and key zones. The options in this section are:
Generate crest spurs. A crest zone is where all boundary edges belong to adjacent triangles that connect to a lower level. Enter a positive value in the ‘Adjust crest heights by’
box to increase the crest elevation. As a guideline, it is recommended that the height setting is at least half the distance upwards between contour strings.
General valley spurs. A valley zone is where all the boundary edges belong to adjacent triangles that connect to an upper level. Enter a negative value in the ‘Adjust valley heights by’ box to reduce the valley elevation. As a guideline, it is recommended that the height
setting is at least half the distance downwards between contour strings.
Generate key spurs. edges Key spurs to a crest or valley spur, but edge are generated when some of the boundary may are not similar have adjacent triangles (i.e. on the of the resulting wireframe). The system will dynamically assign the height to a value between the contour levels as it moves along the spur. Output spur objects. Select this option to display the spur strings that are used during the DTM creation process. The strings are saved to a new string object and the type of spur (i.e. crest, valley or key) is stored in a field named TYPE.
The Attributes section: There are three different ways to define the attributes which will be contained within the DTM.
Use First Point/String. Copies all the non-system attributes from the first string or point encountered when generating the DTM. The precise string or point is essentially undefined, so this option is primarily intended for copying general attributes where the input strings share a common set of attributes (e.g. colour). Use All Points/Strings. Post-processes the DTM and attempts to match each point (or string vertex) to any wireframe triangles which shares the vertex, and will then copy all nonsystem attributes to those triangles. User-Defined. Allows the Edit Attributes dialog to be used to define the attributes and values which will be used in the DTM link. By default the attributes and values in the Edit Attributes dialog will be from the output wireframe, but the Pick Button can be used to select any point, string or other items in the 3D window. More details regarding this dialog can be found later in this section. The default settings for items in the General Options dialog are defined in the DTMs section of the DTM Settings dialog
Select DTM Points and Strings After the General Options have been defined, all the points and strings which will be used to create the DTM can be selected. By selecting the checkbox next to a particular object all the strings (or points, if a point file) within that object will be used to create the DTM. If you wish to select individual points or strings then click on the pick button ( locked 3D window selection methods.
) and select the required strings or points using the
Select Boundary Strings Where the Use Boundary Strings option has been selected in the General Options dialog, you will be given the opportunity to select strings to be used as boundaries. Only closed strings will be used within the process. Boundary strings will limit the extent of the DTM, but will not contribute to the DTM itself. Where this is required, the strings should be selected in both the Select DTM Points and String, and Select Boundary Strings steps.
Wireframe Modeling – Constructing Surfaces
192
Edit Attributes The Edit Attributes dialog will appear if you have selected the User-Defined option in the General Options dialog. This is the standard Edit Attributes dialog that lists the attributes of the selected object(s) and allows the values to be edited interactively. Edit the attributes and values as required. Editing wireframe triangles There are a number of commands available under the ribbon Structure | Current Wireframe that allow you to manipulate individual wireframe triangles and points on individual wireframe triangles. These commands are summarized below: Table 1: Quick keys for wireframes Quick Key
Command
Description
New Triangle
ntr
Allows you to create a new triangle by digitizing three points to define the triangle.
Unlink Triangle
utr
This command will erase data for the selected triangle from the current wireframe file. These modifications will only be stored if saved to the file.
Move Wireframe mpw Point
Allows you to interactively move points on a wireframe. New triangles will be created between the new vertex and the connected vertices.
Insert Wireframe iwp Point
Allows you to interactively insert a point in a wireframe. New triangles will be created between the new point and the vertices of the selected triangle.
Delete Wireframe Point
-
Allows you to delete selected wireframe points.
Show Wireframe Slice
slw
Displays a temporary line in the Designwindow that represents the intersection of wireframe data and viewplane. This data is viewable in the Designwindow.
Wireframe Modeling – Constructing Surfaces
193
Exercises Exercise 1: Creating the DTM without Limits This exercise outlines the procedure involved in creating a wireframe surface from topographical string. 1. Load the topography strings into the 3D window, e.g. _vb_stopo. 2. Run the command to make a DTM using the ribbon Structure | DTM | Make DTM (md) 3. In the General Options dialog, select the required options, for example, to create a new object called stopo which does not use a boundary string enter the following:
Figure 296: General Options for Make DTM
4. In the Select DTM Points and Strings dialog select the objects to be used to create the DTM.
Figure 297: Selected Points and strings for DTM
5. Click on the Finish button to create the DTM. 6. Check that the new stopo wireframe object is listed in the Loaded data control bar and the Sheets control bar under the Overlays category
Wireframe Modeling – Constructing Surfaces
194
Figure 298: The stopo wireframe in the 3D window
To view the wireframe in the legacy Design window navigate to the Home ribbon and select Show | Design
Exercise 2: Creating the DTM with Limits 1. Load the topography strings into the 3D window, e.g. _vb_stopo. 2. Run the command to make a DTM using the ribbon Structure | DTM | Make DTM 3. In the General Options dialog, select the required options, for example, to create a new object called stopo which uses a boundary string as shown:
Figure 299: The General Options in the Make DTM wizard
4. In the Select DTM Points and Strings dialog either select the object(s) to be used to create the DTM or use the pick tool (
) to select individual strings.
5. In the Select Boundary Strings dialog either select the object(s) to be used to create the DTM or use the pick tool (
) to select individual strings.
Wireframe Modeling – Constructing Surfaces
195
6. Check that the new stopo wireframe is listed in the Loaded data control bar and the Sheets control bar under the Overlays category Exercise 3: Saving the New Wireframe In this example, you are going to save the new topography wireframe to a file. The wireframe triangle file will be named stopotr and the wireframe points file will be named stopopt. 1. Select the 3D window tab. 2. In the Current Objects toolbar, select the "Wireframes " option from the Object Types dropdown and then stopo from the Wireframe Objects list.
Figure 300: The Object toolbar
3. Click Save Current Object
in the
Current Objects toolbar.
4. In the Save 3D Object dialog, click Extended Precision Datamine (.dm) File. 5. In the Save stopo dialog, define the file name as "stopotr" and then click Save button. This dialog is prompting for the name of the wireframe triangle file (use the standard *tr naming convention). The process of saving the wireframes will automatically create the wireframe points file as well, with the name stopopt i.e. the " tr" suffix is replaced with " pt".
6. Select the Sheets control bar and check that the stopotr/stopopt (wireframe) is listed under the Overlays category.
Figure 301: The Sheets control bar
7. Select the Project Files control bar and check that the new files stopopt and stopotr are listed under the Wireframe Points and Wireframe Triangles folders respectively. 8. Select the Loaded Data control bar and check that stopotr/stopopt (wireframe) is displayed in the list. Exercise 4: Displaying Wireframe Slices In this exercise you are going to display the wireframe as a slice with the current viewplane in the 3D window. 1. In the Sheets control bar toggle off any Overlays other than the stopotr/stopopt (wireframe) overlay. 2. Under the Wireframes folder, right-click on stopotr/stopopt and go to Properties.
Wireframe Modeling – Constructing Surfaces
196
3. In the General tab, under the Shading section, experiment with the wireframe display by selecting the buttons for Points, Faces and Intersection. Each time you make a button selection, hit Apply; the changes will be applied and the dialog will remain open.
Figure 302: Wireframe Properties dialog box
Format Display does not work in the 3D window; the user can navigate to the Plots window and, select the ribbon Manage | Overlays.
4. Select the Wireframes option and click on Close to close the dialog. You can check the number of point of faces in wireframe by navigating to Sheets control bar, right click on wireframe file and select Data Object Manager. A summary of the wireframe generation process, including possible errors, can be viewed in the Output window.
Exercise 5: Generating Strings from Wireframe Slices We have seen how to display wireframe slices, however, we need to convert these to strings if we are to use them in other operations. 1. Select the ribbon Structure and Wireframes | Operations | Plane | Section to open the Section dialog
Wireframe Modeling – Constructing Surfaces
197
Figure 303: The Section dialog box
2. Select the Use View Plane button and then OK to create a section string from the current view plane.
Additional Exercises Additional Exercise 1: Load the topography contour strings and create the DTM surface. Write the specifics for the exercise in the spaces provided. Topography contour string file name:
New Object (DTM) name:
Color
Errors in DTM creation: Y / N
Number of Points
Wireframe Modeling – Constructing Surfaces
Number of Faces
198
Additional Exercise 2: Digitize an outer limit and recreate the DTM surface New Object (DTM) name
Color
Errors in DTMcreation: Y / N
Number of Points
Number of Faces
Additional Exercise 3: Write the DTM Object to wireframe files. Wireframe Triangle file name Wireframe Points file name
Additional Exercise 4: Wireframe Intersection Display the wireframe as the line of intersection with the current view plane and create a string from this intersection. Save the string file. String File Name:
Wireframe Modeling – Constructing Surfaces
199
C HAPTER
10
WIREFRAME MODELING – CONSTRUCTING CLOSED VOLUMES In this chapter, you will learn to:
Create a wireframe model ofan orebody from drillhole sectioninterpretation strings
Use tag strings tomanually control the wireframing
Automatically create a wireframe volume from strings
Create wireframes from open strings
Create wireframe shapes with bifurcation (trouser legs)
Principles The wireframe linking techniques can be used to link open and closed strings to form wireframe solids and surfaces. Typically these techniques are used to create closed volumes for the following:
geological features (lithology or mineralization volumes)
underground development and stope designs
underground survey measurements The wireframe linking commands can only be used with string data.
String linking to build wireframes involves linking the points on 2 or more separate strings to build a surface made up of triangles. Unlike the Make DTM command, the methods used do not require the strings to be orientated in any particular view or plane. Linking Methods Three separate linking methods are available for linking strings together. The linking method can be changed at any time and as such it is possible to change the linking method for each link in the wireframe if this gives the desired result. If you find that the particular linking method is not giving the desired result, then change the method under Home| Project Settings| Wireframe Linking| Linking Method .
Wireframe Modeling – Constructing Closed Volumes
200
Figure 304: Wireframe Linking settings in the Project Settings
The method names and a brief description are listed below: Command
Quick Key
Description
Minimum Surface Area
tma
The system will create the triangulation which have the smallest wireframe surface area.
Equiangular Shape
tea
The system will create equi-angular triangles (i.e. equilateral or isosceles triangles)
Proportional Length
tpr
This option will create triangles which best maintain their proportional position along the string. The starting edge for triangulation is determined either by user defined tag strings or, if selected by the system, the closest pair of points on the two strings. This option works best where the shape of the two strings is similar.
The default method is the Equiangular Shape method. The following image shows a pair of strings linked using each of the above methods:
Figure 305: String linking options
Wireframe Modeling – Constructing Closed Volumes
201
Tag Strings A Tag string joins together points that must be linked when using the commands link-strings, linkboundary or link-to- line. A tag string is recognized by Studio RM and cannot be used to create wireframes when linking strings. A tag string can join any number of strings, and the line joining the points on each consecutive pair of strings define the triangle edges that constrain the triangulation of the pairs of strings. Intermediate points on the tag string will be ignored. When two strings are to be linked, the tag strings are analyzed to determine the tag lines to be used to constrain the link. Tag string combinations that cross over will cause a link to fail. Tag strings are created using the ribbon Structure | Create | Tag String. When used in conjunction with the various linking methods they are particularly useful when wireframing complex shapes. A tag string can contain any number of points; however, each point of a tag string must be on a different perimeter. Tag strings by default are colored red (COLOUR=2). This color can be changed if necessary using the ribbon Structure | Create | Tag String | Set Tag String Color (taco) command. You must use the Create | Tag String button on the Structure ribbon to create tag strings. Do not use the Structure | Design| New String command.
Creating Wireframe Links The following tools are commonly used in the process of creating closed wireframe volumes: Command
Quick Key
Description
Structure | Create | Link | Link Strings
ls
Links two strings
Structure | Create | end link
eli
Creates a wireframe surface within a closed string
Structure | Create | Link | link to line
ll
Creates wireframe link between a closed string and a line.
Structure | Create | Link | Link Quad
lq
Creates a wireframe link using points on selected segments of two strings. It allows you to build up a complete link between strings in several stages.
Structure | Create | Link | Link Boundary
lbo
Links together two strings honoring any bridge or tag strings.
Structure | Create | Link | link multiple by attribute
lma
Links multiple strings to form a solid wireframe, based on a numeric attribute which determines the linking order.
Structure | Create | Link | create tag string
tsg
Tags specific points to be joined when wireframing strings.
This command is designed to make it easy to link multiple strings to one other string to create a bifurcated or split wireframe model.
Erasing Wireframe Links The last wireframe link created can be deleted using the ribbon Structure| Create | Undo Last Link (ull) command. To select the link you wish to delete select the Structure| Create | Undo Link |
Wireframe Modeling – Constructing Closed Volumes
202
Unlink Wireframe (uw) option. Commands for editing, copying, translating, rotating and erasing wireframes are also available under the Structure| Edit ribbon. Terminology The following terms can be used to describe wireframes.
Face: Used to describe a wireframe triangle.
Vertices: The theoretical edge of a wireframe triangle formed by the interconnection of two
wireframe points. Each triangle has three vertices.
Shared Edge: Used to indicate the boundary of a wireframe triangle that is also the boundary
of a neighbouring triangle. A triangle can have 0,1, 2 or 3 shared edges.
Exercises Exercise 1: Creating a Basic 3D Volume In this example you will create a 3D solid using the linking techniques. 1. Unload any loaded objects from the 3D window. 2. In the Current Objects toolbar select Strings from the objects box and then select the Create New Object
button.
Figure 306: The Current Object tool bar It is good practice to create a New Strings object if you want to save a new string file; otherwise you may overwrite a pre-existing string file.
3. Use New String (ns) (or click on the ribbon) to create a closed circular string. You can find the New String in the Home, Structure and Edit ribbons.
button in the
Structure | Design
button in more than one ribbon. It can be accessed
Wireframe Modeling – Constructing Closed Volumes
203
Figure 307: A closed string in the 3D window
4. Click on the string to select it and use the ribbon Edit | Transform | Translate String (tra) command to project copies of the string vertically 50, 100, and 150 meters away from the current viewplane. Leave the X and Y offsets set to zero and make sure the Z offsets are all positive.
Figure 308: Translate string options
5. Hold down the key and the left-hand mouse button to rotate the view to see the strings. 6. Return to a plane view using the command Plan view icon
in the vertical menu on the right
7. Move the view plane to 200m RL using either the Lock option in the mouse position dialog (double click on the coordinates in the status bar) or the ribbon Format | General | Position. When the mouse position is locked at 200m RL, the status bar highlights the RL in red:
8. previously, (ns) below. Use New String to digitize a two point directly aboveposition. the four strings created as shown When you are open done,string unlock the mouse
Wireframe Modeling – Constructing Closed Volumes
204
Figure 309: Lock and unlock the mouse position
9. Rotate the view by holding down the and the left mouse button until you can see all 5 strings. Run the command View | View | Zoom fit (za) so you can clearly distinguish the five strings.
Figure 310: Strings digitized at different elevations
10. You now need to create a new wireframe object otherwise the wireframe you are about to create will be added to the file that contains the topography wireframe. In the current objects toolbar select Wireframe from the drop down menu in the objects box). Then click on the Create New Objects button. 11. Ensure you can see the ribbon Structure | Create as shown below.
12. Click on the End Link
(or the shortcut
Wireframe Modeling – Constructing Closed Volumes
eli) button and select the lowermost string.
205
Figure 311: End link string
13. Select the Link Strings under the button (ls command). A message will appear in the bottom left hand corner of the Status Bar asking you to “Indicate the first string”, select a point on the lowermost closed string. You will now be asked to “Indicate next string to link to this string”, select a point on the perimeter directly above the string you snapped to
previously. The default linking method is Equi-angular shape; sometimes it may link wrongly as shown below:
If you click on the bottom right corner of the Structure | Create ribbon you can access the Project Settings dialog, (using the
icon) and customize the wireframe Linking Method:
14. If the linking of the first two strings is wrong, select on the ribbon Structure | Create to undo. Then navigate to the Project Settings and change the Linking Method to Minimum surface area. Re-link the first and second strings and make sure the look as shown below:
Wireframe Modeling – Constructing Closed Volumes
206
Figure 312: Linked strings
15. Continue snapping points on the remaining strings making sure you work from the lower most closed unlinked string to the top (including the two point string). Press Cancel or Done to close the Link Strings (ls) command Linking pairs of strings more than once will result in duplicate triangles. The latter will cause numerous problems when you use the wireframes for block modeling or for volume calculations.
16. Scroll around to visiualize the wireframe
Figure 313: Completed string links
You will find that the wireframe forms a complete skin around the strings with the exception of a “hole” near the 2 point string
Exercise 2: Linking a Perimeter to an Open String The reason for the hole in the wireframe was the wrong command was used to link the open and closed strings. The Link Strings (ls) command will link 2 open strings or 2 closed strings and so a different command is needed for this circumstance. 1. Use select the Undo Link (ull) on the ribbon Structure | Create to remove the link to the open string (assuming this was the last link you created!)
Wireframe Modeling – Constructing Closed Volumes
207
2. Re-link the 2 strings with the Link to Line button on the Structure | Create | Link | Link to Line ribbon. 3. Rotate and view the wireframe; the hole should no longer be evident Exercise 3: Creating a Wireframe with Multiple Splits In this exercise you will create a wireframe by linking to portions of a string controlled by boundary strings. 1. Erase/Unload the strings using the ribbon Home | Unload| Strings | All Strings (eal) 2. Erase/Unload the wireframe using the ribbon Home | Unload| Wireframes | All Wireframes (eaw). 3. Return to a horizontal view plane by accessing the RM.
icon on the right hand side of Studio
4. Create a set of perimeters which are made up of a single perimeter on one plane and three smaller perimeters on a second plane 50 meters above the first plane.
Figure 314: Closed strings
5. Digitize two, two point open strings with the end points snapped to points (use the right hand mouse button) on the ellipse shaped perimeter as illustrated below. You may need to insert additional points onto the perimeter. These points MUST be snapped.
These points MUST be snapped. Figure 315: Tag strings
Wireframe Modeling – Constructing Closed Volumes
208
6. Rotate the view in the 3D window so that the completed strings should appear as below:
Figure 316: With completed strings
7. Select the ribbon Structure | Create | Link | Link Boundary (lbo) and when prompted click on the left hand side of the base string (indicated by the label A). Then click on the string labelled B.
Figure 317: With boundary link
8. Re – run the Link Boundary command to create a wireframe between the other two sections.
Wireframe Modeling – Constructing Closed Volumes
209
Figure 318: Link boundary completed
The Link Boundary (lbo) command assumes you will select two closed strings one of which will be crossed by 1 or more open strings. The ends of the open string MUST be snapped onto a point on the perimeter. These open strings are treated as boundary strings by the Link Boundary (lbo) command. If you tried to link the stings with the Link String (ls) command, the boundary strings would have been ignored. To close off one or more of the regions defined by the perimeter and the boundary strings, you will need to use the End Link Boundary (elb) button. This command assumes you select a perimeter crossed by one or more boundary strings unlike the Link | End Link (eli) command which ignores boundary strings. 9. the Unlink the central centre link. link using Undo Link | Unlink Wireframe (uw) from the ribbon and select 10. Use the End Link Boundary button to create the centre section between the 2 boundary strings. Make sure you snap onto a point in the perimeter between the two boundary strings. Do NOT snap onto a boundary string itself. The view should look similar to the following.
Figure 319: End link boundary
Wireframe Modeling – Constructing Closed Volumes
210
Exercise 4: Creating Tag Strings In this example, you will create Tag Strings that will link the Northern and Southern upper and lower mineralized zones sections of the example string file _vb_minst. These will be digitized from West to East and will be colored red. There will be 6 separate strings for each of the top and bottom edges, 3 to the north and 3 to the south. Tag Strings are special types of strings that are used to allow advanced control options in the String Linking wireframing command. This will be used in the later wireframe Modeling examples.
1. Erase/Unload the strings using the ribbon Home | Unload | Strings | All Strings (eal); Erase/Unload the wireframe using the ribbon Home | Unload| Wireframes | All Wireframes (eaw). 2. Load the string file minst into the 3D window and rotate the view by holding down key on the keyboard and rotating the display whilst holding down the left mouse button to obtain a view where you can see the strings clearly.
Figure 320: Ore strings to link
3. Zoom into an area using the Zoom In (zx) button, so that the southern edges of the strings are visible.
Figure 321: Ore strings to link
Wireframe Modeling – Constructing Closed Volumes
211
4. Run the Structure | Create | Tag String (tgs) command and using Right-click (snap), digitize the Tag String for the top of the upper mineralized zone (green), starting in the West, moving towards the East, by snapping to the existing section strings points. 5. Click Done to stop digitizing and then click Redraw (rd) to refresh the display.
Figure 322: Tag string
Remember you can zoom and pan the view whilst digitizing.
6. Check your tag string from various directions by using the rotation, panning and zooming tools. 7. using If required, selectPoints the Tag String and moveClick any Done misplaced points to their correct positions by the Move (mpo) command. to stop editing the string. 8. To save the file right click on the item minst.dm (strings) in the Sheets or Loaded Data control bar and select Save. 9. Now use the create tag string (tgs) command to create a tag string along the contact between the two zones.
Figure 323: Tag strings
Wireframe Modeling – Constructing Closed Volumes
212
10. Repeat this procedure for the base of the lower mineralized zone. This will result in 3 sets of tag strings along the southern edge of the mineralized zone. 11. Create another 3 sets of strings using the same steps along the northern edge of the mineralized zone. Remember to save your strings at regular intervals by ri ght-clicking on minst (strings) in the Sheets or Loaded Data control bar and selecting Save.
Figure 324: Tag strings
Exercise 5: Creating the upper mineralized zone wireframe using tag strings 12. In the 3D window, locate the Current Objects toolbar. Select the “Wireframe ” option from the Object Types dropdown Click Create Object button. A new object New Wireframe should now be displayed in the Wireframe Objects list in the Current Objects toolbar. 13. Check that the New Wireframe object has been added to the Sheets and the Loaded Data control bars. 14. In the Structure | Create | Tag String (tgs), toggle on the Use Tags button, if it is not on (it will turn orange when toggled on). 15. Use a global filter to display only the Tag strings (colour code 2 (red)) and the upper mineralized zone strings (colour code 5 (Green)) using the ribbon Format | Filter | Strings as shown:
Figure 325: Format | Filter | Strings
Using this filter ( fs) the parameters appears as shown in the dialog:
Wireframe Modeling – Constructing Closed Volumes
213
Figure 326
16. Click on the Save Expression button before clicking OK.
Figure 327
17. Select the End Link button and close the ends of the ore body volume by selecting the far western section string and the far eastern section string. Click Done to complete the end links. Check that the wireframes have been created for the two end sections.
Wireframe Modeling – Constructing Closed Volumes
214
Figure 328
18. Select the Link Strings button and starting at the far western section string select each of the 10 section strings in turn. Click Done button to stop the linking function. Watch the Status bar at the bottom of the Studio RM window for messages during the string linking procedure.
19. Check that your wireframe for the upper mineralized zone is as shown below:
Figure 329
Check that the wireframe triangles correctly represent the surface as defined by the section strings. The wireframe is a closed volume containing both wireframe surfaces at each end and between each section string. There should not be any gaps or holes in the wireframe 20. Save the wireframe by selecting the Save Object button make sure this file is saved in your project file.
in the Current Objects toolbar;
21. Select the Extended Precision Datamine (.dm) file button in the dialog and enter the filename mintr before clicking on the Save button. You could also right click on the New Wireframe item in the Loaded Data control bar and select Data | Save as. You could also use the shortcut ww (write wireframe data)
22. Save the whole project file using
| Save.
Wireframe Modeling – Constructing Closed Volumes
215
23. Click OK to automatically reload data in the 3D window Exercise 6: Creating the lower mineralized zone wireframe. 24. Use the ribbon Format | Filter | Strings to display only the tag strings (colour code 2 (red)) and the lower mineralized zone strings (colour code 6 (cyan)) with a filter as follows:
Figure 330
The newly created wireframe of the upper mineralized zone may be obscuring the view of the lower mineralized zone strings making it difficult to wireframe the lower zone. Therefore a filter needs to be set to hide the upper zone wireframe. 25. Run the command Format | Filter | Wireframe Triangles (fwt) and enter the following filter expression.
Figure 331
26. Make sure that mintr/minpt is selected as the wireframe object in the Current Objects toolbar.
Figure 332
If you do not do this step then the wireframe will be part of one of the other wireframe files you have loaded.
27. Select the End Link button and close the ends of the ore body volume by selecting the far western section string and the far eastern section string. Click Done to complete the end links
Wireframe Modeling – Constructing Closed Volumes
216
28. Select the Link Strings button and starting at the far western section string select each of the 10 section strings in turn. Click Cancel to stop the linking function. 29. Save the wireframe by selecting the Save Object button in the Current Objects toolbar. 30. Remove filters for the strings and wireframes by using the ribbon Format | Filter | Erase All Filters.
Figure 333
31. Save the whole project file using
| Save.
32. Click OK to automatically reload data in the 3D window
Additional Exercises Additional Exercise 1: Wireframing towards an open string. 1. Digitize four closed strings (polygons with any shape) and a straight, open string. Space the strings 50 metres apart so that they look similar to the example below. Link all of the strings to create wireframe solid and confirm the wireframe is correct by viewing in the 3D window. 2. Write the specifics for the exercise below. String Filename Wireframe Filenames
Additional Exercise 2: Create Bifurcated Wireframes 1. Digitize three closed strings (polygons with any shape) in a row and in the same plane. Then digitize a closed string which surrounds the first three in the plane they were digitized but is in a plane 50m away (they should look something like the blue strings in the example below). 2. Link the strings so that the final wireframe is a solid which bifurcates (e.g. like trousers for someone with three legs). Confirm the wireframe is correct by viewing in the visualiser. 3. Write the specifics for the exercise below. String Filename Wireframe Filenames
Wireframe Modeling – Constructing Closed Volumes
217
C HAPTER
11
WIREFRAME MODELING – MANIPULATING WIREFRAMES In this chapter, you will learn to:
Use various techniques to manipulate and edit wireframes
Use Boolean tools tocombine, separate and extract wireframes
Verify wireframes
Evaluate wireframes
Determine the true thickness of an ore body
Principles When should I use wireframe manipulation? Wireframe Manipulation techniques are typically used to generate new:
Wireframe objects from the interaction of two loaded wireframe objects, i.e. to create a new combination or subset of interacting surfaces Wireframe or string objects from the interaction of a wireframe object and a defined plane(s) i.e. to create wireframe slices or strings.
These manipulation techniques are grouped according to the following categories:
Boolean Operations: These include the generation of a new wireframe from the union, intersection or difference between two or more wireframes. It also includes the generation of intersection strings between two or more wireframes. Plane Operations: These include splitting a wireframe at a particular plane. It also includes projecting DTMs to a defined plane. Other Commands verify, optimize and calculate wireframe volumes. Wireframe manipulation techniques require the wireframe objects to be loaded so that they can be selected for processing.
How do I select wireframes for manipulation or editing? The key to successfully using the manipulation and editing commands is to fully understand the options for selecting the wireframe or portion of wireframe that you wish to process. In the bottom right corner of the Structure | Create ribbon you can access the Project Settings dialog, (using the icon). There are five methods for selecting wireframes. Each of these options is defined using a toggle switch. The chosen selection method will govern all the commands used to modify and evaluate wireframe data.
Wireframe Modeling – Manipulating Wireframes
218
Selection Method
Description
By Object
Controls the selection of wireframe data by object names. This will cause selection of wireframe data by prompting for wireframe point and triangle filenames.
By Group
Controls the selection of wireframe data by picked wireframe group. Select wireframe data matching the wireframe group of a triangle selected with the cursor.
By Surface
Controls the selection of wireframe data by picked wireframe surface. Select wireframe data matching the wireframe group and surface numbers of a triangle selected with the cursor.
By Attribute
Controls the selection of wireframe data by user attributes. Select wireframe data by the user defined attributes associated with a triangle selected with the cursor. The wireframe group and surface numbers are ignored on input, and new group and surface numbers will be generated on output.
Custom
Controls the selection of wireframe data by user defined filters. Select wireframe data by user defined point and triangle file filters. The fields available in the point file are GROUP, PID, XP, YP and ZP. The fields available in the triangle files are GROUP, SURFACE, LINK, TRE1ADJ, TRE2ADJ, TCOLOUR, COLOUR, NORMALX, NORMAL-Y, NORMAL-Zand any other user-defined attributes. The wireframe group and surface numbers are ignored on input, and new group and surface numbers will be generated on output.
Attribute fields identifying separate wireframes in terms of rock or zone type are a key component of wireframe files. They allow individual wireframes to be identified and are also passed onto model cells when used to build block models. All wireframe attribute fields are stored in the wireframe triangle file. In addition to user defined attribute fields there are four standard Studio RM attribute fields added to every triangle file. These fields are described below
GROUP: In addition to user defined attribute fields there are 4 standard Datamine attribute
fields added to every triangle file. These fields are described below:
SURFACE: A wireframe with a unique GROUP value can consist of one or more individual surfaces identified using the SURFACE attribute. LINK: Each wireframe consists of one or more individual links with each link being assigned a
unique number. This field is only used for internal processing.
COLOUR: This field is set to numbers from 1 to 64 and is used to record the color value for
each triangle. These numbers and colors match those displayed when you use the Make DTM (md) or New String (ns) commands. Studio RM controls the actual GROUP, SURFACE, and LINK values assigned to wireframe data. If you want to assign specific values to wireframe attributes, then you should create user-defined attributes for this purpose. Do not rely on GROUP, SURFACE and LINK values to identify subsets of wireframe data. Use different colors and at least one other attribute field.
The classification of wireframes using the GROUP and SURFACE fields provides a means by which wireframes can be identified for operations such as combining and verifying wireframes, which will be described later. It also provides greater control when erasing wireframes. You can erase wireframes by GROUP, SURFACE or LINK and individual triangles. Why do I need to verify my wireframes? You can access the verify wireframe (wvf) command by navigating to the ribbon Structure | Operations | Verify.
Wireframe Modeling – Manipulating Wireframes
219
Figure 334: The Operations group
The command can be used to perform a number of validation checks. These include:
Identification of discontinuities (holes or bifurcations) within a wireframe surface.
Identification of intersection lines after wireframes have been merged.
Identification of self-intersection or crossovers within a wireframe. Checking for duplicate points
Re-assign wireframe GROUP and SURFACE values.
You can also verify a wireframe by right-clicking on the wireframe in the Loaded or Sheets control bars and choosing Verify.
The actions of the Verify command are controlled by a number of toggle switches which are set when the command is run.
You should run the Verify command before carrying out any merging or splitting of wireframes or calculating wireframe volumes.
The checks performed by the wireframe verify command are listed below: Check
Store surface number Check for open edges Check for shared edges Check for crossovers Remove duplicate vertices
Description
Identifies separated surfaces based on face connectivity, assigns a separate index to each surface, then stores that index in the field specified. Searches for edges which not shared between 2 faces. Where found, a new object is created containing strings made up from the open edges. Checks for edges shared by more than 2 faces. If found a new object is created containing strings made up from the shared edges. Checks for faces that intersect, but are not adjoining. Where found, a new object is created containing strings made up from the edges formed by the intersections. Removes multiple instances of vertices which occur in the same location, and combines them into a single reference.
Remove duplicate faces
Removes multiple instances of faces which share the vertex coordinates.
Remove empty
Removes any faces which have zero surface area.
faces
Wireframe Modeling – Manipulating Wireframes
220
Exercises Exercise 1: Verifying Wireframe Objects In this exercise, you will verify the newly created surface topography and ore body wireframe objects, stopotr/stopopt (wireframe) and mintr/minpt (wireframe) respectively. 1. If not already loaded, load the topography wireframe and the mineralized zone wireframe.
Figure 335
2. Select the ribbon Structure | Operation | Verify. 3. In the Verify Wireframe dialog, Name group, select the stopotr/stopopt (wireframe) object. 4. Tick and select the options as shown in the dialog and click OK.
Figure 336
5. To Verify the mineralized zone wireframes, right-click on mintr/minpt (wireframe) in the Loaded Data control bar and select Verify 6. In the Verify Wireframe dialog, tick and select the options as shown in the dialog below:
Wireframe Modeling – Manipulating Wireframes
221
Figure 337 The Shared Edges shown in the results summary represent the shared edges between the upper and lower mineralized zone wireframes. The Intersections found indicates that two wireframe triangle faces intersect.
7. Depending on the accuracy of your wireframe linking and the verify options selected, one or more new entries have been added to the Sheets or Loaded Data control bar:
Figure 338
These overlays (and associated objects) are generated when Shared Edges or Feature Edges and Crossovers/Intersections are detected during wireframe verification. These objects can be used to indicate areas in the source string objects that may need editing. 8. Turn off the display of stopotr/stopopt (wireframe) and mintr/minpt (wireframe) in the Sheets control bar. 9. Check that any Shared Edges and Crossovers/Intersections string objects, to determine where the wireframe needs editing:
Wireframe Modeling – Manipulating Wireframes
222
The Shared Edges around the outside edge indicate the intersection of the upper and lower mineralization zone wireframes - this is correct. The Shared Edges on the inside of this outside edge indicate possible gaps between the upper and lower mineralization zone wireframes - this is not ideal and the section strings would typically be edited to correct these gaps. In this case, this is the result of small gaps between the upper and lower mineralization zone strings in section 6. The Crossovers/Intersections, if any, indicate an overlap between the upper and lower mineralization zone wireframes - this is also not ideal and would typically be corrected before using the wireframe for further volume calculations or block modeling commands. In this example, these detected "errors" can be ignored as they have little impact on following exercises. Exercise 2: Calculating the Volume of a Wireframe Object In this exercise, you are going to calculate the volume for the ore body. 1. Turn off the display of all objects except for the ore body wireframe. 2. In the Loaded Data control bar right-click on mintr/minpt (wireframe) and select Calculate Volume. 3. In the Calculate Volume dialog, define the settings as shown below and then click OK.
Figure 339
The Verify option is not selected as this wireframe object was verified in the previous exercise. If a Density value (other than 1) is specified, the tonnage can be calculated. It is possible to specify an output file to open/edit in a spread sheet. Volumes can also be calculated for open wireframe surfaces (DTMs) using this technique.
Volumes for closed volume and open surface wireframes can also be calculated using Volumes for closed volume and open surface wireframes can also be calculated using Structure | Process | File Processes | Volume (TRIVOL).
Wireframe Modeling – Manipulating Wireframes
223
Exercise 3: Using the Boolean operations: Extract Separate In this exercise, you are going to create a new wireframe from two wireframes. 1. Turn on the display of stopotr/stopopt (wireframe) in the Sheets control bar and load the _vb_trc_pit240tr /_vb_trc_pit240tr (pit wireframe)
2. Using the ribbon Structure | Operations | Boolean and select Extract Separate and choose the options:
Figure 340
You can also toggle off the “single object output’ to generate different combinations of files that can be combined later using the ribbon Data | Objects | Combine.
3. Check that the output looks as shown:
Figure 341
Exercise 4: Using the Boolean operations: Intersections In this exercise you are going to create the intersection string between 2 wireframes
1. Turn on the display of stopotr/stopopt (wireframe) and _vb_trc_pit240tr /_vb_trc_pit240tr (pit wireframe) in the Sheets control bar 2. Using the ribbon Structure | Operations | Boolean and select Intersections and choose the options:
Wireframe Modeling – Manipulating Wireframes
224
Figure 342
3. Check that the output looks as shown:
Figure 343
Additional Exercises Additional Exercise 1: Plane Operations – Multiple Sections In this exercise, you are going to split a new wireframe into several string sections. 1. Turn on the display of stopotr/stopopt (wireframe) in the Sheets control bar 2. Using the ribbon Structure | Operations | Plane | Generate Strings and select Multiple sections and choose the options:
Wireframe Modeling – Manipulating Wireframes
225
Figure 344
3. Check that the output looks as shown:
Figure 345
Additional Exercise 2: Extract wireframes and Add wireframes In this exercise you are going to learn how to extract two wireframes from a single wireframe based on a key field, and later add the two wireframes
1. Turn off the display of all loaded data except mintr/minpt (wireframe) in the Sheets control bar 2. Using the ribbon Data | Objects | Extract , so that the following dialog appears:
Wireframe Modeling – Manipulating Wireframes
226
Figure 346
3. It will prompt you to accept if you wish to create 2 objects. When you click OK, the following 2 files will appear in you Sheets control bar
Figure 347
4. Save the two wireframes by right-clicking in the Sheets control bar, and go to Data | Save As Datamine Extended Precision File zone1_tr and zone2_tr 5. To add the two wireframes, use the ribbon Structure | Process | Add Wireframes (ADDTRI) and populate as shown:
Figure 348
Wireframe Modeling – Manipulating Wireframes
227
You can add 2 or more wireframes by access the combine data option on the ribbon Data | Objects | Combine and select wireframes.
A number of wireframe processes are found under the ribbon Structure | Process | File Processes, including: •
Calculate Triangle Centres ( COGTRI): This process calculates the centre of gravity and orientation of each triangle in a wireframe file.
•
Trend Surfaces ( WFTREND): This process creates a DTM wireframe surface which can be extended
•
beyond the data limits by a specified distance using a planar trend surface. Evaluate Against Wireframe ( TRIVAL): Evaluate a cell model against a wireframe model.
•
Select Using Wireframe ( SELWF): Select records lying inside/outside wireframe models or above/below triangulated (DTM) surfaces.
•
Project Strings to wireframe ( PERDTM): Project 2D perimeters to 3D perimeters in wireframe DTM surface.
•
Section strings from wireframe ( WIREPE): "Section" wireframe to produce perimeters.
Wireframe Modeling – Manipulating Wireframes
228
C HAPTER
12
INTRODUCTION TO MACROS AND SCRIPTS In this chapter, you will learn to:
Record macros to be able to easily repeat tasks in Studio RM
Edit recorded macros tocustomize it
Understand the differences between macros and scripts
Principles There are two sets of tools available for automating tasks in Studio RM, i.e. macros and scripts. These automation technologies are quite different in nature and have different scope and application in terms of how they can be used. The purpose of this chapter is to provide a brief introduction of these automation technologies and how they can be best applied. The use of macros in Studio RM A macro is in essence a text file which is used to run a series of processes using the user defined files, fields and parameters. This facility allows you define a particular set of processes and then rerun those processes as required without having to run each process manually. Macros makes use of Datamine’s proprietary macro language to automate tasks involving Studio RMprocesses. The macro can either be created within Studio RM by recording a sequence of steps or they can be created in a text editor, e.g. Notepad ®. Macros can be used to do the following: •
To simply and regularly record processing steps.
•
To create basic data capture and processing systems.
•
To keep an audit trail or official record of work done.
It is important to note that macros are only suitable for automating Studio RM processes – not Studio RM commands. In other words, macros can be used for file based data – not object based data.
The use of scripts in Studio RM Studio RM also has a complete published Component Object Model (COM) that can be accessed through scripts, using JavaScript or VBScript, or any COM-aware scripting languages. These scripts can be embedded into an HTML document, which can be loaded into the Studio RM Customization window to execute Studio RM commands or processes. Potentially the degree of automation that can be done with scripts in Studio RM is much higher than with what can be done with macros. Also, there is much more flexibility in terms of what can be done with the interfaces of these scripted systems. However, to fully utilize scripting for automation of Studio RM requires a high level of programming skill, extensive knowledge of the scripting language (mostly JavaScript embedded in an HTML page) and knowledge of Studio RM’s object model. Studio RM also provide a facility to record a sequence of processes in a script.
Introduction to Macros and Scripts
229
Even though commands and processes can be automated in scripts, it is important to note that only processes can be recorded using the script recording facility in Studio RM.
In addition, existing macros can be launched from scripts, getting the best of both worlds. In order to get the best value from the scripting functionality in Studio RM, the following is strongly recommended: •
You should have some prior knowledge of a scripting language such as JavaScript.
•
You should have an understanding of the object-oriented approach to programming, and understand the concept of objects, methods, properties and events.
•
You should have an understanding of common Studio RM commands and processes, and the Studio RM object model.
•
You should have appropriate scripting (and script debugging tools) like Visual Studio Express®.
The difference between scripts and macros From the previous sections it is clear that there are significant differences between the scripting and macro functionality in Studio RM. The scripting functionality in Studio RM makes use of standard programming functionality, which makes it more versatile for fully automating aspects of the software. However, it means it is also m uch more complex than using the Studio RM macro functionality. For both technologies there are facilities available in Studio RM to record Studio RM processes. Using the Studio RM object model, scripts can be used to automate more than just processes. In fact, it is possible to create scripted solutions that performs very complex time-consuming operations in the background, shielding the user from the complexity through a simple HTML interface. The team at Datamine have expert knowledge of all Datamine’s packages, and provide custom solutions service perfectly matched to your business requirements. If you wish to discuss the benefits of automated solutions for your business, please contact your local Datamine support office.
Recording macros in Studio RM To start recording a macro in Studio RM on the Home ribbon select Process | Macro | Start Recording. The macro recorder can also be initialized by the MACST process which like any other process can be typed in at the command prompt in the Command control bar.
When you start recording a macro the user is prompted for two entries:
MA C R O NA ME > Fi le name: The name entered at the MACRO NAME prompt is written to the first line of the text file after a START statement. Every macro you examine will start with !START “Macro Name” statement. A common title is BEGIN i.e. !START BEGIN. The file name specified at the ‘File name:’ prompt is used to name the text file which will be used to
store the macro. The convention is that all macro file names are kept lower case and end in a .mac extension e.g. test.mac. On your computer it is the file name you would see if you listed the contents of a directory using the Windows Explorer® browser.
Introduction to Macros and Scripts
230
To stop the macro recorder on the Home ribbon select Process | Macro | Start Recording. The macro recorder can also be stopped by the MACEND process which like any other process can be typed in at the command prompt in the Command control bar.
When you stop the macro recorder, it adds an !END statement to the end of the text file and saves it to the user-defined file name. Editing Studio RM macros It is possible to edit and modify a Studio RM macros in a text editors such as Notepad®. Open the macro file (*.mac extension) in the text editor. When you edit a macro, you need to be mindful of the basic macro structure and the correct macro syntax. Please refer to the Studio RM online Help for examples of specific macro syntax. When you edit a macro in an external text editor, there are four important points to remember: •
Keep individual macro lines less than 80 columns wide.
•
When adding extra file, field, and or parameter values make sure the use of commas is consistent. Each new value for a specific process is separated by a comma with no trailing comma for the last value, e.g. !MGSORT &IN(HOLES),&OUT(XXTMP1),*KEY1(LODEID)
•
Avoid the use of key strokes in your macros.
•
Ensure that all standard fieldnames use CAPITALS.
The basic structure of a simple macro is as follows: Start 2> End
The table below shows standard symbols to define syntax used in a macro file: Symbol
! &
Description
Indicates Studio RM process. All Studio RM processes start with an exclamation mark symbol, are up to 6 characters long, and end in a space. All File names are distinguished with the “and” symbol. Note that there is always a space between the process name and the first file name.
*
All fields are distinguished using an asterisk symbol.
@
All parameters are identified using an “at” symbol.
For any given process all file, field, and parameter settings are separated by commas. The process name and the first file settings are separated by one or more spaces. Macro Commands is a special category of commands. These commands are used to enhance macros by providing simple programming functionality such as looping, conditional statements and data entry prompts. The macro commands cannot be accessed from the interface. These macro commands do not have any file output, but are instead used in conjunction with other processes within a macro. They function only within a macro.
Macro commands include the following commands: LOADCF, MACEND, MACST, MDEBUG, MENU, NOMENU, NOXRUN, OPSYS and XRUN. Please consult the online Help for more information.
Introduction to Macros and Scripts
231
Exercises Exercise 1: Recording a macro to calculate statistics on a field In this exercise you will record a macro to capture the steps required to calculate the AU grades for each value of NLITH. Follow these steps: 1. In the Home ribbon select Process | Macro | Start Recording and supply a macro name (‘AUCALC’) in the command prompt box:
2. Give the macro a filename, test1, as follows:
3. In the Data ribbon, select Data Tools | Sort. This activates the MGSORT process. Run the process with the following file and field settings: MGSORT Files tab IN
_vb_holes
OUT
xxtmp1
Fields tab KEY1
NLITH
4. Check the output file (xxtmp1.dm) is correctly sorted by opening the file in the Datamine Table Editor. 5. In the Sample Analysis ribbon select Statistics | Statistics Processes | Summary Statistics. This activates the STATS process. Run STATS on the xxtmp1 files with the following settings:
Introduction to Macros and Scripts
232
STATS Files tab IN
xxtmp1
OUT
xxtmp2
Fields tab F1
AU
KEY1
NLITH
6. Click OK to run the process. You will need to press return 4 times as the STATS process will display summary statistics for each rock zone in the Command control bar. To run the STATS process with a keyfield requires the input file to be sorted on the necessary keyfield. This is why we did a sort using MGSORT first.
7. Examine the xxtmp2 file in the Datamine File Editor. It will contain 4 records for each of the four NLITH values (1, 2, 3 and 4). 8. On the Data ribbon select Transfer | Text | Datamine File to Text . This activates the OUTPUT process. Run OUTPUT on the xxtmp2 file using the following settings: OUTPUT Files tab IN
xxtmp2
Fields tab F1
NLITH
F2
FIELD
F3
MEAN
F4
MAXIMUM
F5
MINIMUM
Parameters tab CSV
1
9. In the Select File dialog enter the filename results.txt: 10. In the Home ribbon select Process | Macro | End Recording to stop recording the macro. 11. View the results.txt file in a text editor such as Notepad. Note that the header information has also been included in the text file. 12. Close the results.txt text file before moving onto the next exercise. Exercise 2: Editing and Replaying the Macro In this exercise you will edit the macro created in the previous exercise to report the VARIANCE values for each of the NLITH rock codes, using a text editor and replay the macro in Studio RM. 1. Select the Project Files control bar, open the Macros folder and double click on the file test1.mac.
Introduction to Macros and Scripts
233
There are 4 blank lines between the !STATS command and the !OUTPUT command. These blank lines are important as they represent the number of times you hit the Enter key to display the stats for each NLITH code during the STATS process. Do not remove these blank lines.
2. Now edit test1.mac text and add the text marked in bold below. You must always be very careful when editing macros and avoid syntax errors as such errors will cause the macro to stop with an error message. In particular, note that each file, field, and parameter statement is separated by a comma and that there is no comma after the last parameter (or field in the case of STATS).
In addition to adding the DELETE and ECHO processes you have also added some comments. These comments are all preceded with a hash and a space. This ensures they will be ignored by Studio RM. Instead of the “#” statement you can also use !REM to precede comments. It is strongly recommended you put comments in your macros describing what the macro does and documenting any subsequent changes.
3. Save the macro test1.mac and close the text file. 4. In the Home ribbon select Process | Macro | Run Macro and select test.mac. Check that the VARIANCE field is created and the temporary files are deleted.
Introduction to Macros and Scripts
234
Exercise 3: User Interaction with a Macro This exercise deals with the use of substitution variables which allow you to assign a value to a variable within a macro. Substitution variables are used in macros rather than fixed values where it is necessary for a macro to process a particular file, field or parameter setting and these settings are likely to change. As an example you may wish to calculate the mean and variance of attribute fields in various database files. The database files will all have different names and the attribute fields you are calculating statistics on are also likely to change. The PROMPT process allows you to display text on the screen and prompt for input from the user. Values typed in at the PROMPT process are assigned to substitution variables. This process allows menu screens to be built up and substitution variables defined and redefined as required.
Each line after the PROMPT process starts with a 0 or 1. Text following a 0 is simply printed in the Command window, while lines started with 1 are used when defining a prompt statement requiring user input. A variable name is identified by starting each name with a dollar sign and ending the name with a hash symbol. The length of the variable, including the # and $, is 16 characters.
In the example below, the macro prompts for a filename and then uses the COPY process to copy the specified file to a new file.
All prompt lines (lines starting with 1) end with a variable name, and an “a” or a “n” to define alphanumeric or numeric variables. There are also optional entries to further define what are valid and non-valid responses. In the above example the a,8 indicates the variable is alphanumeric and up to 8 characters long. Default values can be specified in square brackets. The following example macro uses a PROMPT process to enter a single numeric value and assign the value to $num#, the default is 1.
1. Open the test1.mac macro in the editor and make the following changes, marked in blue text:
Introduction to Macros and Scripts
235
2. Test the changes in the macro by select Process | Macro | Run Macro In the Home ribbon. Then select test1.mac. Enter the filename, _vb_holes1, when prompted in the Command window (this file was created earlier by the compositing process COMPDH). If the filename you enter does not exist in the project folder, the macro will abort. 3. Compare the results in the two results files, results.txt and results1.txt, in the text editor.
Additional Exercises Additional Exercise 1: Record the same actions as Exercise 1 in a script. Use the script recording functionality in Studio RM to record the same actions as in Exercise 1 in a script.
Introduction to Macros and Scripts
236
C HAPTER
13
BLOCK MODELING In this chapter, you will learn to:
Understand the basic theory of block models
Use the extents of the data to build a block model
Use wireframe surfaces and solids to create zones inblock a model that canbe used for estimation
Learn how to manipulate block models by adding them together and optimizing
Principles Studio RM has a powerful set tools to create a geological block model. In this section you will construct a block model based on the wireframes and drillhole files created in the previous exercises and view the resultant model in the 3D window. The model will have an upper constraint defined by the topography and use the ore body volume wireframe to control the internal constraints between ore and waste. The resultant model will be used in the following section which deals with estimation of grade into the model cells. All block modelling commands may be found on the Model ribbon menu. The first group is Create, which contains the tools for creating a new volumetric model from geology data, wireframes and/or strings.
Figure 349: The Create group in the Model ribbon
The second group in the Model is the Manipulate group. The Manipulate group contains tools to combine, split, regularise or optimise models and to interactively edit models.
Figure 350: The Manipulate group in the Model ribbon
The last group in the Model ribbon is the Data From Model. This menu contains tools to create new strings, drillholes or wireframes from a block model. These tools are also useful after grade estimation (see the chapter on grade estimation for more details).
Figure 351: The Data From Model group in the Model ribbon
Block Modeling
237
Wizards used for block modelling There are two wizards available for block modelling. These wizards are the Auto Prototype (Model | Create | Auto Prototype) and Volumetric Block Modelling (Model | Create | Fill Wireframes) . These are explained in further detail in this chapter and the exercises that follow. Batch processes used for block modelling All block models are built and processed using wizards and batch processes. The 3D Window and Plots windows can be used to view and evaluate the block model. This section deals with the concepts behind Studio RM block models and common batch processes used in block modelling:
PROTOM – Defines a 3D matrix in which blocks will be built.
TRIFIL – Fills wireframes with cells
ADDMOD – Adds 2 models together
REBLOCK – Creates a new block model on new parent X, Y and Z cells
Other commonly used batch processes are:
SLIMOD – Resets a model prototype, recalculates the IJK field and slices cells accordingly.
PROMOD – Optimizes the use of subcells in a model
REGMOD – Regularizes a block model to parent cell blocks
All these, and other, commands are available in the Block models can be edited interactively in the 3D window using the quick key ‘ecp’ or ‘edit -modelcell-values. If you have to make changes to a lot of cells in a block model, this is easier to do using batch commands
For further information refer to the online Help. Controlling cell sizes in the model A block model is composed of rectangular blocks or cells, each of which has attributes such as grades, rock types, oxidation codes, etc. A parent cell is the largest cell allowed in the model. The size of these cells is defined by the user and should be based on several factors such as the drillhole spacing, mining method, and the geological structures hosting the ore. The concept of a "parent cell" is largely a descriptive term. The only visible product you will see based on the parent cell dimensions is the restriction on the maximum cell size and the fact that cells will never cross the parent cell boundaries. What is subcelling and why is it necessary? Block modelling is all about approximating the volumes below surfaces such as topography or within specified 3D regions such as mineralized zones. In both cases the surfaces and 3D volumes are usually defined using wireframes. Cells are used in preference to the wireframes when it comes to resource modelling because the attributes being modelled will vary within each wireframe zone. As an example the grade of a gold bearing quartz vein will vary with location. Subcelling allows you to subdivide the parent cells into smaller cells to better fit the dimensions of the wireframes. The more subcell splitting you allow for, the closer the fit. The trick is to set the level of subcelling to get a reasonable fit without exceeding what is practical. R emember g eolog ic al boundari es are at bes t
approximations.
Block Modeling
238
Each cell in a model is a record in the file. Excessive use of subcelling is unlikely to improve the final result.
How to start creating a model The creation of a block model in StudioRM always starts with the use of the Auto Prototype (Model | Create | Auto Prototype) wizard to define the model prototype. This tool helps you to define a model prototype using data that is loaded into the 3D window.
Figure 352: Create Model Prototype dialog box
The Auto Prototype creates a prototype model based on the extents of any loaded data, by choosing one of the following types of methods:
Copy an existing prototype
Fit un-rotated prototype from data extents
Fit rotated prototype using existing rotation angles and data extents
Fit a 2D rotated model using data extents
Fit a 3D rotated model using data extents
Once the extents have been determined, you may interactively edit the properties and preview the model prototype. The following properties can be set:
Cell Sizes in X, Y and Z
Origin locations in X, Y and Z
Maximum coordinates in X, Y and Z Number of cells in X, Y and Z
Data margins in X, Y and Z Take care to round down cell srcins to integer numbers rather than decimals. This makes working with your block model easier.
This process creates an empty file with standard model field names. Included in these standard fields are six implicit fields (fields whose value are constant) which are used to store the srcin of the model
Block Modeling
239
and the number of cells in the three orthogonal directions. Effectively the prototype model defines a 3D area using your local grid in which a block model is to be built.
The model srcin takes the value of the coordinates of the bottom left corner of the cell in the southwestern corner of the model and NOT its centroid. .
The standard fields in a Studio RM block model are listed as follows: Field Name
Explicit or Implicit
Description
XMORIG
Implicit
Eastingcoordinateof the model srcin
YMORIG
Implicit
Northingcoordinateof the model srcin
ZMORIG
Implicit
RL coordinateof the model srcin
NX
Implicit
Numberof parent cells in the X direction
NY
Implicit
Numberof parent cells in the Y direction
NZ
Implicit
Numberof parent cells in the Z direction
XINC
Explicit
X axis cell dimension
YINC
Explicit
Y axis cell dimension
ZINC
Explicit
Z axis cell dimension
XC
Explicit
X coordinateof the cell centre
YC
Explicit
Y coordinateof the cell centre
ZC
Explicit
Z coordinateof the cell centre
IJK
Explicit
Integer which is unique for each parent cell and used to index subcells
These fields are represented graphically in Figure 353.
Block Modeling
240
Figure 353: The graphic elements that the model fields represent
If you define a rotated block model then a further 9 implicit fields will be added to the model file to define the two grids and the rotation factors. If you wish to use rotated block models then you learn more about it in the online Help.
It is not necessary for each parent cell location in the 3D region defined of your prototype to contain actual cells. As an example, the final block model will usually have no cells above the current topography surface.
Viewing a prototype model or block in the 3D window By default, block models are displayed as Quick Sections in the 3D window. To change the view properties, right click on the model and select properties under 3D | Block Models in the Sheets control bar; or by double clicking on the model in the 3D window. Below is the block model displayed as an intersection, quick section and blocks. The display of block models is covered in more depth in the Visualization chapter.
Figure 354: Different ways of displaying a block model in the 3D window
Block Modeling
241
A prototype model contains no records, but the bounding block showing the extents of the model file can be viewed. Once you have created and saved a prototype model, this model can be loaded (by dropping and dragging) into the 3D window. The standard fields of prototype model can be viewed and edited in Datamine Table Editor, by opening the file and using Tools | Definition Editor menu. Here you can view and edit the default value of the any Implicit or Explicit fields.
How to fill ore zones with model cells The Volumetric Block Modelling (Model | Create | Fill Wireframes) command creates a block model from multiple wireframes including a digital terrain model (DTM) and/or a solid wireframe model. The process automatically creates a block model based on a series of TRIFIL and ADDMOD commands that are automatically run. The TRIFIL process works by forming a m atrix of possible locations of cell centroids, around which cells are created if they lie within/outside/above/below etc. the wireframe used The ADDMOD process adds the model files together in the order which you specify. To find out more about these processes, refer to the online Help. The process requires a minimum of a model prototype file and one or many wireframe files.
Figure 355: Volumetric Block Modeling dialog box
The process requires the user to select a prototype model or to create a new one. Select a control perimeter (optional) that restricts your model to areas lying within the perimeter. Boundary Wireframe ParameterDescription
Block Modeling
Run
Use this wireframe
Topo
Tick if the wireframe is atopography
Wireframe
Select wireframe triangle file.
242
Zone field
Select a zone field (Default value is ZONE)
Zone code
Sets the zone field a value or from the wireframe.
Plane
Orientation for sub-celling
Boundary Type
XY – Horizontal subcelling
XZ – West east subcelling
YZ – North south subcelling
Select how the model gets filled:
Solid 3D interior to be filled with cells.
Solid 3D exterior to be filled with cells.
DTM surface to be filled below with cells.
DTM surface to be filled above with cells
Create cells between 2 DTM surfaces
Two surfaces. Cells are to be filled above
Use perimeter
Restricts cell filling to inside the perimeter
Density
Set the density
All options of the volumetric model building settings to a file that can be loaded at a later stage.
Subcelling (for each boundary wireframe) can be specified by defining the Number of Subcells in each direction and resolution, or by specifying the number of subcell splits. When selecting multiple boundary wireframe files that will be used to build the block model, the order in which these models should added together should be considered, as shown below.
Block Modeling
243
Figure 356: General process for building a model with different zones
Other ways to create a block model The method Fill Wireframe (Model | Create | From Wireframe) or TRIFIL lets you create a block model manually, where each sub model is created separately, and these models are added together using Combine (Model | Create | Combine) or ADDMOD. The same logic as the boundary types is used to define the MODTYPE parameter in TRIFIL. The other significant parameter settings in TRIFIL are as follows: Parameter
Description
Options
SPLITS
Controls cell splitting and use of X/Y/ZSUBCELL parameters
0, 1, 2, 3
PLANE
Sets the plane perpendicular to the seam filling plane
‘XY’, ‘XZ’, ‘YZ’
XSUBCELLL
Sets the amount of subcelling in the X direction
1-100
YSUBCELL
Sets the amount of subcelling in the Y direction
1-100
ZSUBCELL
Sets the amount of subcelling in the Z direction
1-100
RESOL
Sets the amount of subcelling in the seam filling direction
0-100
Block Modeling
244
How many subcells should I used? This depends on the shape of your geology. The image below shows the same ore body outline filled with cells using varying degrees of subcell splitting. In this case the 3 separate models had the XSUBCELL and YSUBCELL parameters set to 1, 2, and 3 respectively. Note how the overall fit is improved with the increase in the subcell splitting. Note also how the number of cells used rapidly increases with each increment of the 2 parameters, 2 cells in the first model and 16 in the third.
XSUBCELL=1
XSUBCELL=2
XSUBCELL=3
YSUBCELL=1
YSUBCELL=2
YSUBCELL=3
Seam filling Seam filling is a special type of subcelling which can be applied in one direction only. In the direction of seam filling the cell dimension is set automatically to fit the wireframe boundary. The choice of the seam filling direction is determined by setting the Plane parameter to 'XY', 'XZ' or 'YZ'. The Plane parameter defines the plane perpendicular to the direction of seam filling. As an example, if the Plane parameter was set to 'XY', seam filling would apply in the Z direction. In the X and Y directions normal subcell splitting would apply. In the example below the same vein has been modeled 3 times using the 3 available Plane parameter settings. Subcell splitting in the remaining 2 directions has been set to 3.
PLANE='YZ'
PLANE='XZ'
PLANE='XY'
YSUBCELL=3
XSUBCELL=3
XSUBCELL=3
ZSUBCELL=3
ZSUBCELL=3
YSUBCELL=3
Block Modeling
245
RESOL=3
RESOL=3
RESOL=3
Set the seam filling direction to the orientation in which you require the best fit. Set the seam filling direction to the orientation in which you require the best fit.
The Resol parameter The Resol parameter is used to control the length of cells created using seam filling. When applied, it rounds the cell size to a set fraction of the parent cell length in the seam filling direction. In the above image the Resol parameter has been set to 3. This means cells in the seam filling direction will be rounded to the nearest 3rd of the parent cell length in that direction. By default the Resol parameter is set to 0 which means no rounding is applied, i.e. cell lengths in the seam filling direction will give a best fit to the wireframe geometry. The image below shows the same models as above except the Resol parameter has been set to 0. Note that you get a better fit but the cells have widely varying lengths in the seam filling direction.
PLANE='YZ'
PLANE='XZ'
PLANE='XY'
YSUBCELL=3
XSUBCELL=3
XSUBCELL=3
ZSUBCELL=3
ZSUBCELL=3
YSUBCELL=3
RESOL=0
RESOL=0
RESOL=0
Setting Resol to a value reduces the amount of cells created when you add models using ADDMOD. This is because it forces the cell sizes to be one of several fixed lengths.
What if I don’t want any subcelling? A parent cell model may contain no subcelling at all, in which case all blocks will be exactly the same size. To create this type of model, use batch command TRIFIL and set the parameters Splits = 0 and Resol = 0. If you have already have a block model that contains subcells, using the REBLOCK or REGMOD can regularize subcells into parent cells
Block Modeling
246
Combining block models The ADDMOD (Model | Create | Combine) command allows you to combine two models into one by superimposing one model onto another. The resulting output model contains all the fields from both input models. ADDMOD requires both models to have the same model prototype as defined in prototype model. If this is not the case then you will need to reset the prototype of one of the models with the Adjust Prototype (Model | Create | Adjust Prototype) or SLIMOD command. A typical use of the ADDMOD command is to add a grade model onto a waste model. The key to using ADDMOD is the order in which the two input models are specified. If both models contain one or more identical attribute fields with different values, then the second model (In2) will overwrite the attribute field values in the first model where cells overlap or coincide. ADDMOD requires both input models are sorted on the IJK field.
The image below shows 2 parent cell outlines in 2 s eparate models and the end product when the 2 models are combined using ADDMOD. The centre of the two parent cell outlines match, that is, they are both in the same geographic location. In this case model 2 has been added onto model 1.
Figure 357: Cell splitting when models are combined
Exercises In the following exercises you will build 2 block models, one inside the ore wireframe and the other below the topography wireframe, and add them together to generate a single block model which will be used for grade estimation in the following section. The steps will be recorded in a macro, so that if any mistakes are made, the macro can be edited and replayed. You will also learn how to display the model data in the 3D window.
Block Modeling
247
Figure 358: Combining models
Exercise 1: Determining suitable prototype model parameters A prototype model defines the extents of your block model, through setting of the DEFAULT field values in the standard block model file (E.G. XINC, YINC, ZINC, XMORIG, YMORIG, ZMORIG, NZ, NY, NZ plus optional rotated fields) 1. Select the Sheets control bar and turn on the following data objects:
_vb_faulttr/_vb_faultpt (wireframes) stopotr/stopopt (wireframe)
mintr/minpt (wireframe)
2. To create a prototype model, using the Auto Prototype Plus wizard accessed through Model | Create “| Auto prototype or quick key ‘cmp’.
Figure 359: The settings in the Create Model Prototype dialog box
Block Modeling
248
3. Select the loaded data files that should be included in your prototype: _vb_mintr/minpt (wireframe)
4. Click Fit unrotated prototype to data. This option will use the extents of your data to determine a suitable size of your prototype. 5. Set a Cell size for your model, setting blocks of 10m in X by 10m in Y by 5m in Z. Notice how the number of cell count changes when size of your model. 6. Change srcin ( Model size) to round numbers by rounding these numbers down to the nearest sensible value. It is easier to work with a model that has an Origin value of 5600 than 5612. Be consistent with prototype parameters when working with numerous block model, especially when adding and/or manipulating models. This will save you extra work later.
7. Identify the Total number of cells calculation. This tell you the total number of parent cells that your block model could contain.
Figure 360: The settings in the Create Model Prototype dialog box
8. Click Preview Now button to view a box that outlines the block model extents in the 3D window. 9. Once you are satisfied with your prototype parameters, type in modprot as the Output file and click OK to save the prototype. 10. In the Project Files control bar, find the block model modprot.dm and double click to open it. You will notice this file contains no records. Select Tools | Definition Editor to see/edit the default values of the protoype model.
Block Modeling
249
Figure 361: The Definition Editor in the Table Editor
11. Close the block model file. Exercise 2: Defining the Model Prototype - Method 2 Using macros in a script helps you define a workflow that can be repeated. 1. Start the batch command macro recorder by selecting Home | Process | Macro | Start Recording. 2. When prompted use the following macro and text file names: MACRO NAME > proto File Name > lode.mac
3. Once the macro recorder has been started, run Model | Create | Auto prototype. This will load the Auto Prototype dialog from before. Click Restore button to load the previously entered values. 4. Stop the batch command macro recorder by selecting Home | Process | Macro | End Recording. 5. In the Projects Control bar, browse to Macros and double click on lode.mac to open the macro. The macro would have written the batch command PROTOM to the macro. Running this macro will re-create the prototype. Close lode.mac. Exercise 4: Building the Ore Model In this exercise you will build a block model inside the ore wireframe, mintr/pt. This will involve using the Fill Wireframes wizard to fill the wireframe with cells. In this case, the mintr file contains 2 separate wireframes which are each identified by the ZONE field. This field is stored in the triangle file and is set to 1 (upper mineralized zone) or 2 (lower mineralized zone). 1. Run Models | Create Model | Fill Wireframe with Cells setting the following options:
Choose modprot as the prototype block model
Select the _vb_mintr
Set the ZONE field
Choose XY as the plane
Choose Solid Fill Inside as Boundary Type
Block Modeling
250
Set the Subcelling, using 5 subcells in X and Y, with a resolution of 4 Name the output as oremod Click Apply to create the block model
Figure 362: Volumetric Block Modeling dialog box
The Volumetric Block Modelling wizard makes creating block models easier. Block models can also be made using the batch commands TRIFIL (to fill the wireframes with cells), ADDMOD (to combine block models) and SORT (A wireframe created with different zones needs on IJK).
2. Record step 1 of this exercise into a macro. Call the Macro oremod and save this to the same macro file (lode.mac). Exercise 5: Viewing the Model In this exercise the block model will be loaded in the 3D window for viewing. 1. Turn off the display of all data currently loaded using the Sheets control bar. 2. Load the block model, oremod.dm by dragging and dropping from the Projects control bar into the 3D window. 3. By default, a block model is loaded as Quick Section. Right click on oremod (block model) in the Sheets control bar, and select Quick Section Control. This allows you to view the model as a slice in 3D. 4. Using the key and left clicking the mouse, rotate the 3D window while viewing slices through the block model in the IJ, IK and JK planes.
Block Modeling
251
Figure 363: The Section Control dialog box
5. Right-click on the model in the Sheets control bar, and select oremod (block model) properties in the context menu. The properties window gives numerous view options. This window can also be opened by double clicking on the block model in the 3D window. 6. In the properties window, change the display type to Blocks, and press OK. Experiment rotating the display and zooming in and out in the 3D window.
Figure 364: The block model displayed as blocks
Block Modeling
252
Figure 365: The Block Model Properties dialog box
7. Re-open the Display Properties. Change the display type to Intersection. Untick the Show Fill and tick the Show Edges option. This will display the block model as an intersection. Click Ok. 8. To make viewing a block model intersection easier, by clicking View | View | Lock and then option View | View | Align , to lock a 2D view plane in the 3D window. This will allow you to create a section using plane-by-1-point or plane-by-2-points (using the quick keys ‘1’ or ‘2’).
Figure 366: A section through the block model in the 3D window
9. Use create-plot-view (quick key ‘cpv’), create a plot of a section through a block mode.
Block Modeling
253
Figure 367: A section through the block model in the Plots window
10. Unload the model file from the VR window. Exercise 6: Creating a Waste Model In this exercise the waste model (the part of the model that is not ore) will be created. 1. Restart the macro recording using Home | Process | Macro | Start Recording and enter the following when prompted: MACRO NAME > wastemod File Name > lode.mac
As the same file name is being used as with Exercise 1 and 2, the new macro will be appended to the bottom of the previous macro. 2. Run Models | Create Model | Fill Wireframe with Cells setting the following options:
Choose modprot as the Topo Select the stopotr/pt Tick Topo The ZONE field remains as default (this field does not exist in the wireframe), and set the value to 0 Choose XY as the plane Choose Single Surface – Fill Below Inside as Boundary Type Set the Subcelling, using 5 subcells in X and Y, with a resolution of 4
Name the output as wastemod
Click Apply to create the block model
Block Modeling
254
Figure 368: The settings in the Volumetric Block Modeling dialog box
Exercise 7: Adding the Two M odels Together 1. Run Models | Manipulation | Combine (or type ADDMOD in the command line) to create the final model by adding the ore model (oremod) onto the topography model ( topomod) and writing the result to a file called lmodel.
2. Stop the macro recording with the Tools | Macro | Stop Recording command and load the lode.mac macro into a text editor. When you stop and restart the macro recorder using the same filename the new commands are appended to the bottom of the existing macro. 3. Close the text editor and load the lmodel file into the 3D window. Review the extents of the model and zoom in to check the subcelling below the topography and at the edges of the ore wireframe.
Block Modeling
255
Figure 369: Section through block model
Exercise 8: Optimizing the Model The process PROMOD "optimizes" a block model so that the minimum number of subcells is used, without losing accuracy. In this exercise you will use PROMOD to:
Check for overlapping cells and resolve them if they exist.
Combine sub-cells to create the minimum number of sub-cells for each parent cell.
1. Run Models | Manipulate Models | Optimize Model , or enter PROMOD in the command line. 2. Enter the following files, fields and parameters in the PROMOD dialog.
3. Load the file opmodel into the Design window and Zoom In to observe the model cells. Notice that there are now fewer sub-cells.
Block Modeling
256
Figure 370: Section through block model
Exercise 9: Using the Fill Wireframe wizard to create block model In this exercise, see if you can repeat exercises 4, 6, 7 and 8 in one step, using only the Fill Wireframe wizard. 1. Visually compare the two models to check your results. 2. Determine if the number of records between the model created using the Fill Wireframe Wizard and TRIFIL, ADDMOD and PROMOD are the same. You can use the Datamine Table Editor to see how many records a file contains.
Exercise 10: Reblock a model to new cell sizes In this exercise the block sizes of an existing model will be changed from 10m x 10m x 5m to 20m x 15m x 5m. The REBLOCK process is a new process in Studio RM.
1. Launch the process Model | Manipulate | Reblock. 2. Select the Input file as opmod and the Output file as reblmod. In the Fields tab, select the DOMFLD1 as Zone. In the parameters tab, set the XINC as 20, YINC as 15 and ZINC to 5. Click Ok to run. 3. Load the resultant model, and compare the results to previous models. 4. Save the project by clicking on the Save button 5. Click OK to automatically reload data in the 3D window when you next open the project.
Block Modeling
257
C HAPTER
14
GRADE ESTIMATION In this chapter, you will learn to:
Use basic grade estimation techniques to estimate grades into a block model
Use statistical tools to compare characteristics of the sample data set with the grade model
Evaluate the grade model
Principles Having created a block model to represent ore and waste volumes, we can now look at estimation of grades into the model. In the following exercises you will create a new model and estimate grades for gold (Au) and copper (Cu) using both the nearest neighbour and the inverse distance interpolation methods. This training course will not attempt to cover any of the more advanced estimation methods like kriging (ordinary kriging, simple kriging, co-kriging or indicator kriging) or structurally controlled estimation (dynamic anisotropy or unfold) or advanced non-linear methods (conditional simulation or uniform conditioning), which are available. These methods are covered in detail in the advanced Studio RM training courses. Background Estimation commands in Studio RM are shown in the Estimate ribbon menu, where commands have been grouped so that they can be easily found.
Variograms group – tools for creating experimental variograms and fitting variogram models
Estimate group – tools for cross validating and numerous estimation methods
Anisotropy group – tools for determining the orientation of an orebody for estimation
SMU Analysis group – Uniform conditioning and change of support
Conditional simulation group – Gaussian transformation, conditional simulation and determining the confidence of an estimate.
Figure 371: The Variograms, Estimate and Anisotropy groups in the Estimate ribbon
Figure 372: The SMU Analysis and Conditional Simulation groups in the Estimate ribbon
Grade Estimation
258
The ESTIMATE wizard The user friendly wizard Estimate | Estimate | Interpolate Grade ( or typing the batch command ESTIMATE into the command box) allows you to estimate values using one or more of the following estimation methods:
Nearest Neighbor
Inverse Distance
Ordinary Kriging
Simple Kriging
Sichel’s T Estimator
The ESTIMATE wizard was designed to make the batch process ESTIMA, which is a very comprehensive estimation command, easier to use especially as requires a fair amount of input and prove a bit daunting to new users. The ESTIMATE menu creates all the necessary reference files and provides a series of dialogs which allow you to enter all the necessary criteria. The dialogs also provide additional options such as a provision for Indicator Kriging, which is not available from the ESTIMA command. The menu can be run by selecting it from the pulldown menus or by typing ESTIMATE at the command prompt. The standard files needed to run the process are listed below: File Type
Compulsory
Description
Sample File
Yes
This is usually a desurveyed drillhole file which includes one or more grade fields. As an alternative this file can consist of the grade fields plus three coordinate fields defining the centre of each sample in the local mine grid.
Model Prototype
Yes
Block model file. This file will usually contain cells plus one or more ZONE fields.
Search Volume File
Yes
Standard ESTIMA search parameter file There must be a minimum of one defined search ellipse (1 record).
Estimation Parameter File
Yes
Standard ESTIMA estimation parameter file. There must be a minimum of one set of estimation settings (1 Record).
Variogram File
No
Used to store the variogram model settings. The variogram parameter file is only compulsory if you plan to use any of the Kriging methods.
Sample Output File
No
Outputs the X, Y and Z locations of each sample used to interpolate grade for each cell. Can be a very large file.
Output Model File
Yes
Name to be given to the output model
Search Volume File The ESTIMATE dialog requires you to define a three dimensional search volume defined using 3 orthogonal axes. This volume is defined by setting the lengths of the three X, Y, and Z axes along with the search volume shape (cuboid or ellipsoid). The three axes can be rotated to reflect the local geology and statistics of the sample data. The Search Volume file includes all of these values along with other settings which can be used to control the selection of samples used to calculate weighted grades. One or more search volumes are defined using the Search Volume file. Each record in the file defines a separate search volume and each search volume has a unique Search Volume Reference
Grade Estimation
259
Number (field SREFNUM). This means that a search volume may be unique to an individual grade or can be shared by two or more grades. The search volume method is either a three dimensional rectangle or an ellipsoid. The only difference is that the rectangular method will select samples in the ‘corners’ of the search volume. The default value for SMETHOD is 2 (ellipsoid). One, two or three rotations may then be defined. For each rotation, it is necessary to define both the rotation angle and the axis about which the rotation is applied. For this purpose, the X-axis is denoted as axis 1, the Y-axis as axis 2, and the Z-axis as axis 3. The rotation angle is measured in a clockwise direction when viewed along the positive axis towards the srcin. A negative rotation angle means an anticlockwise rotation. For example if the first rotation is through A degrees around axis 3 (Z) then the search ellipse is oriented as shown in the image below:
Figure 373: Examples of rotations
If the search ellipsoid is then rotated through B degrees around the new X -axis the result is:
Figure 374: Examples of rotations
Grade Estimation
260
This example illustrates a conventional rotation of azimuth and dip. However, any rotation method can be used by defining both the angles and axes for up to three rotations. It can sometimes be helpful to use the fingers of your left hand to simulate the rotations. Point your index finger straight out in front of you, your thumb up in the air, and your second finger to the right across your body. Write the number 1 on your second finger, 2 on your index finger and 3 on your thumb. Your second finger is the X-axis, pointing East, your index finger is the Y-axis pointing North and your thumb is the Z-axis pointing up.
Figure 375: The left hand rule
To simulate the two rotations in the previous example first hold your left thumb with your right hand and rotate the other two fingers clockwise. Then hold second finger and rotate your index finger and thumb clockwise in a vertical plane. Your fingers are now pointing along the axes of your rotated search ellipsoid. The batch command ELIPSE creates a wireframe of your search ellipsoid. This is very useful when creating a search with rotations, as you can visually verify the orientation of your search. ELIPSE is explained later in this chapter.
The Estimation Parameter File It is possible to select different grades to estimate, using different methods and different parameters all in a single run. The different combinations of grades/methods/parameters etc. are each defined by a record in the Estimation Parameter file. The following estimation methods can be applied:
Nearest Neighbour (NN)
Inverse Power of Distance (IPD) Ordinary Kriging (OK)
Simple Kriging (SK)
Sichel's T Estimator (ST)
It is possible to estimate the same grade by different methods or by the same method but using different parameters in a single run.
Grade Estimation
261
This is achieved by allowing you to specify an output field name for the grade. For example if you want to estimate AU by both Inverse Power Distance and Ordinary Kriging, then the output field names could be AU-IPD and AU-OK. In both cases, the input field name would be AU. Matching estimation runs with the relevant search ellipsoids Both the Search and Estimation Parameter files contain a field called SREFNUM. This field is set to one or more unique values which can be matched in both files. For example the following excerpts from Estimation and Search Parameter files indicate 2 runs of Inverse Distance estimation for the fields CU and AU. Each run is using a separate set of search volume settings. Search Parameter File Record
SREFNUM
1
1
65
SDIST1
65
SDIST2
70
SDIST3
2
2
100
50
20
Estimation Parameter File Record
SREFNUM
1
1
AU
2
2
2
2
CU
2
2
VALUE_IN
IMETHOD
POWER
The SDIST fields record the length of the Search Ellipse axes in the X, Y, and Z directions. The VALUE_IN field records the field to be estimated while the IMETHOD field lists the estimation method to use. IMETHOD=2 indicates Inverse Distance Estimation is to be used with the power value stored in the POWER field.If another estimation method were used such as Nearest Neighbour (IMETHOD=1), then the POWER field would be ignored. How is the grade estimation done? Each cell is selected in turn from the input model file and samples lying within the search volume are identified. Each grade field which is specified in the Estimation Parameter file is estimated using the selected samples and written to the output model file. How do I ensure certain samples are only used to estimate grades in cells? Typically you will need to control which samples are used to estimate which model cells in terms of rock type, mineralized domain or oxidation state. This is referred to as Zone Control. As an example, the image below shows a vertical section through a lead/silver sulphide deposit. The mineralization is capped by a supergene zone which has been enriched in silver. The supergene zone is marked out using horizontal lines while the sulphide zone is marked out using diagonal lines. The annotated drillhole values are silver grades expressed in grams per tonne.
Grade Estimation
262
Figure 376: A representation of the search ellipsoid for a model cell (marked A)
The ellipsoidal outline represents the outline of a search ellipse centred on a model cell labelled A. If the grade for cell A was estimated using all the samples found within the search ellipse not only would the estimate include waste samples, but primary sulphide samples as well. Clearly a grade calculated using all the samples found within the search ellipse would be incorrect and unrepresentative. An estimate of cell A should only use samples taken within the supergene zone which are also located within the search ellipse. Estimating grades using one or more fields to distinguish different rock and or ore types is called Zone Control. In this case a field called ROCK was built into the model and assigned the values of 0, 1, and 2 to distinguish waste, supergene and sulphide cells. The drillhole file included a field called ROCK which was logged as 0, 1 or 2 to distinguish the same 3 rock types. When the grades were estimated this field was used to match the model cell rock codes with the matching drilling information.
Grade Estimation
263
Exercises Exercise 1: Generating a Search Ellipse In this exercise you will use the ELLIPSE command to create a wireframe of a search ellipse. ELLIPSE allows you to create the search ellipse prior to using it in grade estimation, so that you can view it in the Design and Visualizer windows to ensure it correctly represents the search you wish to use. Imagine you are dealing with an ore body which has a strike orientation of 50 degrees and dips to the south-east at 70 degrees. Prior to rotation, in order to generate the ellipse in the correct orientation the lengths of the axes are X=25, Y=100 and Z=50. 1. Run the command Models | Interpolation Processes | Create Wireframe Ellipse (or type ELLIPSE into the command line) with the following settings: Ellipse Dialog
Files Tab WIRETR
eltr
WIREPT
elpt elpt
Parameters SANGLE1
0
SANGLE2
20
SANGLE3
0
SAXIS1 SAXIS2
3 1
SAXIS3
3
SDIST1
75
SDIST1
100
SDIST1
50
2. When the process is complete, load the wireframe into the 3D window and rotate it. The wireframe consists of 3 components which are identified in the wireframe triangle file, eltr by the field ZONE. This field has the following values: 1 – the surface of the ellipsoid 2 – the three planes orthogonal to the axes of the ellipsoid 3 – a set of wireframe axes for the world coordinate system Each octant of the ellipsoid is displayed in a different colour (1 to 8) and the axes are COLOUR=13. 3. Experiment with filter expressions (Format | Filter All Objects | Wireframe Triangles) to show/hide the display of each value of the ZONE field. 4. Update the Visualizer window. The wireframe ellipse should look similar to the image in Figure 377: The search ellipsoid wireframe in the 3D window
Grade Estimation
264
Figure 377: The search ellipsoid wireframe in the 3D window
Exercise 2: Estimating Gold Grade into the Model In this exercise you will use the ESTIMATE command to estimate gold grade using the inverse distance estimation method and applying zone control. 1. Unload the file opmodel from the design window. 2. ESTIMATE Run the command | Interpolation Processes | Interpolate Grades from Menu (or type into theModels command line), to open the ESTIMATE wizard. 3. Enter the following under the Files - Input tab:
Input model – Opmodel Samples - _vb_holesc (or dholes)
Check Coordinate fields are X, Y, Z
Select Zone 1 for Zone field controls
Grade Estimation
265
Figure 378: The ESTIMATE wizard
4. Click on the Output tab and enter a “Grade Model filename” of model, as model 1. 5. Uncheck the Use Defaults toggle and delete the default file name that appears next to the Variogram Model File.
Figure 379: Files step in ESTIMATE wizard showing Output files tab
6. Click Next button and this will open up the Unfolding options. Since we will not be running UNFOLD in this example, leave these options blank.
Grade Estimation
266
Figure 380: The Unfolding step in the ESTIMATE wizard
7. Click the Next button to move to the Search Volumes. Click on the Add button under “Index” to add a record to the search volume file. 8. In the Shape tab, ensure that the Ellipsoidal is on and the lengths of the axes are as shown below. 9. Uncheck the Use Axis Defaults box and set the rotation angle and axis as shown.
10. To change the number of samples used to interpolate grades into cells, select the Category tab. Change the Minimum number of samples to 3.
Grade Estimation
267
Figure 381: Search Volumes Category tab
11. Check the Summary tab for the settings as shown in Figure 382
Figure 382: Summary tab showing settings
12. Click on the Next button to move to the Variogram Models pane. As we will not be using a kriging method click on the Next button again to move to the Estimation Types pane. 13. Click on the Add button to add a record to the estimation parameter file. 14. On the Attributes tab select the Inverse Power of Distance button. 15. Use the drop-down arrow to select the AU field from the Data Fields section. Ensure that the ‘Same as Sample ’ box is ticked – the output field in the model file will also be AU. 16. In the Search and Variogram Definition section, ensure that “1:Search Volume 1” is selected. 17. In the Zone Field Values section select ‘1’ using the drop-down list. This will ensure that grades are calculated using search ellipse 1 within the upper mineralized zone (labelled 1).
Grade Estimation
268
Figure 383: Estimation Types step in ESTIMA wizard for first estimation
18. Click the Add button under the Index section to add a second record to the estimation parameter file. 19. Select Inverse Power of Distance as the interpolation Method. Define AU as the sample grade. User Search Volume 1 and select ‘2’ from the drop down menu next to the ZONE field value. This will ensure grade are calculated within the lower mineralization zone (labelled zone 2).
Figure 384: Estimation Types step in ESTIMA wizard for second estimation
20. Click on the Next button to move to the Controls tab and set Parent Cell Estimation to “Parent cell estimation using a fill 3D Matrix of points”.
Grade Estimation
269
Figure 385: Parent cell estimation settings
21. Click on the Next button to move to the Controls tab and set the number of discretization points used for each cell to 3 for all directions.
Figure 386: Cell discretization settings
22. Click on the Next button to move to the Preview tab and check all settings against that shown:
Figure 387: The Preview step in the ESTIMATE wizard
23. Run the estimation by clicking the Run button. Look at the Command control bar to see the progress of the estimation. 24. On completion of the processing load the model (model1) into the 3D window, and create a vertical East-West section through your data. 25. In the Sheets control bar turn on the display of the wireframe representing the mineralized zones (mintr/minpt) and the display of the drillhole file dholes. Make sure that the wireframe is displayed as an intersection by right clicking on it, opening the properties and selecting Display Type as Intersection.
Grade Estimation
270
Figure 388: The Sheets control bar
26. In the Sheets control panel right-click on the model file and select Properties. Set the display type to Intersection.
Figure 389: Block Model Properties dialog box showing legend settings
27. In Options, tick the “Show Absents” tickbox. 28. Select the Colour tab and select AU from the Column drop down menu. A message asking you if you wish to generate a default legend may appear, enter Yes at this prompt. 29. Select the Colour using legend column, as AU and select AU-Legend from the legend drop down menu. 30. Select the Labels tab, then tick the Display labels tick box. 31. Select AU column, select 2 decimal places and click Insert. 32. Set AU column and legend to the same as the blocks – AU Legend.
Grade Estimation
271
Figure 390: Block Model Properties dialog box showing label settings
33. Click on OK then on Close to close the dialog. A view of detail of the model is shown in Figure 391.
Figure 391: Model intersection section showing AU grades with annotation and legend
34. Save the project by clicking on the Save button. 35. Click OK to automatically reload data in the 3D window.
Grade Estimation
272
Exercise 3: Estimating AU and CU using Different Methods. In this exercise you will use ESTIMATE to estimate gold grade using the inverse distance estimation method and copper grade using the nearest neighbour method. Zonal control will also be applied. 1. Unload the file model from the 3D window. 2. Run the command Models | Interpolation Processes | Interpolate Grades from M enu (or type ESTIMATE into the Command line). 3. Click on the Restore button at the bottom of the dialog to restore the settings from the previous run. 4. Click the Next button until you are in the Estimation Types panel. 5. Click on “Estima Param 1” and uncheck the Same as Sample box in the Data Fields section. Change the Model Grade from AU to AU-ID. Repeat this process for Estima Param 2.
Figure 392: The Estimation Types step in the ESTIMATE wizard
6. Click on the Add button to add a third estimation parameter. 7. Define the appropriate settings to calculate copper grades within Zone 1 using Nearest Neighbour estimation as shown below.
Grade Estimation
273
Figure 393: Estimation parameters in the Estimation Types step of the wizard
8. Add another Estimation Parameter to estimate copper grades within Zone 2 using nearest neighbour estimation. Name the field CU-NN. Repeat this for CU, naming the model grade as CU-NN. 9. Move to the Preview panel and click Run. 10. Load the model when created into the 3D window and set the legend display for AU-IPD. 11. Click within one of the model cells and the cell information is listed in the Data Properties control panel on the left hand side of Studio RM
Figure 394: The results of a cell in the Data Properties control box
12. Save the project by clicking on the Save button. 13. Click OK to automatically reload data in the 3D window.
Grade Estimation
274
C HAPTER
15
DATA PRESENTATION - PLOTTING In this chapter, you will learn to:
Create plot layouts using static and dynamic plot items
Format data object overlays for visual impact
Setup plot sections andview orientations
Principles Plots Window Once data has been loaded into the project, it is available for viewing and plotting in the Plots window. The Plots window allows you to create any view or section orientation and send those views/sections to a plotter/printer using Windows printer drivers. Displaying the Plots Window The Plots window can only be displayed if a project is active, and if the window is in view, it will be displayed as a tab along the top of the data window area:
Figure 395: The Plots window tab
If you cannot see the Plots tab, you can enable it by accessing the View ribbon, then expanding the Activate option in the Window command group to display a Plots window activation option. This will allow you to turn the Plots window on or off. Click the tab to show the window, and if present, loaded data in the last selected viewing plane. Plots Window Context Menus The Plots window features a context-menu system to allow you to perform specific operations on window items using the right-click mouse operation. In general, there are two different versions of context menu in this area:
In P ag e Layout M ode : if Page Layout Mode is active (you can toggle the status of this mode by activating the Manage ribbon and enabling the Layout Mode toggle whilst in the Plots window), the context menu that is presented will allow you to configure individual plot items, including projections of data.
In S tatic Mode : if page layout mode is inactive, the sheet in view is referred to as 'static'. Whilst in static mode, you will have access to general sheet-level settings that will affect the presentation as a whole.
Four different views are automatically created in the Plots window. They include:
Plan view
North-south section view (including a plan window)
Data Presentation - Plotting
275
West-east section (including a plan window)
3D view
Each view can be edited by selecting the relevant tab along the bottom of the Plots window. Additional views can also be created and edited.
Figure 396: The Plot sheets that are created by default
Some of the features available in the Plots window are:
Graphically interrogate data in section or 3D view. Plot data objects in plan, section or any 3D view desired. A complete family of sections can be defined from a single section definition using a single dialog. Insert plot items such as text boxes, coordinate grids, scale bars, tables and title blocks which automatically adjust as you change the position, orientation and scale of plot sheets. Select different paper sheet sizes, orientations, margins and scales for each view. Use Page Layout mode to display and interactively edit page borders, sheet margins, plot frames, coordinate grids, plot items and parameter profiles.
Controlling the Display of Data The Sheets control bar can be used to control the data displayed in the Plots window and also data formatting properties. The image below shows the standard Plots sheets that are automatically generated for the online tutorial dataset.
Figure 397: In the Sheets control bar the sheets can be accessed
The image above shows two section sheets, Section 6025.00 E and Section 5025.00 N. Your sections will be named differently depending on the extent of the loaded data. Additionally there is a Plan and 3D sheet.
Right-clicking on a sheet will give you a context-sensitive menu. Selecting Plan Properties provides you with a menu in which to modify the relevant settings such as View Direction, View Center, Appearance, Clipping, View Exaggeration and many more.
Data Presentation - Plotting
276
Figure 398: The context menu in the Sheets control bar
Figure 399: The Plan Projection Properties can be adjusted
Each Plot sheet can be expanded to show the items displayed in the sheet by expanding the Overlays. Right-clicking on the Overlays items will also initiate context sensitive menus. These items can be inserted, deleted or modified using the Plots | Manage | Overlays menu or context sensitive menus.
Data Presentation - Plotting
277
Figure 400: The Overlays in the Sheets control bar
A single data object (such as drillholes) can be added to a sheet multiple times as separate Overlays, each with its own display and formatting parameters.
Formatting Data The Format Display dialog can be used to modify the way in which data is displayed. This dialog can be accessed either by:
Selecting Manage | Overlays
from the ribbon menu
Figure 401: The Overlays button in the Plots Manage ribbon
Right-clicking on an object in the Sheets control bar and selecting Format from the drop down menu.
Data Presentation - Plotting
278
Figure 402: The Sheets context menu
This will open the Format Display dialog as indicated below.
Figure 403: The Overlays tab in the Format Display dialog box
The following format settings for displayed data or overlays can be modified:
Style – for example points, labels, lines, arrows etc.
Color – object coloring using fixed colors or legends
Symbols – symbol type, size and rotation
Labels – object annotation settings.
Section Definitions Horizontal, vertical and inclined sections can be quickly defined using the section wizard to define the section type, section azimuth, section width and the center point coordinate. The section wizard can be run either by:
Data Presentation - Plotting
279
Run the command Manage | Insert | Sheet | Custom and selecting the Projection Wizard option.
Figure 404: In the Plots Manage ribbon the Insert | Sheet | Custom
Right-clicking on a sheet item in the Sheets control bar and selecting Wizard from the drop down menu.
Figure 405: Accessing the wizard from the Sheets context menu
A complete family of sections is defined by this single section definition. For example, if data extends between eastings 6100E and 6300E, by defining a single NS section at 6100E and a section width of 25 meters, the program will auto-range the extents of the data and create 8 NS sections.
Figure 406: The Plot Item Library box
Although the entire family of sections is contained in a single section, only one of these sections is displayed in the given sheet at any one time. Multiple sheets could also be used to contain individual sections from this family of sections.
Data Presentation - Plotting
280
View Settings Having created the section, plan or 3D view, the section definition, page size and view settings can be modified as required using the View Settings dialog. To display the section properties/definition for the selected section, activate the Plots View ribbon and select View | Set.
Figure 407: The Plots View ribbon with View | Set
This will open the View Settings dialog as indicated below.
Figure 408: The View Settings dialog box
Changes made to the section can be displayed dynamically to give you immediate feedback on the effect of changing one or more settings. The section in an existing sheet may also be redefined or repositioned interactively by re-selecting the center point or end points for the section or snapping to a particular borehole collar, sample or other data object. The various options in the View Setting dialog are discussed below. To change the section orientation:
Activate the Plots View ribbon and select View | Set. This opens the View Settings dialog. Position the dialog so that you can see the section view and check the Dynamic option. The current section orientation is displayed in the Section Orientation box on the Section Definition tab dialog. Select a different standard orientation ( Horizontal, North-South or East-West) or use the dial buttons to change the Azimuth and Dip.
Figure 409: The View Settings dialog box
Data Presentation - Plotting
281
When you type a value into an entry box, choose the Apply button to accept the new value.
To change the section width:
Activate the Plots View ribbon and select View | Set. This opens the View Settings dialog. Position the dialog so that you can see the section view and check the Dynamic option. Check the Apply clipping option. The current width is displayed in the Width box on the Section Definition tab dialog or select the Section Width tab. Type a new value or use the dial buttons to increase or decrease the Width. Use the Position buttons to review how these changes affect the other section lines in this view.
To change the section position
Activate the Plots View ribbon and select View | Set. This opens the View Settings dialog. Position the dialog so that you can see the section view and check the Dynamic option. The current coordinates of the section mid-point are displayed in the Mid-Point box on the Section Definition tab dialog. Type a new value or use the dial buttons to increase or decrease the X (Easting), Y (Northing) and Z (Elevation) of the section mid-point. Alternatively use the Position buttons to jump between sections (each jump will be equal to the section width defined). Similarly the size, scale, rotation and exaggeration can be set using the View Settings dialog.
Section Definition Files The section definition file (also referred to as a view definition table) is used to store multiple views or section definitions for use in the 3D and Plots windows. Each definition contains parameters for the view plane center coordinate, orientation, extents, clipping and a description. The viewing (and later interpretation and modeling) of data can be facilitated by means of predefined views saved in such a definition file. These views can be saved and retrieved when required and provide the ability to easily return to regularly used view orientations. The use of a Section Definition file is recommended for regularly used views and for defining a series of sections in the Plots window; the once-off or general viewing of data is typically done using only the Set View plane, Zoom, Pan and Clipping functions.
Section Definition files can be generated interactively in the 3D window. With the 3D window active and using the View ribbon, select from the Section dropdown list. A new section with a default name of ‘Section’ will be created. Various sections can be added to this section
by right clicking on the newly created section within the Sheets control bar and selecting Add Section. Details of how to generate these files and their use in the Plots windows can be found in Exercise 8. The following image is an extract from a section definition file.
Data Presentation - Plotting
282
Figure 410: The section definition file in the Datamine Table Editor
Using a section definition table
Activate the Plots View ribbon and select Section | Table - Use. If you have not already loaded a section definition table you will be asked if you wish to load one.
Figure 411: The Plots view ribbon with Section | Table - Use
The sections table contains predefined section definitions. These might be in a predefined, non-parallel pattern such as a fan or they might not have any specific relationship one to the next. You can change the section displayed using the section navigation keys in the usual way.
View Definitions The View Direction dialog can be used to define the direction from which data is viewed, and may not necessarily correlate exactly with the direction and position of a plot section as defined under the Section Definition tab. In the image shown below the section orientation (as defined under the Section Definition tab) is North-South section with a clipping distance of 50m. The view orientation (as defined under the View Direction tab) however has been defined as a 3D view from the South-East with an azimuth of 315° and a dip of 60 °.
Figure 412: The Section definition tab in the View Settings dialog box
Data Presentation - Plotting
283
Figure 413: The View Direction tab in the View Settings dialog box
Figure 414: The results in the Plot sheet
There are a number of pre-defined options for the view direction which can be selected from the Align To Section drop down list. They are:
Perpendicular
Side View
Top View
Reversed Perpendicular
Reversed Side View
Reversed Top View
Figure 415: The Align to Section options in View Settings
Data Presentation - Plotting
284
Plot Items Plot items such as text boxes, title blocks, tables, legends, bitmaps and scale bars can be inserted into any plot sheet. Many of these plot items have smart features which change as other plot and document settings change. For example, a scale bar will change automatically as the plot scale is changed. These plot items can be located anywhere on the page and the size and contents of items such as the title box can be customized. To access this dialog, activate the Manage ribbon and click the top-level Plot Itembutton to display the Plot Item Library. Alternatively select the Plot Item drop-down menu to expand it as indicated in the figure below.
Figure 416: The Plot Item drop-down list
Alternatively, the Plot Item Library can be accessed by one of the following:
In the Sheets control bar, right-click on Plots, select New Plot Sheet | Custom. In the Sheets control bar, Plots folder, right-click on a sheet, projection or overlay, select Insert. In the Plots window, right-click on a sheet, select Insert (Page Layout Mode). In the Plots window, right-click on a sheet, select Insert | Locatable Plot Item (Normal Mode).
The plot items available include:
Title Box - inserts a Title Box item into the current section.
Text Box - inserts a Text Box containing user defined text into the current section.
Table - inserts an in-memory table into the current sheet that is data which has already been loaded into the 3D window. Legend - Allows you to select a legend to display in the current section. Image - insert clip art (in bitmap format) into the current sheet. A file browser is displayed. Locate and load the required bitmap file.
Symbol - inserts a predefined symbol into the current section.
North Arrow - adds a north arrow to the current section.
Dimension Arrow - adds a dimension arrow to the plot.
Data Presentation - Plotting
285
3D Dimension Overlay - add an existing overlay to the section with this command. Initially, the Add Overlay dialog is displayed. When an overlay is selected, you can select an option from the following dialog. Data represented by the selected overlay will then be transferred to your current section.
Scale Bar - adds a scale bar to the current section.
Profile - inserts a profile plot box into the current section.
Log - adds a drillhole log to the current section view.
Figure 417: The Plot Item Library
The Plots window supports the concept of 'child' and 'parent' objects; some plot items are reliant on parent objects - these often referred towith as 'dynamic plotinitems' - such aswhere a North Arrow for example; a North Arroware must be associated a projection order to 'know' to point. In ,this situation, plot items are added by inserting them at the correct layer of the Plots window hierarchy.
When inserting plot items using the Sheets control bar's right click menu it is useful to remember that any plot items that relate to a particular projection (for example, a title bar that will list the description of a projection) should not be added at the Sheets level or above, instead, they should be added by right-clicking the relevant Projection folder and selecting Insert...
Sheet Templates Sheet Templates are an efficient way of introducing standard content to your plot or log views. They can be used to minimize the work required in generating a framework presentation project which can be re-used in the future. Sheet Templates are used to store information which can be applied to the plot or log views. The templates are stored in a proprietary format ( .dmtpl ) which can be read in Studio RM. Any amount of information can be stored in a sheet template and may include:
Layout and formatting information. Visualization information such as projection view direction or section position. Data mapping information by which the data that was used by the sheet upon which the template was srcinally based is related to the data that will be shown when the template is applied to new data objects (see section on Data Mapping below).
Data Presentation - Plotting
286
Sheet Templates should not be confused with Data Display Templates (see chapter on Data Formatting). •
Sheet Templates are used to store plot and log specific sheet layout and data mapping instructions, and are used to automate some of the tasks involved in creating a new presentation item. If specified, Sheet templates will contain all information stored by a Display template.
•
Display templates are more general in nature, and are used to control the display of object overlays in either the Design or Plot window. These templates are global, in that once applied to an overlay of an object, all renditions of that object will be updated automatically.
Saving a Sheet template – Creating a new sheet template is simple; you create the layout and data links that are required (or load an existing sheet you wish to turn into a template) and then save the information in .dmtpl format using the Manage ribbon's Save | Template option . Loading a Sheet Template – Templates are imported by inserting them into an existing data presentation project:
In the Plots or Logs window, use the Manage ribbon to select Insert | Sheet | From Template... Using the file browser, locate the template (.dmtpl) file and Open it. The Import Sheet Template dialog is shown. Specify any data mappings that may be required and click OK to import the template.
Figure 418: The buttons on the ribbon
A preview of the sheet that will be imported is shown in the top-left of the import dialog (if this is required). The preview will automatically update according to selections made on screen. You can turn the preview off by clearing the Preview checkbox. This might be useful if you find that the preview is taking too long to redraw a representation of large data objects. By default, the sheet adjusts its view to fit the data that is being used. You can turn this feature off by clearing the Fit To Data checkbox. A summary window shows the current status of the sheet. It displays the name and type of the sheet it is going to create, and information about the data that is being used by the sheet. Data Mapping – Data mapping is an important aspect of sheet templates; although optional, the ability to map data in memory to a ‘hook’ stored in a template makes generation of standard plots and
logs easy.
Mapping relates to the way that data stored within a template, is used to configure the view of currently loaded plot or log data. Say you had a view of a wireframe shown in four different projections, representing different views through the data body. As these views cover the full panorama of the wireframe, you may find it useful to present other wireframes in a similar way. By storing a template, the view directions of each projection are stored and applied when that template is inserted into your project, providing a wireframe object exists in memory and it is mapped to the srcinal object.
Data Presentation - Plotting
287
The overall concept is best described by way of a graphical example; in the following sheet, a block model file has been loaded into memory. The model is displayed in two projections; the right hand projection shows a top-down view of the model cells at a scale of 1:1000, and the left hand projection shows a North-South section through the orebody:
Figure 419: The plot sheet
Note that other plot items have been added - a title box, legend, image and table view are also shown. Of particular note is the table view, which relates to the block model data set - even though this isn't a geometric object, as far as the plot template is concerned, it is still a view of the data and, as such, can be mapped to loaded data. Next, a new session is started and a different block model loaded into memory. By inserting the Manage ribbon to select Insert | Sheet | From Template...) the .dmtpl file previous (use the Sheet Template is loaded template and the Insert dialog displayed. The initial preview shows no data as the template cannot 'find' the srcinal block model file that was used to create the template. At this point, you would have two choices:
Reload the srcinal block model file by selecting the model file name in the data list (bottom left of the import dialog) and clicking Reload Original - note that this would simply reimplement the data setup in place when the srcinal template was created. See "Reloading Files", below, for more information. Map the new block model to the srcinal; this is achieved by ensuring the Use Data check box is active, and then selecting the srcinal model file as referenced by the template, e.g.:
Figure 420: The Use Data check box
Once selected, a list of all data types in memory that match the type of the one selected (in this case, block models) are listed in the column to the right. Only models of a corresponding type will be listed, and the list will always be headed with an [ absent] option - selecting this option denotes that no mapping is to take place. A match will automatically be made if an object in memory matches the file name referenced by the template. In the example above, the model names are different, so no automatic matching is possible and the left hand template object is mapped to [ absent]. Manual mapping is achieved by selecting a valid entry on the right, e.g.:
Data Presentation - Plotting
288
Figure 421: The Use Data check box
Once an object is mapped, and providing the Show Preview check box is selected, a thumbnail of the mapped data object is shown in the preview pane, e.g.:
Figure 422: A preview of the plot
Compare this to the image above - note how the orientations of the model are the same in both projections. In addition to mapping objects it is also possible to map individual fields referenced by the template file against fields of the data objects in memory. In the example illustrated by the image above, the srcinal drillhole file upon which the template was based included drillholes annotated with the field BHID and drillhole traces coloured according to the field Avg(Au). When you manually map a different drillhole file the system automatically maps the field BHID, however, because no Avg(Au) field can be found in the mapped drillhole file the field is set to [absent]. To map the Avg(Au) template field to another field (e.g. AU), select [AU] in the right hand list. This updates the mapping on the left.
Figure 423: Coloured on AU
Reloading Files and Importing New Data Once a template has been selected for import, the Import Sheet Template allows you to reload the data object associated with the srcinal template file using the Load Original button at the base of the Data Mapping section of the dialog. You will only be able to reload the srcinal data if: The object exists in the same location (and with the same name) on the local system as when the template was created. The data object that was in memory when the template was created was associated with a separate external file. If the data object was stored within the project at the time of template creation, you will not be able to reload the srcinal data. The object to be reloaded does not already exist in memory. There is also an option to load a new data file to map to the template using the Import New button.
Data Presentation - Plotting
289
Managing Multiple Templates It is possible to select more than one template file from the file browser dialog when running the command Insert | Sheet | From Template. If more than one file is selected, the resulting Import Sheet Template dialog will be laid out in a tabbed arrangement allowing access to each template.
Figure 424: Import Sheet Template window
When multiple templates are in view, any data mapping tasks will be performed on all templates, if possible. For example, if template 1 was created with wireframe 1 in memory and coloured according to the SURFACE field, and template 2 was created with the same wireframe and legend but with different projection layouts any data mapping changes would cause the mapping instructions held by both templates to be updated. The same principle applies to both object and field level data mapping.
Exercises Exercise 1: Exploring the Menus for Plots In this example, you are going to view the various context sensitive menus available for setting Plot sheet related parameters. You will be viewing the context sensitive menus for both the Sheets control bar and Plots window items: 1. Display the Plots window. The Plots window can only be displayed if a project is active, and if the window is in view, it will be displayed as a tab along the top of the data window area:
Figure 425: The Plots tab
If you cannot see the Plots tab, you can enable it by accessing the View ribbon, then expanding the Activate option in the Window command group to display a Plots window activation option. This will allow you to turn the Plots window on or off. Click the tab to show the window, and if present, loaded data in the last selected viewing plane. 2. Select the Plots window and click on the Plan tab.
Data Presentation - Plotting
290
Figure 426: The Plots window
3. Select the Sheets control bar. In the Plots tree, fully expand the Plan sheet tree by clicking on all the "+" boxes listed below the Plan sheet tree item, as shown in the image below:
Figure 427: The Sheets control bar
4. Left click anywhere inside the plot area (inside the grid area) to select the plotting area and then Right-click and select Insert | North Arrow. Alternatively, use the Manage ribbon to select Insert | Plot Item | North Arrow
Data Presentation - Plotting
291
Figure 428: The Plot Item Library
5. Select the North Arrow plot item and note that the North Arrow item is highlighted with a dashed border in the Plots window, Plan sheet. Also note the North Arrow item created in the Sheets control bar.
Figure 429: The North Arrow plot item in the Plot sheet
6. Click on the tab labelled 3D in the Sheets control bar or click on the tab at the bottom of the Plots window. 7. In the Sheets control panel expand the 3D sheet item under Plots. Experiment by turning of the display of the various overlay items in the Sheets control bar.
Data Presentation - Plotting
292
Figure 430: The 3D plot sheet
Exercise 2: Creating, Renaming, Copying and Deleting Sheets In this example, you are going to define a new 3D sheet, rename the newly created sheet, copy the sheet and delete the copy. 1. Create a new 3D sheet by accessing the Manage ribbon, then expanding the Sheet option in the Insert command group. Select Custom.
Figure 431: Create a Custom sheet from the ribbon
2. Select 3D Projection from the Plot Item Library dialog and then OK.
Data Presentation - Plotting
293
Figure 432: The Plot Item Library
3. A new plot sheet called 3D has been created displaying all loaded data.
Figure 433: The new 3D sheet
4. Right-click on the newly inserted 3D tab at the bottom of the Plots window and select Rename....
Figure 434: The context menu
5. The Rename Sheet dialog will open. Rename the sheet to “3D-Above” and then click OK.
Data Presentation - Plotting
294
Figure 435: The Rename Sheet dialog box
6. In the Sheets control bar, right click on “3D -Above” and select Copy 3D-Above. Click on Plots item in the Sheets control bar and right click and select Paste. A new item called “Copy of 3D-Above” will appear in the Plots window.
Figure 436: The Sheets control bar
7. In the Sheets control bar, right click on “Copy of 3D -Above” and select Delete. The user will be prompted with “Are you sure you want to delete Copy of 3D-Above?” Select Yes. The copied sheet will be deleted.
Figure 437: The context menu in the Sheets control bar
Data Presentation - Plotting
295
Exercise 3: Modifying the Paper Size and Grid Settings In this example, you are going to change the plot size to A3 and format the coordinate grid applied to the plot sheet. 1. Select sheet displaying the East-West section (Section 6025.00 E) in the Plots window. Use the Manage ribbon to select Format | Page Setup. The Page Setup dialog will open.
Figure 438: The Plots Manage ribbon with Format | Page Setup
2. In the Page Setup tab, select the Paper Size and Orientation dropdown and select “A3 297 x 420 mm”. Press OK to continue and answer Yes to the prompt asking if you want to rescale all plot items.
Figure 439: The Page Setup dialog box
3. Use the Manage ribbon to select Format | Overlays. The Format Display dialog will open.
Figure 440: The Plots Manage ribbon with Format | Overlays
4. Select the Grid tab and set the Decimal Places to 0.
Data Presentation - Plotting
296
Figure 441: The Grids tab in the Format Display dialog box
5. Click on the Advanced Options sub-tab and enter Suffix Label items as follows.
Figure 442: The Grids tab in the Format Display dialog box
6. Select the Options tab and change the position of the grid annotation to Outside Border and the style to Parallel.
Data Presentation - Plotting
297
Figure 443: The Grids tab in the Format Display dialog box
Exercise 4: Changing the scale and zoom In this example, you are going to experiment with setting the scale of a plot, panning and changing the zoom. 7. Use the View ribbon to select Scale | Area. Notice how the cursor shape changes.
Figure 444: The scale options in the Plots View ribbon
8. Whilst holding in the left mouse button, drag around the data to be viewed in more detail in the Plot sheet. The scale will increase.
Data Presentation - Plotting
298
Figure 445: Choosing an area for the scale in the Plot sheet
9. Use the View ribbon to select Scale | Fit to rescale the plan to the data extents. Notice how the scale changes to show all the loaded data.
Figure 446: The scale option in the Plots View ribbon
10. Set the scale of the plot to a specific value by using the View ribbon and selecting Scale | Set. Set the scale to 1:2 500 . Choose OK.
Data Presentation - Plotting
299
Figure 447: The fixed scale
11. To centre the selected plan, click in the plot area with the left mouse button and then select one of the Pan options in the View Ribbon. Use the Pan options until you have centred you data in the plot sheet.
Figure 448: Pan options in the Plots View ribbon
12. To change the zoom view of the plot, select the Zoom | Fit from the View ribbon. This will extend the view to include the entire plot. Experiment using the Zoom | In and Zoom | Out buttons.
Figure 449: Zoom options in the Plots View ribbon
Exercise 5: Changing the section definition 1. Click in the plot area with the left mouse button. Using the View ribbon, select View | Set to open the View Setting dialog. Change the Section Definition values as per below.
Figure 450: The View Settings dialog box
Data Presentation - Plotting
300
Exercise 6: Modifying the Data Format Settings 2. To display the wireframe as a slice intersecting the view plane, choose the Manage ribbon and then Format | Overlays . This will open the Format Display dialog.
Figure 451: The Plots Manage ribbon with Format | Overlays
3. Select the topography wireframe (_vb_stopotr/_vb_stopopt (wireframe)) from the Overlays pane. Click on the Intersection option and then OK.
Figure 452: The Overlays tab in the Format Display dialog box
4. Repeat this step for the fault wireframe ( _vb_faulttr/_vb_faultpt). The plot should look more or less similar to the one below.
Data Presentation - Plotting
301
Figure 453: The plot sheet
5. To annotate the drillholes select the drillholes file (_vb_holes) in the Format Display dialog and click on the Insert button under the Drillholes tab.
Figure 454: The Overlays tab in the Format Display dialog box
6. Click on NLITH from the list of available attributes and click OK. Select the [Bars] option from the list of Style Templates.
Data Presentation - Plotting
302
Figure 455: The list of Style Templates
7. Click on the Width/Margins tab and enter a value of ‘2’ for th e column width. 8. Click OK then Close and compare your section to that shown in the image below:
Figure 456: The plot sheet
Data Presentation - Plotting
303
9. Click anywhere within the plot sheet and use Section | Next and Section | Previous in the View ribbon. This will step through the project area in parallel sections, 25 m apart which is the width of our section.
Figure 457: The Plots View ribbon
10. As you step through each section, notice that the section name change on the Sheets tab and also on the sheet and projection items listed in the Sheets control bar. Exercise 7: Inserting Plot Items 1. In the Manage ribbon select Insert | Plot Item | Title Box
Figure 458: Insert Title Box
2. In the Title Box dialog click on the Frame Properties tab and set the Height and Width to ‘50’ and ‘100’ respectively.
Data Presentation - Plotting
304
3. Click on the Font button and change the Min Size to 6 and Max Size to 9. 4. Click OK and select the Contents tab which will allow you to add and remove cells and to adjust the cell contents. 5. Set the Row and Cell fields to 1 and click on the Insert button next to the Cell field. 6. Select the Clip Art option and when prompted select: \Database\DMTutorials\Data\VBOP\pics\minelogo.bmp. Press Apply and OK to close the
Title Box dialog. 7. We now want to re-edit the title box and move it to the bottom left corner of our plot. Toggle the Layout Mode on in the Manage ribbon.
Figure 459: The Layout mode option in the Plots Manage ribbon
8. Left click on the Title Box in the plot area. Notice the Title Box is selected. Drag the Title Box to the bottom left corner of the plot by holding in the left mouse button and dragging the box.
Figure 460: In the Layout mode
9. Left click on the Title Box (whilst the Layout mode is toggled on) and select Title Box Properties… This will re -open the Title Box dialog.
Data Presentation - Plotting
305
Figure 461: The context menu
10. We want to enter a name of the project into the second row in the Title Box. Make sure Row 2 and Cell 1 is selected as indicated below. Select Contents.
Figure 462: Inserting rows and cells
11. The Cell Contents dialog will open. Set the Category to Static and enter the text as below. Select Apply and OK.
Figure 463: The Cell contents dialog box
12. Select Format from the Title Box dialog and set the alignment to Centre. Select Apply and OK.
Data Presentation - Plotting
306
Figure 464: The Cell Format dialog box
13. Your title box should look similar to the example displayed below. You will have noticed some lines of text are hard coded while others as set as “Fields” such as the section number. By
using fields some of the title box text will change as each new section is displayed. Try stepping through a few sections.
Figure 465: The title box
14. Click outside the title box with the mouse to make sure it is not selected. In the Manage ribbon, select Insert | Plot Item | Legend Box and select [Lith-Legend] from the drop down list.
Figure 466: Insert | Plot Item | Legend Box in the Plots Manage ribbon
15. Set the number of Columns to 2. The Rows will automatically increase to 3. Set the Font to size 9 (Minimum and Maximum). Drag the Legend to the top right corner of the plot.
Data Presentation - Plotting
307
Figure 467: The Legend Box contents
16. We want to insert a Dimension Arrow to indicate the distance between the two faults. Select Insert | Plot Item | Dimension Arrow. The Insert Dimension Arrow dialog will open. Select the Horizontal type and select OK.
Figure 468: The Insert Dimension Arrow dialog box
17. Select the point from which to start measuring the distance by left click with the mouse button. Then select the end point. Drag the position of the Dimension Arrow’s label to the desired position.
Data Presentation - Plotting
308
Figure 469
18. Double click on the dimension arrow in the plot. This will open the Dimension Arrow dialog. Set the Decimal Places to 0.
Figure 470
Exercise 8: Creating a Section Definition File and using it in the Plots window In this exercise the user will learn how to create a section definition file and how to apply a section definition file to create a series of section plots based on the predefined sections contained in the section definition file. 1. Create a new section in the 3D window by using the View ribbon and selecting from the section dropdown list under Sections. A new section with the default name of ‘Section’ will be visible in the Sheets control bar. The section will by default be horizontal/plan.
Data Presentation - Plotting
309
Figure 471
2. Select Set Section Using 1 point and right click to snap to the most easterly borehole collar. The Orientation dialog will open; select ‘North-South’ and OK.
Figure 472
3. In the Sheets control bar, right click on the newly created Section and select Rename. The Rename 3D Object Overlay will open. Rename the section as indicated below.
Figure 473
4. In the Sheets control bar, right click on the section ‘Section Definition’ and select ‘ Add Section’. A new section will be created under the main Section Definition.
Data Presentation - Plotting
310
Figure 474
Figure 475
5. Repeat Step 4 above to add another section to the main Section Definition. The new section added will have the same name as the section created in Step 4 above.
Figure 476
6. Click inside the 3D Window area and type in MPL into the keyboard (Move- Plane). Enter 35 and OK.
Figure 477
7. Right click on the newly created sub-section and select Overwrite. The sub-section will be renamed to reflect the position of the section.
Data Presentation - Plotting
311
Figure 478
8. Repeat Steps 4 to 7 until sections have been created over the entire drilled area.
Figure 479
9. Move to the Loaded Data control bar. Notice a table named S ectionDef was created. Rightclick on it and select Data | Save as. Save the files an ‘Extended Precision Datamine (.dm) File’.
Figure 480
Exercise 9: Editing the Section Definition File using the Table Editor The user will open the newly creates section definition file and change the clipping distance of the sections.
Data Presentation - Plotting
312
1. Go to the Project Files control bar. The newly created sectiondef file will be under the ‘Section Definitions’ folder. Double click on the file; this will open the file in the Datamine Table Editor.
Figure 481
2. In the Table Editor, type in ‘10’ in the first row of the column named ‘ DPLUS’. Right click in the cell and select Fill | Down. All the cells in the DPLUS column should have a value of 10. Repeat this process for column DMINUS. Save the table and close it.
Figure 482
3. In the Loaded Data Control bar, right click on sectiondef and select Data | Refresh.
Data Presentation - Plotting
313
Exercise 10: Applying the Section Definition File in the Plots window In this exercise the user willapply a section definition file to produce prede fined sections in the Plots window.
4. In the Plots window, select Section 6125.00 E. 5. In the View ribbon, select Sections | Table | Use. Notice how the section changes.
Additional Exercises Additional Exercise 1: Create a Section Definition File Generate a section definition file which includes all the N-S or E-W sections through the ore body. File Name: Additional Exercise 2: Generate a series of plots Generate a series of plots in the plot window and include the following items:
Generate a plan view and display the following: o
Topography contours and drillholes
o
Set an appropriate scale, paper size, grid
o
Add a title box and North Arrow
Generate a series of N-S or E-W sections with a plan window. Display all relevant data which may include: o
Drillholes
o
Ore strings
o
Mine Design
o
Topography wireframe
o
Apply the section definition file generated in exercise 1
o
Annotate drillholes with at least one grade field and downhole lithology if using
o
Set an appropriate scale, paper size, grid
o
Add a title box and legend
Data Presentation - Plotting
314
C HAPTER
16
DATA PRESENTATION – STRIP LOGS In this chapter, you will learn to:
Create scaled strip logs of drillhole data
Format drillhole data for visual impact
Use dynamic composting
Principles Studio RM can produce publish quality strip logs of loaded boreholes. A default drillhole Log sheet is created in the Logs window when drillhole data tables are loaded to create dynamic drillholes. The Log sheets can be independently modified for both data content and formatting. The default log sheet created includes header and footer information and scaled columns representing data in the drillhole data tables. Fields may be duplicated, displayed as text or graphs, and fields from more than one table source can be viewed in the same log view including composited and system fields. Many formatting options are available for changing the layout and content of log sheet header, columns and footer. Log plots may be enhanced by the addition of smart plot items which have inbuilt intelligence and will adjust automatically to relevant changes to the project. These plot items available include text boxes, legend boxes, tables and clip art images. Most of the setup options available to plots, including sheet size and orientation, printer margins and plotting scale, are available to logs too.
Figure 483: Strip logs in Studio RM
Data Presentation – Strip Logs
315
Exercises Exercise 1: Loading Dynamic Drillholes In this example, you are going to load dynamic drillholes which will be used to create strip logs. The drillholes will be loaded from an external database: 1. In the 3D Window, using the Data ribbon, select Load | Hole Wizard . This will open the Data Load Wizard dialog.
Figure 484: The Data Load wizard
2. Select Next and then tick the Drillhole Database button. Select Next.
Figure 485: Import Data Types in the Data Load wizard
3. In the Data Load Wizard dialog, the Import a dri llhole databas e dialog will open. Select Add. In the Data Providers dialog select the Earthworks ODBC Data Provider option and then click OK.
Data Presentation – Strip Logs
316
Figure 486: Data Providers
4. In the Select Data Source dialog, Machine Data Source tab, select the Excel Files option from the list under Data Source Name and then click OK. 5. In the Select Workbook dialog, Directories pane, browse to the folder C:\Database\DMTutorials\Data\VBOP\ODBC, in the Database Name pane, select the _vb_drillhole_data.xls spreadsheet file from the list so that the name appears in the top dialog box and then click OK.
Figure 487: Select Excel workbook
6. In the Data Source - Select Tables dialog, select (tick) the [Assays], [Collars], [Lithology], [Surveys] and [Zones] TABLES and then click OK.
Data Presentation – Strip Logs
317
Figure 488: Select tables
7. In the Select Table Type dialog, the user is prompted to ‘ Select the table type for ‘Assays$_vb_assays’. Select the Assays option from the list and then click OK.
Figure 489: Select Table Type
8. In the Define Drillhole Data Table dialog, Field Assignments group, assign the table fields as shown in below and then click OK.
Data Presentation – Strip Logs
318
Figure 490: Assign fields
9. Continue assigning the correct table types to the remaining tables and assigning the correct field assignments. The required settings are provided below. Collars:
Figure 491: Select Table Type
Data Presentation – Strip Logs
319
Figure 492: Assign fields
10. Continue assigning the correct table types to the remaining tables and assigning the correct field assignments. The required settings are provided below. Lithology:
Figure 493: Select Table Type
Data Presentation – Strip Logs
320
Figure 494: Assign fields
11. Continue assigning the correct table types to the remaining tables and assigning the correct field assignments. The required settings are provided below. Surveys:
Figure 495: Select Table Type
Figure 496: Assign fields
Data Presentation – Strip Logs
321
12. Continue assigning the correct table types to the remaining tables and assigning the correct field assignments. The required settings are provided below. Zones:
Figure 497: Select Table Type
Figure 498: Assign fields
13. The last step in the Data Load Wizard dialog will show the message “ Load Complete!” Choose the options as indicated below and select Finish.
Data Presentation – Strip Logs
322
Figure 499: Data Load Complete
14. A new item called Dynamic Drillholes will appear in the 3D window and in the Sheets control bar. Also note that the tables loaded in the process above is indicated in the Loaded Data control bar. Exercise 2: Opening the Log window and inserting a new log sheet In this exercise the user will open the Log window and insert a new log sheet. 1. In the Home ribbon, select Window | Show | Logs. A blank Logs window will open.
Figure 500: Open Logs window
2. In the Logs window, using the Manage ribbon, select Insert | Sheet | Log. A default strip log will open in the Logs window.
Data Presentation – Strip Logs
323
Figure 501: Insert | Sheet | Log in the Logs Manage ribbon
Exercise 3: Formatting the strip logs In this exercise, the user will experiment with changing the appearance of the strip log and switching to different boreholes. 3. With the Logs window active, use the Manage ribbon to select Logs | Log Properties. This will open the Log View Properties dialog.
Figure 502: Logs | Log Properties in Logs Manage ribbon
4. In the Log View Properties dialog, under the Hole tab, set the Current Hole to ‘VB4292’ using the dropdown list. Set the Extents to ‘Entire Hole’ and set the Initial extents when hole changes: to ‘Entire Hole’.
Figure 503: The Hole tab in the Log View Properties
Data Presentation – Strip Logs
324
5. In the Header tab, Delete Row 2. Select Row 1, Cell 1 and insert a Cell. Choose ClipArt from the Plot Item Library dialog and browse to C:\Database\DMTutorials\Data\VBOP\Pics and select minelogo.bmp. Select OK in the ClipArt dialog. The mine logo should appear in the Log sheet. 6. In the Log View Properties dialog, select the Column Titles tab and make the following settings.
Figure 504
7. Select the Columns tab and make the following changes: ZONE: Change Style Template to ‘Bars with annotation’ Change the font color to black Change the font size to 10 NLITH:
Delete the column
LITH:
Change the Style Template to ‘Text offset to prevent overlaps’ . Change the font color to black Change the border color to black
AU:
Change the Graph/Color maximum to 5
CU:
Change the Graph/Color maximum to 5
Depth at:
Change the font color to black
Elevation:
Change the font color to black
8. Select the Frame tab and set the Width to 170 mm. Select Apply and OK to close the Log View Properties dialog.
Data Presentation – Strip Logs
325
Figure 505
The strip log should look more or less similar to the one below.
Figure 506
9. In order to make the column titles more readable, we are going to increase the row’s height. Select Layout Mode from the Manage ribbon. Left click anywhere inside the plot sheet. Notice the different cells and columns become selectable. Drag the row hosting the column titles down to increase its height.
Data Presentation – Strip Logs
326
Figure 507
10. To jump to the next borehole, use the Manage ribbon and select Logs | Previous and Logs | Next buttons. Notice how the log sheet changes.
Figure 508
Additional Exercises Additional Exercise 1: Generate a series of log sheet plots with different column data displayed and different header information. In this exercise you will be required to add additional log sheets with different data and formatting to the log sheet that has already been created in the previous exercise. Use your own creativity.
Data Presentation – Strip Logs
327
C HAPTER
17
DATA PRESENTATION – ANIMATIONS AND 3D PDF’S In this chapter, you will learn to:
Create a virtual reality scene of the geological and mining data
Animate objects in the v irtual reality scene
Publish the virtual reality scene as a video
Publish the data as a3D PDF
Principles Studio RM provides an intuitive way in the 3D window to look at your geological and mining information. It uses Virtual Reality modeling with connections to external data sources to provide a realistic and simple visual method of examining and navigating through all your data. Uses include:
Geological data immersion - unlock the full value of your geological data with full stereovision immersion right there on your desktop. Display fault planes, geophysical grids, geological interpretations, structural surface models, grade surface models, drillholes and terrain surfaces, then color and texture for the objects to reveal their hidden secrets. Real world data connection - every object in the virtual world can be linked to other documents and programs accessible on the local network, company intranet or worldwide internet. You can click on say a drillhole to display a drill log or section plot, or on a blast mark-up line to report the tonnes and grades, or step inside the mine office and click on the telephone to dial-up and upload the latest drilling results - the possibilities are endless and limited only by your imagination. Terrain navigation - jump into any vehicle and take it for a drive up the road, across country, or down the mine. Take a visitor or a company director on a virtual tour of your exploration project or mine site. Change the transparency of the terrain surface and peer down to see the orebody and pit design surface. Fly-through’s - drape an aerial photo over your terrain surface and fly around your mine. Swing down into the pit then dive below ground and fly right inside the orebody. Simulations - define haulage routes, then add trucks, shovels, draglines, drill rigs and service vehicles and watch the mine come to life.
Conventional 3D visualization programs do little more than spin data around while you view it, whereas the Studio RM 3D window is a 3D immersion system which puts you right inside your data. The data links then give you access to as much detail about the objects as you want, or wish to publish, and enable easy access to plots, logs, reports and charts without specialist knowledge of where the data is stored, the format it is stored in or the programs used to create them - in other words, it puts everyone in touch with the project. And because none of the objects, or the linked information, are stored within the document, any changes to the data are automatically reflected in the world view.
Data Presentation – Animations and 3D PDF’s
328
Understanding Virtual Reality data VR data is categorized into distinct areas, and although all share the same core functionality, each data type is supported by its own range of specific tools; for example, there are texturing options available for wireframe surfaces, dynamic section view controls for block models and vertex and edge formatting options for string data, amongst many others. Once a file has been imported – there are no sacrifices that need to be made due to the srcinal format of the file. If a DXF topography file was imported, for instance, and a separate aerial survey image needed to be applied according to the georeferenced data held within the image file, it could be applied to the surface model using VR in an identical manner to if the srcinal topography file was in a native Datamine format. The VR Window organizes its data into the following categories:
Points
Strings
Surfaces Block Models
Objects Object Types
GVP Files
Sections
The interrelation of these components is a key aspect of the VR system. Strings not only act as a visual aid or enhancement, they are also capable of acting as simulation control strings, guiding the route of a mobile VR Object along a predetermined path, according to the specified object settings (maximum acceleration, maximum turning angle etc.) Similarly, objects can be ‘dropped’ onto a
surface and instructed to follow the topographical angles of the virtual scene during animation, if required. All of these data types sit within your virtual scene – the environment, which is also eminently controllable.
Figure 509
Data Presentation – Animations and 3D PDF’s
329
The VR Environment Despite being part of a simulation, the level of control over how your scene is rendered permits many different effects. You can change the lighting (ambience, direction, strength, color), if and how data is clipped (to focus on a particular section of the scene, for example) and wh ether any environment ‘fog’ is to be used (and if so; what color? How thick? Getting the idea?). Lighting can also be applied to individual objects, and these objects can be mobile. Animated sky ‘maps’ are also supported, adding still more layers of realism to your virtual world. Once your objects are loaded and the environment set, you can then opt to create dynamic fly-through ’s and
simulations. Perspective and Orthogonal 3D Views
Figure 510
You can change your current view mode using the View ribbon's Perspective toggle. What is meant by 'Perspective' and 'Orthogonal'? A perspective view implies that the view emulates a real-world panoramic view of the displayed data. Simply put, a perspective view provides a display of a three-dimensional image that portrays height, width, and depth. In the 3D window, a perspective view displays the expected foreshortening affect indicating a virtual 'distance' away from the viewpoint (the 'camera').Two characteristic features of perspective are:
objects are drawn smaller as their distance from the camera increases, the size of an object's dimensions along the line of sight are relatively shorter than dimensions across the line of sight.
An orthogonal view, also referred to as an 'isometric' view does not indicate depth of field. Instead, geometric data is shown with screen geometry that matches the actual distances associated with the object regardless of how 'far' it is from the camera.
Perspective mode is the default view type
Orthogonal mode is not permitted if Stereo mode is enabled.
Selecting a View Type Your application allows you to view 3D scenes using an orthogonal (isometric) or perspective (vanishing point) view. Whereas the latter will give a more accurate rendition of a model in relation to viewing it in a real-world context (with objects 'shrinking into the distance' and all that implies when rotating and moving the viewpoint), an orthogonal non-perspective view does not apply the vanishing point distortion associated with perspective viewing. This can be useful when comparing the dimensions of an object without having to compensate for virtual 'distance' from the viewpoint.
Data Presentation – Animations and 3D PDF’s
330
The selection of a view type can impact how data is perceived in the 3D window; a perspective view will provide a sense of depth and immersion, making navigational controls 'feel' more intuitive than say, moving towards and rotating around an orthogonal object. This is because your perception of what is going on is more easily resolved in your brain when the perspective mode is applied - it is a more 'natural' view of a simulated scene. For example, in an orthogonal view, objects that are 'behind' another in the 3D scene will not scale into the distance, enforcing (potentially) a distorted view of object scales in the 3D window. In the example below, two images are shown of the same scene; the image on the left is shown in a perspective view. The perceived depth of field gives both the human and haultruck objects spatial context - you can perceive the virtual distance between the two. However, with an orthogonal perspective, as the illusion of depth is no longer supported (as no vanishing point exists), both objects are shown at their actual scales.
Figure 511
This gives the impression that the haul truck is much closer to the human. In this respect, even though neither view is technically or computationally incorrect, does the left hand image simulate the 'realworld' more effectively due to its support for denoting all three dimensions. Drawn from a view more directly above the object pair, the effect of the different view modes becomes less apparent. e.g.:
Figure 512
Zooming Navigating in a parallel projection can feel counter-intuitive to those used to perspective projections. The main reason for this is that as the 'camera' moves forwards, objects in the view do not appear to get closer, as they do not get any bigger. The only indication of forward motion is usually when objects start getting clipped by the view’s front clipping plane. This can be a problem if you are trying to use the free-flight tools, as any subsequent rotations around the camera may be confusing. It is
Data Presentation – Animations and 3D PDF’s
331
recommended, therefore, you only use the free flight tools for panning whilst in this mode. All other navigation should be done using either pre-set viewpoints, or Look At mode. There are 2 primary options for making an object look bigger on the screen: either move the camera closer to it (move forwards), or reduce the field of view (apply zoom). The various zoom controls can be used to zoom in to the data. After selecting a zoom control, a new viewing area is either automatically or manually selected using the left mouse button and dragging the bounding rectangle. Releasing the button will cause the camera to pan so that the rectangle is central, and alter the view width to fit the bounding rectangle. For convenience, the system will also apply a Look At point in the centre of the view, to make subsequent rotations easier. The depth of the Look At point will either be on the first item intercepted in the middle of the view, or an average depth of objects in the view if no item is intercepted. In an orthogonal view, unlike the perspective view, zooming will alter the view width and not move the camera position forward.
Zooming with the Mouse Wheel will zoom around the cursor position. In the perspective view, the view zooms by moving the camera. If a Look At point has been defined, then the speed of moving is based on the distance to the viewpoint. If the cursor is away from the view centre, then the Look At point is moved horizontally or vertically (relative to the viewport) to keep it in the new view centre
Panning The point to note with 3D scene 'panning' is that although the movement is 'flat', movement results will be dependent on the type of view currently selected. For example, the following image represents a series of still images of data being 'panned' whilst in a perspective view:
Figure 513
The same data dragged in an orthogonal view would show the following result:
Figure 514
Recommendations Generally, it is recommended that, for any activities that require the construction or navigation of VR data for the purpose of producing a presentation, a perspective view will deliver a more immersive experience, and may also be more intuitive to navigate. Navigational Control The view position and orientation in the 3D window can be changed using standard views or by interactive navigation. In addition, regularly used views can be saved as viewpoints. Points to remember are:
The harder you push the control the faster the action e.g. push the mouse up to accelerate the forward motion. Release the control to stop the action.
Data Presentation – Animations and 3D PDF’s
332
Choose the Controller Settings command from the menu to adjust the sensitivity of individual controls.
A number of standard views can be used to view the full extents of the data in the 3D window. You can access these view commands using the View ribbon (View commands group). These commands include:
Plan: view the data in plan, zoomed to its full extents (quick key + ). North: view the data looking north, zoomed to its full extents (quick key + ).
East: view the data looking east, zoomed to its full extents (quick key + ).
South: view the data looking south, zoomed to its full extents.
West: view the data looking west, zoomed to its full extents.
There are various options to enable you to move around the workspace in the 3D window. The actions of the navigational controls are dependent on the view mode. Floating view
Allows you to navigate anywhere in the world. The current view point is the focus around which the data is rotated.
Look At mode
Allows you to fix the focus on a particular point. Movement is restricted so that you zoom, rotate and pitch around the selected point
Plan view
Rotates the view direction to look vertically down and the view position is moved up to give a wider view. To avoid losing sight of data, before entering Plan View mode, position yourself above an objet or towards the center of a surface.
Outside view
Restricts movement so that you are always pointing towards a selected object . As a result it is not possible to pan in this mode.
Inside view
Fixes the position at, or offset from the srcin of the object .
Control mode
Any mobile object can be placed into ‘control’ mode and “driven”
anywhere on the terrain surface The following table lists the different navigation controls available in the 3D window, for various view mode combinations.
Data Presentation – Animations and 3D PDF’s
333
Navigating in a parallel projection feel counter-intuitive. main reason for this the 'camera' moves forwards, objectscan in the view do not appearThe to get closer, as they do is notthat getas any bigger. The only indication of forward motion is usually when objects start getting clipped by the view’s front clipping plane. This can be a problem if you are trying to use the free -flight tools (i.e. floating), as any subsequent rotations around the camera may be confusing. It is recommended, therefore, you turn on the perspective mode (
) when in Floating mode.
Using a variety of the methods above, you will find it easy to locate the correct aspect for your virtual reality scene. Remember that these tools are useful not only in static scenes, but can also be selected prior to and during simulation playbacks, which will be discussed later in this module.
Data Presentation – Animations and 3D PDF’s
334
View Modes and Controls The actions of the Navigational Controls in the 3D window are dictated by the type of view mode that is operational at the time. This topic outlines the various options and methods for viewing data in the 3D window. Viewing options are controlled by a combination of modes and controls:
a view mode is a particular viewing state or setting that is applied to the 3D window view; all subsequent view controls will honor the currently active mode. For example, if in Look At mode, the Spin View control can be used to rotate the view around a particular point; whereas in Floating View mode, the view cannot be spun in this way. a view control is a command that will perform an action, such as setting or interactively changing the view direction. For example, the Perspective View toggle will automatically switch between a vanishing-point perspective and isometric view of the data.
Navigating in an Orthogonal Projection Navigating in a parallel projection can feel counter-intuitive to those used to perspective projections. The main reason for this is that as the 'camera' moves forwards, objects in the view do not appear to get closer, as they do not get any bigger. The only indication of forward motion is usually when objects start getting clipped by the view’s front clipping plane. This can be a problem if you are tryin g to use the free-flight tools, as any subsequent rotations around the camera may be confusing. It is recommended, therefore, you only use the free flight tools for panning whilst in this mode. All other navigation should be done using either pre-set viewpoints, or Look At mode. In perspective projections, there are 2 primary options for making an object look bigger on the screen: either moves the camera closer to it (move forwards), or reduce the field of view (apply zoom). Neither of these options are available in a parallel projection, so the ‘Zoom to region’ button should be used
instead. After selecting this button, the new viewing area should be outlined on the current view by using the left mouse button and dragging the bounding rectangle. Releasing the button will cause the camera to pan so that the rectangle is central, and alter the view width to fit the bounding rectangle. For convenience, the system will also place the Floating Viewpoint in the centre of the view, to make subsequent rotations easier. The depth of the Floating Viewpoint will either be on the first item intercepted in the middle of the view, or an average depth of objects in the view if no item is intercepted. Using a Mouse Wheel If you have a Mouse Wheel, the wheel can be used in certain viewing modes to access the following functions: Zoom In - rotate wheel forward Zoom Out - rotate wheel backwards
Zooming with the Mouse Wheel will zoom around the cursor position. In the perspective view, the view zooms by moving If aIfLook At point has been the speed of Look movingAtispoint based on the distance to the thecamera. viewpoint. the cursor is away fromdefined, the viewthen centre, then the is moved horizontally or vertically (relative to the viewport) to keep it in the new view centre
Data Presentation – Animations and 3D PDF’s
335
Please note: •
If you get disoriented, choose Level View to return to a horizontal view, then, if you are still lost, choose an object or viewpoint from the Viewpoint list to get you back to familiar territory.
•
When navigating around an immersive world, use the Look At command to move towards and around an object of interest. Once active, you can rotate the entire VR scene quickly around the selected point, using the Rotate View command
•
Use the Viewpoint list to quickly move from one object or view position to another. When saving viewpoints, use a descriptive name to help you select the right viewpoint while navigating. Tips are used to provide hints and suggestions about how best to achieve an end result. Tips will be used to provide alternative methods, or shortcuts that may be useful.
•
Changing the View during Simulation Playback Different view modes and controls can be accessed even during play back of a simulation, for example, you can:
change the Inside View in a vehicle to find a better driving position keep your view fixed on a moving object by choosing the Look At command and click on a moving object when inside a simulation object, keep your view fixed on another object, using a similar approach to above. The "Look At object" may also be moving in the simulation.
Setting Auto-Spin and Auto-Roll Hold down the key and use the left or right arrows to start an automatic rotation of the contents of the 3D window. Subsequent presses of the relevant direction key can be used to speed up/slowtodown the rotation, or stop it and reverse direction. Similarly, you can use the up and down arrows instigate an automatic roll. Draping Textures
Figure 515: Image texture draped over wireframe surface
Textures are used not only to make a scene more believable as part of a presentation (although this is a huge benefit on its own), it is also available as a way of delivering more information than a simple
Data Presentation – Animations and 3D PDF’s
336
geometry can provide: mine surface features, blast marks, natural obstacles that may affect mine efficiency etc. There are two options for draping textures:
Attach a patterned texture to the wireframe surface. This generic texturing method allows you to specify a generic image for more than one scene, although the result may be less realistic than a real-world texture taken in situ, the image will not need any specific alignment. Attach a real-world photograph (.bmp) texture to the wireframe surface. If a photograph is used alignment with the underlying wireframe is needed in order to match up the topographical features with the draped image. Note that VR also supports the use of geo-referenced images; these images contain additional landmark information that allows a texture to be automatically
aligned to the surface it is applied to. If a photograph is used then it should meet the following requirements:
The photograph should be taken vertically above the pit. The photograph should be taken when the sun is not directly overhead, so shadows can be used to help alignment.
The photograph should be square or rectangular with the sides a multiple of 256 pixels.
Various file types can be used. Please see the help menu for a comprehensive list.
Placed into an image editing package to edit the file as required before draping it onto a surface.
It is also greatly beneficial if key distinguishing features are surveyed to gain their coordinates. These can be saved as Datamine string files and imported into Studio RM. These highlighted features can then aid alignment enormously; you should use strings that cover a wide area of the image. Viewing Block Model Data Block models represent three-dimensional shapes, volumes, tonnages and grades of solids such as ore zones, waste zones and other volumes of geological or mineralogical interest. Block models consist of blocks, which are cubes or cuboids, stacked together to fill the defined volume as closely as the block sizing criteria will allow. Several options are available to you when viewing VR representations of block model. You can choose to represent your block model as:
Points: show the current model as a series of points, with each point representing the volumetric center of each block cell.
Lines: view as a series of lines.
Blocks: show shaded model cells.
Quick Section: show the model as a section along either the IJ, JK or IK planes (or, by loading the model more than once, several sections simultaneously). Note that this option will display full cells only, and does not rely on a previously defined section plane in memory. Intersection: if selected, you can access one of the previously defined VR sections in order to display a detailed cross-sectional view of your geological model, including sub-celling.
You can also view your model with a mixture of formats. Point, line and block views of block model data can also be animated according to a sequencing field (see section on Block Model Sequencing Animations for more information). The display type is defined using the Block Model Properties dialog which is accessed by right-clicking on a block model object in the Sheets control bar and selecting Properties from the drop down menu.
Data Presentation – Animations a nd 3D PDF’s
337
Figure 516: Viewed as points
Viewing Block Models as Points The block model is displayed as a cloud of points. The points, as with all viewing formats, are subject to coloring via an applied legend or fixed color.
Figure 517: Viewed as lines
Viewing Block Models as Lines The block model is displayed as a set of independent lines.
Figure 518: Viewed as blocks
Viewing Block Models as Blocks The block model is displayed as cuboid blocks, with each block representing the total area of a block model cell. This is the most memory-intensive options, which may affect system performance adversely when viewing high-density block model data in conjunction with a restricted system hardware specification.
Data Presentation – Animations and 3D PDF’s
338
Viewing Block Models as ‘Quick Sections’
Figure 519: Quick section
Once a block model is loaded it is viewed by default as a single section through the data as shown below. The position and orientation of the section can be adjusted by right-clicking the block model object in the Sheets control bar and selecting the Quick Section Controls option. This option is only available when the object is currently viewed as a quick section
The slide control in the Section Control dialog allows you to move through the sections. The orientation of the section is controlled by the IJ Plane, IK Plane and JK Plane buttons.
Figure 520: Secion Control
Data Presentation – Animations and 3D PDF’s
339
To view multiple block model sections simultaneously you need to load the block model a second time and select the Quick Section Controls option for block instances. This will allow you to control more than one section of the same block model independently (see example 4). When viewing block model data, you can choose to interpolate the section colors. Interpolated textures show a more ‘blended’ view of the disparate cell colors and can be useful when a hard boundary between parent cells isn’t necessarily desirable. The images below show an interpolated
(left) and a non-interpolated (right) section display type.
Interpolated display type
Non-interpolated display type
The Quick Section option is designed to allow a rapid display of successive sections through a block model. Individual sub-cells are not displayed, so the color of the parent cell is based on the legend item associated with the first sub-cell within each parent cell volume. Therefore, if detailed sub-cell information is required it is better to view the model as an intersection as described in the next section. Viewing Block Models as Intersections It is possible to view a slice of the block model in any direction using the Intersection option. This technique relies on a VR section being defined beforehand, using the Section area of the Sheets control bar. For more information refer to the following section. Creating, Importing and Manipulating Section Planes Under the VR Folder in the Sheets control bar it is possible to define various view properties for loaded objects. The Sections sub-folder contains a list of all loaded section objects and section definition files. Section definitions can either exist in isolation, as a single plane, or can be part of a section definition table (a file containing several records, each of which relates to a unique section orientation and position). To interactively create a new section definition, right click the Sections sub-folder and select New from the drop down menu. This will put you into section creation mode ( ). A new section is defined by clicking in the 3D window to open the section Orientation dialog which is used to define the orientation of the new section to intersect the position where the cursor was clicked.
Data Presentation – Animations and 3D PDF’s
340
Figure 521: Section orientation
The various options include:
A lig n to Wi refr ame: this option will only be present if the object clicked on was a Surface or VR Object, and if selected, will align the section with the plane described by the selected face. After selecting an orientation, the section object will appear on screen. Only one section plane can be defined using this option, and this option will not be shown if one has already been defined within the current project. The dotted line around the edge of the section and the arrow designating the section’s front aspect help to define ‘front’ and ‘back’ clipping.
Figure 522: Multiple sections
Horizontal : create a horizontal section (oriented orthogonally to the Z axis) passing through the selected point.
Data Presentation – Animations and 3D PDF’s
341
North-South : create a section running in the north-south direction passing through the selected point. East-West : create a section running in the east-west direction passing through the selected point. If a table is created in memory (or imported) only one section from that table can be shown on screen at any one time.
B y 2 Points : create a horizontal, vertical or perpendicular section through two selected points. B y 3 Points : create a section through three selected points. The visual qualities of a section are controlled using the Section Properties dialog, accessed by right clicking the newly defined section and selecting the Properties menu option.
Figure 523: Section properties
To apply a section view to an object such as a block model right click on the object in the sheets control bar and select the Properties menu option. Selection the Intersection display type and select the required Intersection Section name from the drop down menu. To move the section, make use of the Interactive Section Editor in the View ribbon. This will allow the section orientation to be adjusted using the on-screen widgets. Select the green arrows at the corners of the section to move the section parallel to its srcinal position.
Select the red arrows to change the orientation of the section.
Select the blue arrows to change the pitch of the section
Data Presentation – Animations and 3D PDF’s
342
Adding Objects
Figure 524: Office with trucks
To make the display look more realistic it is possible to add objects such as trucks, offices, trees etc. Every object is derived from an object type. An object type is a Microsoft DirectX file, (.X). Examples include Land Rover, Haultruck, Chair and Laptop. It is necessary to create an object type before individual instances of an object can be added to the VR world. For example, it is possible to locate two haultrucks in the VR world that have different names but are both derived from the object type Haultruck. Objects can be seen in the VR Objects folder in the Sheets control bar. Object Types can be seen in the VR Object Types folder in the Sheets control bar. There are options object type. To access these options right-click on the object typevarious folder or on theassociated object typewith itself.
Figure 525: Haul truck
Refer to Example 7 for details regarding how to load a new object type and then locate an object in the VR scene. Every object in the 3D Window has information attached. For most, it is coordinate position information, however, more information, in the form of files, can be attached. To display any attached files right-click an object in the display. If any files are attached a menu will display the names of the files. If no files are attached the name of the object is displayed on its own. For instructions on how to attach information to objects refer to Example 8.
Data Presentation – Animations and 3D PDF’s
343
Animations and Simulations VR data objects can be mobile or stationary. Animations are displayed according to the real criteria that affect the day-to-day mine transportation operations – each object has a set of properties, including a maximum acceleration, turning circle, climbing angle, a storage capacity and other properties that help to simulate mine site operations. Simulations aren’t restricted to the movement of objects around a static scene – this functionality is
extended to show sequencing animations, for example, that can clearly display how a particular geological model would be turned into reserves over a predefined period of time – this sequencing information is contained within the model file itself (and srcinally generated by other Datamine packages, such as Studio 5D Planner and NPV Scheduler). After creating a string on the surface of a wireframe you may find that some aspects of the string are hidden below the surface. To understand this behaviour, it is necessary to look a bit more in detail at how string points are added to a topographical surface; each newly-defined point is 'dropped' onto the wireframe surface, where it will sit, aligned with the surface. The next point along will be positioned in the same way. However, as a topography is an organic shape, the zone between the two points (i.e. the position of the string 'edge') may have to go above or below certain surface bumps and troughs on its journey from point 1 to 2 in a direct line, e.g.:
Figure 526: Parts of string hidded
In this situation, some of the string edges may not be visible. There are two ways around this problem:
Create more points on the string. Right-click on the string in the Sheets control bar and select Fit to Surface from the drop down menu.
Refer to Exercise 9 for details on how to create a simulation.
Exercises Exercise 1: Displaying windows This example outlines the procedure for loading data directly into the 3D window. 1. Click on the 3D window tab and in the Data ribbon select Load | Datamine | Wireframes.
Data Presentation – Animations and 3D PDF’s
344
Figure 527: Load | Datamine | Wireframes
2. Browse to C:\Database\DMTutorials\Data\VBOP\Datamine and select the file _vb_SurfaceTriangles and click OK. Due to the fact that this file does not follow the wireframe naming convention (i.e. tr and pt suffix) you will need to select the triangle and point file from the second file browser that appears. In the second browser, locate the file _vb_S urfacePoints Pt.dm and click Open. 3. Once loaded, the surface file will appear in the Sheets control bar, in the 3D | S urfaces F older. Right-click this item and select the Look At option. This will bring the surface file into view if it is not already in the 3D window.
Figure 528: The pit wireframe
Data Presentation – Animations and 3D PDF’s
345
Example 2: Modifying Surface Properties The imported surface is grey. To change it (in this example to a grey pit and green surrounding it) follow these steps. 1. Right-click the imported surface name in the Sheets control bar and select ….Properties. The name of an imported file, in this example, has been generated automatically (although it can be amended). As the surface is a composite of two files, the default naming convention for surface objects is: Triangle File Name/Surface File name (wireframe)
2. Set the Color Legend field to [Rainbow 7]. 3. Set the Color Column field to [COLOUR] (not 'COLOR' - this distinction is important). COLOUR is a field in the surface object containing numbers relating to colour numbers. You won't normally see these numbers (unless you view the .dm files outside of Studio RM). 4. Click Apply, the surface should now be displayed in two colors, similar to that shown below (although the object orientation may be different):
Figure 529
5. In the Shading section of the Surface Properties dialog select the Flat option and click OK. This will render the surfaces of the wireframe without smoothing.
Figure 530
Exercise 3: Navigational Control In this exercise you will learn to work with the navigation controls.
Data Presentation – Animations and 3D PDF’s
346
1. Using the View ribbon, make sure Floating View is selected
.
2. Select Look Atmode, - if it is already selected (i.e. orange), click it once to disable, and once again to re-enable. When Look At mode has been successfully activated, your cursor will change into a magnifying glass.
3. Click on one of the corners of your VR scene. The view will rotate to center the “Look At Point”
Figure 531
4. Hold down the button and then drag with the left mouse button. The view is rotated around the Look At point. 5. Toggle off the Look At button. By disabling this button, you are removing the ‘focus’ of the virtual camera, such that it no longer has a specific position in your VR scene to rotate around. Once this mode is disabled, the viewpoint itself becomes the anchor for rotation. Rotation is performed around your virtual position. 6. Drag the mouse left and right with the left mouse button down (no this time), and note how the view now rotates around your current position rather than a point you are looking at. Note that in this ‘free view’ mode, moving the mouse up and down has an alternative effect to moving left and right, permitting the camera to zoom in and out of the scene. 7. It is also worth noting that in this viewing mode, the button does not have any effect on how rotating and/or zooming is performed. 8. Drag the mouse forwards and back with the left mouse button down (no necessary) and watch how the view moves forward and back in the direction you are looking (rather than to and from a specific point). 9. Another method of centring your view on a specific position (even one that is not readily viewable on screen at the time) is to use the Workspace context menu’s Look At menu command. Expand the Surfaces folder in the Sheets Control Bar and you will see your
single surface file shown:
Data Presentation – Animations and 3D PDF’s
347
Figure 532: The Look At option in the context menu
10. Right-click this item and select the Look At option. This will then automatically centre the view so that the centre of the selected item is shown in the centre of the display area. The Look At option is supported for all VR data types (including block models, points, strings etc.). 11.One more option available is to show your entire scene in a plan view. This can be achieved,
regardless of the mode you are presently in, by clicking the Plan View icon For rapid orientation of your scene around a fixed point, it is advisable to make regular use of the Look At mode & key combination, and to smoothly traverse your scene in a more freeform manner, disabling the Look At mode and using the up/down and left/right cursor movement, you can gradually migrate your viewpoint to the desired location.
Exercise 4: Viewing Block Models with Sections This example outlines the procedure of loading a block model and viewing it using sections. 1. Load a block model (e.g. _vb_modgrd ) into the 3D window. 2. Assign a legend to the block model by right-clicking on the object in the Sheets control bar and selecting Properties from the drop down menu. 3. Select the required legend from the Color Legend list and then the required column from the Color Column list. 4. Also make sure the Display Type is set to Quick Section and click OK to close the dialog.
Data Presentation – Animations and 3D PDF’s
348
Figure 533: Block model properties
5. Open the Section Control dialog by right-clicking on the block model under the 3D folder in the Sheets control bar and selecting Quick Section Controls. 6. Select the section plane (for the purpose of this example a JK Plane (N-S section) is selected). Move through the model using the slider bar.
Figure 534: Section control
7. To view another section using the Quick Section functions load the block model a second time and repeat steps 2 through to 6, but this time select another section plane to view (e.g. IJ Plane (plan)).
Figure 535: Multiple sections
Data Presentation – Animations and 3D PDF’s
349
Exercise 5: Viewing Block Models as blocks When viewed as blocks, the cuboids of the block model reveal themselves, allowing you to format the display in different ways to section views. 1. Ensure a block model is loaded in the VR window (e.g. _vb_modore). Open the Properties dialog by right-clicking on the block model under the VR folder in the Sheets control bar. 2. In the Display Type area, select the Blocks option and click Apply. The view of the data will update to show your block model as filled block cells. 3. The default exaggeration is 100% which results in each block touching its neighbour without gaps. To change this, enter 50 in the exaggeration field. Click OK or Apply to see how this affects the cuboids.
Figure 536: As small blocks
Exercise 6: Draping Textures This example outlines the procedure of draping a .jpeg image over the pit and topography wireframe _vb_SurfacePointsPt.dm \ _vb_SurfaceTriangles.dm. 1. Make sure that the file _vb_SurfacePointsPt.dm \ _vb_SurfaceTriangles.dm is loaded into the 3D Window. 2. In the Sheets control bar right-click on the loaded surface (_vb_SurfacePointsPt.dm \ _vb_SurfaceTriangles.dm(wireframe) ) and select Properties. This will display the Surface Properties dialog. 3. Select the browse button ( ) next to the Texture field, and locate the required file. For the purposes of this example the file is located in the folder C:\Database\DMTutorials\Data\VBOP\Pics. The file name is _vb_ITPhoto-Texture.jpg . 4. In the Surface Properties dialog click OK to see the effect. You may, at this stage, see the Choose Texture Size dialog. This is displayed in order to 'down-sample' an image that may cause your system to be adversely affected by the loading of a large image file.
5. Select the Plan View icon. 6. You should now see the surface of the imported wireframe update to display the loaded texture, similar to the image below:
Data Presentation – Animations and 3D PDF’s
350
Figure 537
Exercise 6: Manual Alignment The texture, at present is not aligned accurately, although it is difficult to see the misalignment from the current elevation. For this reason, it is often useful to overlay an alignment string (or strings) onto the scene to highlight the distinguishing features of the geometry and make manual alignment easier. 1. Load the alignment string _vb_Alignstr into the 3D window.
Figure 538
2. Ensure you are in Plan view. 3. To make the alignment strings clearer, and drawn ‘on top’ of the surface data – double click anywhere in the 3D window to open the Environmental Settings dialog. Select the Use Polygon Offset function. This will show the imported strings over the surface.
Figure 539: Environmental settings
4. To make things even clearer change the color of all strings to red. Right-click the _vb_alignstr.dm item in the Sheets control bar (under the Strings folder) and select the Properties option. 5. Select the Edge Visual tab, and in the Color Legend drop-down list, select [Red]. Click OK. 6. Use the navigational tools to zoom in on the scene so that the following area is magnified.
Data Presentation – Animations and 3D PDF’s
351
Figure 540
7. Textures can only be manipulated whilst Drape mode is active. To activate it right-click on _vb_SurfaceTrianglesTR/_vb_SurfacePointsPT in the Sheets control bar and select Drape Mode from the menu. 8. To align textures efficiently, it is a good idea to locate key topographical landmarks on the image that can be easily aligned with a contour string. Shadows cast by pit walls are often effective in doing this as they can indicate the edge of a particular aspect. For example, the image below has many potential landmarks for lining up, one of which is shown below in the blue ellipse (the ellipse is for demonstration purposes only):
Figure 541
9. It can be seen from this area that the texture is not aligned with the topography. To manipulate the texture, you will need to use the Translate Texture icon . Select the icon and move your cursor into the work area. The cursor will now appear as a cross. 10. Using the image below as a guide, click and hold the mouse down at point 1, drag to point 2 and release, you will see the texture shift on releasing the mouse button. Note that we are selecting the position on the texture, and then the new position of that part of the texture.
Data Presentation – Animations and 3D PDF’s
352
. .
Figure 542
11. Once the alignment is quite close it can be useful to fix the texture at a point. This is possible by selecting the anchor icon . After selecting the icon, the cursor will change shape. Press the left mouse button to fix the image at a point. The texture and topography may not always line up exactly, in all places - there are several possible reasons for this: •The srcinal photograph may not have been taken from directly above the centre of the pit. •The resolution of the underlying wireframe data may not be dense enough to capture all real -world features. •Errors may have occurred during surveying.
Exercise 7: Adding Objects This example outlines the procedure for defining a new object type and loading an associated object into the 3D window. The following image shows a topographic surface (_vb_SurfaceTrianglesTR/_vb_SurfacePointsPT ) with a photograph draped over it. Before you can add objects of any type, it is necessary to load an object type, from which you can create instances in your scene.
Data Presentation – Animations and 3D PDF’s
353
Figure 543: Haul truck properties
1. To load a new object type, right click on the VR Object Types folder (not the VR Objects folder) and select New. This will open the Object Type Properties dialog. 2. To select a model file (Studio 3 supports the use of DirectX (.x) files) click the browse ( ) button next to the model field and locate the samples folder, found under C:\Program Files (x86)\Common Files\Earthworks\VR. All suitable files will be listed. 3. Select the Haultruck.x model file and open it. 4. Back in the Object Type Properties dialog, set the Max speed to 35. This is important as, without a maximum speed above zero, object movement cannot be simulated in later exercises. 5. Click on the OK button to close the dialog. 6. A new Object Type called Haultruck has been added to the VR Object Types folder in the Sheets control bar.
Data Presentation – Animations and 3D PDF’s
354
Figure 544: Sheets control bar
7. The next step is to place an instance of the Haultruck in your VR scene. 8. To place a haultruck object you must right-click the Haultruck object type, and select Place Objects:
Figure 545: Place objects option
9. Move the cursor into the work area. The shape of the cursor will have changed to the image shown below:
Figure 546: Cursor to place object
10. It is now possible to place an object. Press the left mouse button to place an object anywhere on the textured landscape (the positioning isn't important at this stage). 11. To end the place object mode, press the right mouse button. 12. When you place an object, a new entry will be displayed in the VR Objects folder. The default name is Haultruck 1. The name of the object can be changed by right-clicking on the item in the Sheets control bar and selecting Properties. Enter the new name in the Name area of the dialog.
Data Presentation – Animations and 3D PDF’s
355
Figure 547: Haul truck name
13. Right-click the newly created haultruck in the VR Objects folder and select Outside View.
Figure 548: Set outside view
This will show an outside view of the selected item quickly, as shown below:
Place objects mode must be turned off to adjust the position of an object. If the cursor is displayed as right-click in the work area to disable it.
Data Presentation – Animations and 3D PDF’s
356
A PPENDIX
1
STUDIO RM TRAINING COURSES Geostatistics and Resource Evaluation Course overview This programme covers both geostatistical theory as well as the practical application using tools within Studio RM to carry out validation of drilling data, statistical and spatial analysis (variography), as well as linear and non-linear estimation techniques including ordinary, simple and multiple indicator kriging. The programme also covers the process of model validation and model evaluation, the techniques available for the classification and reporting of resources, and the use of the Mineable Reserves Optimiser (MRO). This tool is a quick and simple method of determining the portions of the mineral resource which satisfy key mining criteria such as cut-off grade, mining width and internal and external dilution. Who should attend Geologists Course duration Five days
Uniform Conditioning Course overview The programme will provide delegates with a comprehensive overview of the theory and practical application of the uniform conditioning functionality in Studio RM. Who should attend Geologists Course duration Three days
Conditional Simulation Course overview The programme provide delegates a comprehensive of the theory and practical application of thewill conditional simulationwith functionality in Studiooverview RM. Who should attend Geologists Course duration Three days
Studio RM Training Courses
357
Ore body unfolding Course overview The programme will provide delegates with a comprehensive overview of the theory and practical application of the orebody unfolding functionality in Studio RM. Who should attend Geologists Course duration Three days
Macros in Studio RM Course overview The programme will provide delegates with a comprehensive overview of the theory and practical application of the macro functionality in Studio RM. Who should attend Geologists Course duration Three days
Studio RM Training Courses
358
A PPENDIX
2
DATAMINE FILE TYPES Block Model File Numeric or Alphanumeric
Field
XMORIG
N
Implicit or Explicit
I
Description
The X, Y and Z coordinates of the model srcin. Studio sets the srcin at
YMORIG ZMORIG
the corner not the centroid of the first parent cell.
XINC YINC ZINC
N
I/E
The dimensions of the cell in the X, Y and Z directions. If the model will not contain any subcells then these three fields can be implicit (not stored on every record). This will reduce the storage space required by the model.
NX NY NZ
N
I
Number of parent cells in the X, Y and Z directions of the model. Studio allows a value of 1 for modelling seams. The number of cells, in combination with the cell dimensions, defines the extent of the model.
XC YC ZC
N
E
The X, Y and Z coordinates of the cell center.
IJK
N
E
Code generated and used by Studio to identify each parent cell position uniquely within the model. Subcells that lie within the same parent cell will have the same IJK value.
In addition to the above, block model files normally contain one or more value fields. They are typically sorted on increasing IJK value.
Wireframe Triangle File Numeric or Alphanumeric
Field
Implicit or Explicit
Description
TRIANGLE
N
E
The triangle number.
PID1 PID2 PID3
N
E
The Point Identifier (PID) numbers from the wireframe points file which make up this triangle.
Wireframe Points File Field
PID
Numeric or
Implicit or
Alphanumeric
Explicit
N
E
Description
Sequential Point Identifier, starting from 1. The Point Identifier is equal to the file record number.
XP YP ZP
N
Datamine File Types
E
The X Y and Z coordinates of the Point.
359
String File Field
Numeric or Alphanumeric
Implicit or Explicit
Description
XP YP ZP
N
E
The coordinates of the String vertex.
PTN
N
E
The String vertex number.
PVALUE
N
E
The String number
Desurveyed Drillhole File Numeric or Alphanumeric
Field
Implicit or Explicit
Description
BHID
N/A
E
The Drillhole Identifier.
FROM
N
E
The distance down the hole to the top of the sample.
TO
N
E
The distance down the hole to the bottom of the sample.
LENGTH
N
E
The length of the sample.
X Y Z
N
E
The Sample centre coordinates.
A0
N
E
The Azimuth of the sample in degrees measured clockwise from north.
B0
N
E
The dip of the sample in degrees. (90 degrees is vertically downwards, and -90 degrees is vertically upwards).
Drillhole Collars File Field
Numeric or Alphanumeric
Implicit or Explicit
Description
BHID
N/A
E
The Drillhole Identifier.
XCOLLAR
N
E
X coordinate of collar location.
YCOLLAR
N
E
Y coordinate of collar location.
ZCOLLAR
N
E
Z coordinate of collar location.
Downhole Survey File Numeric or Alphanumeric
Field
Implicit or Explicit
Description
BHID
N/A
E
The Drillhole Identifier.
AT
N
E
The distance down the hole to the survey measurement.
BRG
N
E
The bearing of the survey measurement in degrees measured clockwise from North.
Datamine File Types
360
DIP
N
E
The dip of the survey measurement in degrees. (90 degrees is vertically downwards, and -90 degrees is vertically upwards).
Downhole Sample File Numeric or Alphanumeric
Field
Implicit or Explicit
Description
BHID
N/A
E
The Drillhole Identifier.
FROM
N
E
The distance down the hole to the top of the sample.
TO
N
E
The distance down the hole to the bottom of the sample.
Point Data File Field
Numeric or Alphanumeric
Implicit or Explicit
Description
XPT
N
E
X coordinate of data point.
YPT
N
E
Y coordinate of data point.
ZPT
N
E
Z coordinate of data point.
Plot File Prototype A plot file prototype is used to define the scaling, size and position of the plot file to be created. The prototype file may contain data. If it does this will sometimes be appended to the file being created. Often the data from the prototype is appended to the new plot file depending upon the setting of the APPEND parameter. A new plot file prototype can be generated using the PROTOP process.
Plot File Field
Numeric or Alphanumeric
Implicit or Explicit
Description
X Y
N
E
Plot element location.
S1 S2
N
E
The plot element definition.
CODE
N
E
The plot element code.
COLOR
N
E
The plot element color.
XMIN
N
I
The plot limits.
XSCALE YSCALE
N
I
The plot scale.
XORIG YORIG
N
I
The plot srcin.
CHARSIZE
N
E
The plot element character size.
XMAX YMIN YMAX
Datamine File Types
361
ASPRATIO
N
E
The plot element character aspect ratio.
Variogram File - Experimental The experimental variogram will normally be created by the VGRAM process. An experimental variogram is required as input to the interactive variogram fitting process VARFIT. Numeric or Alphanumeric
Field
GRADE
A
Implicit or Explicit
E
Description
Name of the grade field whose variogram has been calculated. This will always be an alpha (character) field with a maximum size of 8 characters.
AZI
N
E
Azimuth of the variogram, measured clockwise in degrees from north.
DIP
N
E
Dip of the variogram, measured in degrees from the horizontal plane. (Downwards is positive).
LAG
N
E
Lag distance.
AVE.DIST
N
E
Average distance between sample pairs for that lag.
NO.PAIRS
N
E
Number of sample pairs for that lag.
COVAR
N
E
Covariance between sample pairs for that lag.
VGRAM
N
E
Variogram value between sample pairs for that lag.
PWRVGRAM
N
E
Pairwise relative variogram value for that lag.
LOGVGRAM
N
E
Log variogram value for that lag.
Variogram Model File Numeric or Alphanumeric
Field
Implicit or Explicit
Description
VREFNUM
N
E
Variogram reference number. This is a numeric identifier to enable one or more variograms to be selected from the file.
VANGLE1
N
E
First rotation angle, defining orientation of range ellipsoid.
VANGLE2
N
E
Second rotation angle, defining orientation of range ellipsoid.
VANGLE3
N
E
Third rotation angle, defining orientation of range ellipsoid.
VAXIS1
N
E
First rotation axis (1=X axis, 2=Y axis, 3=Z axis).
VAXIS2
N
E
Second rotation axis (1=X axis, 2=Y axis, 3=Z axis).
VAXIS3
N
E
Third rotation axis (1=X axis, 2=Y axis, 3=Z axis).
NUGGET
N
E
Nugget variance (Co).
ST1
N
E
Variogram model type for structure 1: 1=spherical, 2=power, 3=exponential, 4=gaussian, 5=De Wijsian.
ST1PAR1
N
E
Structure 1, parameter 1 (Range in X direction for spherical model).
Datamine File Types
362
ST1PAR2
N
E
Structure 1, parameter 2 (Range in Y direction for spherical model).
ST1PAR3
N
E
Structure 1, parameter 3 (Range in Z direction for spherical model).
ST1PAR4
N
E
Structure 1, parameter 4 (Spatial variance for spherical model - C value).
A variogram model consists of a nugget variance, Co , and up to 9 individual structures, Gi(h). The combined model, V(h), is of the form: V(h) = Co + G1(h) + G2(h) + G3(h) + ..... + G9(h)
The individual models Gi(h) can be spherical, power, exponential, gaussian or De Wijsian. The fields shown in the above table are the minimum required for a single structure variogram model. If the model variogram includes two or more structures then an additional four fields are required for each structure - STi, STiPAR1, STiPAR2, STiPAR3, STiPAR4 for each structure i. Refer to the Grade Estimation User Guide for further details of variogram models and the definition of orientation.
Dependency File The dependency file is used in scheduling to define dependencies between blocks. The block in the PNUM1 field must be mined first before the block in the PNUM2 field. For further details refer to the Scheduling User Guide. Field
Numeric or Alphanumeric
Implicit or Explicit
Description
PNUM1
N
E
Block number of block to be mined first.
PNUM2
N
E
Block number of block to be mined after PNUM1.
Section File The section definition file is used to store the coordinates and orientation of a view plane for use in the Design and Plots windows. Field
Numeric or Alphanumeric
Implicit or Explicit
Description
XCENTRE
N
E
X coordinate of the center of the section.
YCENTRE
N
E
Y coordinate of the center of the section.
ZCENTRE
N
E
Z coordinate of the center of the section.
SDIP
N
E
Dip of the section.
SAZI
N
E
Azimuth of the section.
HSIZE
N
E
Horizontal size of the section.
VSIZE
N
E
Vertical size of the section.
If the file is created automatically from the 3D window it will also include the following fields: Field
Numeric or Alphanumeric
Implicit or Explicit
Description
SVALUE
A
E
A section identifier of up to 8 characters.
Datamine File Types
363
DPLUS
N
E
Distance of influence of the section measured forwards from the displayed section towards the viewer.
DMINUS
N
E
Distance of influence of the section measured backwards from the displayed section away from the viewer.
TEXT
A
E
A description of up to 20 characters.
Results File The results file is created when an evaluation is undertaken in the Design window. Field
Numeric or Alphanumeric
Implicit or Explicit
Description
MODEL
A
I
he name of the model file which has been evaluated.
BLOCKID
N
E
The mining block identifier.
DENSITY
N
E
The average density within the block.
VOLUME
N
E
The volume of the block.
TONNES
N
E
The tonnage of the block.
The results file may contain additional fields such as grades and a classification category.
Search Volume Parameters File The search volume parameter file defines a set of search volumes to be used by grade interpolation processes such as ESTIMA and XVALID. It can be created using standard database processes such as INPUTD and AED, or using Alternatively can be created using theofCAE Editor. The file contains 24 fields all of ESTIMATE. which are compulsory. A itmore detailed description the Table fields is given in the Grade Estimation User Guide. Numeric or Alphanumeric
Field
Implicit or Explicit
Description
SREFNUM
N
E
Search volume reference number. This is a numeric identifier to allow one or more search volumes to be selected from the file.
SMETHOD
N
E
Search volume method (1 = 3D rectangle, 2 = ellipsoid).
SDIST1
N
E
Length of axis 1, initially in X direction prior to rotation.
SDIST2
N
E
Length of axis 2, initially in Y direction prior to rotation.
SDIST3
N
E
Length of axis 3, initially in Z direction prior to rotation.
SANGLE1
A
E
First rotation angle, defining orientation of search ellipsoid.
SANGLE2
N
E
Second rotation angle, defining orientation of search ellipsoid.
SANGLE3
N
E
Third rotation angle, defining orientation of search ellipsoid.
SAXIS1
N
E
First rotation axis: 1=X axis, 2=Y axis, 3=Z axis.
SAXIS2
N
E
Second rotation axis 1=X axis, 2=Y axis, 3=Z axis.
Datamine File Types
364
SAXIS3
N
E
Third rotation axis 1=X axis, 2=Y axis, 3=Z axis.
MINNUM1
N
E
Minimum number of samples for first dynamic search volume.
MAXNUM1
N
E
Maximum number of samples for first dynamic search volume.
SVOLFAC2
N
E
Axis multiplying factor for second dynamic search volume.
MINNUM2
N
E
Minimum number of samples for second dynamic search volume.
MAXNUM2
N
E
Maximum number of samples for second dynamic search volume.
SVOLFAC3
N
E
Axis multiplying factor for third dynamic search volume.
MINNUM3
A
E
Minimum number of samples for third dynamic search volume.
MAXNUM3
N
E
Maximum number of samples for third dynamic search volume.
OCTMETH
N
E
Octant definition method 0 = do not use octants, 1 = use octants.
MINOCT
N
E
Minimum number of octants to be filled.
MINPEROC
N
E
Minimum number of samples in an octant.
MAXPEROC
N
E
Maximum number of samples in an octant.
MAXKEY
N
E
Maximum number of samples with same key field value.
Estimation Parameters File The grade estimation parameter file defines a set of grade estimation parameters to be used by grade estimation processes such as ESTIMA and XVALID. It can be created using standard database processes such as INPUTD and AED, or using ESTIMATE. Alternatively it can be created using the CAE Table Editor. The file contains up to 29 fields of which only VALUE_IN and SREFNUM are compulsory. A more detailed description of the fields is given in the Grade Estimation User Guide. Numeric or Alphanumeric
Field
Implicit or Explicit
Description
VALUE_IN
A-8
E
Name of field to be estimated.
VALUE_OU
A-8
E
Name of field to be created.
SREFNUM
N
E
Search volume reference number.
{ZONE1_F}
A/N
E
First field controlling estimation by zone.
{ZONE2_F}
A/N
E
Second field controlling estimation by zone.
NUMSAM_F
A-8
E
Field to contain number of samples used.
SVOL_F
A-8
E
Field to contain dynamic search volume.
VAR_F
A-8
E
Field to contain variance.
MINDIS_F
A-8
E
Field to contain transformed distance to nearest sample.
Datamine File Types
365
IMETHOD
N
E
Estimation method: 1=Nearest Neighbour, 2=Inverse Power of Distance, 3=Ordinary Kriging, 4=Simple Kriging, 5=Sichel's t-Estimator.
ANISO
N
E
Anisotropy method for IMETHOD=1 or 2: 0=isotropic, 1=use search volume, 2=use ANANGLE1, etc.
ANANGLE1
N
E
First rotation angle, defining anisotropy ellipsoid for IMETHOD=1 or 2.
ANANGLE2
N
E
Second rotation angle, defining anisotropy ellipsoid for IMETHOD=1 or 2.
ANANGLE3
N
E
Third rotation angle, defining anisotropy ellipsoid for IMETHOD=1 or 2.
ANDIST1
N
E
Length of anisotropy axis 1, initially in X direction prior to rotation, for IMETHOD=1 or 2.
ANDIST2
N
E
Length of anisotropy axis 2, initially in Y direction prior to rotation, for IMETHOD=1 or 2.
ANDIST3
N
E
Length of anisotropy axis 3, initially in Z direction prior to rotation, for IMETHOD=1 or 2.
POWER
N
E
Power of distance for Inverse Power of Distance (IPD) weighting.
ADDCON
N
E
IPD - constant added to distance. Sichels t - additive constant for lognormal distribution.
VREFNUM
N
E
Variogram model reference number
LOG
N
E
Lognormal kriging flag: 0=linear, 1=log.
GENCASE
N
E
Lognormal kriging method:0=Rendu, 1=General Case.
DEPMEAN
N
E
Mean for lognormal variance calculation.
TOL
N
E
Convergence tolerance for log kriging.
MAXITER
N
E
Maximum number of iterations for log kriging.
KRIGNEGW
N
E
Treatment of negative kriging weights: 0=keep and use, 1=ignore samples with negative weights.
KRIGVARS
N
E
Treatment of kriging variance > sill: 0=keep KV>sill, 1=set KV=sill.
LOCALMNP
N
E
Method for calculation of local mean for simple kriging: 1=field from PROTO file, 2=calculate mean.
LOCALM_F
N
E
Name of local mean field in PROTO for simple kriging.
Attribute Validation File Validation files are used when defining and editing data using commands such as new string and editattributes Validation files are used to control the values which a user can enter for attributes. For example, the value of the attribute LITHO could be constrained to be entered as only LIME, QUARTZ, and GRANITE. This would be done by having three lines in the validation file for ATTNAME "LITHO" and specifying LIME, QUARTZ, and GRANITE as three values.
Datamine File Types
366
Validation files are opened using the open-validation-file command. Numeric or Alphanumeric
Field
Implicit or Explicit
Description
ATTTYPE
A
E
Attribute type: N = Numeric, A = Alphanumeric.
ATTNAME
A-8
E
Attribute (or Field) name to be validated.
VALUE
A
E
Possible value for this attribute. Used if ATTTYPE is A.
MIN
N
E
Minimum value for this attribute. Ignored if ATTYPE is N.
MAX
N
E
Maximum value for this attribute. Ignored if ATTYPE is N.
DEFAULT
N
E
Default value for this attribute.
Planes File The planes file is used to store the parameters describing planes — that is, flat surfaces. It is typically used to store mapped geological or geotechnical planar features, for example a fault or joint surfaces. This file can be viewed in 3D in the window, and is used when creating Stereonet Charts or using the calculate-geotechnical-attributes command. Numeric or Alphanumeric
Field
Implicit or Explicit
Description
XP
N
E
X coordinate of the center of the plane.
YP
N
E
Y coordinate of the center of the plane.
ZP
N
E
Z coordinate of the center of the plane.
SDIP
N
E
Dip of the section.
DIPDIRN
N
E
Dip direction of the plane.
HSIZE
N
E
Horizontal size of the plane.
VSIZE
N
E
Vertical size of the plane.
SYMBOL
N
E
Display symbol.
COLOUR
N
E
Default plane and symbol colour.
VARIANCE
N
E
Where a plane has been generated from another process, this value describes a measure of how closely point data in the srcinal object relates to the position of the plane (best fit analysis).
BLOCKID
N
E
A mining block identifier.
Datamine File Types
367
Datamine File Types
368
