Origins of the arctic fox variant rabies viruses responsible for recent cases of the disease in southern Ontario
Bibliographic record
Abstract
A subpopulation of the arctic fox lineage of rabies virus has circulated extensively in red fox populations of Ontario, Canada, between the 1960s and 1990s. An intensive wildlife rabies control program, in which field operations were initiated in 1989, resulted in elimination of the disease in eastern Ontario. However in southwestern Ontario, as numbers of rabid foxes declined the proportion of skunks confirmed to be infected with this rabies virus variant increased and concerted control efforts targeting this species were employed to eliminate the disease. Since 2012 no cases due to this viral variant were reported in southwestern Ontario until 2015 when a single case of rabies due to the arctic fox variant was reported in a bovine. Several additional cases have been documented subsequently. Since routine antigenic typing cannot discriminate between the variants which previously circulated in Ontario and those from northern Canada it was unknown whether these recent cases were the result of a new introduction of this variant or a continuation of the previous enzootic. To explore the origins of this new outbreak whole genome sequences of a collection of 128 rabies viruses recovered from Ontario between the 1990s to the present were compared with those representative of variants circulating in the Canadian north. Phylogenetic analysis shows that the variant responsible for current cases in southwestern Ontario has evolved from those variants known to circulate in Ontario previously and is not due to a new introduction from northern regions. Thus despite ongoing passive surveillance the persistence of wildlife rabies went undetected in the study area for almost three years. The apparent adaptation of this rabies virus variant to the skunk host provided the opportunity to explore coding changes in the viral genome which might be associated with this host shift. Several such changes were identified including a subset for which the operation of positive selection was supported. The location of a small number of these amino acid substitutions in or close to protein motifs of functional importance suggests that some of them may have played a role in this host shift.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 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 teacher head, 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".