A Review of Current Knowledge with Geomechanical Fault Reactivation Modelling: The Importance of CO2 Mechano-Chemical Effects for CO2 Sequestration
Bibliographic record
Abstract
Abstract A fault stability study constitutes a fundamental element of any subsurface injection project that involves faults within a storage complex, yet the transient geomechanical effects introduced due to CO2-rock chemical interactions are rarely considered. This paper presents a review of the published work investigating the potential alteration of rock properties due to short to long term CO2-host rock chemical interactions during commercial scale carbon capture and storage (CCS) operations. Furthermore, the authors of this paper are attempting to highlight the potential significance of these mechanical-chemical effect on the fault reactivation potential for a commercial scale carbon capture and storage (CCS) operation. The reactive nature between CO2 dissolved in formation water and the storage reservoir can significantly alter the hydraulic and mechanical properties of the host rock, which could in turn affect the storage potential of the target reservoir. Alteration of the host rock mineralogy due to chemical interactions with CO2 have been well studied (Farquhar et al. 2015), but little is available in the published literature on the resulting changes in rock elastic properties (i.e. Young's modulus and Poisson's ratio) due to these reactions. Some recent experimental studies have suggested significant changes in rock properties occur. When we incorporated the geomechanical effects, induced by the rock elastic property changes documented in these published cases, into both 1D analytical and 3D numerical models based fault stability analyses for a Surat Basin reservoir, we observed significant modification of the reservoir storage capacity prior to reaching fault reactivation criteria. Based on our review of the published literature and our fault stability analyses, we conclude that the chemical effects of CO2 interaction with host rock needs to be experimentally tested to confirm if these effects are significant. If yes, then these effects should constitute an integral part of the geomechanical study for any large scale CO2 injection exercise if there is a critically stressed fault as part of the storage complex.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
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 teacher head, 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".