MétaCan
Menu
Back to cohort
Record W1970791566 · doi:10.4236/jwarp.2010.211110

Measuring Ice Thicknesses along the Red River in Canada Using RADARSAT-2 Satellite Imagery

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

Bibliographic record

VenueJournal of Water Resource and Protection · 2010
Typearticle
Languageen
FieldEarth and Planetary Sciences
TopicArctic and Antarctic ice dynamics
Canadian institutionsGovernment of Manitoba
Fundersnot available
KeywordsBreakupGeologySnowBackscatter (email)Sea ice thicknessSatelliteArctic ice packDebrisEnvironmental scienceSea iceRemote sensingClimatologyGeomorphologyOceanography

Abstract

fetched live from OpenAlex

The spring flood of 2009 in the Red River Valley was exacerbated with severe ice breakup and ice jamming. To assist ice jam mitigation by cutting and breaking up the river ice cover before the flood season and to support the operation of the Red River Floodway, Manitoba Water Stewardship is striving to model the occurrence of ice breakup and simulate the behaviour of ice jamming along the river. An important parameter in ice breakup forecasting is the ice thickness. RADARSAT-2 standard satellite images were collected along the course of the Red River in Manitoba during the 2009-2010 winter to help determine ice thicknesses along the river. Standard images can have transmit-receive polarizations in the horizontal-horizontal (HH) or horizontal-vertical (HV) configurations. Ice thickness measurements were taken in the field during the same time frame when the satellite passed over the Red River Valley. Good correlations were obtained between the HH-backscatter readings and the surveyed ice thicknesses. HV-backscatter readings correlate better with fresh snow depth measurements. Additionally, using same sensor incident angle and flight geometry allows ice thickening rate behavior over the course of the winter to be determined.

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: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.164
Threshold uncertainty score0.294

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.001
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.018
GPT teacher head0.181
Teacher spread0.163 · 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