Maptek vulcan
If you select from the DH database you are offered the ability to use the data as is or generate a composite file – given the estimate is an ordinary kriged estimate, compositing the data to a regular sample support is recommended. You can model from a drillhole database, or from an Isis composite file. You have the option of selecting a categorical model (such as lithology) or a grade model – which is either categorical (as in indicators) or continuous. The first option is the Open Specifications page which allows you to select a parameter file – when selected it will populate all the fields with saved parameters, if you type in a new parameter name the options you enter will be saved in this parameter file.
#Maptek vulcan series
The editor fires up a standard Vulcan form with a series of options on the left. Yep, not many options but what does the Implicit Modelling Editor do? The menu shown below contains the various options available Now to the program under discussion, as mentioned Vulcan 9 has introduced a new module they call Implicit modelling and it comes at no cost for anyone owning the standard geology tools modules. Implicit models of a drillhole dataset using Eureka. All in all from the demonstration it appears to be quite a challenger even in its early form – but only available to those select few that own and use Eureka.įigure 1. The output appears reasonable as indicated in Figure 1. As well as drillhole data any data that contains points (points, lines and triangulations) can be modelled. Searches can be controlled using multiple ellipses, polylines (with normals to control inside/outside) and input points can be edited to add new information to control the interpolated boundary. It is able to create surfaces and generate non-intersecting surfaces for seam / vein modelling etc) and solids of grade and object data. Whilst I have not used Eureka Beta myself I got to see a demonstration of the Beta at the Vulcan Users Conference last year (thank you Maptek for the invitation) and it certainly looks more than capable.
#Maptek vulcan 64 Bit
I believe this decision has roots in the 32 bit / 64 bit issue (Maptek can correct me if I am wrong), Eureka is a born and bred 64 bit program whereas Vulcan is historically a 32 bit program and 32 bit systems are unable to handle the memory requirements. They have chosen to use this in their Eureka software, a tool designed for regional exploration and data visualisation rather than their more widely known (and used) Vulcan mine planning software. In a strange twist Maptek have solved the memory management issue that plagues RBF functions and actually have an RBF implicit modelling algorithm.
The Vulcan IM module is not a true RBF implicit modelling method, rather it utilises Ordinary kriging to build a blockmodel and emulate implicit modelling, much like GeoVia’s dynamic shells (which utilises Inverse Distance estimation) and CAE Studios Implicit Shells (Inverse distance or Ordinary Kriging).
In case you have happened to miss the saturation marketing, Maptek has recently released its assault on Leapfrog in the form of its Implicit Modelling Module released with Vulcan 9.