Sporadic diurnal fluctuations of cyanobacterial populations in oligotrophic temperate systems can prevent accurate characterization of change and risk in aquatic systems
Bibliographic record
Abstract
Cyanobacteria increasingly threaten recreational water use and drinking water resources globally. They require dynamic monitoring to account for variability in their distribution arising from diel cycles associated with oscillatory vertical migration. While this has been discussed in marine and eutrophic freshwater contexts, reports of diurnal vertical migration of cyanobacteria in oligotrophic freshwater lakes are scant. Typical monitoring protocols do not reflect these dynamics and frequently focus only on surface water sampling approaches, and either ignore sampling time or recommend large midday timeframes (e.g., 10AM-3PM), thereby preventing accurate characterization of cyanobacterial community dynamics. To evaluate the impact of diurnal migrations and water column stratification on cyanobacterial abundance and composition, communities were characterized in a shallow well-mixed lake interconnected to a thermally stratified lake in the Turkey Lakes Watershed (Ontario, Canada) using amplicon sequencing of the 16S rRNA gene across a multi-time point sampling series in 2018 and 2022. This work showed that cyanobacteria are present in oligotrophic lakes and their community structure varies (i) diurnally, (ii) across the depth of the water column, (iii) interannually within the same lake and (iv) between different lakes that are closely interconnected within the same watershed. It underscored the need for integrating multi-timepoint, multi-depth discrete sampling guidance into lake and reservoir monitoring programs to describe cyanobacteria community dynamics and signal change to inform risk management associated with the potential for cyanotoxin production. Ignoring variability in cyanobacterial community dynamics (such as that reported herein) and reducing sample numbers can lead to a false sense of security and missed opportunities to identify and mitigate changes in trophic status and associated risks such as toxin or taste and odor production, especially in sensitive, oligotrophic systems.
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.001 | 0.002 |
| 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.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| 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".