Recognition and Molecular Discrimination of Severe and Mild PVY<sup>O</sup> Variants of <i>Potato virus Y</i> in Potato in New Brunswick, Canada
Bibliographic record
Abstract
A field isolate of Potato virus Y (PVY) was collected in New Brunswick, Canada in 2007 due to unusual symptoms observed on different potato cultivars. To unveil the PVY strain identity, tobacco and potato bioassays, PVYO and PVYN-specific antibody-based enzyme-linked immunosorbent assays, and reverse-transcription polymerase chain reaction (PCR)-based genotyping were carried out. All the assays demonstrated that the isolate, designated as PVYO-FL in this study, belonged to the PVYO strain group. Greenhouse tests with the potato cvs. FL 1533 and Jemseg confirmed the severe nature of infection by PVYO-FL. The complete genome sequences of PVYO-FL and PVYO-RB, the latter a mild PVYO isolate, were determined. BLAST analysis revealed that the two isolates shared 97 and 98% sequence identities at the nucleotide and polyprotein levels, respectively. Further BLAST analysis unveiled that PVYO-FL shared 99.7% nucleotide sequence identity with PVYO-Oz, an isolate reported in New York, United States, whereas the PVYO-RB isolate shared 99.2% sequence identity with PVYO-139, a PVYO isolate reported in New Brunswick, Canada. A phylogenetic tree of available, full-length sequences of PVY isolates demonstrated two subgroups within the PVYO branch, one clustered with PVYO-RB and the other with PVYO-FL. Group-specific sense primers for differentiation of the two subgroups were developed and evaluated. A limited survey of potato tubers collected from a field plot at the Potato Research Centre, Agriculture and Agri-Food Canada, using the newly developed PCR primers, indicated that 65.3 and 2.4% of the PVYO-positive tubers were infected with PVYO isolates belonging to the PVYO-FL and PVYO-RB subgroups, respectively. Assessment of the pathogenicity of three representative isolates from each subgroup on the potato cv. Jemseg demonstrated that severe and mild symptoms were induced by the PVYO-FL-like and PVYO-RB-like isolates, respectively.
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.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| 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".