Behaviors of the Yukon River Sediment Plume in the Bering Sea: Relations to Glacier-Melt Discharge and Sediment Load
Bibliographic record
Abstract
Sediment plumes, released to the Bering Sea from the delta front of the Yukon River, Alaska, are initiated mainly by glacier-melt sediment runoffs in the glacierized regions of the Yukon River drainage basin. The surface sediment plumes are extended around the fan-shaped Yukon River delta, which is followed by the northwestward dispersion. During continuous measurements of the Yukon River discharge and sediment load, behaviors of the sediment plumes were explored by shipboard and coastal observations in the Bering Sea. At the high river sediment load of ca. 2500 kg/s, the plume partially plunged into the sea bottom layer. The plunging probably originated in the nepheloid-layer formation from the flocculation of river-suspended sediment, of which more than 90% wt. is silt and clay (grain size d < 63 μm). In order to numerically obtain the area of the surface sediment plumes, a satellite image analysis was performed by using three near-infrared bands in MODIS/Aqua or MODIS/Terra. The plume area was significantly correlated (R2 = 0.735, p < 0.01) to the sediment load averaged for the two days with time lags of 20 days and 21 days to the date of a certain satellite image. Hence, the dispersion of plume-suspended sediment appears to be controlled by the sediment runoff events in the Yukon River rather than the northward “Alaskan Coastal Water”.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".