MétaCan
Menu
Back to cohort
Record W2902490973 · doi:10.1139/cgj-2017-0630

Runout evaluation of Oso landslide with the material point method

2018· article· en· W2902490973 on OpenAlex

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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueCanadian Geotechnical Journal · 2018
Typearticle
Languageen
FieldEngineering
TopicFluid Dynamics Simulations and Interactions
Canadian institutionsnot available
FundersEngineering and Physical Sciences Research CouncilWashington State Department of TransportationU.S. Department of Transportation
KeywordsLandslideGeologyLandslide mitigationGeotechnical engineeringLandslide classificationMining engineering

Abstract

fetched live from OpenAlex

Long runout landslides can cause significant damage and represent one of the most important problems in geotechnical engineering. Understanding the mechanics of the landslide runout process is important for risk assessment and is challenging due to its complexities. This work examines the runout of the 22 March 2014 Oso, Washington, landslide. The Oso landslide is one of the worst landslide disasters in USA history with 43 fatalities. It occurred in multiple failure stages, involving several failure surfaces and significant soil softening, and travelled over 1 km across the valley. It initiated after a period of wet weather in an area prone to landslide movements. The triggering causes of the landslide movement are still under investigation. In this paper, the material point method is used to simulate the runout of the Oso landslide. This numerical tool is capable of modeling large deformation problems. It is used to investigate several hypothetical scenarios to identify key factors that contributed to the Oso landslide long runout distance.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.553
Threshold uncertainty score0.763

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.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.013
GPT teacher head0.264
Teacher spread0.251 · 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