Methodology to generate orthogonal fractures from a discrete, complex, and irregular fracture zone network
Bibliographic record
Abstract
Dual continuum computational models that include both porous media and discrete fracture zones are valuable tools in assessing groundwater flow and pathways in fractured rock systems. Fracture generation models can produce realisations of discrete fracture networks that honour geological structures and fracture propagation behaviours. A methodology and algorithm are presented to incorporate a discrete, complex and irregular fracture zone network, represented as a triangulated two-dimensional mesh, within an orthogonal three-dimensional finite-element mesh. Orthogonal fracture faces, between adjacent finite-element blocks, were used to represent the irregular discrete-fracture zone network. A detailed coupled density-dependent groundwater flow analysis of a hypothetical 104 km2 portion of the Canadian Shield has been conducted using the discrete-fracture dual continuum finite-element model FRAC3DVS-OPG to investigate the importance of large-scale fracture zone networks on flow and transport. Surface water features and a Digital Elevation Model (DEM) were applied in a GIS framework to delineate the sub-watershed and to populate the finite-element mesh. The crystalline rock between the structural discontinuities was assigned properties characteristic of those reported for the Canadian Shield. Total Dissolved Solids (TDS) concentrations of 300 g/l are encountered at depth. A comparison is made to a model which represents the fracture zones as an Equivalent Porous Medium (EPM). Differences in freshwater heads, TDS, and pore water velocities in fracture zones are demonstrated. The discrete fracture zone approach yields simulated TDS values which are lower at depth than TDS values simulated using the EPM approach, primarily due to higher simulated pore water velocities within the discrete fracture zones. Solute transport is sensitive to fracture zone characterisation and dispersivity values required to achieve stable solutions. Steady-state density-independent simulations using both approaches yield similar freshwater heads.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.005 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".