Migratory Patterns of Wild Chinook Salmon Oncorhynchus tshawytscha Returning to a Large, Free-Flowing River Basin
Bibliographic record
Abstract
Upriver movements were determined for Chinook salmon Oncorhynchus tshawytscha returning to the Yukon River, a large, virtually pristine river basin. These returns have declined dramatically since the late 1990s, and information is needed to better manage the run and facilitate conservation efforts. A total of 2,860 fish were radio tagged during 2002-2004. Most (97.5%) of the fish tracked upriver to spawning areas displayed continual upriver movements and strong fidelity to the terminal tributaries entered. Movement rates were substantially slower for fish spawning in lower river tributaries (28-40 km d-1) compared to upper basin stocks (52-62 km d-1). Three distinct migratory patterns were observed, including a gradual decline, pronounced decline, and substantial increase in movement rate as the fish moved upriver. Stocks destined for the same region exhibited similar migratory patterns. Individual fish within a stock showed substantial variation, but tended to reflect the regional pattern. Differences between consistently faster and slower fish explained 74% of the within-stock variation, whereas relative shifts in sequential movement rates between "hares" (faster fish becoming slower) and "tortoises" (slow but steady fish) explained 22% of the variation. Pulses of fish moving upriver were not cohesive. Fish tagged over a 4-day period took 16 days to pass a site 872 km upriver. Movement rates were substantially faster and the percentage of atypical movements considerably less than reported in more southerly drainages, but may reflect the pristine conditions within the Yukon River, wild origins of the fish, and discrete run timing of the returns. Movement data can provide numerous insights into the status and management of salmon returns, particularly in large river drainages with widely scattered fisheries where management actions in the lower river potentially impact harvests and escapement farther upstream. However, the substantial variation exhibited among individual fish within a stock can complicate these efforts.
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.001 | 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.001 | 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".