Looking for Guidance on Leapfrog Geo Optimization for Big Geological Models

KellyGloria

Hello Everyone,

I’ve been working on a project that involves building a large-scale geological model using Leapfrog Geo, and I’m running into some challenges. I’m reaching out to tap into the collective expertise here and hopefully gain some insights or tips.

My model incorporates multiple data sources, including extensive drillhole datasets, geophysical surveys, and some historical geological mapping. As the model grows in complexity, I’ve noticed the following issues:

• Performance Slows Down: Operations like updating the geological surfaces or modifying parameters take significantly longer.
  
• Visualization Lag: Rendering the model in 3D becomes slower, making it harder to navigate and analyze.
  
• Data Management: Keeping all the input data well-organized and linked correctly is becoming cumbersome.

Here are a few specific questions I’m hoping the community can help me with:

• Are there any best practices for managing performance in large models? For example, would splitting the project into smaller segments and combining them later help?
  
• What are the most effective techniques for managing and cleaning large datasets before importing them into Leapfrog?
  
• Are there specific hardware configurations or system settings that can help improve the software's responsiveness for large-scale modeling?

I’ve already tried optimizing my drillhole intervals and reducing the resolution of some geophysical grids, which helped slightly, but I’d love to hear what others have done in similar situations.

If anyone has faced similar challenges or has tips to share, I’d greatly appreciate your insights! I’m happy to provide more details about my workflow or project specifics if that helps.

Thank you in advance for your time and expertise!

kelvinsalesforce

AlissaAlvim2

Hi, Kelly!

About the computer setting, I would suggest at least 32 GB RAM memory and 100 GB of free space on your computer to run leapfrog process. Also, a good video card.

Inside the software, you can try:

• increase the surfaces resolution;
• check if you're not using desnecessary polylines and points.

JamesLally

One setting that has caught me out in the past is the 'adaptive' triangle sizing when creating meshes. This can really slow down processing. When visualising, rendering points or drillholes as 3d objects is slower than simple lines or points. Images draped on meshes such as topography also slow down rendering. When making a lot of edits freeze the parts of the model you aren't working on, then batch update them later.

With drillholes I find it's best to do all the validation checks you can before building models, remembering that every time you have to change something all the linked objects have to update.

good luck!

NiklasSääv

Splitting a big model into smaller parts can sometimes be a good approach, if so try to split it using natural boundaries (fault planes / major formations or similar).

This way it's a little easier to combine them later on (if that is even required) as well as working with the "seams" between models becomes easier.