MétaCan
Menu
Back to cohort
Record W7048069994

Interaction between opposite river bank dynamics

2017· other· en· W7048069994 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
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

VenueResearch Repository (Delft University of Technology) · 2017
Typeother
Languageen
FieldEngineering
TopicPulsed Power Technology Applications
Canadian institutionsnot available
Fundersnot available
KeywordsBank erosionAccretion (finance)ErosionBankBank failureLagDuration (music)
DOInot available

Abstract

fetched live from OpenAlex

<p style="margin: 0cm 0cm 10pt;">Although many studies regarding bank erosion and accretion can be found in the literature, it is not common to find works studying the interaction between opposite banks. Some existing morphodynamic models describe bank erosion as an event that depends on near-bank flow and bed topography, as well as on eroding bank properties. Most developed models do not include opposite bank accretion, with the exception of, e.g. Asahi et al. (2013) and Eke et al. (2014). . These models can represent opposite bank dynamics. Analyses of bank-to-bank interactions, showing for instance where the effects of depositing bank push are felt (where exactly opposite bank erosion occurs), are lacking. Observations by Nanson and Hickin (1983) on the Beatton River, in Canada, suggest that bank accretion is important for opposite bank erosion to occur, in addition to the magnitude and duration of hydrological events. The present study focuses on the interaction between opposite river banks. The aim is to describe how bank accretion influences opposite bank erosion and whether there is a spatial lag in this interaction. This paper presents only some preliminary results. </p>

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 categoriesMeta-epidemiology (narrow), Research integrity
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Other · Consensus signal: Other
Teacher disagreement score0.362
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0030.001
Science and technology studies0.0000.002
Scholarly communication0.0000.000
Open science0.0020.001
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0000.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.019
GPT teacher head0.278
Teacher spread0.259 · 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