Mitigation for the Construction and Operation of Libby Dam, 2001-2002 Annual Report.
Bibliographic record
Abstract
Libby Reservoir was created under an International Columbia River Treaty between the United States and Canada for cooperative water development of the Columbia River Basin (Columbia River Treaty 1964). Libby Reservoir inundated 109 stream miles of the mainstem Kootenai River in the United States and Canada, and 40 miles of tributary streams in the U.S. that provided habitat for spawning, juvenile rearing, and migratory passage (Figure 1). The authorized purpose of the dam is to provide power (91.5%), flood control (8.3%), and navigation and other benefits (0.2%; Storm et al. 1982). The Pacific Northwest Power Act of 1980 recognized possible conflicts stemming from hydroelectric projects in the northwest and directed Bonneville Power Administration to ''protect, mitigate, and enhance fish and wildlife to the extent affected by the development and operation of any hydroelectric project of the Columbia River and its tributaries...'' (4(h)(10)(A)). Under the Act, the Northwest Power Planning Council was created and recommendations for a comprehensive fish and wildlife program were solicited from the region's federal, state, and tribal fish and wildlife agencies. Among Montana's recommendations was the proposal that research be initiated to quantify acceptable seasonal minimum pool elevations to maintain or enhance the existing fisheries (Graham et al. 1982). Research to determine how operations of Libby Dam affect the reservoir and river fishery and to suggest ways to lessen these effects began in May, 1983. The framework for the Libby Reservoir Model (LRMOD) was completed in 1989. Development of Integrated Rule Curves (IRCs) for Libby Dam operation was completed in 1996 (Marotz et al. 1996). The Libby Reservoir Model and the IRCs continue to be refined (Marotz et al 1999). Initiation of mitigation projects such as lake rehabilitation and stream restoration began in 1996. The primary focus of the Libby Mitigation project now is to redevelop fisheries and fisheries habitat in basin streams and lakes.
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.002 | 0.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.002 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.028 | 0.007 |
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".