MétaCan
Menu
Back to cohort
Record W2121492257 · doi:10.1098/rspa.2013.0689

Understanding the chain fountain

2014· article· en· W2121492257 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

VenueProceedings of the Royal Society A Mathematical Physical and Engineering Sciences · 2014
Typearticle
Languageen
FieldPhysics and Astronomy
TopicExperimental and Theoretical Physics Studies
Canadian institutionsTrinity College
FundersEngineering and Physical Sciences Research Council
KeywordsBeakerFountainChain (unit)DragEnhanced Data Rates for GSM EvolutionSquare (algebra)TOPSRest (music)

Abstract

fetched live from OpenAlex

Abstract If a chain is initially at rest in a beaker at a height h1 above the ground, and the end of the chain is pulled over the rim of the beaker and down towards the ground and then released, the chain will spontaneously ‘flow’ out of the beaker under gravity. Furthermore, the beads do not simply drag over the edge of the beaker but form a fountain reaching a height h2 above it. We show that the formation of a fountain requires that the beads come into motion not only by being pulled upwards by the part of the chain immediately above the pile, but also by being pushed upwards by an anomalous reaction force from the pile of stationary chain. We propose possible origins for this force, argue that its magnitude will be proportional to the square of the chain velocity and predict and verify experimentally that h2∝h1.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.175
Threshold uncertainty score0.292

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.001
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
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.016
GPT teacher head0.219
Teacher spread0.203 · 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