Introduction
The aim of this example is to demonstrate procedures of fracture data import and export. In the current example, we import fracture data that has been generated using FracMan software into ParaGeo environment. We then customise the fracture distribution through scaling and offsetting of fracture set within specified region of interest. Note that fractures that intersect with the defined fracture region boundaries are excluded, as illustrated below.
This modified fracture set is then exported in FracMan data file format so that the file can be re-used in subsequent simulation tests without the need to re-specify the fracture distribution.
|
The data file for the example is in: fract_001\Data\fract_001.dat. The basic data includes: 1Include imports FracMan-formatted fracture data. 2Contact_property defines the mechanical and flow properties on the contact surfaces that are associated with the imported fracture data. 3Fracture_set assigns the fracture data to the contact property and volume geometry, customises the fracture distribution through scaling and offsetting of fracture set, defines the region size that encloses fracture distribution of interest and sets the flag to output modified fracture data file that can be re-used in subsequent simulation tests.
Note that only key data structures are described below. |
Include imports FracMan-formatted fracture data.
|
Contact_property defines the mechanical and flow properties on the contact surfaces that are associated with the imported fracture data.
|
Fracture_set assigns the fracture data to the contact property and volume geometry, customises the fracture distribution through scaling and offsetting of fracture set, defines the region size that encloses fracture distribution of interest and sets the flag to output modified fracture data file that can be re-used in subsequent simulation tests.
|
Nodal_data assigns coordinate points for each node defining the simulation domain.
|
The result files for this example is available in directory: fract_001\Results. The fracture data is imported in such a way that any fractures that cross the defined fracture region boundaries (not simulation domain boundaries) are excluded. The final form of the model is also illustrated below.
|