Green, yellow, red, or out of the blue? An assessment of Traffic Light Schemes to mitigate the impact of hydraulic fracturing-induced seismicity
Bibliographic record
Abstract
Abstract Mitigating hydraulic fracturing-induced seismicity (HF-IS) poses a challenge for shale gas companies and regulators alike. The use of Traffic Light Schemes (TLSs) is the most common way by which the hazards associated with HF-IS are mitigated. In this study, we discuss the implicit risk mitigation objectives of TLSs and explain the advantages of magnitude as the fundamental parameter to characterise induced seismic hazard. We go on to investigate some of the key assumptions on which TLSs are based, namely that magnitudes evolve relatively gradually from green to yellow to red thresholds (as opposed to larger events occurring “out-of-the-blue”), and that trailing event magnitudes do not increase substantially after injection stops. We compile HF-IS datasets from around the world, including the USA, Canada, the UK, and China, and track the temporal evolution of magnitudes in order to evaluate the extent to which magnitude jumps (i.e. sharp increases in magnitude from preceding events within a sequence) and trailing events occur. We find in the majority of cases magnitude jumps are less than 2 units. One quarter of cases experienced a post-injection magnitude increase, with the largest being 1.6. Trailing event increases generally occurred soon after injection, with most cases showing no increase in magnitude more than a few days after then end of injection. Hence, the effective operation of TLSs may require red-light thresholds to be set as much as two magnitude units below the threshold that the scheme is intended to avoid.
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.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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 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".