The Fate and Transport Of Methoprene in an Urban West Nile Virus Mosquito Control Program
Bibliographic record
Abstract
The recent occurrence of vector-borne West Nile virus in Canada has resulted in the use of larvicides for widespread urban mosquito control. The City of Toronto has focused its larviciding program on storm water catch basins as they are concentrated breeding grounds of the mosquito (Culex pipiens) most likely to carry West Nile virus. The City of Toronto undertook a larviciding program to control mosquitoes during the summer months of 2003. The larvicide approved for mosquito control in Canada is methoprene, commercially known as Altosid, in pellet formulation. In order to determine the fate of the larvidice methoprene, the researcher, in conjunction with current studies at Ryerson University, the City of Toronto and the Ontario Ministry of the Environment, have undertaken a water quality monitoring study within the Toronto area. Three study catch basins in the Newtonbrook sewershed in Toronto, Ontario, were dosed with methoprene (Altosid) pellets three times over the summer of 2003, at the recommended mosquito control does of 0.7g. Water from each catch basin was sampled daily and analyzed for methoprene concentration, and mosquito larvae presence was observed. Precipitation, as well as the chemical composition of each of the catch basins was also monitored. A catch basin model in the laboratory was also dosed with methoprene pellets and sampled daily to observe methoprene concentration over time. The fate of methoprene in the urban environment is of interest, to ensure that the larviciding program is not conpromising human and environmental safety. It was found that rainfall flushes methoprene from the catch basins into the storm sewer outfall. The storm sewer outfall did not release methoprene at detrimental concentrations during the sampling period. Many factors such as physical dissolution, chemical degradation and catch basin water volume, affect the concentration of methoprene in a catch basin. In order to monitor the impacts of larviciding programs, comprehensive water quality monitoring and mosquito control efficacy should continue.
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".