Geol_002 Geological Modelling with Zmap Import

 

Note: The present tutorial example is only recommended to advanced users already familiar with ParaGeo.

 

In the present tutorial example a geological basin modelling workflow incorporating Zmap file import in ParaGeo will be demonstrated. Four case models are presented in this tutorial example (see figure below):

1Case01 - 3D column model with 5x5 grid mesh (red cell).

2Case02 - Pseudo-3D slice model (green cells).

3Case03a - Small 3D irregular grid model with 'ragged' boundaries (pink cells).

4Case03b - Large 3D irregular grid model with 'ragged' boundaries (white cells).

 

Geol_002_00_02

Full Basin Model showing Four Extracted Sub-model Cases

 

 

Features of the example are:

1Utility to import Zmap files and output to ParaView plot file and Abaqus file incorporating various functionalities, e.g. sub-grid extraction, grid subdivisions, actnum functionality, horizontal horizon extraction for column, etc.

2Restoration modelling (geomechanical only).

3THM sedimentation modelling.

4Kerogen oil and gas generative layer for hydrocarbon generation.

5Basal thermal flux.

6Hexahedral mesh model.

7Moving water table with time.

8Directional decompaction.

9Multi-material layer model with permeable (sandstone), impermeable (shale) and facies mixture layers.

10Boundary node extraction functionality for irregular grid hex models with 'ragged' boundaries.

 

 

Click to expand/collapseProblem Description

 

 

Click to expand/collapseSummary of Workflow

 

 

Simulation Cases

 

The simulation files for the four case models are found in: ParaGeo_Tutorial_Examples\Geol_002.

 

A full description of the data required for the column model is provided in Case01 Column Model description.  Subsequent cases will only contain description of additional data or data different to the preceding case model in increasing complexity.  To this end, the user is recommended to work through each of the case examples relevant to the required target model.

 

The following table shows the run statistics for the four simulation cases on a single processor :

Geol_002_00_05

Run statistics for simulation cases on single 3.6 GHz AMD processor

 

Notes on parallel simulation:

Solver

Advantage

Disadvantage

Mumps (Default)

More likely to give answers if problem is poorly conditioned

Takes much more memory for large problems

Likely to fail in parallel for large problems (Windows only)

Petsc

 

* Solver_control NUM=1

! --------------------------------------

Solver_type  "Petsc"

Generally quicker if solution can converge

Uses less memory for large problems

May not converge for poorly conditioned problems