The scope and severity of white‐nose syndrome on hibernating bats in North America
Bibliographic record
Abstract
Assessing the scope and severity of threats is necessary for evaluating impacts on populations to inform conservation planning. Quantitative threat assessment often requires monitoring programs that provide reliable data over relevant spatial and temporal scales, yet such programs can be difficult to justify until there is an apparent stressor. Leveraging efforts of wildlife management agencies to record winter counts of hibernating bats, we collated data for 5 species from over 200 sites across 27 U.S. states and 2 Canadian provinces from 1995 to 2018 to determine the impact of white-nose syndrome (WNS), a deadly disease of hibernating bats. We estimated declines of winter counts of bat colonies at sites where the invasive fungus that causes WNS (Pseudogymnoascus destructans) had been detected to assess the threat impact of WNS. Three species undergoing species status assessment by the U.S. Fish and Wildlife Service (Myotis septentrionalis, Myotis lucifugus, and Perimyotis subflavus) declined by more than 90%, which warrants classifying the severity of the WNS threat as extreme based on criteria used by NatureServe. The scope of the WNS threat as defined by NatureServe criteria was large (36% of Myotis lucifugus range) to pervasive (79% of Myotis septentrionalis range) for these species. Declines for 2 other species (Myotis sodalis and Eptesicus fuscus) were less severe but still qualified as moderate to serious based on NatureServe criteria. Data-sharing across jurisdictions provided a comprehensive evaluation of scope and severity of the threat of WNS and indicated regional differences that can inform response efforts at international, national, and state or provincial jurisdictions. We assessed the threat impact of an emerging infectious disease by uniting monitoring efforts across jurisdictional boundaries and demonstrated the importance of coordinated monitoring programs, such as the North American Bat Monitoring Program (NABat), for data-driven conservation assessments and planning.
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.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| 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".