Step01 Zmap Import

 

The data files for the Zmap import for the current example are in: Geol_002b\Case01\01_Zmap_import\Data.

 

Note that the Zmap data is similar to that of the Geol_002 case and hence will not be described here. Only description of the data relevant to the additional functionality demonstrated in the present example will be discussed. The additional data required during Zmap import in order to apply couple freedoms on boundary node columns is found Geol_002b_Case01b_Zmap_Imp.dat file and described below.

 

 

Data

 

The Util_eclipse_import data structure is used to define the importing and exporting format of the mesh/geometry as well as cell subdivision options, pinchout parameters for thin elements and any other conversion option.

 

Data File

 

* Util_eclipse_import

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

 Input_file_type         "Zmap"

 Output_coordinate_type  "None"

  (...)

 Grid_subdivision_i   1

 Grid_subdivision_j   1

 Grid_subdivision_list_k IDM=10   JDM=2

  /Layer Number/       1  2  3  4  5  6  7  8  9  10

  /No. Subdivisions/   2  2  2  2  2  2  3  2  2  1

 Active_cell_property    "Active_flag"

 Spatial_grid_name      Geol_002b_Case01_prop

 Spatial_grid_type      Element

 Output_property_names  IDM=3

   "I" "J" "K"  

 

•Note that the present case did not consider subdivisions of cells in the i and j directions and considered less subdivisions in k direction relative to case Geol_002.

 

•Spatial_grid_name, Spatial_grid_type and Output_property_names keywords are used to request the output of a .spat file containing a Spatial_grid with I, J and K values for each cell (which will be required to identify boundary nodes and generate data for application of the couple freedoms constrain).

 

•Note that any other property imported via an Util_zmap_import data structure may be output as a Spatial_grid by listing it within the Output_property_names keyword. The different properties will be output in separate .spat files which will be named according to the name defined in Spatial_grid_name with the property name appended (i.e. in this case the code will output a file named Geol_002b_Case01_prop_IJK.spat)

 

 

The Zmap data imported to define the geometry and properties for the model are imported via Util_zmap_import data structures and are located in a sub-folder named "Zmaps". The current example considers two Util_zmap_import data structures, one for importing the geometry Z coordinates for each horizon and one containing the values for the "Actnum" property which defines which cells are active and which not. Those data structures are identical to Geol_002 case.

 

 

 

 

Results

 

The results for the present workflow steps are provided in Geol_002b\Case01\01_Zmap_import\Results

 

After Zmap import two key files are ouput:

 

1.Geol_002b_Case01_abaq.inp file containing the mesh in abaqus format. This will be run by ParaGeo on the next workflow step in order to obtain the .geo file.

2.Geol_002b_Case01_prop_IJK.spat containing a Spatial_grid with the i, j, and k values for each element (see below).

 

Data File

 

* Spatial_grid                     NUM=1

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

 Name                     "grid_IJK"

 File_name                "Geol_002b_Case01_prop_IJK.spat"

 Type                     "Element"

 Element_variables  IDM=3

    "I"

    "J"

    "K"

 Cell_values  IDM=3  JDM=7661

   1.00000        1.00000        1.00000    

   2.00000        1.00000        1.00000

    (...)

   41.0000        15.0000        20.0000    

 Element_numbers  IDM=7661

    1   2   3  ...    14093    14094

 

•The Geol_002b_Case01_prop_IJK.spat file contains a Spatial_grid with the requested output properties which in this case are the i, j and k values for each element.

 

 

 

The considered mesh may be visualised by loading the file Geol_002b_Case01_Zmap_Imp_update_eclipse.xmf in ParaView.