Geoscience ANALYST Pro 4.8: Connecting Drillhole Evidence to Interpretation

A drill target is only as defensible as the connection between the drillholes, physical-property assumptions, and geophysical response used to justify it. Geoscience ANALYST Pro is worth considering when that connection must be examined across several data types before committing to another interpretation or drilling decision.

This research-based technical assessment draws on official material checked on 8 November 2026; the software has not been independently installed or tested.

Start with the right product and entitlement

Geoscience ANALYST Pro is developed and supplied by Mira Geoscience. The company describes itself as privately owned and Canadian; the public sources reviewed do not identify its current shareholders. GOCAD Mining Suite is a separate product in Mira’s portfolio, rather than the developer of ANALYST. No verified acquisition or renaming of ANALYST was established in this research.

The clearest release evidence is Mira’s 4.8 announcement dated 6 July 2026. It identifies a specific Pro change: composite interval logs can be confined to one or more reference data classes. That matters when compositing must respect a geological classification instead of treating all adjacent intervals alike. The announcement establishes the 4.8 release family, not an independently verified latest maintenance build. Obtain the exact supported installer and patch history from Mira before standardizing a project.

Edition selection changes the technical scope. The official product comparison assigns object editing, drillhole tools, minimum-curvature gridding, and unconstrained gravity, total-field magnetic, and gravity-gradient modelling and inversion to Pro. Geologically constrained inversion, the detailed SimPEG integrations, and the API for cloud or on-premise HPC inversions belong to Pro Geophysics. Explicit geological section interpretation and several geological modelling tools belong to other product options. Treat these as different entitlements, not interchangeable labels.

A useful workflow starts before the 3D view

A practical evaluation would bring together surveyed drillhole collars and trajectories, interval logs, topography, processed geophysical observations, and the surfaces or block models needed to frame the target. Mira’s format and object tables list drillholes, wireframe surfaces, 2D grids, multiple 3D grid types, and imports including GOCAD objects, Geosoft formats, OMF, and SEG-Y. Format recognition alone does not establish preservation of every attribute or coordinate convention.

The first engineering task is therefore reconciliation: check coordinate reference systems, units, object extents, missing-value conventions, and the meaning of categorical logs. Pro documents coordinate transformations, data transfer between objects, masking, desurveying, and composite logs. These tools can support that reconciliation, but they do not decide which source should control a conflicting geological interpretation. Preserve the original observations and record the choices made during conversion.

The resulting working model can then be interrogated through linked tables and visualizations, edited, and exported for a downstream calculation or review. The export matrix differentiates the free viewer’s GEOH5 output from Pro’s CSV tables, drillhole LAS 2.0 output, and object-specific exports. A buyer should test the exact object-property combination required for handover, rather than accept a generic promise of compatibility.

When a project also needs faulted structural surfaces or a more extensive subsurface modelling workflow, our SKUA GOCAD overview provides context for that modelling stage. It does not establish a licensed connector or lossless exchange with a particular ANALYST build.

Modelling capability is not geological certainty

Pro’s documented unconstrained potential-field inversion is useful to distinguish from the geologically constrained workflows assigned to Pro Geophysics in the edition matrix. The distinction affects the question being asked: does the project need an unconstrained physical-property distribution to investigate, or an inversion explicitly incorporating geological constraints? A Pro purchase should not be assumed to include the latter.

As an engineering interpretation, a model that reproduces observed potential-field data still needs geological assessment; the computed response alone cannot resolve all plausible subsurface arrangements. A project evaluation should examine how data uncertainty, mesh extent, property bounds, and alternative starting interpretations are represented in the selected method. The public feature matrix is evidence of availability, not a benchmark of accuracy or proof that a particular target is real.

Interchange and Python need a versioned contract

The connectivity table lists a Python API across all options, while live Python integration and Python UI creation tools start at Pro. It also lists Pro live links to ioGAS and Maxwell. Those statements establish supported integration routes; they do not specify every external application version, runtime dependency, or transferred object type.

Mira’s 2023 GEOH5 technical paper explains the HDF5-based data structure and the geoh5py interface. The geoh5py documentation separately describes manipulation and storage of points, curves, surfaces, and grids and licenses that library under LGPL terms. That open-source library license is not a commercial ANALYST Pro license. Pin and verify the application, library, and exchange-format versions for any production script; do not infer that an unversioned example defines a supported automation contract.

Deployment and support are part of the decision

Mira’s ANALYST-specific FAQ lists Windows 10 and 11 x64, recommends at least 8 GB RAM, specifies 4 GB application disk space with additional project-dependent storage, and requires an OpenGL 3.3-capable graphics adapter. It does not recommend integrated graphics. These are public baseline requirements, not a sizing result for a large octree or multi-dataset project. Confirm the exact build’s supported OS, GPU driver, practical memory requirement, and remote or virtual deployment policy.

The Pro offer describes an annual subscription with one key for a single installation, technical support, and updates. The activation FAQ distinguishes online activation from an offline procedure using a computer-bound key and says license transfers require prior written consent. Before field deployment, confirm renewal consequences, offline operation and reactivation procedures, transfer rights, and support response arrangements in the actual order. The material reviewed does not establish a general cloud desktop or concurrent-seat entitlement.

Choose against the workflow, then verify a representative handover

For a team comparing gravity or magnetic processing, mapping, and interpretation workflows, Oasis montaj is a relevant alternative over that shared scope. Seequent’s current product description organizes it around survey QC, processing, maps, profiles, and grids, with configurations, extensions, and separately licensed VOXI inversion. Our Oasis montaj technical assessment discusses those boundaries. Compare the required corrections, editable data structures, inversion configuration, script maintenance, and recipient deliverables using the same project data. Neither the broader feature count nor an attractive 3D display answers that comparison.

Geoscience ANALYST Pro is a plausible fit when an exploration team needs to edit and reconcile multidisciplinary objects, inspect drillhole evidence, and exchange those results with specialist tools. A visualization-only recipient may need only the free viewer; a constrained geophysical inversion team should evaluate Pro Geophysics and its solver entitlements. Prefer another workflow when its documented processing steps and deliverables match the project’s controlling requirements more closely.

Confidence is strongest for the documented edition boundaries, public baseline requirements, and 4.8 release announcement. The exact maintenance build, version-specific integration compatibility, workload sizing, and deployment rights still require confirmation. Ask Mira to demonstrate one representative import–edit–export cycle, identify the properties that survive it, and supply the supported version matrix and license terms. That evidence will be more useful than a generic feature demonstration.