Movement of Lake-Origin Burbot Reared in a Hatchery Environment and Released into a Large River Drainage
Bibliographic record
Abstract
Abstract Burbot Lota lota in Kootenay Lake and the Kootenay River of British Columbia, Idaho, and Montana (U.S. spelling: “Kootenai River”) are at risk of demographic extinction. We conducted a pilot study to evaluate poststocking dispersal and movement of hatchery-reared, lake-strain burbot (Moyie Lake, British Columbia) in a riverine environment to determine the potential utility of this hatchery strain for future burbot rehabilitation efforts in this system. We implanted ultrasonic tags into 30 hatchery-reared burbot (ages 2 and 3) and released them into the Goat River, a tributary to the Kootenay River, in October 2009. Dispersal over a distance of 2 km from the Goat River release site to the Kootenay River occurred within 1–9 d after release (mean = 3.1 d; n = 28 active tags). Thereafter, 14 burbot remained in the Kootenay River for the rest of the 144-d study period; nine of these fish were observed moving upstream from the Goat River confluence, and five were observed both upstream and downstream from the confluence. The other 14 burbot were observed in Kootenay Lake; of these fish, eight were detected in the lake for the duration of the study, and six were observed to move regularly between the lake and the river. Dispersal distances (distance between the upstream-most and downstream-most detections per individual) within the Kootenay River ranged from 10 to 138 km (mean = 80 km), and tagged fish were detected over a 236-km reach (from 135 km downstream to 101 km upstream of the Goat River confluence). We also observed burbot in the vicinity of known spawning locations during the February spawning season. The observed dispersal suggests that a limited number of stocking locations may be sufficient to allow burbot to access available habitats within a few months postrelease. Our observations therefore suggest that lake-origin, hatchery-reared burbot may be suitable for stocking in a riverine environment. Received June 11, 2010; accepted December 4, 2010
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.001 | 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".