Managing cyanobacterial blooms in recreational waters: decision support tools for public health responses
Bibliographic record
Abstract
Freshwater blooms of cyanobacteria present a challenge to those tasked with managing beaches during bathing season, both to ensure the protection of public health, and to avoid lengthy beach closures. The combined effects of climate change and environmental pollution could cause blooms to become more frequent, intense, and persistent in the future in some locations, necessitating regularly review and update of response protocols. Decision support tools are used to help manage bloom events and inform responses. These can advise on the triggers for inspection, testing, posting of advisories, closing of beaches, and when to rescind advisories and reopen beaches. The aim of this paper was to present an overview of approaches and decision support tools used to inform public health responses to cyanobacterial blooms. During bathing season in Canada, most bloom monitoring is reactive, with a limited coverage of proactive monitoring, except at priority beaches. Responses to blooms vary widely, but many are informed by decision protocols or flow charts using visual inspection and single-level indicators, or alert level frameworks using multiple indicators and alert levels. The only health-based indicators used in any system are cyanotoxins, but capacity for frequent testing is often limited. Approaches to rescinding advisories also vary in the types of indicators and length of time used to determine when it is safe to resume recreational activities. This can vary from days to weeks, with some jurisdictions taking more precautionary approaches. Responsible authorities must balance public health protection with available resources for testing and monitoring with public acceptance of extended beach closures. With the prospect of more frequent and pervasive blooms in the future, there will be a need to allocate scare resources efficiently, which may require regular review and update of response protocols. Adapting approaches may require using a range of more accessible indicators alongside local knowledge, site history, and new tools to inform site-specific responses.
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.017 | 0.039 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.007 | 0.004 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.012 | 0.008 |
| Open science | 0.003 | 0.004 |
| Research integrity | 0.003 | 0.003 |
| Insufficient payload (model declined to judge) | 0.008 | 0.003 |
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".