MétaCan
Menu
Back to cohort
Record W3117371050 · doi:10.1089/ham.2019.0069

Was an Avalanche Swarm Responsible for the Devastation at Mount Everest Base Camp During the April 2015 Nepal Earthquake?

2020· article· en· W3117371050 on OpenAlex
G. W. K. Moore, Paolo Cristofanelli, Paolo Bonasoni, G Verza, John L. Semple

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueHigh Altitude Medicine & Biology · 2020
Typearticle
Languageen
FieldEarth and Planetary Sciences
TopicEarthquake Detection and Analysis
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsMountGeographyHistoryEngineering

Abstract

fetched live from OpenAlex

Moore, G.W.K., Paolo Cristofanelli, Paolo Bonasoni, Gian Pietro Verza, and J.L. Semple. Was an avalanche swarm responsible for the devastation at Mount Everest Base Camp during the April 2015 Nepal earthquake? High Alt Med Biol . 21:352–359, 2020. Introduction: An avalanche triggered by an earthquake on April 25, 2015, struck the Mount Everest Base Camp (EBC) resulting in 15 deaths and over 70 injuries. Despite the common occurrence of avalanches in this region, little is known about their intensity and the stability of the glaciers that ring the Mount Everest massif. Here we present unique observations from a nearby automatic weather station (AWS) in the minutes just after the earthquake. Methods: Several (AWS) were deployed along the Khumbu Valley in Nepal. The site at Kala Patthar (elevation 5,613 m asl) 3.5 km from EBC and 4 km from the col along the ridge between Pumori and Lingtren was active from 2010 to 2015 and recorded temperature, relative humidity, pressure, solar radiation, and wind speed and direction. Results: The sequence of wind direction anomalies indicated that multiple air blasts passed the AWS, each associated with a distinct avalanche source, suggesting that earthquake likely caused a number of distinct avalanches from different source regions along this ridge. Discussion: Results suggest that a swarm of avalanches collectively lead to the death and destruction at EBC, suggesting the need for improvement in our understanding of avalanches in the region as well as in our ability to model and forecast such events.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.126
Threshold uncertainty score0.998

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0030.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.

Opus teacher head0.030
GPT teacher head0.267
Teacher spread0.237 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it