.

Annual Maintenance &

Services Offer

2014 - 2015

Release Notes

Datamine Studio RM v1.1.13.0 (32-bit)

Datamine Studio RM v1.1.13.0 (64-bit)

Public Release

1

Table of Contents

What’s New for Datamine Studio RM v1.1 2

Main Messages for Datamine Studio RM v1.1 2

Studio RM Licensing – Technical Note 4

32 vs. 64 Bit – Technical Note 5

Technical Note on 64-bit System Output 5

The SUMMIT Window – Getting Started 9

Introducing the SUMMIT window 9

RELEASE NOTES – STUDIO RM 1.1 11

Core System Commands & Processes 11

User Interface 13

Visualization 13

Charting & Reporting 14

Data Transfer 14

Utilities & Supporting Services 15

Documentation 15

2

WHAT’S NEW FOR DATAMINE STUDIO RM V1.1

Studio RM is Datamine’s latest Resource Modelling solution, and represents a major step

forward for Datamine customers worldwide. Studio RM is built on the proven Datamine Studio

RM platform.

Main Messages for Datamine Studio RM v1.1

New!! 64-bit System Studio RM v1.1 is available as both 32- and 64-bit installation packages. The 64-bit version allows you to access more system resources on suitably-equipped systems. We recommend you review the Technical Note, further below, for more information.

New!! Seamless SUMMIT Connectivity Studio RM introduces the new Summit window; this provides access to your Summit portal to easily transfer data from desktop to cloud. You and your colleagues can visualize your data using Summit. An active Summit subscription is required.

New!! New Processes and Process Improvements New processes are available in this version, including:

• COMBMOD: Combine multiple block models that may have different data definitions.

• EXPNDMOD: Expand a block model to fill a larger volume and/or fill its full volume with cells.

• DILUTMOD: Adjust model cell values where adjacent ore/waste values differ to model dilution across material boundaries.

• CLOSEPTS: Identify pairs of points or drillhole samples and collars that are within a specified distance of each other. This is useful for checking samples prior to Kriging.

• STATS: a new PCNTILES parameter is now available to calculate percentiles and the Median Absolute Deviation. The 50% percentile is the median.

The coefficient of variation and mid-range values are now always calculated.

3

The KEYSORT parameter can be used to automatically sort the input file on its key fields, removing the need to manually sort the input file before using STATS. The SORTOUT parameter can be used to automatically sort the output file by FIELD. This makes it much easier to compare the statistics of fields across different key fields, for example grades within different rock types.

• CORREL: now has the option to output a file containing the correlation matrices. It also has an option to specify a zone key field that can be used to calculate correlations per rock type.

• SLIMOD and PERFIL: now automatically output models sorted on IJK. In addition, PERFIL now supports a CHECKROT parameter to automatically check for an input rotated model.

• COUNT: COUNT now has an optional KEYSORT parameter which can be used to automatically sort the input file on its key fields before processing.

New!! Wireframe Clean Function The new wireframe-clean command provides a set of options which can be used to fix many problems in wireframes found as a result of the Verify command.

New!! Quick Filters A new “Quick Filter” function allows you to rapidly define filters which can be used to hide or show loaded data with the minimum of fuss. You can select one or more bins in a selected legend and your 3D scene will update automatically.

New!! Uniform Conditioning Improvements Continuing the efforts made for Studio RM 1.0, Studio’s Uniform Conditioning module has been enhanced to provide support for even more cut-offs, and to provide more feedback on variances and parameters used in the UC process.

New!! Studio Command Library Studio products have always been supported by an extensive library of documentation. As part of this update, the previous “Command Table”, showing an alphabetized list of processes and commands, has been overhauled to show (per command) the product(s) in which it can be found, a description and link to a more detailed help file.

…and many other improvements made since the last release of Studio RM. A full list of changes is

available in the “Release Notes” section.

4

STUDIO RM LICENSING – TECHNICAL NOTE

Studio RM has a new and much simpler licensing model than Studio 3. It greatly reduces the

number of licensable modules required to gain access to all available functionality. It is simple

and easy to understand.

Instead of having to license multiple modules individually, Studio RM provides just two basic

license types:

• CORE: This license grants you access to all proprietary resource modelling and

evaluating functionality contained within the Studio RM product, including wireframing,

editing, modelling and geostatistics. Everything you need to perform resource modelling

tasks is in here.

• 3rd Party: Where 3rd party functionality has been integrated within Studio RM,

additional licensing may be required to access it. There are currently only 3 instances

of functionality that require additional licensing:

o Wireframe-create-from-points: this command, which accesses the

Reshaper® technology from Technodigit® is licensed (as with Studio 3) via a 3rd

party dongle, a 3rd party license and a separate ‘point hulling’ Datamine license.

o Uniform Conditioning: co-developed in partnership with Geovariances©, this

module is licensed independently of the core Studio RM system.

o Mineable Shape Optimizer: developed in partnership with Alford Mining

Systems, stope optimization routines within this module are separately licensed.

Your existing Studio 3 license cannot be used to activate Studio RM.

You will need to access a dedicated Studio RM license in order to run Studio RM. Your Datamine

office can assist you with this transition.

5

32 VS. 64 BIT – TECHNICAL NOTE

Studio RM V1.1 is available in both 32 and 64-bit

There’s often a lot of misinformation surrounding 32- vs. 64-bit systems so to avoid confusion

we recommend reading the following notes.

Using a 64-bit software version of a program instead of its 32-bit equivalent can have very

positive results, but only if the environment in which it is running is appropriate.

Technical Note on 64-bit System Output

Due to compilation differences on 32-bit and 64-bit targets, minor numerical differences of less

than 0.001% may be seen in the results of the 64-bit version of Studio when compared to the

32-bit version. These are down to the inherent restriction of how computers represent and

process floating point values, and should not be regarded as an error.

In brief:

• A program running in a 32-bit Windows® operating system can access up to 2 Gigabytes

(4096 MB) of memory in one go by default, but this is extended in Studio 3 and Studio

RM to 3GB by using a “Large Address Aware” switch.

o This 3GB limit includes the ‘room’ needed for the operating system itself, and

other system resources such as the graphics card and motherboard BIOS.

Applications have to grab whatever is left.

o 32-bit operating systems can only deal with data in 32-bit-sized data ‘chunks’.

o 32-bit operating systems can only run 32-bit applications.

o Even if you install them under a 64-bit operating system, 32-bit programs (e.g.

Studio 3) can only access a maximum of 3GB with a Large Address Aware

configuration. In reality, the available system resources will be lower than 3GB

as the OS will be using some of the available space, as will other applications

and processes.

• In theory, a 64-bit machine can access up to 17.2 BILLION gigabytes of system

memory, but this is dependent on the operating system in use, which in our case is

Windows as other platforms aren’t currently supported.

o Your flavour of Windows matters: What many people don’t realise, is that

some Windows versions deliberately restrict access to the full system resources

through licensing.

6

Windows 64-bit Home editions are deliberately limited to 16 GB of RAM, but the

Professional and Ultimate versions can use up to 192 GB of RAM – this should

be enough for even the most ambitious modelling projects.

o 64-bit operating systems can transfer data around in larger chunks, if an

application can create data of this resolution.

o 32- and 64-bit applications can run on a 64-bit operating system; the 32-bit

version will still be restricted to 2GB (or 3GB) of memory. A 64-bit version can

access more memory providing it is physically available.

o Hardware matters too: A 64-bit operating system sitting on a machine with

4GB of RAM won’t show much benefit over a 32-bit system, and may actually

run with degraded performance.

Scenarios and FAQs

• I have a 64-bit operating system - is it worth me installing a 64-bit version of Studio

RM?

If you are running with more than 4GB of RAM on your system then it could be

advantageous. If your system supports 8GB of RAM or higher, it is highly recommended

that you install the 64-bit system. Systems with less memory may not benefit from

higher memory accessibility and may even see increased memory limitations due to

the additional memory required by the 64-bit architecture.

• I have an 8GB machine running Windows 7 Ultimate (64-bit edition). If I install 64-bit

Studio RM, will I be able to load more data than Studio RM’s 32-bit version?

Yes – a lot more.

• Can I still transfer data between Studio products and 32-bit products, e.g. GDMS

products such as Fusion?

Yes – all Data Source Drivers in Studio RM have been modified to ensure you can still

connect to your remote or local database, regardless of whether you are using a 32- or

64-bit version of Studio RM.

• Do I need a 64-bit web browser for Customization window functions in the 64-bit edition

of Studio RM

No – the Customization window will continue to access whatever browser is set as the

default on your system.

• Will my system run more quickly with a 64-bit version of Studio RM (compared to the

32-bit version)?

A 64-bit application will allow data of a higher resolution to be passed between the

various switchboards of your system, but this is unlikely to result in an increase in

system performance (this will be limited by a mix of other elements, such as the speed

at which your HD can access disk data, the CPU frequency, Graphics card capabilities

and other architectural influences).

7

Where you are likely see improvements is where a process involves the loading of large

amounts of data - in this case, you will be able to work with more data in RAM without

having to read from disk as frequently.

In short – a 64-bit application cannot ‘speed up’ your machine; it can only allow you to

access more RAM, and send data around in bigger packets.

• Will the 64-bit system deliver improved graphics?

No. This is controlled by your systems visualization capabilities and is outside the

influence of Studio.

• Will 64-bit systems contain more features than 32-bit versions?

There are no plans to diverge the development of 32- and 64-bit versions of our

products, and both installer versions will derive from the same source code. In the

future, this situation may change.

• Will 32- and 64-bit systems be released at the same time?

The current plan is to release both versions concurrently as independent 32- and 64-

bit installer packages.

• Can I install a 64-bit edition of Studio RM if I have a 32-bit operating system?

No - you will not be able to proceed with this installation. 64-bit Studio RM editions can

only be installed on 64-bit operating system platforms. This restriction applies to all

Windows® applications.

• Can I install a 32-bit edition of Studio RM if I have a 64-bit operating system?

If you really want to. 32-bit Studio RM instances can be installed on a 64-bit OS, but

you should be aware that it will not take advantage of system resources as effectively

as our dedicated 64-bit application running in an appropriately resourced 64-bit

operating system.

• Can I swap data and/or projects between 32- and 64-bit systems?

Yes, the data you are creating is no different between each system – the difference is

in the operating system environment in which the data is being processed. Providing

you aren’t trying to load projects from a newer version to an older version of Studio RM

(Datamine cannot support backwards compatibility of projects), 32- and 64-bit systems

are fully-compatible.

• Does Studio RM automatically install a 64-bit application if my operating system allows

it?

No. Independent 32- and 64-bit Studio RM installers are available from your Datamine

representative and online support portal. You will need to choose which one you want

before you download and install it.

• Will I be able to run Studio RM alongside Studio 3/OP/EM/5D Planner….?

Yes. Datamine applications are ‘COM-isolated’ and have been deliberately configured to

allow simultaneous usage of Studio family products, providing a valid license is available

for each running application. You do not need to uninstall Studio 3 to install Studio RM.

8

• Do I have to uninstall my other Datamine applications before I install Studio RM?

With one exception his isn’t necessary. Studio RM will upgrade any previous version of

itself, and can be installed happily alongside other Datamine products. Datamine QA

staff routinely run an extensive range of ‘side-by-side’ checks as mandatory exit criteria

for a public release of our software.

Here’s the exception: if you wish to install a 64-bit version of Studio RM and have

already installed a 32-bit version (or vice versa) with an identical version number, you

should uninstall the existing copy of Studio RM before installing the alternative,

identically numbered version.

• How much system memory does Studio RM use?

This depends entirely on what you're doing, what data you have loaded, how much

priority your operating system is assigning to the various processes etc. A 'base'

memory footprint of around 130-140Mb is normal, but this will vary as your session

continues.

• Will Studio RM run under Windows 8?

Yes, all Datamine products released after June 2015 are supported under the Windows

8 and 8.1 operating systems (with the exception of Microsoft’s educational supplements

due to their restricted driver and networking capabilities).

• Will Studio RM run under Windows 10?

Although no issues are expected, formal testing of Datamine products under Windows

10 is not complete at the time of writing this document. As such, our products are not

formally supported under the Windows 10 operating system. More information will be

distributed via your local Datamine office when this situation changes.

9

THE SUMMIT WINDOW – GETTING STARTED

Introducing the SUMMIT window

Studio RM 1.1 provides seamless access to Datamine’s Summit web reporting, 3D visualization

capabilities and mining domain apps.

Upload your data and allow others in your organization, potentially anywhere in the world, to

understand it and visualize it immediately. No more lengthy FTP uploads, lagging remote

desktop sessions or oversized email attachments. Summit also provides a host of dedicated

apps that allow you to process and analyse your data in a shared, secure environment.

• How do I access SUMMIT from within Studio RM?

1. Using the Home ribbon, select Project | Options and navigate to the

Environment tab and the Summit panel

2. Set your startup preference using the check box Show Summit Page on Startup

3. Select Login or Sign Up

4. New accounts may take up to 48 hours to be activated. Your company

administrator will provide an invitation email to your secure company email

address.

• How do I subscribe to a Datamine SUMMIT solution?

For all subscription enquiries, either visit summit1.dataminesoftware.com to sign up, or

contact your local Datamine office for more guidance.

• Can I have a demo of SUMMIT in action?

Absolutely. Your local Datamine office will be happy to organize this with you so give

them a call. You can also find out more about Summit from the Datamine website:

www.dataminesoftware.com

• Are Datamine planning to provide SUMMIT access via other Studio products in the

future?

Studio OP and Studio UG will include the Summit feature in future versions, scheduled

for 2016. Studio EM users will also be able to access the Summit facility, but this will

require purchase of an additional license.

• I currently subscribe to a Summit “App” such as SOPP – can I use data uploaded from

Studio as part of a cloud case study?

Certainly. Summit is an online data management, visualization and functional domain.

Once data is uploaded, and providing you have access to it/them, you can utilize your

workspace data in other Summit applications.

• Can I download processed data from Summit into Studio products directly?

10

Not yet, but we have plans to implement the two-way data transfer in all desktop

products in due course.

• I want to show my data to someone in a remote office. They have access to SUMMIT.

What’s the best plan?

It couldn’t be easier – upload your data via the dedicated Summit portal in Studio RM.

All you need to do then is assign it to a shared workspace, and let your recipient know

it is there, so they can log in and see it.

11

27

RELEASE NOTES – STUDIO RM 1.1

The following cases have been resolved since the last released version of Studio RM

Core System Commands & Processes ID Type Description Various Feature A 64-bit version of Studio RM has been created

Various Feature You can now connect to a Summit portal directly from Studio RM.

CORE-452 Feature A new set of wireframing cleaning commands are available in this version.

CORE-798 Feature A new Quick Filter control bar has been implemented in this version to allow rapid hide/show

of data relating to specific legend bins

STUDIO-3480 Imp. Additional options have been added to the Uniform Conditioning wizard following an update

to the PolAPI library.

STUDIO-3465 Bug An issue preventing the display of the 3D Grid Properties dialog has been resolved.

STUDIO-3450 Bug An issue causing STATS to fail with an alphanumeric keyfield over 16 characters in length has

been resolved.

STUDIO-3437 Bug Dmserver3.exe no longer halts unexpectedly after multiple loops of a macro.

STUDIO-3433 Bug PANELEST no longer gives incorrect values for FVALUE and VARIANCE if run for a second time

with a different variogram model.

STUDIO-3358 Bug UNIFCOND and SUPPCORR process results now (correctly) match the output from Studio 3.

STUDIO-3356 Bug UNIFCOND now estimates all cells in a block model.

STUDIO-2931 Imp. The Uniform Conditioning wizard now outputs more detailed information relating to

parameters used in the process.

STUDIO-2908 Bug SURTRI no longer fails to create triangles with very large numbers of input points.

CORE-322 Imp. Insert-at-intersections now completes much more quickly than previous versions.

CORE-467 Feature PERFIL now supports the use of rotated sections.

CORE-918 Bug OUTPUT now creates CSV files as expected.

CORE-927 Imp. MODSPLIT now includes an option to adjust grades in the output model cells (@DEFGRADE)

CORE-980 Imp. WIREPE will now process all records in a section file.

CORE-1111 Imp. STATS now includes an output file sort option

CORE-1238 Bug The MGSORT process now deals correctly with 0-record files

12

CORE-1281 Bug An issue that could force ACCMLT to display incorrect results has been resolved.

STUDIO-828 Feature SLIMOD, PROMOD and ADDMOD will now automatically sort the resulting model on IJK

STUDIO=879 Feature STATS now includes median and coefficient of variation calculations

STUDIO-1942 Bug STATS no longer reports a file name incorrectly in specific circumstances

STUDIO-3437 Bug An obscure issue whereby the Datamine Server process would disappear after multiple loops

of a macro has been resolved.

STUDIO-3305 Bug A report of LUNICOND failing with an out-of-memory error has been resolved.

STUDIO-3079 Bug CORREL can now outputs correlation matrix information to an external file.

CORE-1284 Bug A minor issue that presented erroneous section selection prompts has been resolved

STUDIO-2795 Feature A new command - DILUTMOD - has been created to model dilution between ore and waste.

CORE-1281 Bug A report of ACCMLT not generating identical results to an earlier version of Studio has been

resolved.

CORE-1246 Bug An issue preventing the completion of the NSCORE process has been resolved.

CORE-1238 Bug MGSORT no longer gives unexpected results when the input file has zero records.

CORE-1116 Feature A new command - COMBMOD - to conjoin multiple model data files.

CORE-1115 Feature A new command - EXPNDMOD - to add waste blocks to ore models.

CORE-103 Bug rename-drillhole no longer overwrites other column values to 0.00 for other columns in the

table

CORE-1315 Imp. The latest version of the MSO engine is included with this update.

STUDIO-3106 Feature An option to exclude 'grade above' from a UC model has been implemented to allow for more

cut-offs to be specified.

STUDIO-3532 Bug An issue preventing the successful shutdown of Studio RM’s system process has been

resolved.

STUDIO-3529 Bug Unexpected results when projecting strings to the view plane have been investigated and

resolved.

STUDIO-3528 Bug TRIFIL no longer creates models with missing cells when @MODLTYPE=2

STUDIO-3474 Bug An issue preventing Uniform Conditioning from running in the 64-bit system will be resolved.

CORE-1300 Bug An intermitent error message shown when creating a DTM has been resolved.

CORE-1274 Task The create-wireframe-from-points commands has been re-implemented for the 64-bit version

of Studio RM.

STUDIO-3449 Bug An issue preventing MSO from being run in the 64-bit version of Studio RM has been resolved.

CORE-1283 Bug The new Clean Wireframe option - T Junction removal – no longer decimates wireframe data

unexpectedly.

CORE-1397 Bug CORREL will now correctly handle absent ZONE data.

CORE-1378 Bug An issue preventing the projection of points to wireframe data has been resolved.

CORE-1573 Bug You can now translate 2-point strings without unexpected results.

CORE-1369 Bug Break-string-at-intersections now generates expected results.

CORE-1364 Bug You can now connect 2-point strings as expected.

13

User Interface ID Type Description

STUDIO-3436 Bug The Logs window's View ribbon now correctly displays the toggle status of the Zoom buttons

for 100% and 200%

STUDIO-3413 Bug [StudioRM] references have been replaced by [Studio RM] throughout the UI.

STUDIO-3389 Bug An intermittent script erorr displayed by the Studio RM start page after a period of inactivity

has been resolved.

STUDIO-3351 Bug An incorrect link on the online Start Page has been resolved.

CORE-1292 Imp. The Project Files and Customization control bars have been given different icons

STUDIO-2864 Bug Unexpected behaviour following the minimize/maximize of data windows has been resolved

STUDIO-2908 Bug SURTRI no longer fails to create triangles with a very high number of of input points

STUDIO-3342 Bug The Files window now shows file sizes correctly if they are in excess of 2GB

STUDIO-3351 Bug A broken hyperlink on the Start page has been rectified.

CORE-1240 Bug The default section name is now recreated correctly after an initial deletion.

CORE-1169 Imp. Datamine branding has been set for dialogs showing previous legal entity name.

STUDIO-3544 Bug Point projection commands are no longer inaccessible due to an inactive parent menu item.

STUDIO-3530 Task The 64-bit version now displays ’64-bit’ in the application title bar and About… box.

STUDIO-3520 Task The Project Wizard no longer displays an “Add File(s) from MineTrust” option, as this

functionality has been superseded by Summit sharing options.

STUDIO-3479 Task STATS UI documentation has been updated.

STUDIO-3481 Task SLIMOD UI documentation has been updated.

STUDIO-3478 Task PERFIL UI documentation has been updated.

STUDIO-3458 Bug The 64-bit version of Studio RM now correctly displays legend icons in the Legends Manager

summary list.

STUDIO-3484 Task The Wireframe-slice option has been returned to the ribbon.

STUDIO-3364 Bug The copy-wireframe command now has a tooltip.

STUDIO-3349 Bug A non-fatal and intermittent “Unable to get property ‘indexOf’ error, caused by deprecated

VBScript, has been resolved.

CORE-1324 Task Drape mode has now been deprecated and removed from the UI

Visualization ID Type Description

CORE-1287 Bug A data-specific instance of the 3D window's information mode not displaying expected results

has been resolved.

14

CORE-1259 Bug Exporting 3D templates to Plots no longer fails for Wireframes and Planes objects.

CORE-1258 Bug 3D templates for Wireframes and Planes objects can now be successfully imported as .tpl files.

CORE-1245 Bug Minor issues relating to the 3D window's Information Mode have been resolved.

CORE-972 Bug The 3D view of a block model no longer disappears unexpectedly if the view type is changed

whilst <100% opacity is used

CORE-1180 Bug The 3D window Colored by Model option no longer requires a manual redraw on completion

CORE-1245 Bug Multiple minor issues have been resolved in relation to Information Mode

Various Bug Several minor issues and improvements have been made to the 3D window templating system

CORE-1263 Bug The reported issue that could force the system to become unresponsive or halt when applying

a legend to a dynamic drillhole in the 3D window, has been resolved.

CORE-1287 Bug A data-specific issue preventing the correct functioning of Info Mode has been resolved

CORE-1248 Bug An issue whereby a 3D section table is renamed unexpectedly after saving the project has been

resolved.

Charting & Reporting ID Type Description

STUDIO-3368 Imp. The tooltip shown when hovering over the picker button for Charting | Variogram 3D ellipsoid

has been improved.

STUDIO-3013 Bug Y axis scale locking now works correctly with the Variogram Fitting Tool.

STUDIO-3012 Bug Saving an isotropic modelled variogram no longer incorrectly sets the Z range to 1.

STUDIO-1100 Bug Omni-directional variogram UI controls are now hidden when no variogram of such a type exists

in memory.

STUDIO-1075 Bug Erasing a modelled variogram no longer incorrectly resets the Y scale.

STUDIO-3443 Bug The “Thunder Gulch” tutorial project can now be opened in the 64-bit version of Studio RM.

Data Transfer ID Type Description

CORE-1254 Bug Unexpected behaviour after renaming a file on export has been resolved.

CORE-1127 Bug You can now export to CAD with spaces in the LAYER field data name

STUDIO-3473 Task

Connection to a Fusion database from the 64-bit system has been blocked in this version.

Integration efforts will be continued for a subsequent release - the user will be informed of this

situation via the UI.

STUDIO-3548 Bug An error when opening projects with Sirovision images preloaded has been resolved.

15

28

STUDIO-3537 Bug The DGN driver now completes as expected in the 64-bit version of Studio RM

STUDIO-3533 Task Feedback on the status of the GDAL driver operation has been increased in this version.

Utilities & Supporting Services ID Type Description

LICSERV-178 Feature A new license type - Hosted License - has been implemented in License Manager to support

Datamine's hosted licensing offering.

LICSERV-177 Feature A subset of administrative functionality has now been exposed to users of hosted licensing

portals.

LICSERV-175 Imp. Enterprise and Department Server license types have now been merged.

Documentation ID Type Description

STUDIO-3446 Bug A broken link in the Drillhole Templates context help file has been fixed.

STUDIO-1294 Task The Datamine Command Table has been split into alphaticized topics, each showing the

availability of each command or process for each Studio product.