First Field Report of Tomato Brown Rugose Fruit Virus (ToBRFV) Naturally Infecting Rapeseed ( <i>Brassica napus</i> ) in China
Notice bibliographique
Résumé
Tomato brown rugose fruit virus (ToBRFV), a tobamovirus causing significant damage to tomato and pepper crops, has been primarily associated with Solanaceae species. However, its potential presence in non-solanaceous crops under natural conditions remains poorly characterized (Salem et al. 2023). In May 2024, over 60% of Solanum lycopersicum plants cultivated in an approximately 500 m² open field in Shandong Province, China, exhibited symptoms ranging from mild leaf curling to severe fruit deformation. Five symptomatic plants were randomly sampled, and all tested positive for ToBRFV using reverse transcription-recombinase aided amplification with lateral flow strip (RT-RAA-LFS) assays, following the method of Cao et al. (2023). Five months later, in October, Brassica napus plants grown in the same rotation field exhibited virus-like symptoms, including leaf wrinkling and interveinal chlorosis. Total RNA was extracted from five symptomatic B. napus plants. Four overlapping genomic fragments were amplified using reverse transcription PCR, and the 5′ and 3′ untranslated regions (UTRs) were obtained using a cDNA synthesis kit (Wang et al. 2025). The complete viral genome (6378 bp) was assembled and deposited in the China National GeneBank (accession: CNP0007029). Sequence alignment revealed 99.70%, 99.71%, and 99.78% nucleotide identity with Chinese (GenBank accession no. PV701254.1), Canadian (GenBank accession no. OQ674195.1), and Mexican (GenBank accession no. OM892691.1) ToBRFV isolates, respectively. To assess infectivity, sap extracted from symptomatic B. napus leaves (100 mg tissue per 1ml of 1× PBS) was mechanically inoculated onto B. napus cv. ‘Wanchoutai-Suman’, S. lycopersicum cv. ‘Fenguan’, and Nicotiana benthamiana. Three individuals per plant species were inoculated, and all exhibited typical symptoms, such as chlorosis and leaf deformation, within 7 to 14 days. ToBRFV infection was confirmed by reverse transcription quantitative PCR (RT-qPCR) using primers and probes from EPPO 2021 and western blot analysis of newly emerged symptomatic leaves in all three species. Negative control plants inoculated with 1× PBS showed no symptoms and tested negative by RT-qPCR. This represents the first confirmed field case of ToBRFV naturally infecting a Brassicaceae species. While natural infections have previously been reported in Solanaceae and, less frequently, in Amaranthaceae, Apocynaceae, and Asteraceae (Salem et al. 2022), the detection of ToBRFV in B. napus significantly broadens the known host range of the virus. The prior detection of ToBRFV in tomato plants in the same field suggests that crop rotation without effective field sanitation may facilitate cross-family transmission. In this context, the presence of B. napus as a rotation crop may have allowed the virus to persist and spill over beyond its usual hosts. The exact transmission route remains uncertain, but contaminated tools (Skelton et al. 2023), irrigation water or soil (Mehle et al. 2023), and insect-mediated mechanical transmission (Caruso et al. 2024) are all plausible sources. B. napus is widely planted in China and often rotated with tomato, so its role as an intermediate or symptomless host should be considered. These findings suggest that virus monitoring should also include non-solanaceous crops, especially in mixed-cropping systems where proximity may increase the risk of cross-species transmission.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,000 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,001 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,001 | 0,001 |
| Études des sciences et des technologies | 0,001 | 0,001 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,001 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,001 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».