In the present workflow step the .inp file containing the mesh will be run to obtain the ParaGeo geometry.
The data file for generation of the geometry is in: Geol_003\Case01\Step02_Hex_Geometry\Data. It consists on the Geol_003_Case01_Step02_geom.inp file which is an edited version of the Geol_003_Case01_Step01_abaq.inp file output during the Zmap import in the previous step. The edits are described and highlighted below .
Data File |
|
*PARAGEO CONVERSION, TYPE=GEOMETRY, PARAGEO FILE=Geol_003_Case01_Step02_geom_hex *CONVERSION OUTPUT, LEVEL=2, GEOMETRY=YES, MESH=YES *CONVERSION OPTIONS, LINE SPLIT=NO ** *NODE 1, 51000.0000 , 28000.0000 , 5995.14622 2, 52000.0000 , 28000.0000 , 6036.02102 (...) 462, 56000.0000 , 34000.0000 , 744.342644 (...) *spatial_grid, INPUT=Geol_003_Case01_Step01_Facies.spat, OUTPUT=Geol_003_Case01_Step01_Facies_ReNum.spat
|
The required edits to the .inp file in order to obtain a HEX meshed geometry that can be later converted to a TET meshed geometry are:
1.The conversion type must be set to TYPE=GEOMETRY to enable later HEX to TET conversion
2.The ouput file name defined in PARAGEO FILE has been edited for convenience to "Geol_003_Case01_Step02_geom_hex".
3.The line *CONVERSION OPTIONS, LINE SPLIT=NO must be added to the data file when generating ParaGeo geometry from HEX meshes with the TYPE=GEOMETRY in order to avid generation of individual lines for each individual HEX cell edge.
4.At the bottom of the .inp file the line with the *SPATIAL_GRID keyword needs to be removed (such line is only required for HEX workflow)
The rest of the data is not discussed here |
The Geol_003_Case01_Step_02_geom.inp is run in ParaGeo to perform the conversion and obtain the results.
Results
The results for the present workflow steps are provided in Geol_003\Case01\Step02_Hex_Geometry\Results
The key results comprise:
1.Geol_003_Case01_Step02_geom_hex.geo file containing the geometry and hex mesh in ParaGeo format 2.Geol_003_Case01_Step02_geom_hex.geometry containing the generated Group_data for the 10 formations and 26 Geometry_set data structures.
|