Extreme rainfall drives early onset cyanobacterial bloom
Bibliographic record
Abstract
Abstract The increasing prevalence of cyanobacteria-dominated harmful algal blooms is strongly associated with nutrient loading and changing climatic patterns. Changes to precipitation frequency and intensity, as predicted by current climate models, are likely to affect bloom development and composition through changes in nutrient fluxes and water column mixing. However, few studies have directly documented the effects of extreme precipitation events on cyanobacterial composition, biomass, and toxin production. We tracked changes in a eutrophic reservoir following an extreme precipitation event, describing an atypically early toxin-producing cyanobacterial bloom, successional progression of the phytoplankton community, toxins, and geochemistry. An increase in bioavailable phosphorus by more than 27-fold in surface waters preceded notable increases in Aphanizomenon flos-aquae throughout the reservoir approximately 2 weeks post flood and ~5 weeks before blooms typically occur. Anabaenopeptin-A and three microcystin congeners (microcystin-LR, -YR, and -RR) were detected at varying levels across sites during the bloom period, which lasted between 3 and 5 weeks. Synthesis and applications: These findings suggest extreme rainfall can trigger early cyanobacterial bloom initiation, effectively elongating the bloom season period of potential toxicity. However, effects will vary depending on factors including the timing of rainfall and reservoir physical structure. In contrast to the effects of early season extreme rainfall, a mid-summer runoff event appeared to help mitigate the bloom in some areas of the reservoir by increasing flushing.
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.000 | 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".