Best Of

Hi Kathryn,

Thank you for your detailed and insightful reply — it’s great to see how Seequent and Deswik are strengthening integration through Evo.

It’s very encouraging to know that Evo will enable this type of workflow natively in the near future. We’ve already started exploring the new mesh attribution features in Leapfrog 2025.1, especially for extruded and grouped meshes, and they’ve helped a lot in maintaining consistent attributes across different domains.

We’ll be glad to get in touch with the Seequent team in Brazil to learn more about Evo and upcoming integration capabilities with Deswik.

Thank you again for your feedback and for sharing the resources!

Best regards,
Valter Oliveira
Geologist — Vale Base Metals, Brazil

Seequent was excited earlier this month to announce our new technology partnership with Deswik. The aim of the partnership is to build smoother transfer of data between our products. TO demonstrate the partnership we made a video to showcase integration via Evo using our open python data converter for Deswik .duf. However, while it uses Python, the video aims to show the potential of the partnership and build more seamless integration in the future. You can watch the video here:

https://www.seequent.com/introducing-the-new-integration-between-seequent-evo-and-deswik/

The workflow you have described above would be enabled via Evo. I would recommended speaking to the local sales team in Brazil to learn more about Evo. Evo will be the data platform that is used to power cloud compute capabilities and integration across a number of different workflows and products (both Seequent and non Seequent).

For the moment, in recent versions of Leapfrog, we have been adding better to support for attribution of data in Leapfrog. This was first added for polylines and then meshes in 2025.1. However, there are some limitations. The For polylines, you can convert the polyline to a mesh, using the extruded mesh functionality. This will retain the attribution within leapfrog from the polyline. This is a great workflow for blast domains. https://help.seequent.com/Geo/2025.2/en-GB/Content/meshes/extruded-mesh.htm?Highlight=extruded%20mesh

For meshes, you need to assign the attributes after input, using the attribution table - https://help.seequent.com/Geo/2025.2/en-GB/Content/meshes/meshes.htm?Highlight=attributed%20mesh#mesh-attributes

The best way to evaluate meshes onto a block model is via the Grouped Mesh. Fro non attributed meshes, you can add each mesh into a Grouped Mesh, and then assign the attribute manually to each mesh. When this mesh is evaluated onto the block model, it will apply the attribute. See more details here: https://help.seequent.com/Geo/2025.2/en-GB/Content/combined-models/grouped-mesh.htm?Highlight=group%20mesh

When you're working on a geologic model and need to fine-tune a mesh shape: if you reserve structural discs for actual field measurements and use a polyline point with a disc for controlling a surface contour, it will help you keep your measurements separate from your modeled control points. The effect on modeling is the same, but with a much more robust data auditing ability. Get Modeling!

This is due to incompatibility with the graphics card drivers. It is usually the NVIDIA GeForce drivers. Stay away from the game ready drivers as they tend to be a bit more focused on some of the cutting edge gaming features.
If it happens again, then go to the very bottom right of your screen in Leapfrog (under the compass ball) and click where it says Full Acceleration. In the pop-up window select "Partial Acceleration".

This is only a temporary fix though, and as Findlay says, if you upgrade to the latest version of Leapfrog, then the problem goes away for good.

Thought I'd share a quick trick that helped visualize the risk of historic underground diamond drill holes that weren't grouted to standard. A csv file was created with the hole ID, from & to, and fill percentage (calculated by total bags of grout/(NQ hole diameter x length of hole x bag fill factor) as an interval table applied to the diamond drilling database. When plotted in 3D, it became a very easy and visual way to identify holes or areas that were not filled to standard, including where they were collared and what drifts they might pass through. Then a custom color scheme was applied to make the traces easy to understand and found this was very helpful when planning stopes and identifying hazards. This way holes that were not grouted to standard could be tracked down and plugged to eliminate the hazards of an open hole. (all sub-standard holes in this image were properly managed for safety hazards). This was easy to update and keep current, and easy to share in presentations and meetings. Hope this helps!

There is definitely some good materials in the help, but my biggest piece of advice is not to try and build the refined model from the same selection column as the main model, it will be difficult, and most likely end badly. Instead what I would do is regroup your codes into a new grouped column (and remember you can drop out some of the stuff already modelled, like faults or overburden, or any units you are not refining), and then make a new selection column from that, and use that as the input to the refined model. I usually label the selection columns going into the models something like Lith_Select_Level_1 for my main model, and lith_select_Level_2 for the refined model. From there, it's basically the same process as building a regular geology model.