Stratigraphy_pinchout_data

 

Data Structure: Stratigraphy_pinchout_data

Description

Stratigraphy merge/pinchout data

Usage

Stratigraphy_pinchout_data     NUM=ival   where ival  is the data structure number

 

Description

Overview

It should be noted that Stratigraphy_pinchout_data follows different strategies / algorithms depending on whether it is used in a 2D or 3D model.

 

Pinchout in 2D

In some cases a given element group edge might become very thin due to pinchout. Therefore very small elements may be required in order to represent properly such pinchout of stratigraphy, thus increasing the computational cost. Furthermore numerical instabilities might arise due to mesh distortion if stratigraphy pinchout zones are deformed. Therefore a pinchout removal and geometry merge operation is an efficient tool that can help to mitigate such situations. The Stratigraphy_pinchout_data structure defines the data to control merge and pinchout checks caused by sediment geometry evolution.

 

Pinchout_001

 

Pinchout in 3D

Geometry operations in 3D are more complex and may lead to undesired intersections. Thus the pinchout algorithm in 3D works by preventing further thinning of those regions of a formation which satisfy the user input criteria. To that end the stratigraphy nodes in the problematic region are moved to increase the formation thickness to a target thickness thus preventing the pinchout.

 

Examples

demonstrating the usage of 2D pinchout include:

merge*.dat

 

 

Click to expand/collapseActive_flag    Pinchout active flag

 

Click to expand/collapseLower_horizon_name    Name of lower horizon

 

Click to expand/collapseUpper_horizon_name    Name of upper horizon

 

Click to expand/collapseLower_horizon_number    Lower horizon number

 

Click to expand/collapseUpper_horizon_number    Upper horizon number

 

Click to expand/collapseInitiation_time    Pinchout check initiation time

 

Click to expand/collapseUpdate_frequency_time    Time increment for pinchout checks

 

Click to expand/collapseUpdate_control_flag    Flag indicating that a pinchout check should be performed at the start of each control stage

 

Click to expand/collapseMinimum_thickness    Layer thickness below which merge is performed

 

Click to expand/collapseAbsolute_minimum_thickness    Layer thickness below which merge is performed irrespective of merge region length

 

Click to expand/collapseMesh_size    Mesh size for generation of new stratigraphy

 

Click to expand/collapseMinimum_merge_length    Length tolerance for pinchout evaluation

 

Click to expand/collapseAngle_tolerance    Angle tolerance for pinchout evaluation

 

Click to expand/collapseRestart_output_flag    Output a restart file before merge operation

 

Click to expand/collapseTarget_thickness    Target Layer thickness after merge is performed

 

Click to expand/collapseOutput_level    Flag for indicating amount of output to the log (.res) file

 

Click to expand/collapseSide_bound_corr_flag    Pinchout side boundary correction flag