MétaCan
Menu
Back to cohort
Record W4327729942 · doi:10.3390/quat6010022

Enigmatic Surface Ruptures at Cape Rytyi and Surroundings, Baikal Rift, Siberia: Seismic Hazard Implication

2023· article· en· W4327729942 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.

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

Bibliographic record

VenueQuaternary · 2023
Typearticle
Languageen
FieldEnvironmental Science
TopicLandslides and related hazards
Canadian institutionsCarleton University
Fundersnot available
KeywordsGeologyPaleoseismologySeismologyFault (geology)ShoreRidgeLandslideCapeRiftActive faultMagnitude (astronomy)GeomorphologyTectonicsPaleontologyArchaeologyOceanographyGeography

Abstract

fetched live from OpenAlex

The geomorphic expression of active faulting and distinction of paleoseismic events in areas that are rapidly obscured by erosion/sedimentation still remains a considerable scientific problem. The present article discusses the revealing of surface faulting ruptures and their parameters to identify capable faults without trenching and to estimate the magnitude of earthquakes. The case study was at Cape Rytyi, located in Baikal-Lena Nature Reserve on the northwestern shore of Lake Baikal. Based on unmanned aerial photography, GPR, and structural observations, we mapped and investigated the relation between geomorphological forms and ruptures. The obtained results show that past landslides and paleoruptures at Cape Rytyi and its surroundings are associated with at least two earthquakes. The Mw of the earlier event was 7.3 (Ms = 7.4); the Mw of the later one was 7.1 (Ms = 7.3). The paleoruptures in the distal part of the delta of the Rita River and on the southeastern slope of the Baikal Ridge were included in the seismogenic rupture zone, which traces some 37 km along the Kocherikovsky fault. The approximate intervals in which earthquakes occurred are 12–5 ka and 4–0.3 ka, respectively. The applied analysis methods can be useful for paleoseismology and assessing seismic hazards in similar regions elsewhere.

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.000
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.139
Threshold uncertainty score0.998

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.002

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.009
GPT teacher head0.232
Teacher spread0.223 · 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