MétaCan
Menu
Back to cohort
Record W4250897501 · doi:10.1006/qres.2000.2157

Changes in the Bathymetry and Volume of Glacial Lake Agassiz Between 11,000 and 9300 <sup>14</sup>C yr B.P.

2000· article· en· W4250897501 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 Research · 2000
Typearticle
Languageen
FieldEarth and Planetary Sciences
TopicGeology and Paleoclimatology Research
Canadian institutionsUniversity of Manitoba
Fundersnot available
KeywordsGeologyBathymetryOceanographyGlacial periodShelf iceVolume (thermodynamics)Glacial lakeDrainage basinStructural basinHydrology (agriculture)GeomorphologyGeography

Abstract

fetched live from OpenAlex

The volume and surface area of glacial Lake Agassiz varied considerably during its 4000-year history. Computer models for seven stages of Lake Agassiz were used to quantify these variations over the lake's early history, between about 11,000 and 9300 14 C yr B.P. (ca. 13,000 to 10,300 cal yr B.P.). Just after formation of the Herman strandlines (ca. 11,000 14 C yr B.P.), the volume of Lake Agassiz appears to have decreased by &gt;85% as a consequence of the abrupt rerouting of overflow to its eastern outlet from its southward routing into the Mississippi River basin. This drainage released about 9500 km 3 of water into the North Atlantic Ocean via the Great Lakes and Gulf of St. Lawrence. Following closure of this eastern routing of overflow, the lake reached its maximum size at about 9400 14 C yr B.P. with an area of &gt;260,000 km 2 and a volume of &gt;22,700 km 3 . A second major reduction in volume occurred shortly after that, when its volume decreased &gt;10% following the opening of the Kaiashk outlet to the east into the Great Lakes, and 2500–7000 km 3 of water was released into the North Atlantic Ocean. These discharges may have affected ocean circulation and North Atlantic Deep Water production.

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.003
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.018
Threshold uncertainty score0.998

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.001
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0060.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.052
GPT teacher head0.309
Teacher spread0.257 · 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