Threshold Definition for Monitoring Gapa Landslide under Large Variations in Reservoir Level Using GNSS
Bibliographic record
Abstract
The triggering threshold is one of the most important parameters for landslide early warning systems (EWSs) at the slope scale. In the present work, a velocity threshold is recommended for an early warning system of the Gapa landslide in Southwest China, which was reactivated by the impoundment of a large reservoir behind Jinping’s first dam. Based on GNSS monitoring data over the last five years, the velocity threshold is defined by a novel method, which is implemented by the forward and reverse double moving average of time series. As the landslide deformation is strongly related to the fluctuations in reservoir water levels, a crucial water level is also defined to reduce false warnings from the velocity threshold alone. In recognition of the importance of geological evolution, the evolution process of the Gapa landslide from topping to sliding is described in this study to help to understand its behavior and predict its potential trends. Moreover, based on the improved Saito’s three-stage deformation model, the warning level is set as “attention level”, because the current deformation stage of the landslide is considered to be between the initial and constant stages. At present, the early warning system mainly consists of six surface displacement monitoring sites and one water level observation site. If the daily recorded velocity in each monitoring site exceeds 4 mm/d and, meanwhile, the water level is below 1820 m above sea level (asl), a warning of likely landslide deformation accelerations will be released by relevant monitoring sites. The thresholds are always discretely exceeded on about 3% of annual monitoring days, and they are most frequently exceeded in June (especially in mid-June). The thresholds provide an efficient and effective way for judging accelerations of this landslide and are verified by the current application. The work presented provides critical insights into the development of early warning systems for reservoir-induced large-scale landslides.
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.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.001 |
| 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 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".