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. 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.
0 kommentar(er)
