.

Annual Maintenance &

Services Offer

2014 - 2015

Preliminary Release Document

Datamine Studio 5D Planner

Version 14.26.65.0 (Public Release)

Requires EPS: 3.0.112.6032

Or;

EPS: 2.24.63.0

1

Table of Contents

What’s New for Datamine Studio 5D Planner MR26 2

Main Messages for Datamine Studio 5D Planner v14.26 2

RELEASE NOTES – STUDIO 5D PLANNER 14.26 3

Control Panel & Workflow 3

Core Commands & Processes 4

User Interface 6

Utilities and Supporting Services 6

Data Transfer 8

Documentation 8

Datamine Product – About Release Versions 9

Major Version Releases 9

Minor Version Updates 9

Maintenance Updates 9

Appendix A: Recommended Hardware Requirements 10

Processor 10

Memory 10

Hard Disk / Storage 10

Operating System 11

Swap Space 11

Monitor(s) 11

Graphics Cards 11

2

WHAT’S NEW FOR DATAMINE STUDIO 5D PLANNER MR26

This release includes many updates in response to feedback from previous versions. In

addition, there are functional changes which are particularly significant.

This is the second maintenance update for Studio 5D Planner v14.26.

Main Messages for Datamine Studio 5D Planner v14.26

New!! Enhanced Production Scheduler v3 Support

This update to Studio 5D Planner allows you to connect your projects

to version 3 of Enhanced Production Scheduler (or later). Please note

that EPS versions 2 or lower are not supported with this update.

New! Model Conversion Utilities

New conversion utilities have been provided to import Gemcom

format models without cell size fields, and Minesight models. Both

options appear in the File dropdown menu.

New! More memory efficient export to Enhanced Production Scheduler v2

This update to Studio 5D Planner allows you to export even larger

projects to EPS v2 without running out of memory.

EPS Connectivity

(Excerpt from “TN00248_EPS_and_Datamine_Products.pdf” – available from Freshdesk or

your local Datamine representative)

Later versions of Studio 5D Planner are designed to work with a minimum version of EPS v3.

Consult the table below for more information:

Studio 5D Planner version Minimum or recommended EPS version(s)

14.25.76.0 or earlier EPS v2.24.63.0 (recommended)

14.26.65.0 EPS v2.24.63.0 (recommended if using v2)

EPS v.3.0.112.6032 (required if using v3)

3

28

RELEASE NOTES – STUDIO 5D PLANNER 14.26

The following cases have been resolved since the last released version of Studio 5D Planner.

This table uses the following key to describe issue types:

A new feature or product

An improvement or extension to existing functionality

Resolution of a defect within the software

Control Panel & Workflow

ID Type Description

Various

Studio 5D Planner now provides support for EPS version 3

CAESDP-2892

The EPS export routines have been optimized to work within a smaller

memory footprint.

CAESDP-2888

You can now specify the M4DSTOPE as a key field when validating the

WFM design file

CAESDP-3016

An issue that could prevent the system from responding after closing EPS

has been resolved.

CAESDP-2996

A data-specific issue resulting in the message “SQL instruction is not valid:

it expected 'DELETE', 'INSERT', PROCEDURE', 'SELECT' or 'UPDATE'” has

been resolved.

CAESDP-2993

Editing of external data sources has been reimplemented in Studio 5D

Planner

CAESDP-2992

It is now possible to use an External Data Source during evaluation

routines.

CAESDP-2985

An issue whereby incorrect columns were being used in Resynchronize

Attrbutes and Scheduling Constraints has been resolved.

CAESDP-2984

An issue causing unexpected behaviour when multiple active EPS

schedules exist has been resolved.

CAESDP-2965

An unexpected attribute when restoring visual tables has been

investigated and resolved.

CAESDP-2944

An incorrectly set TYPE attribute after adding a derived activity has been

resolved.

CAESDP-2942

Resynchronization now occurs as expected for imported wireframes after

Walls and Points have been run.

CAESDP-2935

An error was produced by Studio 5D Planner when attempting to access an

already-open EPS schedule – this has been resolved.

CAESDP-2933

An issue preventing the restoration of visual tables has been resolved.

CAESDP-2924

CAESDP-2876

A project-specific issue causing a failure to export to EPS (due to available

resources) has been resolved.

4

CAESDP-2914

The “Export these colours to EPS” now works as expected.

CAESDP-2837

An issue relating to EPS synchronization has been resolved

CAESDP-2818

An EPS export message “A COM Exception occurred while communicating

with EPS” was reported and resolved.

CAESDP-2791

An unexpected message reporting an invalid SQL statement when

preparing CXS has been resolved.

CAESDP-2349

A project-specific “Problems were encountered with the database

structure” error has been investigated and resolved.

CAESDP-2645

A project-specific issue causing unexpected behaviour during dependency

editing/animation has been resolved.

CAESDP-2710

Dependency editing will now set the snap settings to points as expected.

CAESDP-2136

An issue preventing the accurate display of the section grid when a model

prototype was loaded has been verified as resolved.

CAESDP-2199

The “Finish no later than” dependency is now maintained after

synchronization as expected.

CAESDP-2726

Fields are no longer removed from the Tag String table unexpectedly after

editing tag strings.

CAESDP-2797

A data-specific issue preventing the successful sending of data to EPS has

been resolved.

CAESDP-2823

Resource assignments are now retained during import as expected.

CAESDP-2855

An issue was reported when using all 4 design types and the design

definitions for all 4 design types are being reconnected at the same time.

Subsequent reprocessing of wireframes now completes successfully

CAESDP-2860

A project-specific issue that could cause the system to halt unexpectedly

when filtering imported wireframes has been resolved.

CAESDP-2890

You can no longer add system attributes as non-visual attributes in

Imported Wireframe Validation

CAESDP-2915

Dependencies direction are no longer hidden unexpected when the user

saves in the VR window

CAESDP-2922

A project-specific issue caused by unexpected snap settings preventing the

digitizing of new strings has been resolved.

CAESDP-2829

An issue preventing the successful display of wireframe intersection data

has been resolved.

Core Commands & Processes

ID Type Description

CORE-1995

EPS-505 EPS is no longer closed as part of the S5DP shutdown routine.

CORE-1818

A new command “merge-string-segments-attrib” has been created to

preserve the edge attributes from any strings being merged.

5

CORE-1175

HOLES3D now provides an optional @PROMPT parameter to manage

interactive message when called from a script/macro.

CORE-1969

An issue causing unexpected filtering behaviour after unload-all-filters has

been resolved.

CORE-1963

Created data no longer honors previously erased filters.

CORE-1960

A potential instability during the coloring of dynamic drillholes has been

resolved.

CORE-1959

A data-specific instance of the system halting unexpectedly when applying

collar labels has been resolved.

CORE-1942

Wireframe-clean has been updated to resolve an issue with hole

management.

CORE-1942

Wireframe-clean now closes holes as expected, and with the same output

as legacy versions.

CORE-1939

The “saveonly” procedure in EXTRA no longer changes implicit fields into

explicit fields.

CORE-1920

An issue whereby HOLES3D failed to correctly desurvey all holes, if any

hole is missing a survey sample at AT=0, has been resolved.

CORE-1883

Selection crosses are now visible again.

CORE-1817

An issue with duplicate quick keys showing in the Find Command dialog

has been resolved

CORE-1815

The COUNT process no longer fails to automatically sort when using

multiple alphanumeric keyfields.

CORE-1813

The STATS process has been updated so that TOTAL, MEAN and

MIDRANGE fields in the output file are now always absent if all input field

values, including by keyfield, are absent.

CORE-1789

The extend-string-to-string command was incorrectly using the Design

window orientation during operations, even when used in the 3D view.

This has been resolved.

CORE-1734

A data-specific issue leading to incorrect triangulation during boolean

functions has been resolved.

CORE-1733

Merge-string-segments command no longer produces strings with

inconsistent attributes.

CORE-1680

A performance issue caused when data is copied into an object being

actively filtered has been resolved. This could be exposed in a previous

version, for example, when extruding strings when the option to copy

wireframes was set.

CORE-1656

When using the “Inside DTM strings” attribute option in the dtm-create

command, the highest COLOUR value is used if overlapping strings are

found for a region.

CORE-1636

Problems with the scriptable interface for the VR.Indicator() function have

been corrected.

CORE-1631

The performance of block model evaluations, when run against a large

number of multiple wireframes has now been improved significantly

CORE-1509

Trace labels now take their attributes from the vertices when labelling

points

6

CORE-351

An issue causing incorrect recorded script output when used in

conjunction with EXTRA has been resolved.

User Interface

ID Type Description

CAESDP-2601

CORE-1307

The move-string-section command will now update the position of

string/point data dynamically

CAESDP-2862

You can now sort outlines with errors in the grid proved by the Edit Ouline

Centrelines form.

CAESDP-3000

A typographic error (“addtnional”) on the Import EPS Changes dialog has

been corrected.

CAESDP-2990

OK and Cancel buttons are now disabled in the Import EPS Changes dialog

during an import operation.

CAESDP-2949

A “Tip of the Day” containing a CAE reference has been removed.

CAESDP-2701

A data-specific issue whereby EPS was facing system resource limits after

an export from S5DP, has been resolved.

CAESDP-2686

Minor issues with the Studio 5D Planner Start page have been resolved.

CAESDP-2691

A tooltip has been corrected for the Combine Project Options icon.

CAESDP-2857

An issue preventing the picking of LSTYLE 1001 in some circumstances has

been resolved.

CAESDP-2803

CAESDP-2883

A potentially misleading element of the message displayed during FXS

Design Definition processing has been corrected

CAESDP-2886

CORE-1817

The Find command dialog now correctly reports the ‘ou’ quick key for the

generate-outlines command

CORE-1826

The © notice within the Studio UI has been updated to show the correct

year.

CORE-1763

An issue preventing the correct coloring of grade values with dynamic

drillholes has been resolved.

CORE-1509

Labels on string points in the 3D window now show the correct attribute

CORE-1399

The Datamine Data Converter now correctly displays a version number.

Utilities and Supporting Services

ID Type Description

LICSERV-240

LICSERV-235

LICSERV-230

LICSERV-228

LICSERV-227

License Services: a new “User Logging” facility has been introduced to

allow licensing activity (client or server) to be captured in a format that can

be easily presented.

7

LICSERV-226

LICSERV-222

LICSERV-221

LICSERV-220

LICSERV-219

LICSERV-218

LICSERV-132

LICSERV-213

License Services now allows you to specify a connection to a remote server

broadcasting either an Ipv4, Ipv6 or both protocols.

LICSERV-237

LICSERV-215

Datablast product and module licenses are supported in the latest version

of License Services

LICSERV-167

License Services: the server login dialog will now remember (optionally) a

previously-entered password.

LICSERV-233

LICSERV-224

License Services: documentation has been updated to describe the new

User Logging feature.

LICSERV-223

License Services: a demonstration spreadsheet is now installed, providing

an example of User Logging Pivot Table charting, plus a scripted utility to

facilitate the import of CSV log file data.

LICSERV-268

LICSERV-265

An issue relating to maintenance timestamping has been resolved.

LICSERV-243

License Services: an issue introduced with v5 feature development causing

single temporary keys to be unexpectedly presented as solutions after

being extended, has been resolved.

LICSERV-242

License Services: an annoying issue that caused the license password

dialog to launch “behind” other Datamine windows (i.e. not be visible) has

been resolved.

LICSERV-241

License Services: the remote server password dialog now shows the

correct tab-order.

LICSERV-238

License Services: an issue preventing the Apply button from becoming

enabled after swapping Remote Servers has been resolved.

LICSERV-232

License Services: the Remote Servers grid is now greyed out when this

option is disabled.

LICSERV-213

License Services: an issue preventing the “inactivity timeout” function from

unlocking abandoned licenses has been resolved on both desktop and

cloud server installations.

LICSERV-191

License Services: an issue causing the removal of solution names and

permissions (if used) after applying new maintenance keys has been

resolved.

CORE-1729

An issue preventing the successful import of a DGN file, and resulting in

the system halting unexpectedly, has been resolved.

CORE-1652

Google analytics triggers have been added to all Studio Product Start

pages.

DSDIE-166

The value attribute is now loaded correctly from Vulcan files

CORE-1820

A data specific issue when loading dgn format data has now been resolved

8

Data Transfer

ID Type Description

CAESDP-2574

CAESDP-2902

The GEMS and Minesight model importer utilities are now available from

the File drop-down menu.

Documentation

ID Type Description

CAESDP-3015

The online and offline Start page content for S5DP has been updated.

CAESDP-2472

The Automatic Dependencies Help file has been extended.

CAESDP-2420

More documentation has been added on how dependency-constrained dip

angles are managed within the system.

CORE-1979

Documentation for the !SCRON and !SCROFF macro commands has been

updated.

CORE-1641

The RUNPROG macro command has been documented and can be found

in your Help file.

CORE-1637

Errors in the Help topics for evaluate-1-string and evaluate-2-strings have

been corrected.

9

DATAMINE PRODUCT – ABOUT RELEASE VERSIONS

Datamine desktop products are scheduled to deploy updates as efficiently as possible in order

to provide maximum benefit to clients, ensure our products are competitive and react quickly

to market needs.

Major Version Releases

Major version upgrades (e.g. v1.0, v2.0) are used to deliver significant features or functional

groups. This could be a complete overhaul of the user interface, or where major product

restructuring has taken place. One example of this is the change between Studio OP v1.2 and

Studio OP v2.0, which included a completely new UI plus significant functional additions (e.g.

the managed reserves workflow.

Major Version updates will always contain new features, and can in many ways be regarded as

a “relaunch” of a product.

The scope of change in a major version update is high; these products will contain a mixture

of features, improvements and fixes but will always represent an important new phase in a

product’s evolution (or simply a new product).

Minor Version Updates

Minor version udpates are used to provide new functionality that supports existing core

business processes of the major version. For example, Studio RM has always delivered powerful

grade estimation functionality, but v1.2 introduced the “Advanced Estimation” module for the

first time, vastly extending the capabilities of our resource modelling solution.

There is often a “theme” surrounding each minor version update but they can also contain an

array of unrelated features and fixes. These updates are progressed as per a planned body of

work, based on feedback from previous releases and other business analysis.

Maintenance Updates

Maintenance updates are primarily used to deliver fixes to issues found in a previously-released

version, but can also contain minor improvements. These updates are also referred to as a

“patch”.

Generally, the scope of change in these releases is small, but important enough to warrant

deploying an update to clients. These updates are scheduled as required and will be inserted

into existing development project schedules as required. This allows Datamine to react quickly

to industry needs.

10

APPENDIX A: RECOMMENDED HARDWARE REQUIREMENTS

This section contains an overview of recommended and minimum hardware requirements for

Studio RM.

For all hardware items, a minimum specification is set – this will permit the software to run but

you may encounter performance issues with large and/or complex data sets, and your system

will be sensitive to other (non-Datamine) running processes. A recommended specification is

also provided – this will reflect systems that are similar to those used in pre-release testing,

including load testing.

Note that this information is also available in your online Help.

Processor

Minimum Recommended

Intel or AMD processor with a CPU speed of

at least 1Ghz

Hex-Core CPU (or equivalent) running at

2.4Ghz

Comments on Processors: For applications and tasks which are processor-intensive e.g. NPV

Scheduler, Conditional Simulation, Geostatistics, Mineable Shape Optimization), the faster the

CPU the better. Be aware that most Datamine processes are not multi-threading and will only

make use of a single CPU, however, additional system load with other applications running will

not impact Studio’s performance as obviously with multiple processors, as the external

processes may use other processors as a result of OS or application-level load balancing.

Memory

Minimum Recommended

1GB RAM 8GB RAM (or as much as your motherboard

will permit)

Comments on Memory: 8GB or higher is preferable. As would be expected, the amount of

memory installed on a particular machine can make a big difference to system performance

although, 32-bit versions of Studio products can only access up to 2GB of memory under

default conditions, even if more has been installed. 32-bit Studio is, however, a “Large Address

Aware” system, meaning that under a 64-bit operating environment, up to 4GB can be

accessed. In addition, It is possible to extend the amount of memory available to a 32-bit

operating system by the use of the operating system’s “/3Gb” switch. Consult the following

section for more information on setting up a large address aware 32-bit system. 64-bit Studio

systems will be able to utilize more available RAM.

Hard Disk / Storage

Minimum Recommended

10 GB Free Space As much as possible – 1TB or higher

Comments on Hard Disks: It is preferable to have files located on a local disk for rapid

access, although network access is only restricted by your current LAN or WAN structure and

administration. Note that swap space utilizes hard disk space, and as such, it is important to

11

run regular system housekeeping on your disk(s) to ensure as much free space as possible is

available. Note that a minimum of 500MB must be available for Datamine product installations.

Operating System

Minimum Recommended

Windows 7 Home Basic 32-bit Windows 8.1 Professional 64-bit

Swap Space

Minimum Recommended

1GB 4GB, but should match the amount of RAM

available

Monitor(s)

Minimum Recommended

1024 x 768 pixels, high color, VGA input Dual Monitor Setup: Twin 1920 x 1080 HDMI

input

Comments on Monitors: The choice of monitor(s) that you make should be defined by your

own requirements. Larger, higher resolution monitors (providing the graphics card that is

installed supports such settings) will always give superior results to lower resolution options,

but the best choice should be based on the type of work being undertaken.

Graphics Cards

Minimum Recommended

256 Mb dedicated video memory 1GB NVidia® Quadra FX

Comments on graphics cards:

· It is recommended that, when purchasing new hardware, integrated ('on board')

graphics cards are avoided due to potential system performance degradation.

· With all high performance graphics cards, it is very important to make sure that you

obtain and use the latest OpenGL drivers, at least OpenGL2. For advice, contact

your local Datamine support office.

· NVidia Quadra FX cards are recommended for Datamine environments for enhanced

visual performance. These cards are routinely used during pre-release testing.

· 1GB+ cards are preferred but, as with monitors (see above), the choice will be based

on the type of work you need to perform. Your application draws resources from

both system and video memory. If you are more inclined to produce complex

graphics, particularly if using textured VR-style functions, more graphic memory will

show more significant gains than for users working with lower-resolution data sets,

spreadsheets etc.

12

· Settings for your particular card can also affect the running of Datamine applications

both positively and adversely; if unexpected (and unwanted) system performance

is encountered, it may be necessary to disable (or reduce) certain acceleration

options until the optimum performance is found. Screen resolution, for example, has

a significant impact on system performance, and can be adjusted downwards in

some cases whilst maintaining an acceptable visual feedback.

· Drivers for your card must be managed; it is not always the case that the latest

driver for your card will resolve issues; in fact, it may even introduce issues if new

card features are enabled that cannot be interpreted correctly by your Datamine

application (an example of this is the "Threaded Optimisation" feature introduced

with newer NVidia Cards - this must be disabled before using Datamine

applications). Video card firmware must also be maintained.

· With the sheer volume and variety of graphic cards on the market, your choice will

be governed by several factors. Although Datamine do not recommend a specific

manufacturer, internal QA testing is performed against a variety of different card

environments using primarily NVidia hardware, including NVidia Quadro cards for

high-end textured data process testing.