Skip to main content
PLOS One logoLink to PLOS One
. 2025 Aug 7;20(8):e0329289. doi: 10.1371/journal.pone.0329289

Virus and viroid diversity in hops, investigating the German hop virome

Ali Pasha 1, Gritta Schrader 2, Heiko Ziebell 1,*
Editor: Ahmet Uludag3
PMCID: PMC12331113  PMID: 40773451

Abstract

Germany is worldwide one of the largest hop (Humulus lupulus L.) producers, an essential crop for the brewing industry. However, infections caused by viruses and viroids can severely impact hop yield and quality. In 2019, citrus bark cracking viroid (CBCVd) – a highly aggressive pathogen in hop – was first reported in Germany, raising concerns about its spread and prompting a broader investigation of the German hop virome.To investigate the viro-diversity in German hops, we started with a pilot study in 2021 targeting three hopyards in the Hallertau region (Bavaria), where CBCVd was previously detected. This study was expanded in 2022 and 2023 to include other main hop growing regions of Tettnang (Baden-Wuerttemberg) and Elbe-Saale (Saxony, Saxony-Anhalt, Thuringia). Leaf samples were collected from hop as well as non-hop plants inside and outside the hopyard, pooled, and proceeded for double-stranded RNAs extraction. High-throughput sequencing (HTS) was used as a diagnostic tool, followed by RT-PCR confirmation. Our analysis identified four viruses infecting hops; hop latent virus (HpLV), hop mosaic virus (HpMV), apple mosaic virus (ApMV), arabis mosaic virus (ArMV) – and two viroids; hop latent viroid (HLVd) and CBCVd. HpLV, HpMV, and HLVd were consistently found across all targeted hopyards, while CBCVd was confined to the Hallertau region. ArMV was only detected in one hopyard at one sampling timepoint. ApMV was the only virus detected in both hop and non-hop plants. Additional analysis of hop pool datasets revealed the presence of other potential hop pathogens, i.e., fungi and bacteria. The results showed a low diversity of viruses and viroids infecting hops. However, this study provides a comprehensive overview on the major viruses and viroids in German hopyards. The results may serve as a useful resource for the development of disease management strategies in hop cultivation and highlight the valuable implementation of HTS in plant pathogen surveillance.

Introduction

Hop (Humulus lupulus L.) is a dioecious perennial climbing plant native to Europe, Asia, and North America [1]. It belongs to the family Cannabaceae and the genus Humulus, which contains three species: Humulus japonicus, Humulus lupulus, and Humulus yunnanensis [2,3]. Since the middle ages, hop has become an important additive for fermented brews due to their anti-microbial properties, and later it became the basic flavoring ingredient of beer [4].

This distinctive status was formally documented in 1516 by the Bavarian “Reinheitsgebot”, which later became the current “Purity law” regulating beer production in Germany [4]. In 2024, Germany had almost 20,289 hectares of hop-growing area distributed in three main regions (Hallertau, Tettnang and Elbe-Saale), with a hop yield of 40,300 tons according to the Federal Ministry of Agriculture, Food and Regional Identity (BMELH) (https://www.bmel-statistik.de/landwirtschaft/bodennutzung-und-pflanzliche-erzeugung/hopfenanbau, accessed on May 14, 2025). Infections caused by viruses, viroids and various microorganisms, e.g., fungi and bacteria that reduce hop yield and quality have been reported in several studies [2,3,5]. Five viruses and two viroids affect hops worldwide and can cause significant losses in commercial hopyards: apple mosaic virus (ApMV), arabis mosaic virus (ArMV), and the three carlaviruses hop mosaic virus (HpMV), hop latent virus (HpLV), and American hop latent virus (AHLV), as well as hop latent viroid (HLVd) and hop stunt viroid (HSVd) [2]. In addition, several other viruses and viroids were reported with limited distribution or sporadic occurrence in hops [2]. Citrus bark cracking viroid (CBCVd) is an emerging threat to hops production; it was detected in severely stunted hop plants in Slovenia in 2007 [5]. CBCVd is an aggressive viroid on hops killing infected plants within a few years. Further outbreaks of CBCVd have been reported from Germany in 2019 [6] as well as Brazil in 2020 [7]. Hop plants have a vigorous annual growth resulting in high biomass. Automated pruning and harvesting of hops facilitates the easy transmission of viruses and viroids by mechanical means [2]. In addition, carlaviruses can be transmitted in a non-persistent manner by hop aphids (Phorodon humuli) [8], and ArMV can be transmitted by the nematode Xiphinema diversicaudatum [9] within and between hopyards. Traditional virus detection methods, such as ELISA or PCR, have limitations as they can only detect a few targets in one sample and require prior knowledge of the target pathogen [10]. The use of next-generation diagnostic tools such as high-throughput sequencing (HTS) enables the detection of multiple targets in a sample by generating massive amounts of sequencing data from native isolated DNAs/RNAs [10]. Over the past few years, the cost of HTS has dropped considerably, making it possible to use this technology for routine plant diagnostics [11,12]. HTS has significant potential in plant virus diagnostics, allowing comprehensive assessment of a plant’s health status and distinguishing between virus variants that may contribute differently to disease etiology [13]. In addition, HTS has been used in viral metagenomics (viromics) studies to address important topics such as virus transmission among host reservoirs, the impact of agricultural activities on ecosystems and biodiversity, and the detection of new viruses in crops and natural surroundings [1417]. However, there are still limitations to using HTS as a diagnostic tool, including the need for high computing power and specialized personnel with bioinformatics expertise to analyze large sequencing datasets. To overcome the challenges of HTS data analysis, the e-Probe Diagnostic Nucleic-acid Analysis (EDNA) was developed and improved [18,19] and used in several studies to develop electronic probes (e-probes) for the in silico detection of a wide variety of known plant pathogens without the need for bioinformatics expertise [2023]. In this study, an HTS-based approach has been applied to investigate the viro-diversity in German hops. A preliminary study to optimize sampling and processing strategies was started in 2021 targeting one region (Hallertau); the virome study was expanded in 2022 and 2023 to cover all main hop growing regions in Germany. To explore potential alternative reservoirs of viruses and viroids infecting hops, samples were also collected from non-hop plants within and surrounding the hopyards. This is the first virome study to investigate the viro-diversity of the German hops.

Materials and methods

Sampling

In 2021, samples were collected in the end of August from three hopyards in the Hallertau region in the southern of Germany (Fig 1A). The targeted hopyards had been infected with CBCVd as confirmed by the monitoring program of the Bavarian State Research Center for Agriculture, Bayerische Landesanstalt für Landwirtschaft (LfL) [24]. Plant leaf material was collected randomly from each hopyard, whether symptomatic or asymptomatic, as follows: Ten hop samples (consisting each of three leaves from one plant, ranging from the fully matured to the newly emerged leaves), ten non-hop samples from within the hopyards; including grasses and weeds growing among the hop rows, and ten non-hop samples from weeds and wild plants growing around the hopyard (≤ 50 meter around the hopyard).

Fig 1. Sampling locations in 2021 (A), 2022 and 2023 (B).

Fig 1

The type of sample and the number of samples of each type collected per yard. Created in BioRender. Pasha, A. (2025) https://BioRender.com/6o9sv6f.

In 2022 and 2023, samples were collected at the end of June – beginning of July from two hopyards in each hop growing region. The hop growing locations were: Hallertau region, Tettnang region, and Elbe-Saale (ranging from Halle to Dresden) as shown in Fig 1B.

In those two years, the samples from each hopyard included: 35 hop samples, 5 non-hop samples within the hopyard, and 10 non-hop samples outside the hopyard (Fig 1B). Samples were collected from hopyards cultivated with different hop varieties and applying different agricultural practices (Table 1); and for sampling a “W” pattern was applied as suggested by [25]. Detailed information on the plant samples collected is provided in S1S3 Tables.

Table 1. Detailed information on sampling locations. Samples were collected from hopyards 1 to 3 during the 2021 sampling, and from hopyards 4 to 9 in both 2022 and 2023 samplings.

Sampling year Hopyard Hop variety Farming type Sampling location
Hallertau Tettnang Elbe-Saale
Geisenfeld Rohrbach Meckenbeuren Burkau Quellendorf
2021 Hopyard 1 Perle Conventional X
Hopyard 2 Herkules Conventional X
Hopyard 3 Herkules Conventional X
2022 and 2023 Hopyard 4 Herkules Conventional X
Hopyard 5 Perle Conventional X
Hopyard 6 Tettnanger Conventional X
Hopyard 7 Spalter, Tettnanger, Perle Organic X
Hopyard 8 Magnum Conventional X
Hopyard 9 Magnum Conventional X

Pooling of samples

Plant leaf material (200 mg) from each sample collected from a hopyard was pooled with other samples according to the pooling strategy (Fig 2 and Table 2). In addition, all hop samples collected each year from all hopyards were pooled, as well as all non-hop plant samples from inside and outside the hopyards, resulting in a total of six pools (2021) and nine pools (2022 and 2023) (Fig 2). Samples were ground under liquid nitrogen using a mortar and pestle and then collected in 50 ml Falcon tubes. The tubes were stored at −80°C for subsequent RNA extraction. The remaining sample tissues were stored at −20°C.

Fig 2. Pooling strategy for all samples.

Fig 2

Collected samples from each yard were properly pooled in the hopyard pool. The hop samples collected in each sampling year were sampled in an additional pool called “hop pool”, and the same was done for non-hop plants collected from inside and outside the hop yard, resulting in “non-hop inside pool” and “non-hop outside pool”. Created in BioRender. Pasha, A. (2025) https://BioRender.com/ts4jf0m.

Table 2. Sample pool.

Sampling year Pool type Amount of each sample (mg) Number of pooled samples Total amount of plant material (mg)
2021 Hopyard pool 200 30 6000
Hop pool 200 30 6000
Non-hop inside pool 200 30 6000
Non-hop outside pool 200 30 6000
2022 and 2023 Hopyard pool 200 50 10000
Hop pool 200 210 42000
Non-hop inside pool 200 30 6000
Non-hop outside pool 200 60 12000

Nucleic acid extraction, virus/viroid enrichment and high-throughput sequencing

Double-stranded RNA (dsRNA) was extracted from each sample pool using the Double-RNA Viral dsRNA Extraction Mini Kit (plant tissue) (iNtRON Biotechnology, USA). A total of 200 mg of ground plant material was used as the starting material according to the manufacturer’s instructions. A different dsRNA enrichment protocol had to be used for the 2023 samples as the iNtRON kit was no longer commercially available. Total RNA was extracted from all sample pools. Extraction was performed using the Monarch® Total RNA Miniprep Kit (New England Biolabs, Ipswich, USA) according to the manufacturer’s instructions. For enrichment of viral and viroidal RNAs, total RNAs were enzymatically treated using a mix of DNase I (Thermo Scientific) at a final concentration of 10 U/μL and RNase T1 (Thermo Scientific) at a final concentration of 10 U/μL for 30 minutes at 37°C. The undigested double-stranded viral/viroid RNAs (dsRNAs) were then purified using the RNA Mini Elute Kit (Qiagen, Hilden, Germany) [26]. The quantification of dsRNA was done by Qubit spectrofluorometry using the Qubit dsDNA high sensitivity kit (Qubit fluorometer, Invitrogen, Life Technologies). Samples were sequenced using the Illumina platform (NovaSeq 6000) to obtain 150 bp paired-end reads (INVIEW Virus, Eurofins Genomics, Constance, Germany). Ten million reads were ordered per sample. The obtained datasets were archived in the Sequence Read Archive (SRA) under Bioprojects: hop virome 2021: PRJNA1165201, hop virome 2022: PRJNA1167474, and hop virome 2023: PRJNA1167495. More details on bioproject datasets are provided in S4 Table.

For amplicon sequencing of fungal and bacterial sequences, DNA was extracted from hop pool samples using the DNeasy Plant Mini Kit (QIAGEN, Germany) following the manufacturer’s instructions. DNA samples were sent to a commercial service provider for amplicon sequencing targeting the internal transcribed spacer 1 (ITS1) region to identify the fungal sequences, and 16S ribosomal RNA to identify the bacterial sequences. Samples were sequenced using the Illumina platform (MiSeq) to obtain 300 bp paired-end reads (Microbiome Profiling, Eurofins Genomics, Constance, Germany). The obtained datasets were archived in the Sequence Read Archive (SRA) under the Bioproject: PRJNA1254465.

Bioinformatics analysis

The raw fastq datasets were imported into Geneious Prime® version 2024.0.4. Reads were paired and then quality trimmed (including removal of low quality reads and duplicated reads) using the BBNorm tool version 38.84 using default settings. De novo assembly for the normalized reads was performed using “Geneious” assembler: “medium sensitivity/fast” default settings. The obtained contigs were mapped against a local virus/viroid reference sequences (RefSeq Nucleotide) database downloaded in September 2024 from the National Center for Biotechnology Information (NCBI Virus) GenBank non-redundant nucleotide database. Contigs matching virus/viroid sequences were re-blasted with BLASTn and BLASTx using the National Center for Biotechnology Information (NCBI) GenBank non-redundant nucleotide and protein databases, respectively. Based on the BLAST results, virus or viroid GenBank sequences matching the consensus sequences with the highest similarity were used as reference genomes for re-mapping of quality-trimmed reads.

Mapping normalized reads to individual reference genomes was performed in Geneious Prime® version 2024.0.5. using Geneious RNA mapper (High sensitivity/Medium) with adjusting the settings: ‘Trim before mapping “Do not trim”. Results “save in sub-folder”’.

For confirmation of the identified virus and viroid consensus sequences in the original plant samples, (RT-)PCR primers were designed using a modified version of Primer3 (version 2.3.7) within Geneious Prime®.

Variant analysis of viroid sequences was performed using the “Find Variations/SNPs” tool in Geneious Prime version 2024.0.5. A minimum variant frequency threshold of 0.2 (20%) was applied; at least 20% of the reads had to support a variant. To ensure reliability, a minimum coverage of 5 reads at the SNP position was also set, and the variants were manually inspected in the alignment viewer.

Pairwise nucleotide alignments were performed with MAFFT (Multiple Alignment using Fast Fourier Transform) version 7.490 within Geneious Prime®. Phylogenetic analysis was performed using the MrBayes version 3.2.6 [27].

The fastq datasets acquired by amplicon sequencing were analyzed by the sequencing service provider (Eurofins Genomics, Constance, Germany) using their microbiome analysis pipeline as follows: Ambiguous and chimeric reads were identified and removed based on the de-novo algorithm of UCHIME [28] as implemented in the VSEARCH package [29]. High quality reads were processed using minimum entropy decomposition (MED) [30]. To assign taxonomic information to each Operational Taxonomic Unit (OTU), DC-MEGABLAST alignments of cluster-representative sequences to the sequence database were performed. A most specific taxonomic assignment for each OTU was then transferred from the set of best-matching reference sequences (lowest common taxonomic unit of all best hits). A minimum sequence identity of 70% over at least 80% of the representative sequence was used as the minimum requirement for consideration of reference sequences. Further processing of OTUs and taxonomic assignments was performed using the QIIME software package (version 1.9.1). An analysis report was submitted for each sample containing the results (taxonomic composition of the sample).

RT-PCR confirmation of viral sequences

To confirm that the identified virus/viroid sequences were indeed of viral origin, total RNA was re-extracted from all sample pools using the Monarch® Total RNA Miniprep Kit. Samples were subjected to RT-PCR using OneTaq One-Step RT-PCR, NEB kit following the manufacturer’s instructions. The PCR conditions were as follows: reverse transcription 48°C for 15 min, initial denaturation 94°C for 1 min, denaturation 94°C for 15 sec, appropriate annealing temperature for the primer set in use (S5 Table) for 30 sec, extension at 68°C for 60 sec (40 cycles) followed by a final extension 68°C for 5 min, then hold at 4°C. The amplicons were purified using DNA clean-up and concentrator kit (Zymo Research) according to the manufacturer’s instructions and sequenced using the same RT-PCR primers by Sanger sequencing (Microsynth, Germany). The primers used for the PCR assays from this study, as well as those from other studies, are listed in S5 Table.

Results

Sequencing data quality

A substantial higher amount of raw sequence reads was received by the sequencing provider, in some cases almost ten times more reads were produced. However, most of these “extra” reads were duplicated or of low quality and were not used for downstream bioinformatics analyses. The double-stranded RNA enrichment strategy resulted in RNA qualities that were interpreted by the sequence provider as insufficient for sequencing after library preparation so that the same library was sequenced multiple times introducing a high number of technical duplicate reads, and increasing the total number of raw reads artificially (S4 Table). Only reads after QC were used for de novo assembly and reference mapping producing sufficient read depth and coverage for virus and viroid detection (S4 Table, S6 Table).

Identified viruses and viroids in hops across the sampling sites over three years

Four viruses and two viroids were identified in the hop pools over three years of sampling. These viruses belong to three virus families (Betaflexiviridae, Bromoviridae, and Secoviridae). The two identified viroids belong to Pospiviroidae family (Table 3 and 4).

Table 3. Identified viruses and viroids in all sample pools over three years.

Sampling year 2021 2022 2023
Hopyard no. 1 2 3 4 5 6 7 8 9 4 5 6 7 8 9
Hop pools Hop latent virus                              
Hop mosaic virus                              
Apple mosaic virus                
Arabis mosaic virus  
Hop latent viroid                              
Citrus bark cracking viroid            
                     
Non-hop inside Barley virus G  
Turnip ringspot virus    
Raphanus sativus cryptic virus 1  
Plant associated deltapartitivirus 1        
Turnip mosaic virus  
Turnip yellows virus  
Beet western yellows virus associated RNA  
Plantago yellow mosaic virus    
Turnip yellows virus associated RNA2   
Raphanus sativus cryptic virus 4  
Radish mosaic virus  
                     
Non-hop outside Turnip yellow mosaic virus  
Turnip ringspot virus    
White clover mosaic virus    
Plant associated deltapartitivirus 1  
Apple mosaic virus  
Plantago yellow mosaic virus      
Peanut stunt virus  
Prune dwarf virus  
Senna severe yellow mosaic virus  
Mentha macluravirus 1  

Table 4. Identified viruses and viroids in hop pools over three years of sampling.

Year Sample Virus/Viroid Family, genus Ref. genome Pairwise ID % (BLASTn) Pairwise ID % (BLASTx) Genbank accession
2021 Hop pool Hop latent virus Betaflexiviridae, Carlavirus KP861891 98.12 98.68 PV364036
Hop mosaic virus Betaflexiviridae, Carlavirus EU527979 99.95 99.95 PV364039
Apple mosaic virus RNA 1 Bromoviridae; Ilarvirus NC_003464 99.75 99.81 PV364044
Apple mosaic virus RNA 2 Bromoviridae; Ilarvirus NC_003465 90.7 92.8 PV364045
Apple mosaic virus RNA 3 Bromoviridae; Ilarvirus NC_003480 95.91 96 PV364048
*Hop latent viroid Pospiviroidae, Cocadviroid MK795526 99.22, 98.83, 95.7 PV364051, PV364052, PV364053
*Citrus bark cracking viroid Pospiviroidae, Cocadviroid KM211546 99.3, 99.65 PQ650572, PQ650573
2022 Hop pool Hop mosaic virus Betaflexiviridae, Carlavirus EU527979 99.95 99.95 PV364040
Hop latent virus Betaflexiviridae, Carlavirus KP861891 99.71 99.5 PV364037
Apple mosaic virus RNA 1 Bromoviridae; Ilarvirus NC_003464 98 99.04 PV364042
Apple mosaic virus RNA 2 Bromoviridae; Ilarvirus NC_003465 98.51 99.3 PV364046
Apple mosaic virus RNA 3 Bromoviridae; Ilarvirus NC_003480 97.73 97.88 PV364049
Arabis mosaic virus RNA2 Secoviridae, Nepovirus BK059335 85.96 90.38 PV364058
Hop latent viroid Pospiviroidae, Cocadviroid MK795526 99.61, 99.22 PV364054, PV364055
Citrus bark cracking viroid Pospiviroidae, Cocadviroid KM211546 98.94, 98,94 PQ650574,PQ650575
2023 Hop pool Hop mosaic virus Betaflexiviridae, Carlavirus ON409684 99.21 99.79 PV364041
Hop latent virus Betaflexiviridae, Carlavirus KP861891 99.3 99.49 PV364038
Apple mosaic virus RNA 1 Bromoviridae; Ilarvirus NC_003464 97.09 98.15 PV364043
Apple mosaic virus RNA 2 Bromoviridae; Ilarvirus NC_003465 98.2 98.7 PV364047
Apple mosaic virus RNA 3 Bromoviridae; Ilarvirus NC_003480 97.73 98 PV364050
Hop latent viroid Pospiviroidae, Cocadviroid MK795539 99.61, 99.22 PV364056, PV364057
Citrus bark cracking viroid Pospiviroidae, Cocadviroid KM211546 99.65, 98.94, 98.25, 98.59 PQ075924, PQ075925, PQ655430, PQ655431

*Viroid sequences identified in the hopyard and hop pools datasets were subjected to variant analysis. The identified variants were submitted to GenBank. The BLASTn results for the variants are separated by commas and are in the same order as the GenBank accessions in the right column.

HpLV, HpMV, and HLVd were consistently identified in all hopyard pools across all the sampling sites over three years (Table 3 and S6 Table). Based on our sampling strategy, we could assign the identification of ApMV to one hopyard pool in 2021, three hopyard pools in 2022 and four hopyard pools in 2023 (Table 3). ArMV was identified only in one hopyard pool in 2023. CBCVd was identified in three hopyard pools in 2021, in one hopyard pool in 2022 and in two hopyard pools in 2023 (Table 3).

Viruses and viroids identified in non-hop plants.

Nine viruses belonging to four virus families in addition to two virus associated RNAs were identified in the non-hop plant samples collected from inside the hopyard over three years (Table 3 and 5). The plant diversity of non-hop plants within the hopyards was low with 90 plant samples belonging to 11 plant families.

Table 5. Identified viruses in weeds collected from inside the hopyards “non-hop inside” over three years.
Year Sample Virus/Viroid Family, genus Ref. genome Pairwise ID % (BLASTn) Pairwise ID % (BLASTx)
2021 Non-hop inside Barley virus G Solemoviridae, Polerovirus NC_029906 98.5 99.35
Turnip ringspot virus RNA1 Secoviridae, Comovirinae GQ222381 94.9 95.13
Turnip ringspot virus RNA 2 Secoviridae, Comovirinae FJ516746 95.8 96.2
Raphanus sativus cryptic virus 1, dsRNA1 Partitiviridae, unclassified NC_008191 99.7 99.83
Raphanus sativus cryptic virus 1, dsRNA2 Partitiviridae, unclassified NC_008190 95.4 97
2022 Non-hop inside Plant associated deltapartitivirus 1 RNA 1 Partitiviridae, Deltapartitivirus OL472010 99.5 99.79
Plant associated deltapartitivirus 1 RNA 2a Partitiviridae, Deltapartitivirus OL472011 99.2 99.79
Plant associated deltapartitivirus 1 RNA 2b Partitiviridae, Deltapartitivirus OL472012 99.4 99.98
2023 Non-hop inside Turnip mosaic virus Potyviridae, Potyvirus AB989659 98.5 98.9
Turnip yellows virus Solemoviridae; Polerovirus OP797722 95.4 97.2
Plant associated deltapartitivirus 1 RNA 1 Partitiviridae, Deltapartitivirus OL472010 99.7 100
Plant associated deltapartitivirus 1 RNA 2a Partitiviridae, Deltapartitivirus OL472011 99 99.8
Plant associated deltapartitivirus 1 RNA 2b Partitiviridae, Deltapartitivirus OL472012 99.5 100
Beet western yellows virus associated RNA Riboviria; virus-associated RNAs ON603912 93 94.2
Plantago yellow mosaic virus Riboviria, unclassified ON012585 99.5 99.86
Turnip yellows virus associated RNA2 Solemoviridae; Polerovirus MN497827 95.4 96.3
Raphanus sativus cryptic virus 4 RNA1 Partitiviridae, Durnavirales MF686921 97.6 98
Raphanus sativus cryptic virus 4 RNA2 Partitiviridae, Durnavirales MF686922 99.6 99.7
Radish mosaic virus, RNA1 Comovirinae; Comovirus NC_010709 99.1 99.4
Radish mosaic virus, RNA2 Comovirinae; Comovirus NC_010710 99.2 99.34

In contrast, the sample pools representing plants from outside the maintained hopyards had a wider variety of plant species, as a total of 150 plant samples belonging to 25 plant families were collected from outside the hopyards over three years (S1, S2, and S3 Tables). This plant diversity is also represented by a higher diversity of viruses that were identified from those plants: ten viruses belonging to six families (Table 6).

Table 6. Identified viruses in weeds and wild plants collected from outside the hopyards “non-hop outside” over three years.
Year Sample Virus/Viroid Family, genus Ref. genome Pairwise ID (BLASTn) Pairwise ID (BLASTx)
2021 Non-hop-outside Turnip yellow mosaic virus Tymoviridae; Tymovirus NC_004063 92 93.7
Turnip ringspot virus RNA1 Secoviridae; Comovirinae GQ222381 94.1 94.5
Turnip ringspot virus RNA 2 Secoviridae; Comovirinae FJ516746 91 92.8
2022 Non-hop-outside White clover mosaic virus Alphaflexiviridae; Potexvirus OL472250 94 94.6
Plant associated deltapartitivirus 1 RNA 1 Partitiviridae, Deltapartitivirus OL472010 99.2 99.7
Apple mosaic virus RNA3 Bromoviridae; Ilarvirus NC_003480 94.7 96
Plantago yellow mosaic virus Riboviria, unclassified OK523415 98.4 98.65
2023 Non-hop-outside Plantago yellow mosaic virus Riboviria, unclassified ON012585 96.2 97
White clover mosaic virus Alphaflexiviridae, Potexvirus MN399743 93.8 94.3
Peanut stunt virus RNA 1 Bromoviridae; Cucumovirus OK558739 98.8 99.2
Peanut stunt virus RNA 2 Bromoviridae; Cucumovirus OR233184 98.3 98.8
Peanut stunt virus RNA 3 Bromoviridae; Cucumovirus OR233185 98.5 98.76
Prune dwarf virus RNA1 Bromoviridae; Ilarvirus MZ291947 98.2 98.45
Prune dwarf virus RNA2 Bromoviridae; Ilarvirus NC_008037 97.9 98.1
Senna severe yellow mosaic virus Alphaflexiviridae; Allexivirus NC_076419 96.6 97
Mentha macluravirus 1 Potyviridae, Macluravirus OL472141 82.4 85.3

Commonalities and specificities between the different sites/pools

The analysis of non-hop plant pools collected from inside and outside the hopyards over three years could only identify one virus in both hop and non-hop plants, ApMV. ApMV was consistently detected in hop pools over three years of sampling and in addition in a “non-hop outside” pool at the 2022 sampling (Fig 3). An apple tree sample was collected in 2022 outside the hopyard 8. This individual sample as well as the hop sample in which ApMV was identified at hopyard 8 were re-analyzed by RT-PCR using the primers from Menzel et al. [31] which confirmed that ApMV was present in both the apple tree and hop plants.

Fig 3. Venn-diagram illustrating the viruses and viroids identified in all sample pools (hop, non-hop inside, and non-hop outside) over three years of sampling. Only one virus (ApMV) was detected in both the hop plant pool as well as in the non-hop plants outside the hopyard pool in 2022. Pasha, A. (2025) https://BioRender.com/k13y381.

Fig 3

Mycoviruses and other non-plant virus sequences identified in the datasets

In addition to plant-infecting virus and viroid sequences, HTS data analysis enabled also the detection of other viral sequences associated with insects, fungi, and oomycetes. These viruses which can infect plant-associated fungi and oomycetes are known as mitoviruses or mycoviruses. In this study, several non-plant viruses were identified in the datasets (Table 7).

Table 7. Non-plant viral sequences identified in the datasets.

Virus Family, genus Sequencing library (year) Ref. genome Pairwise ID % (BLASTn) Pairwise ID % (BLASTx) Natural host
Fusarium asiaticum mitovirus 2 Mitoviridae; Mitovirus Hopyard 4 (2022) MZ969052 91.8 92 Fusarium asiaticum
Plasmopara viticola lesion associated ourmia-like virus 63 Scleroulivirus, epsilonplasmoparae Hopyard 4 (2022) ON812983 97.4 98.6 Plasmopara viticola
Erysiphe necator associated ourmia-like virus 21 Penoulivirus, alphaerysiphe Hopyard 4 (2022) MN611549 98 99.1 Erysiphe necator
Hubei sobemo-like virus 34 Riboviria, unclassified Hopyard 5 (2023) KX882879 80 84.2 Tetragnatha maxillosa
Erysiphe necator associated ilar-like virus 1 Bromoviridae; Ilarvirus Hopyard 6 (2023) MN630188 98.7 98.9 Erysiphe necator
Erysiphe necator associated mitovirus 9 Mitoviridae; Mitovirus Hopyard 9 (2023) MN557015 92.5 93 Erysiphe necator
Alternaria arborescens mitovirus 1 Mitoviridae; Unuamitovirus Hop pool (2023) ON714134 95.3 95.8 Alternaria arborescens

Identification of other hop pathogens in the hop pool datasets

Mapping the consensus sequences of the three hop pool datasets (2021, 2022, and 2023) against NCBI BLASTn database revealed genomic sequences of hop genome as well as various sequences from other microorganisms, e.g., fungi and bacteria, some of which are known to infect hops. The presence of fungi and bacteria was confirmed by amplicon sequencing. While many microorganisms (fungi and bacteria) were identified by both sequencing methods, only those previously reported to infect hop were considered in Table 8.

Table 8. Hop pathogenic fungi and bacteria identified in the RNA-seq datasets and confirmed by amplicon sequencing.

Pathogen Type Disease on hop Hop pool sample Confirmation
Detected by RNA-seq Detected by amplicon sequencing
Agrobacterium tumefaciens Bacterium Crown gall 2022 Yes Yes
Alternaria alternata Fungus Alternaria cone disorder 2021, 2022, 2023 Yes Yes
Colletotrichum sp. Fungus Anthracnose 2021, 2022, 2023 Yes Yes
Ascochyta rabiei Fungus Ascochyta leaf spot 2021, 2022 Yes Yes
Fusarium avenaceum Fungus Cone tip blight 2021, 2022, 2023 Yes Yes
Phoma sp. Fungus Phoma wilt 2021, 2022, 2023 Yes Yes
Septoria rosae Fungus Septoria leaf spot 2022 Yes Yes
Verticillium nonalfalfae (V. albo-atrum) Fungus Verticillium wilt 2022, 2023 Yes Yes
Verticillium dahliae Fungus Verticillium wilt 2021, 2022, 2023 Yes Yes
Cladosporium sp. Fungus Sooty mold 2021, 2022, 2023 Yes Yes
Fusarium sambucinum Fungus Canker 2023 Yes Yes
Botrytis cinerea Fungus Gray mold 2023 Yes Yes

Phylogenetic analysis of CBCVd

CBCVd sequences were detected only in the Hallertau region but in five different hop yards over three years of sampling. Variant analysis of the full genome sequence of CBCVd revealed eight CBCVd sequence variants, which were deposited in GenBank under accession numbers: PQ075924, PQ075925, PQ650572, PQ650573, PQ650574, PQ650575, PQ655430, and PQ655431.

The multiple sequence alignment of these eight CBCVd variants with other 87 CBCVd sequence variants obtained from GenBank showed that three of our detected variants (PQ655430, PQ650573, PQ075924) were 100% identical to three of CBCVd sequence variants previously reported in the Hallertau (PP332307, PP332297, and PP332305, respectively).

In addition, two of the variants from our study (PQ650573, PQ650572) shared 100% identity with CBCVd variants that were reported from Slovenian hops (GenBank accession numbers: KM211546 and KM211547, respectively). The phylogenetic analysis showed that the CBCVd sequence variants identified in this study were clustering with CBCVd variants from hops that were previously reported from Germany and Slovenia. This highlights their close evolutionary relationship suggesting a common origin, probably derived from a CBCVd-citrus sequence variant (Fig 4).

Fig 4. Phylogenetic analysis of 95 CBCVd sequence variants.

Fig 4

MrBayes was used to perform Bayesian inference of phylogeny. The numbers on the branches represent Bayesian posterior probabilities indicating the statistical support for each clade. Posterior probability values range from 0.5 to 1.0. Values closer to 1.0 indicate greater support. CBCVd sequence variants from German hops are shown in blue, while other variants identified in this study are shown in red. CBCVd-hop variants from Slovenia are shown in grey. CBCVd-hop variants from Germany and Slovenia are clustered together and share the same ancestor (CBCVd-citrus). Each node is labeled with GenBank accession number of the corresponding variant, host plant, and the country where the variant was identified. The sequence of CBCVd sequence variant from pistachio (MF198463) was used as outgroup. The scale bar indicates the genetic distance.

Discussion

In recent years, many virome studies have been conducted to explore the viro-diversity of a crop within its ecosystem and the role of other weeds and wild plants as reservoirs of plant viruses [1416]. In addition, a few of the studies have explored the viro-diversity at the same sampling location over two to three seasons, helping to obtain a better understanding of the viruses present in the targeted agroecosystem [14].

In this study, a preliminary HTS-based pilot study was carried out in 2021 to explore alternative reservoirs of CBCVd. Samples were collected from hops, non-hop plants growing inside and outside hopyards in locations where CBCVd was previously detected. Plant viruses may not cause symptoms on infected plants due to latency, host tolerance or just a mild strain of the virus/viroid infecting the plant [32,33]. Therefore, samples were collected regardless of whether the plants were symptomatic or asymptomatic. The pooling strategy applied in this study allowed the determination of potential hosts of the detected viruses and viroids by overlapping the detections across hopyard pools with hop pool, non-hop inside and non-hop outside pools. Identified viruses in the non-hop pools were not further investigated to determine the original host plant, unless the virus/viroid was a known hop pathogen or a novel virus/viroid species. The dsRNA approach for enrichment of viral and viroid sequences enabled the detection of different viruses and viroids with varying genomic backgrounds [34]. At least ten million reads were acquired per dataset, resulting in recovering ≥ 40% of the viral genomic sequences and 100% of the viroid genomic sequences. Malapi-Wight et al. [35] found that ten million reads generated from a metagenomic sample were sufficient to obtain near-complete coverage of viral RNA and DNA genomes. In addition, Schönegger et al. [36] found that using dsRNA as an enrichment method and 10 million reads datasets has provided more than 90% representation of a complex virome of 72 viral agents, regardless of the assembled contig lengths. The pilot study revealed the presence of known hop pathogens, in particular HpLV, HpMV, ApMV, HLVd and CBCVd (Table 3 and 4). By extending the sampling to other main hop-growing locations in Germany in the following years, it was possible to investigate any potential outbreak of CBCVd outside the Hallertau region, to get a comprehensive overview of the viruses and viroids infecting hops in Germany, and to explore other alternative host plants for the detected hop viruses and viroids. In addition, sampling from the three main hop-growing locations over two consecutive years targeting the same hopyards helped to investigate spatio-temporal differences at these regions which may have been overlooked if only one region had been sampled for one year. Sampling in the Hallertau in 2022 and 2023 targeted different hopyards than those sampled in 2021, as the three hopyards were eradicated following the severe CBCVd outbreaks.

Interestingly, the total number of viruses and viroids detected in this study is less than in other virome studies. For example, Rivarez at al. [15] detected 125 viruses, including 79 new species in the Slovenian tomato virome study. Similarly, Gaafar et al. [14] reported 35 viruses in addition to nine associated nucleic acids when they looked at the pea virome in Germany. It is counter intuitive that hop, being perennial with very few replacements of plants, is a reservoir to fewer viruses and viroids than annual crops such as tomatoes or peas. In addition, hop planting material in Germany has been propagated through certified virus-free production schemes in dedicated nurseries for more than three decades. These efforts align with the EPPO standard “Certification Scheme for Hop” [37], which aims to minimize the spread of viral agents and other pests through planting material. These phytosanitary measures likely contribute significantly to the reduced pathogen diversity observed in German hopyards. Also, it may be possible that due to the sampling and pooling strategy that the amount of plant material may have been insufficient to detect low titer viruses and viroids in the pooled samples. Although the pools (already representing between 30–210 individual plant samples) contain at least 6 g of plant material, only a fraction of this could be used for dsRNA enrichment and HTS (Table 2).

Common viruses and viroids in German hops

In total, four viruses and two viroids were detected in all hop pools over the three years. Two of them (HpLV and HpMV) were detected across all the nine hopyards (Table 3 and S6 Table), which means that both carlaviruses are widely distributed in German hopyards. Both are mainly spread between hop plants by aphid vectors in a non-persistent manner and mechanical means [2]. HpLV and HpMV have been shown to occur in all hop-growing locations in the world [3]. HpLV infection tends to be symptomless. In contrast, HpMV is associated with leaf mosaic symptoms, stunted growth, and lower cone yield in some old hop cultivars. However, it is often asymptomatic in most commercial hop cultivars grown today [2]. In the United States, mixed infection of HpLV and HpMV in the hop cultivar Chinook caused significant impact on lateral length, leaf weight, cone yield, number of cones per plant, and reduction of the organic acids and oils content in infected plants [38].

ApMV belongs to the genus Ilarvirus and was detected in one hopyard in 2021, in three hopyards in 2022, and in five hopyards in 2023 (S6 Table). Interestingly, in two hopyards, ApMV was not detected in 2022 but was detected one year later. This indicates either the infected plants were missed during sampling or only few plants were infected in 2022 but the infection spread to more plants in 2023 thus allowing to be collected during sampling. As the sampling was carried out randomly in each year, this question cannot be answered. Interestingly, ApMV sequences of all three viral RNAs were identified in the non-hop plants pool from outside a hopyard in 2022. ApMV was confirmed by RT-PCR in the same pool and in an individual sample belonging to the same pool, collected from an apple tree outside hopyard 8 (Elbe-Saale, Dresden). It may be possible that ApMV was transmitted to the hop plants when apple harvest residues were used as fertilizer in the hopyard, as ApMV is transmitted exclusively by mechanical means [39]. This hypothesis is based on our observations that at some of the sampling sites, apple harvest residues are used in hopyards as organic fertilizer. It is also possible that the growers may have used uncertified planting material that could have been infected with ApMV and/or other hop pathogens. ApMV is considered one of the most harmful viruses for hop production. The spread of ApMV in hopyard is slow but it is strongly dependent on the cultivar [2]. ApMV seems to reduce the ability to propagate hop plants vegetatively, and it can also reduce alpha acid content by up to 22% [2,40]. The detection of ApMV along with HpMV and HpLV in many hopyards across different hop growing locations in Germany may be alarming, as the co-infection of these viruses can cause a significant reduction in the cone weight and alpha acid content. This reduction is attributed to the low number of lupulin glands in the cones of co-infected hop plants [2,40].

The detection of ArMV in one hopyard (Tettnang) and only in one sampling (2022) may indicates that this virus is less common in the German hops. ArMV infection has been associated with several diseases including spidery hop, split leaf blotch, and hop chlorotic disease [2]. Significant yield losses were demonstrated in New Zealand [41] when hops were co-infected with ArMV with HpMV or HpLV despite the absence of symptoms. However, nematodes transmitting ArMV are less mobile between plant roots, so their effect is locally limited [42].

HLVd was detected in the nine hopyard pools over the three years, confirming that it is widely distributed in commercial hops worldwide [5]. HLVd causes often latent infection in the majority of hop cultivars and was firstly reported in German hops by Puchta et al. [43]. HLVd infection is less severe than other viruses or viroids infecting hops, but can still result in reduction of alpha acid content [44]. Our findings align with those from Eppler [42], who investigated the viro-diversity in many hop growing regions in Germany and tested the collected samples by ELISA for 15 viruses which were previously reported in hops, e.g., HpLV, HpMV, ApMV, ArMV, AHLV, potato virus X (PVX), potato virus Y (PVY), tobacco mosaic virus (TMV), cucumber mosaic virus (CMV), etc. The results showed that there was no hop growing region or hop variety virus-free. HpLV, HpMV, ArMV, and ApMV were detected in the tested samples. Furthermore, dot-blot hybridization was used to detect viroids. HLVd was detected in many of the tested samples, whereas HSVd, though present in Germany in grapevine since the 1980s [45], was not detected in any of them. In addition, during the monitoring of hop viruses in Germany from 2008 to 2012, Seigner et al. [46] analyzed 1,170 symptomatic hop leaf samples collected from all German hop growing regions by ELISA and RT-PCR. The results showed that HpLV, HpMV and ApMV were the omnipresent viruses in the German hops, while ArMV was rarely detected, which is also in line with the findings of our study. In addition, HSVd was detected in nine samples in 2009, and the infected plants were eradicated effectively.

Although CBCVd infection is still limited to the Hallertau region, as confirmed by our results, it could be possible that CBCVd infection is spreading to new hopyards in the same region. This is shown by the data from hopyard 4 (Hallertau), where CBCVd was not detected in 2022, but was detected in 2023. These results are consistent with the findings of the LfL during their CBCVd-monitoring programme [24]. There could also be the risk of spread to other regions in the future, if no sufficient measures are applied. Currently, CBCVd is regulated in the European Union as a regulated non-quarantine pest (RNQP), which means that the threshold for planting material (other than pollen and seeds) of Humulus lupulus is 0%. Furthermore, several requirements for the production of hop plants for planting are mandatory (http://data.europa.eu/eli/reg_impl/2019/2072/2025-01-26, accessed on May 15. 2025).

Štajner et al. [47] found that coinfected hop plants with HLVd and CBCVd showed a significant reduction in biomass up to 81% compared to plants infected with either HLVd or CBCVd. These findings highlighted the aggressiveness of CBCVd in causing a severe disease in hops with synergistic interaction with HLVd.

Identified viruses in alternative plants inside and outside the hopyards

We were interested to know whether we could identify alternative hosts for the viruses and viroids found in the hop plants. In particular, we wanted to know if there were alternative hosts for CBCVd as this would have had implications on control measures. Several virome studies identified alternative reservoirs for viruses infecting a crop, e.g., in the case of tomatoes where ten viruses were detected in both the tomato and the surrounding weeds [15] or peas where two pea viruses were also identified in non-legume weeds [14].

For this purpose, many samples were collected from weeds and wild plants growing inside and outside the hopyard. The number of the collected samples from inside the hopyard (five per yard) was lower than the collected samples from the outside (ten per yard, Fig 1) because the weeds were removed from the hopyard as agricultural practice during hop production. Furthermore, regular tilling and producing “hop hills” in which the hop plants were growing, were also seen as common practice thus reducing the occurrence of weeds within the crops. Many of the hopyards that were sampled were surrounded by other hopyards, in particular in the Hallertau region; in the case of Tettnang region, apple orchards were often seen next to hopyards.

All the viruses that were identified in non-hop inside and non-hop outside pools (except ApMV), are not known to infect hop. Eppler [48] investigated for alternative reservoirs for HpMV and ArMV in Tettnang. Samples of 36 weed species belonging to 10 plant families were collected from different hopyards, and tested by ELISA techniques. ArMV was detected in 22 plant species, while HpMV was detected in four plant species. However, the results of ArMV detection in 15 of the tested species, and same for HpMV detection in 2 of the tested species, were questionable due to weak ELISA reaction. Further attempts to induce infections in hops by mechanical inoculation of these potentially infected weed species were unsuccessful. However, in our study, none of the reported hop viruses and viroids were detected in non-hop plant pools, except ApMV.

From the pools of non-hop plants within the hopyards, we detected viruses of weeds and root vegetables. Other viruses detected in non-hop outside pools are known to infect weeds and other crop plants including legumes and fruit trees. Two of these viruses are economically important: peanut stunt virus (PSV) and prune dwarf virus (PDV). PSV was detected in a white clover (Trifolium repens) sample collected from Tettnang (non-hop outside pool, 2023). PSV was reported to artificially infect a wide range of legume species, and is known to naturally infect peanut (Arachis hypogaea) [49]. Since the climatic conditions in Germany are not suitable for peanut cultivation, we do not know how this virus arrived in Germany. However, PSV may pose a risk to other legume species cultivated in Germany. PDV is known to infect stone fruits and causes significant losses. PDV was detected in a European pear (Pyrus communis) sample collected from Elbe-Saale region (Halle) (non-hop outside pool, 2023).

Mycoviruses and non-plant viruses detected in the datasets

The implementation of HTS in virome studies has revealed not only plant-associated viruses and viroids, but also viruses of other organisms that live on plants, such as fungi, oomycetes, and insects. Although mycoviruses are generally not considered pathogenic to plants, their association with pathogenic fungi suggests that they may influence the dynamics of fungal infections in plants, and thus they may play a role as biocontrol agents of fungal infections [50]. For instance, Al Rwahnih et al. [51] showed in their study that the grapevine virome is dominated by mycoviruses. In another study, nine mycoviruses were identified by Vinogradova et al. [52] in their investigation of the mycovirome of the vineyard.

We identified six mycovirus sequences present in different sample pools (Table 7). Among them, alternaria arborescens mitovirus 1 was detected in a hop pool sample from 2023. The host sequence (Alternaria arborescens) was also detected in the same sample pool (Table 8). This virus was also detected before in a virome study characterizing the mycovirome of the vineyard [52]. Its fungal host Alternaria arborescens was reported on hops [53]. Their study suggested that the fungal pathogen is latent on the leaf surface and is only pathogenic when the host is injured. Other mycoviruses were identified in hop yard pools containing both hop and non-hop plants. These mycoviruses were associated with fungal or oomycete hosts that have not previously been reported to infect hops. However, further investigation is needed. A non-plant virus was detected (Hubei sobemo-like virus 34). It is associated with stretch spiders (Tetragnatha maxillosa), which are one of the main components of the natural enemies of crop pests in ecosystems [54].

Identification of other hop pathogens in the hop pool datasets

The reuse of HTS datasets is becoming an important topic in life sciences, particularly in the frame of open science and fair data sharing. Although data reuse has its limitations and challenges, it can successfully lead to novel discoveries [55]. In plant pathology, re-analysis of previously published RNA sequencing datasets, originally used to detect viruses and viroids, allowed the detection of other plant-associated pathogens [56]. In addition, the use of the virus and viroid enrichment methods does not fully eliminate RNAs of the host plant and other microorganisms living on the surface of the plant (phyllosphere), within the plant (endosphere), as well as from insects and nematodes that have physical contact with the plant [57].

In our study, we expanded the scope of the virus and viroid focused analysis by mapping consensus sequences from the three hop pool datasets (2021, 2022, and 2023) against the NCBI BLASTn database. This approach revealed hop genome sequences as well as sequences of other microorganisms, e.g., fungi and bacteria. These microorganisms may be epiphytic, living on the plant surface, non-harmful to plants, or may have been introduced through environmental contamination, making it challenging to determine true hop pathogens. By cross-referencing the identified fungal and bacterial species with previous literature [3,53,58] we were able to identify fungi and bacteria which are pathogenic to hops. One bacterium sequence (Agrobacterium tumefaciens) was identified in the dataset of hop pool 2022. This bacterium was previously reported in hops [58]. In two pools from 2022 and 2023, Verticillium nonalfalfae (formerly V. albo-atrum) sequences were identified; V. nonalfalfae causes a severe wilt disease threating the hop production in Europe [59]. However, other pathogenic hop fungal species detected seem to be a low risk to hop production as none of them are known to cause severe diseases on hops.

Although this approach is not yet optimized to eliminate potential false positive results caused by cross contamination during sampling or sample preparation for sequencing, it highlights the importance of expanding the use of the virome datasets to unveil other plant-associated microorganisms. It may be an interesting topic for future research to achieve a more comprehensive understanding of plant health, including pathogen-pathogen and pathogen-plant interactions.

Phylogenetic analysis of CBCVd

The phylogenetic analysis of CBCVd sequences generated in this study and from sequences obtained from GenBank revealed that CBCVd isolates from hop samples share the same ancestor with CBCVd isolates found in citrus hosts with nucleotide identities ranging from 84.9% to 95.8%. These findings are in line with the Slovenian hypothesis [60] that the CBCVd outbreak in Slovenia was associated with the establishment of a hopyard on a former waste dump of citrus fruit residues. In addition, the phylogenetic analysis showed that two of the CBCVd variants identified in this study are 100% identical to the CBCVd variants from Slovenia, while other CBCVd sequence variants from Germany clustered closely with the Slovenian variants which may indicate the illegal trade of CBCVd-infected, vegetative hop material from Slovenia.

Conclusion

This study presents a comprehensive investigation of the diversity and prevalence of viruses and viroids infecting German hops. Although the sampling targeted a small number of hopyards compared to the total cultivated hop area in Germany, the results present an overview of the dominant viruses and viroids in the German hopyards. Surprisingly, in contrast to other virome studies, a smaller number of viruses and viroids were identified in hop samples. Furthermore, apart from ApMV, no common host reservoirs between hop viruses and alternative host plants were identified. However, the hop viruses and viroids identified in this study using HTS were similar to those detected in a previous study conducted more than 30 years ago using ELISA as a diagnostic tool [42]. Since then, only CBCVd was a novel pathogen infecting German hops in the Hallertau region, as it was detected for the first time in 2019. It is interesting to note that H. lupulus does not seem to be very susceptible to viral infections when compared to other crops such as tomatoes (Solanum lycopersicum), potatoes (Solanum tuberosum) or legumes (e.g., Vicia faba, Pisum sativum, Phaseolus vulgaris). However, the host change from citrus plants to hops had a severe effect on this new host plant with hop plants dying within a few years of infection. Therefore, the possibility that other viruses or viroids from different hosts may have a similar dramatic effect on hops cannot be excluded. HTS analyses of propagation material may help to provide virus- and viroid free plantlets to establish healthy production sites. The detection of fungal and bacterial hop sequences in the virome datasets also highlights the broader usefulness of HTS beyond virus discovery, including the improved understanding of interactions of organisms (within and between species) due to the high detection capacity, providing deeper insights into plant diseases and an integrated analysis for plant health.

Supporting information

S1 Table. Samples collected in 2021.

Description of all plant samples collected from three hopyards, including the sampling location, sample type (hop or non-hop), taxonomic classification, and observed symptoms.

(XLSX)

pone.0329289.s001.xlsx (16.4KB, xlsx)
S2 Table. Samples collected in 2022.

Description of all plant samples collected from six hopyards including the sampling location, sample type (hop or non-hop), taxonomic classification, and observed symptoms.

(XLSX)

pone.0329289.s002.xlsx (26.2KB, xlsx)
S3 Table. Samples collected in 2023.

Description of all plant samples collected from six hopyards including the sampling location, sample type (hop or non-hop), taxonomic classification, and observed symptoms.

(XLSX)

pone.0329289.s003.xlsx (26.2KB, xlsx)
S4 Table. Numbers of obtained raw-reads, sequences left after QC including removal of duplicate reads and numbers of assembled contigs from QC-controlled reads.

(XLSX)

pone.0329289.s004.xlsx (11.2KB, xlsx)
S5 Table. Primers used for conventional (RT-)PCR confirmation.

(XLSX)

pone.0329289.s005.xlsx (13.1KB, xlsx)
S6 Table. Viruses and viroids identified in each sequence data pool.

(XLSX)

pone.0329289.s006.xlsx (32.2KB, xlsx)

Acknowledgments

The authors would like to thank Jonas Hartrick (deceased) and Hannes Piepenbrink for the technical assistance. The authors would like to express their gratitude to the LfL, Institute for Crop Science and Plant Breeding, IPZ 5b Plant Protection, for their support and the assistance with the sampling in the Hallertau over the three years. We are grateful to HVG (Hopfenverwertungsgenossenschaft e. G.) for their support and partial funding of the sampling trip.

We would like to thank Max Weber (Hopfenversuchsanlage Strass, LTZ) for allowing us the access to their hopyards and for helping with sampling in 2022 and 2023. We would like to extend our thanks to APH e.G. Hinsdorf GbR and Taucherwald Agrar GmbH for allowing the sampling in their hopyards in Elbe-Saale region.

We are grateful to Dr. Michael Hagemann, University of Hohenheim as well as Dr. Sebastjan Radišek, Slovenian Institute of Hop Research and Brewing, for the fruitful cooperation and discussion.

We would like to extend our gratitude to Prof. Dr. Boas Pucker, University of Bonn, for the constructive comments on the manuscript.

Data Availability

The obtained datasets were archived in Sequence Read Archive (SRA) under Bioprojects: hop virome 2021: PRJNA1165201, hop virome 2022: PRJNA1167474, and hop virome 2023: PRJNA1167495. The obtained datasets were archived in Sequence Read Archive (SRA) under the Bioproject: PRJNA1254465. Variant analysis of the full genome sequence of CBCVd revealed eight CBCVd sequence variants, which were deposited in Genbank under accession numbers: PQ075924, PQ075925, PQ650572, PQ650573, PQ650574, PQ650575, PQ655430, and PQ655431.

Funding Statement

The project was supported by funds of the Federal Ministry of Agriculture, Food and Regional Identity (BMLEH) based on a decision of the Parliament of the Federal Republic of Germany via the Federal Office for Agriculture and Food (BLE) under the innovation support programme (Grant number 2818714B19). The sequencing was funded by the Euphresco projects: VirusCurate 2019-E-312: Using High Throughput Sequencing to gain insights from virus collections and strengthening the infrastructure of Plant Virus Collections and 2020-A-347: Baseline studies on virus reservoirs.

References

  • 1.Small E. A numerical and nomenclatural analysis of morpho-geographic taxa of Humulus. Systematic Botany. 1978;3:37–76. [Google Scholar]
  • 2.Pethybridge SJ, Hay FS, Barbara DJ, Eastwell KC, Wilson CR. Viruses and Viroids Infecting Hop: Significance, Epidemiology, and Management. Plant Dis. 2008;92(3):324–38. doi: 10.1094/PDIS-92-3-0324 [DOI] [PubMed] [Google Scholar]
  • 3.Gargani E, Faggioli F, Haegi A. A survey on pests and diseases of Italian Hop crops. Italus Hortus. 2018;(24):1–17. doi: 10.26353/j.itahort/2017.2.117 [DOI] [Google Scholar]
  • 4.Biendl. Hops and Health. TQ. 2009. doi: 10.1094/tq-46-2-0416-01 [DOI] [Google Scholar]
  • 5.Jakse J, Radisek S, Pokorn T, Matousek J, Javornik B. Deep‐sequencing revealed Citrus bark cracking viroid (CBCVd) as a highly aggressive pathogen on hop. Plant Pathology. 2015;64(4):831–42. doi: 10.1111/ppa.12325 [DOI] [Google Scholar]
  • 6.Kaminski K. First finding of Citrus bark cracking viroid (CBCVd) in Germany (Bavaria). Braunschweig. 2019. [Google Scholar]
  • 7.Eiras M, de Oliveira AM, de Fátima Ramos A, Harakava R, Daròs J-A. First report of citrus bark cracking viroid and hop latent viroid infecting hop in commercial yards in Brazil. J Plant Pathol. 2023;105(2):603–603. doi: 10.1007/s42161-023-01313-4 [DOI] [Google Scholar]
  • 8.Luigi M, Donati L, Sciarroni R, Gentili A, Taglienti A, Tiberini A, et al. Carlavirus Species Infecting Hop Plants in Italy: Molecular Identification and Phylogenetic Analyses of the Detected Isolates. Plants (Basel). 2023;12(19):3514. doi: 10.3390/plants12193514 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 9.Komínek P, Svoboda P, Abou ghanem-sabanadzovic N. Improved detection of Arabis mosaic virus in grapevine and hop plants. Acta Virologica. 2003. [PubMed] [Google Scholar]
  • 10.Olmos A, Boonham N, Candresse T, Gentit P, Giovani B, Kutnjak D, et al. High‐throughput sequencing technologies for plant pest diagnosis: challenges and opportunities. EPPO Bulletin. 2018;48(2):219–24. doi: 10.1111/epp.12472 [DOI] [Google Scholar]
  • 11.Lebas B, Adams I, Al Rwahnih M, Baeyen S, Bilodeau GJ, Blouin AG, et al. Facilitating the adoption of high‐throughput sequencing technologies as a plant pest diagnostic test in laboratories: A step‐by‐step description. EPPO Bulletin. 2022; 52:394–418. doi: 10.1111/epp.12863 [DOI] [Google Scholar]
  • 12.Massart S, Adams I, Al Rwahnih M, Baeyen S, Bilodeau GJ, Blouin AG, et al. Guidelines for the reliable use of high throughput sequencing technologies to detect plant pathogens and pests. Peer Community Journal. 2022;2. doi: 10.24072/pcjournal.181 [DOI] [Google Scholar]
  • 13.Hadidi A, Flores R, Candresse T, Barba M. Next-Generation Sequencing and Genome Editing in Plant Virology. Front Microbiol. 2016;7:1325. doi: 10.3389/fmicb.2016.01325 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 14.Gaafar YZA, Herz K, Hartrick J, Fletcher J, Blouin AG, MacDiarmid R, et al. Investigating the Pea Virome in Germany-Old Friends and New Players in the Field(s). Front Microbiol. 2020;11:583242. doi: 10.3389/fmicb.2020.583242 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 15.Rivarez MPS, Pecman A, Bačnik K, Maksimović O, Vučurović A, Seljak G, et al. In-depth study of tomato and weed viromes reveals undiscovered plant virus diversity in an agroecosystem. Microbiome. 2023;11(1):60. doi: 10.1186/s40168-023-01500-6 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 16.Schönegger D, Marais A, Babalola BM, Faure C, Lefebvre M, Svanella-Dumas L, et al. Carrot populations in France and Spain host a complex virome rich in previously uncharacterized viruses. PLoS One. 2023;18(8):e0290108. doi: 10.1371/journal.pone.0290108 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 17.Gholampour Z, Zakiaghl M, Asquini E, Moser M, Gualandri V, Mehrvar M, et al. Application of High-Throughput Sequencing for Comprehensive Virome Profiling in Grapevines Shows Yellows in Iran. Viruses. 2024;16(2):204. doi: 10.3390/v16020204 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 18.Stobbe AH, Daniels J, Espindola AS, Verma R, Melcher U, Ochoa-Corona F, et al. E-probe Diagnostic Nucleic acid Analysis (EDNA): a theoretical approach for handling of next generation sequencing data for diagnostics. J Microbiol Methods. 2013;94(3):356–66. doi: 10.1016/j.mimet.2013.07.002 [DOI] [PubMed] [Google Scholar]
  • 19.Espindola AS, Cardwell KF. Microbe Finder (MiFi®): Implementation of an Interactive Pathogen Detection Tool in Metagenomic Sequence Data. Plants (Basel). 2021;10(2):250. doi: 10.3390/plants10020250 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 20.Bocsanczy AM, Espindola AS, Cardwell K, Norman DJ. Development and Validation of E-Probes with the MiFi System for Detection of Ralstonia solanacearum Species Complex in Blueberries. PhytoFrontiers™. 2023;3(1):137–47. doi: 10.1094/phytofr-04-22-0043-fi [DOI] [Google Scholar]
  • 21.Dang T, Wang H, Espindola AS, Habiger J, Vidalakis G, Cardwell K. Development and Statistical Validation of E-Probe Diagnostic Nucleic Acid Analysis (EDNA) Assays for the Detection of Citrus Pathogens from Raw High-Throughput Sequencing Data. PhytoFrontiers™. 2023;3(1):113–23. doi: 10.1094/phytofr-05-22-0047-fi [DOI] [Google Scholar]
  • 22.Espindola AS, Cardwell K, Martin FN, Hoyt PR, Marek SM, Schneider W, et al. A Step Towards Validation of High-Throughput Sequencing for the Identification of Plant Pathogenic Oomycetes. Phytopathology. 2022;112(9):1859–66. doi: 10.1094/PHYTO-11-21-0454-R [DOI] [PubMed] [Google Scholar]
  • 23.Pasha A, Espindola AS, Ziebell H, Ochoa‐Corona FM. Highly Curated and Reliable E-Probes for Detection of Viral Pathogens in Unassembled High-Throughput Sequencing Datasets from Hops. PhytoFrontiers™. 2025;5(2):165–73. doi: 10.1094/phytofr-09-24-0106-fi [DOI] [Google Scholar]
  • 24.CBCVd-Monitoring in der Hallertau. https://www.lfl.bayern.de/ipz/hopfen/261410/index.php. 2025. 2025 March 21.
  • 25.Barnett OW. Surveying for plant viruses: design and considerations. Plant Virus Epidemics. 1986;:147–66. [Google Scholar]
  • 26.Poursalavati A, Larafa A, Fall ML. dsRNA-based viromics: a novel tool unveiled hidden soil viral diversity and richness. bioRxiv. 2023. [Google Scholar]
  • 27.Huelsenbeck JP, Ronquist F. MRBAYES: Bayesian inference of phylogenetic trees. Bioinformatics. 2001;17(8):754–5. doi: 10.1093/bioinformatics/17.8.754 [DOI] [PubMed] [Google Scholar]
  • 28.Edgar RC, Haas BJ, Clemente JC, Quince C, Knight R. UCHIME improves sensitivity and speed of chimera detection. Bioinformatics. 2011;27(16):2194–200. doi: 10.1093/bioinformatics/btr381 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 29.Rognes T, Flouri T, Nichols B, Quince C, Mahé F. VSEARCH: a versatile open source tool for metagenomics. PeerJ. 2016;4:e2584. doi: 10.7717/peerj.2584 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 30.Eren AM, Morrison HG, Lescault PJ, Reveillaud J, Vineis JH, Sogin ML. Minimum entropy decomposition: unsupervised oligotyping for sensitive partitioning of high-throughput marker gene sequences. ISME J. 2015;9(4):968–79. doi: 10.1038/ismej.2014.195 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 31.Menzel W, Jelkmann W, Maiss E. Detection of four apple viruses by multiplex RT-PCR assays with coamplification of plant mRNA as internal control. J Virol Methods. 2002;99(1–2):81–92. doi: 10.1016/s0166-0934(01)00381-0 [DOI] [PubMed] [Google Scholar]
  • 32.Fraile A, García-Arenal F. Environment and evolution modulate plant virus pathogenesis. Curr Opin Virol. 2016;17:50–6. doi: 10.1016/j.coviro.2016.01.008 [DOI] [PubMed] [Google Scholar]
  • 33.Ilyas R, Rohde MJ, Richert-Pöggeler KR, Ziebell H. To Be Seen or Not to Be Seen: Latent Infection by Tobamoviruses. Plants (Basel). 2022;11(16):2166. doi: 10.3390/plants11162166 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 34.Gaafar YZA, Ziebell H. Comparative study on three viral enrichment approaches based on RNA extraction for plant virus/viroid detection using high-throughput sequencing. PLoS One. 2020;15(8):e0237951. doi: 10.1371/journal.pone.0237951 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 35.Malapi-Wight M, Adhikari B, Zhou J, Hendrickson L, Maroon-Lango CJ, McFarland C, et al. HTS-Based Diagnostics of Sugarcane Viruses: Seasonal Variation and Its Implications for Accurate Detection. Viruses. 2021;13(8):1627. doi: 10.3390/v13081627 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 36.Schönegger D, Moubset O, Margaria P, Menzel W, Winter S, Roumagnac P, et al. Benchmarking of virome metagenomic analysis approaches using a large, 60+ members, viral synthetic community. J Virol. 2023;97(11):e0130023. doi: 10.1128/jvi.01300-23 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 37.PM 4/16(2): Certification scheme for hop. EPPO Bulletin. 2009;39(3):278–83. doi: 10.1111/j.1365-2338.2009.02309.x [DOI] [Google Scholar]
  • 38.Probasco G, Murphey JM. The effects of hop viruses on brewing and agronomic characteristics in the hop variety Chinook. Technical quarterly-Master Brewers Association of the Americas. 1996;33:160–5. [Google Scholar]
  • 39.Pethybridge SJ, Wilson CR, Hay FS, Leggett GW, Sherriff LJ. Mechanical transmission of Apple mosaic virus in Australian hop (Humulus lupulus) gardens. Annals of Applied Biology. 2002;141(1):77–85. doi: 10.1111/j.1744-7348.2002.tb00198.x [DOI] [Google Scholar]
  • 40.Lizotte E. Virus visible in Michigan hopyards. MSU Extension. 2016.
  • 41.Hay FS, Close RC, Hetcher JD, Ashby JW. Incidence and spread of viruses in hop (Humulus lupulusL.) in New Zealand. New Zealand Journal of Crop and Horticultural Science. 1992;20(3):319–27. doi: 10.1080/01140671.1992.10421774 [DOI] [Google Scholar]
  • 42.Eppler A. Ökologie der Hopfenviren und ihre Vektoren. Universität Gießen. 1989. [Google Scholar]
  • 43.Puchta H, Ramm K, Sänger HL. The molecular structure of hop latent viroid (HLV), a new viroid occurring worldwide in hops. Nucleic Acids Res. 1988;16(10):4197–216. doi: 10.1093/nar/16.10.4197 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 44.Adams AN, Morton A, Barbara DJ, Ridout MS. The distribution and spread of hop latent viroid within two commercial plantings of hop (Humulus lupulus). Annals of Applied Biology. 1992;121:585–92. [Google Scholar]
  • 45.Puchta H, Ramm K, Sänger HL. Nucleotide sequence of a hop stunt viroid isolate from the German grapevine cultivar “Riesling”. Nucleic Acids Res. 1988;16(6):2730. doi: 10.1093/nar/16.6.2730 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 46.Seigner L, Lutz A, Seigner E. Monitoring of hop stunt viroid and dangerous viruses in German hop gardens. International Hop Growers’ Convention. 2013. [Google Scholar]
  • 47.Štajner N, Radišek S, Mishra AK, Nath VS, Matoušek J, Jakše J. Evaluation of Disease Severity and Global Transcriptome Response Induced by Citrus bark cracking viroid, Hop latent viroid, and Their Co-Infection in Hop (Humulus lupulus L.). Int J Mol Sci. 2019;20(13):3154. doi: 10.3390/ijms20133154 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 48.Eppler A. Epidemiologische Untersuchungen zum Virusbefall in den deutschen Hopfenanbaugebieten. Universität Tübingen. 1980. [Google Scholar]
  • 49.Xu ZY, Barnett OW, Gibson PB. Characterization of peanut stunt virus strains by host reactions, serology, and RNA patterns. Phytopathology. 1986;76. [Google Scholar]
  • 50.Lopez-Jimenez J, Herrera J, Alzate JF. Expanding the knowledge frontier of mitoviruses in Cannabis sativa. Infect Genet Evol. 2023;116:105523. doi: 10.1016/j.meegid.2023.105523 [DOI] [PubMed] [Google Scholar]
  • 51.Al Rwahnih M, Daubert S, Urbez-Torres JR, Cordero F, Rowhani A. Deep sequencing evidence from single grapevine plants reveals a virome dominated by mycoviruses. Arch Virol. 2011;156(3):397–403. doi: 10.1007/s00705-010-0869-8 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 52.Vinogradova S, Porotikova E, Navrotskaya E, Galbacs ZN, Massart S, Varallyay E. The First Virome of a Russian Vineyard. Plants (Basel). 2023;12(18):3292. doi: 10.3390/plants12183292 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 53.Phalip V, Hatsch D, Laugel B, Jeltsch J-M. An overview of fungal community diversity in diseased hop plantations. FEMS Microbiol Ecol. 2006;56(2):321–9. doi: 10.1111/j.1574-6941.2006.00102.x [DOI] [PubMed] [Google Scholar]
  • 54.Baba YG, Tanaka K. Factors affecting abundance and species composition of generalist predators (Tetragnatha spiders) in agricultural ditches adjacent to rice paddy fields. Biological Control. 2016;103:147–53. doi: 10.1016/j.biocontrol.2016.09.004 [DOI] [Google Scholar]
  • 55.Sielemann K, Hafner A, Pucker B. The reuse of public datasets in the life sciences: potential risks and rewards. PeerJ. 2020;8:e9954. doi: 10.7717/peerj.9954 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 56.Haegeman A, Foucart Y, De Jonghe K, Goedefroit T, Al Rwahnih M, Boonham N, et al. Looking beyond Virus Detection in RNA Sequencing Data: Lessons Learned from a Community-Based Effort to Detect Cellular Plant Pathogens and Pests. Plants (Basel). 2023;12(11):2139. doi: 10.3390/plants12112139 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 57.Tedersoo L, Drenkhan R, Anslan S, Morales-Rodriguez C, Cleary M. High-throughput identification and diagnostics of pathogens and pests: Overview and practical recommendations. Mol Ecol Resour. 2019;19(1):47–76. doi: 10.1111/1755-0998.12959 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 58.O’Neal SD, Walsh DB, Gent DH, Barbour JD, Boydston RA, George AE, et al. Field guide for integrated pest management in hops. Pullman, WA: US Hop Industry Plant Protection Committee. 2015. [Google Scholar]
  • 59.Cregeen S, Radisek S, Mandelc S, Turk B, Stajner N, Jakse J, et al. Different Gene Expressions of Resistant and Susceptible Hop Cultivars in Response to Infection with a Highly Aggressive Strain of Verticillium albo-atrum. Plant Mol Biol Report. 2015;33(3):689–704. doi: 10.1007/s11105-014-0767-4 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 60.Radišek S, Benko-Beloglavec A. Pest risk analysis for citrus bark cracking viroid (CBCVd). Slovenian Institute of Hop Research and Brewing. 2016. https://gd.eppo.int/taxon/CBCVD0/documents [Google Scholar]

Decision Letter 0

Ahmet Uludag

Dear Dr. Ziebell,

Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process.

Both reviewers gave detailed revisions on your manuscript. I hope you can complete the revision fast.

Please submit your revised manuscript by Aug 02 2025 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org . When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file.

  • A rebuttal letter that responds to each point raised by the academic editor and reviewer(s). You should upload this letter as a separate file labeled 'Response to Reviewers'.

  • A marked-up copy of your manuscript that highlights changes made to the original version. You should upload this as a separate file labeled 'Revised Manuscript with Track Changes'.

  • An unmarked version of your revised paper without tracked changes. You should upload this as a separate file labeled 'Manuscript'.

If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols . Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols .

We look forward to receiving your revised manuscript.

Kind regards,

Ahmet Uludag, Ph.D.

Academic Editor

PLOS ONE

Journal Requirements:

When submitting your revision, we need you to address these additional requirements.

1. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at

https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and

https://journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf

2.  Thank you for stating the following financial disclosure:

“The project was supported by funds of the Federal Ministry of Food and Agriculture (BMEL) based on a decision of the Parliament of the Federal Republic of Germany via the Federal Office for Agriculture and Food (BLE) under the innovation support programme (grant number 2818714B19).

The sequencing was funded by the Euphresco projects: VirusCurate 2019-E-312: Using High Throughput Sequencing to gain insights from virus collections and strengthening the infrastructure of Plant Virus Collections and 2020-A-347: Baseline studies on virus reservoirs. “

Please state what role the funders took in the study. If the funders had no role, please state: "The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript."

If this statement is not correct you must amend it as needed.

Please include this amended Role of Funder statement in your cover letter; we will change the online submission form on your behalf.

3. Please review your reference list to ensure that it is complete and correct. If you have cited papers that have been retracted, please include the rationale for doing so in the manuscript text, or remove these references and replace them with relevant current references. Any changes to the reference list should be mentioned in the rebuttal letter that accompanies your revised manuscript. If you need to cite a retracted article, indicate the article’s retracted status in the References list and also include a citation and full reference for the retraction notice.

[Note: HTML markup is below. Please do not edit.]

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. Is the manuscript technically sound, and do the data support the conclusions?

Reviewer #1: Yes

Reviewer #2: Yes

**********

2. Has the statistical analysis been performed appropriately and rigorously? -->?>

Reviewer #1: Yes

Reviewer #2: Yes

**********

3. Have the authors made all data underlying the findings in their manuscript fully available??>

The PLOS Data policy

Reviewer #1: Yes

Reviewer #2: Yes

**********

4. Is the manuscript presented in an intelligible fashion and written in standard English??>

Reviewer #1: Yes

Reviewer #2: Yes

**********

Reviewer #1: The manuscript “Virus and viroid diversity in hops, investigating the German hop virome” submitted by Dr. Ziebell presents comprehensive and well-structured study on the Hop virome in different hop growing areas in Germany. The study provides valuable insights into the virome of German hops using high-throughput sequencing over multiple years and regions.

While the manuscript is scientifically sound and methodologically robust, there are several areas where clarification, additional detail, or minor revisions would enhance the clarity and impact of the work. These are outlined below:

Lines 52-55: Please include the full names of all viruses and viroids mentioned, even if they were previously introduced in the abstract. This ensures clarity and consistency for readers who may refer to specific sections independently of the abstract.

Materials and methods:

For sampling in 2022 and 2023 add the information which hopyard was collected in which year(s). In Table 1 you have the data about temperature on sampling day, then you never refer to this data anymore. It can be moved to some supplementary table and instead the data regarding the exact year of collection should be added.

All supplementary tables should have titles in the beginning, or it can be the first sheet of the table. Now they are in the end of the manuscript, but it would be easier to reader is the titles aro also in the tables.

Supplementary S2 Table. In some tables you have “Sample No.” information in some you don’t have it. Suggest unifying.

Did you perform any search for potentially new viruses/viroid which are more divergent from the RefSeq sequences. If I am not mistaken mapping parameters of “High sensitivity/Medium” are something 80–85% regarding similarity of sequences. What about potentially more divergent sequences? Suggest Diamond BlastX or pFam search.

Which controls you included in the sequencing. Was all sequencing performed in one lane? How are you sure that the result where you have “Sequencing depth” low or very low is not cross talk?

Lines 171-173 you wrote that you designed primers for identified viruses, then in S4 you have some primers from literature (with references). Please, be clear about this in the text and include full references in the S4.

In S5 Table you have a column “Seq depth” is it a “average coverage” at one place you describe it, but it should be explained in each instance, and you also use sequencing dept od 150bp, so it can be confusing for potential reader. Did you apply any threshold when creating final consensus sequences? Instead of “Sample” it should be “Sequencing library”

I suggest creating new Supplementary table where you will for all sequenced libraries collect following data (from table S5) “Library read length” “Total raw reads” and “Reads no. after QC” and you can include year f sampling (in that way you will address one of my previous comments).

Results:

In line 44 of S5 you have for “Total raw reads” and “Reads no. after QC” numbers which are probably belonging to other library or the result is from another library?

In table 3 you have most data repeated from S5. I suggest removing most of the repeated data and include the results of Blast (nucleotide and amino acid-where applicable) for the consensus sequence.

In Table 3 for virodid you have more than one accession. Describe very clearly how you obtained those sequences (how you called variants how you are sure that those are not “artificially” assembled sequences). I understand that they are most probably consequence of pooling samples, but you need to be very clear about how your decisions were made.

Blast results of consensus sequences should be added Table 6.

In table 7 add the column of the pathogen detected in the data (if possible). For example you have Verticilium wilt 2 times with different years, are they different Verticilium species?

Unify writing of GebBank (sometimes it is written Genbank).

In figure 4 caption indicate what number on branch represents.

Discussion:

The discussion part can be shortened.

Regarding ApMV can the detection in hop be consequence of pollen contamination?

Reviewer #2: The manuscript PONE-D-25-26477, entitled "Virus and viroid diversity in hops: Investigating the German hop virome", presents an important study on the prevalence of viruses and viroids in hop production areas in Germany. It also explores potential reservoirs of the viroid CBCVd, which was recently detected in hops and is known to cause severe damage to production. The analysis is based on high-throughput sequencing (HTS), and the resulting data were also used to detect the presence of mycoviruses and other hop pathogens in the collected samples. From an epidemiological perspective, the phylogenetic analysis of CBCVd is particularly noteworthy. It demonstrates that sequences from hop samples share high identity with variants previously identified in citrus plants, supporting earlier hypotheses about cross-host transmission from citrus fruits. The results highlight the importance of producing and trading healthy planting material. Since hop cultivation relies on vegetative propagation, infected material can readily transmit dangerous pathogens. Before publishing I recommend few minor corrections:

Page 5, Line 103: Please clarify what is meant by "outside the hop yard." What was the approximate distance from the nearest hop yard? Additionally, why were wild hop plants—which often grow in the vicinity of hop yards—not included in the sampling?

Page 10, Lines 210–215 and Table 3: The results for the “hop pool” are presented and discussed. I suggest including the data for the “hop yard pool” as well, to allow for comparison and discussion of samples originating from different hop-growing regions.

Page 14, Table 7: Please add a column listing the Latin names of the fungi and bacteria identified in the RNA-seq dataset. Consider removing the reference column, as the cited sources do not represent first reports of the listed pathogens.

Page 18, Lines 329–331: Please consider adding that the lower diversity may also be attributed to the fact that, for more than three decades, hop planting material in Germany has been propagated through certified production of virus-free material in hop nurseries and virus-free hop yards, in accordance with the EPPO standard PM 4/16 (2) – Certification Scheme for Hop.

Page 19, Line 362: correct to uncertified planting material.

Page 19, Line 362-368: ApMV is the most widespread and economically important ilarvirus affecting hop. Numerous studies conducted in the 1990s in the UK, USA, Czech Republic, Poland, and Germany demonstrated its negative impact on hop yield and quality. Several studies have also shown a synergistic effect between ApMV and other hop viruses. These findings prompted the implementation of virus-free hop planting material production in most European hop-growing countries. I suggest rewriting this section to include these points, supported by relevant references (see, for example, Pethybridge et al., 2008).

Page 20, Lines 388–392, Reference 45: Please add that during the monitoring period (2008–2012), HSVd was detected in a few hop plants, which were subsequently eradicated.

Page 20, Line 399: planting material

Page 21, Lines 420: “Earth dams” is not correct term. Probably you mean hop hilling.

Page 21, Line 423: add what kind of orchards. Apple?

Page 21, Line 425-427: Apple plants are not host of Phorodon humuli. The winter hosts are Prunus sp.

Page 24, Line 489: Agrobacterium tumefaciens, and has been reported on nearly every country where hops are commercially grown.

Page 24, Line 490: Verticillium albo-atrum. The species on hop is now classified as V. nonalfalfae.

**********

what does this mean? ). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy

Reviewer #1: No

Reviewer #2: No

**********

[NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.]

While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/ . PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org

PLoS One. 2025 Aug 7;20(8):e0329289. doi: 10.1371/journal.pone.0329289.r002

Author response to Decision Letter 1


3 Jul 2025

We would like to thank the academic editor and both reviewers for their valuable feedback and for evaluating our manuscript. We have revised the manuscript accordingly and provided detailed responses to each comment below. All changes are marked with track changes in the revised manuscript.

All supplementary tables have been updated according to the reviewers’ suggestions.

All tables (except table 2) have been updated according to the reviewers’ suggestions.

Reviewer #1: The manuscript “Virus and viroid diversity in hops, investigating the German hop virome” submitted by Dr. Ziebell presents comprehensive and well-structured study on the Hop virome in different hop growing areas in Germany. The study provides valuable insights into the virome of German hops using high-throughput sequencing over multiple years and regions.

While the manuscript is scientifically sound and methodologically robust, there are several areas where clarification, additional detail, or minor revisions would enhance the clarity and impact of the work.

These are outlined below:

Lines 52-55: Please include the full names of all viruses and viroids mentioned, even if they were previously introduced in the abstract. This ensures clarity and consistency for readers who may refer to specific sections independently of the abstract.

Thank you for the suggestion. It has been addressed.

Materials and methods:

For sampling in 2022 and 2023 add the information which hopyard was collected in which year(s). In Table 1 you have the data about temperature on sampling day, then you never refer to this data anymore. It can be moved to some supplementary table and instead the data regarding the exact year of collection should be added.

Samples were collected from the same hopyards in 2022 and 2023, as shown in Table 1, marked with “X”. An explanation has been added to the heading of Table 1.

Table 1 has been updated, and the temperature information has been moved to Supplementary Tables 1, 2, and 3.

All supplementary tables should have titles in the beginning, or it can be the first sheet of the table. Now they are in the end of the manuscript, but it would be easier to reader is the titles aro also in the tables.

The title of each supplementary table has been added in the first sheet of the Excel file.

Supplementary S2 Table. In some tables you have “Sample No.” information in some you don’t have it. Suggest unifying.

We unified the format by removing the “Sample No.” column because it refers to the sample number in our internal database.

Did you perform any search for potentially new viruses/viroid which are more divergent from the RefSeq sequences.

If I am not mistaken mapping parameters of “High sensitivity/Medium” are something 80–85% regarding similarity of sequences.

What about potentially more divergent sequences? Suggest Diamond BlastX or pFam search.

Thank you for this valuable comment. Yes, we explored the possibility of detecting novel viruses or viroids. We further analyzed consensus sequences derived from de novo assembly that showed any similarity to viral or viroid sequences using both BLASTn and BLASTx against the NCBI non-redundant database to identify potential matches. We also performed additional BLASTn searches against the broader NCBI nucleotide database for sequences with low pairwise identity to known viruses or viroids in RefSeq. However, these sequences were highly similar to known plant-derived sequences or to other microorganisms present in the sample.

As mentioned in the M&M, the “High sensitivity/Medium” setting was used to re-map the raw reads to the selected reference genomes, ensuring accurate read abundance quantification. This step followed the identification and taxonomic assignment of candidate viral sequences and was not the primary method used for discovering novel viruses. However, no novel viral or viroid species were identified in this study.

We focused on the identified hop virus and viroid sequences from the German hopyards, all of which were submitted to GenBank (see Table 3).

Which controls you included in the sequencing.

Was all sequencing performed in one lane?

How are you sure that the result where you have “Sequencing depth” low or very low is not cross talk?

Thanks for this important comment. Although internal (spiked) control was not included in the sequencing libraries, several quality indicators confirm the efficiency and reliability of our sequencing runs.

The target for each dataset was 10 million reads. In practice, we obtained at least 12 million raw paired-end reads per dataset (S4 Table).

Furthermore, the successful mapping of more than 100 reads to small genomes, such as viroids, indicates that the libraries were suitable for downstream analysis (S6 Table).

Consequently, these results support the efficiency of the sequencing despite the absence of an internal control. However, we acknowledge the importance of including internal controls in sequencing experiments and will use them in future studies to strengthen quality of the results.

According to the service provider, samples from the same year were sequenced in the same lane unless a sample had to be resubmitted due to an initially low RNA concentration.

We acknowledge that low-level cross-talk between samples cannot be fully excluded during library preparation or sequencing. To address this issue, we performed RT-PCR using RNA extracted from each sample pool to confirm the presence or absence of the identified virus or viroid. This validation step helped us distinguish between true low-titer infections and potential index cross-talk.

We also recognize that low sequencing depth may indicate a low viral or viroid titer in the sample. For this reason, we did not apply a strict cut-off threshold for read depth in our detection criteria. However, since sequencing depth per virus or viroid was not directly relevant to our study’s main objective of detecting “presence or absence” rather than performing quantitative transcriptomics, we have removed “Seq depth” from S6 Table.

Since not all viral genomes were fully recovered, we changed the “Seq depth” column in S6 Table to “average coverage”.

Lines 171-173 you wrote that you designed primers for identified viruses, then in S4 you have some primers from literature (with references). Please, be clear about this in the text and include full references in the S4.

In lines 171-173 we are referring to the tool used for primer design. A clarification has been added in lines 204-205.

In S5 Table you have a column “Seq depth” is it a “average coverage” at one place you describe it, but it should be explained in each instance, and you also use sequencing dept od 150bp, so it can be confusing for potential reader. Did you apply any threshold when creating final consensus sequences? Instead of “Sample” it should be “Sequencing library”

Thanks for the correction. As mentioned above that the “Seq depth” column has been substituted with “Average coverage”. The recovered length (bp) and (%) of each identified virus and viroid genomes have been added to S6 Table.

At least 40% of the virus genomes and 100% of the viroid genomes were recovered and confirmed by another diagnostic test to give the results of this study more reliability.

I suggest creating new Supplementary table where you will for all sequenced libraries collect following data (from table S5) “Library read length” “Total raw reads” and “Reads no. after QC” and you can include year f sampling (in that way you will address one of my previous comments).

Thanks for this suggestion. A new supplementary table (S4) has been created to describe the content of each Bioproject of RNA-seq.

The information related to the sequencing libraries has been removed from S6 Table to avoid redundancy.

Results:

In line 44 of S5 you have for “Total raw reads” and “Reads no. after QC” numbers which are probably belonging to other library or the result is from another library?

It has been corrected. The “Total raw reads” and “Reads no. after QC” numbers have been moved to the S4 Table.

In table 3 you have most data repeated from S5. I suggest removing most of the repeated data and include the results of Blast (nucleotide and amino acid-where applicable) for the consensus sequence.

To avoid repetition: the genome recovery has been moved to S6 Table, and BLASTn and BLASTx results have been added to Tables 5, 6, and 7.

In addition, to make the results easier to understand and compare, so we have created a new table (Table 3) presenting all detected viruses and viroids in all sample pools over the three years.

In Table 3 for virodid you have more than one accession. Describe very clearly how you obtained those sequences (how you called variants how you are sure that those are not “artificially” assembled sequences). I understand that they are most probably consequence of pooling samples, but you need to be very clear about how your decisions were made.

Thank you for mentioning this important point. We focused particularly on CBCVd diversity because this viroid recently emerged in German hop cultivation and is known to cause significant economic losses in European hop production. The observed sequence variation among CBCVd isolates supports the hypothesis that the viroid jumped from infected citrus plants to hops.

We submitted multiple viroid sequences to GenBank based on the identification of sequence variants within pooled samples. These variants were identified after de novo assembly and taxonomic identification. They were further validated through reference-guided mapping. This ensured that the identified sequences were true variants and not artifacts of sequencing or misassembly.

The following criteria were considered:

1. Sequence variants were only considered if the coverage depth at the site of variation was ≥5 reads, which reduces the likelihood that sequencing errors will be mistaken for real variants.

2. Each variant sequence was identified at least in one distinct sample pool (i.e., from different hopyards or hop pools).

3. We identified and verified variants using the Variation/SNPs tool in Geneious Prime, which allowed us to visualize and manually confirm SNPs across the viroid genomes.

Due to the use of pooled RNA samples and the known high mutation rates of viroids (Flores et al., 2014), CBCVd and HLVd quasispecies were expected.

The predominance of CBCVd sequences that were identical to or highly similar to Slovenian isolates supported the reliability of our methodology for variant analysis.

The analysis details have been added to M&M. In addition, a clarification has been added as a footnote to Table 3.

Blast results of consensus sequences should be added Table 6.

It has been added to the respective Tables.

In table 7 add the column of the pathogen detected in the data (if possible). For example you have Verticilium wilt 2 times with different years, are they different Verticilium species?

A column of “Pathogen” containing the Latin names of detected pathogen has been added to the Table 7.

Unify writing of GebBank (sometimes it is written Genbank).

It has been unified “GenBank”.

In figure 4 caption indicate what number on branch represents.

Thanks for the suggestion. The information has been added to the caption.

Discussion:

The discussion part can be shortened.

We acknowledge the reviewer’s suggestion to shorten the discussion section. After carefully reviewing the section, we made minor edits to improve clarity and conciseness. However, we believe that a detailed discussion of our findings and a comparison with previous studies is necessary to provide context for the results and emphasize the importance of our work. Therefore, we have retained the structured format, beginning with an overview of the study and its main findings and then providing details on the detected pathogens and their potential impacts on hops.

Regarding ApMV can the detection in hop be consequence of pollen contamination?

In general, fruit trees are flowering in Germany in April/May. Our sampling time was at the end of June/beginning of July so we think it is very unlikely that ApMV-contaminated apple pollen was still present as residual surface contaminant on our hop samples.

----------------------------------------------------------------------------------

Reviewer #2: The manuscript PONE-D-25-26477, entitled "Virus and viroid diversity in hops: Investigating the German hop virome", presents an important study on the prevalence of viruses and viroids in hop production areas in Germany. It also explores potential reservoirs of the viroid CBCVd, which was recently detected in hops and is known to cause severe damage to production. The analysis is based on high-throughput sequencing (HTS), and the resulting data were also used to detect the presence of mycoviruses and other hop pathogens in the collected samples. From an epidemiological perspective, the phylogenetic analysis of CBCVd is particularly noteworthy. It demonstrates that sequences from hop samples share high identity with variants previously identified in citrus plants, supporting earlier hypotheses about cross-host transmission from citrus fruits. The results highlight the importance of producing and trading healthy planting material. Since hop cultivation relies on vegetative propagation, infected material can readily transmit dangerous pathogens. Before publishing I recommend few minor corrections:

Page 5, Line 103: Please clarify what is meant by "outside the hop yard." What was the approximate distance from the nearest hop yard? Additionally, why were wild hop plants—which often grow in the vicinity of hop yards—not included in the sampling?

A clarification has been added to “outside the hopyard”. The samples were randomly collected in small proximity to the hopyard itself, approximately not exceeding 50 meters. Wild hop plants were not present near the hopyards; due to the risk imposed by male wild hop plants, any wild growing hops is generally eradicated to prevent pollination of the production site.

Page 10, Lines 210–215 and Table 3: The results for the “hop pool” are presented and discussed. I suggest including the data for the “hop yard pool” as well, to allow for comparison and discussion of samples originating from different hop-growing regions.

Thank you for your suggestion. The detailed analysis results for all hopyard pools are listed in S6 Table. However, we created a new table (Table 3) which shows all the viruses and viroids detected in the hopyard pools, as well as in the hop and non-hop (inside and outside) pools over the three sampling years.

Page 14, Table 7: Please add a column listing the Latin names of the fungi and bacteria identified in the RNA-seq dataset. Consider removing the reference column, as the cited sources do not represent first reports of the listed pathogens.

A new column “Pathogen” has been added, containing the Latin names of the detected bacteria and fungi. The reference list has been removed, and the references are now cited in the discussion section.

We agree that these references were not the first reports of these pathogens. However, they contain valuable information about pathogens that infect hops. We used these references to overlap the RNA-seq analysis results with known hop pathogens in order to determine which of the identified pathogens infect hops.

Page 18, Lines 329–331: Please consider adding that the lower diversity may also be attributed to the fact that, for more than three decades, hop planting material in Germany has been propagated through certified production of virus-free material in hop nurseries and virus-free hop yards, in accordance with the EPPO standard PM 4/16 (2) – Certification Scheme for Hop.

Thank you for this valuable suggestion. It has been added to the discussion lines 340-345.

Page 19, Line 362: correct to uncertified planting material.

It has been corrected.

Page 19, Line 362-368: ApMV is the most widespread and economically important ilarvirus affecting hop. Numerous studies conducted in the 1990s in the UK, USA, Czech Republic, Poland, and Germany demonstrated its negative impact on hop yield and quality. Several studies have also shown a syn

Attachment

Submitted filename: Response to Reviewers.docx

pone.0329289.s007.docx (25.5KB, docx)

Decision Letter 1

Ahmet Uludag

Dear Dr. Ziebell,

Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process.

I need a rebuttal letter with your submisson

Please submit your revised manuscript by Aug 22 2025 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org . When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file.

  • A rebuttal letter that responds to each point raised by the academic editor and reviewer(s). You should upload this letter as a separate file labeled 'Response to Reviewers'.

  • A marked-up copy of your manuscript that highlights changes made to the original version. You should upload this as a separate file labeled 'Revised Manuscript with Track Changes'.

  • An unmarked version of your revised paper without tracked changes. You should upload this as a separate file labeled 'Manuscript'.

If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols . Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols .

We look forward to receiving your revised manuscript.

Kind regards,

Ahmet Uludag, Ph.D.

Academic Editor

PLOS ONE

Journal Requirements:

Please review your reference list to ensure that it is complete and correct. If you have cited papers that have been retracted, please include the rationale for doing so in the manuscript text, or remove these references and replace them with relevant current references. Any changes to the reference list should be mentioned in the rebuttal letter that accompanies your revised manuscript. If you need to cite a retracted article, indicate the article’s retracted status in the References list and also include a citation and full reference for the retraction notice.

Additional Editor Comments:

I think your manuscript is only one step ahead from publishing. Could you please write a good rebuttal for reviewer1's concern and make all rquested changes if possible.

[Note: HTML markup is below. Please do not edit.]

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

Reviewer #1: All comments have been addressed

Reviewer #2: All comments have been addressed

**********

2. Is the manuscript technically sound, and do the data support the conclusions??>

Reviewer #1: Yes

Reviewer #2: Yes

**********

3. Has the statistical analysis been performed appropriately and rigorously? -->?>

Reviewer #1: N/A

Reviewer #2: Yes

**********

4. Have the authors made all data underlying the findings in their manuscript fully available??>

The PLOS Data policy

Reviewer #1: Yes

Reviewer #2: Yes

**********

5. Is the manuscript presented in an intelligible fashion and written in standard English??>

Reviewer #1: Yes

Reviewer #2: Yes

**********

Reviewer #1: On more thing needs to be addressed, in the supplementary table S4, number of reads after QC is very low, which is unexpected. Did you maybe preformed host plant genome subtraction and then you reported the number of reads after that? If that is true please state it in the table and in the manuscript where you describe bioinfo pipeline. If this is not the case, please re-check the data you provided in the supplementary table S4, because it is really suspicious that after QC sometimes you have only about 5% of reads left, this shouldn't be the case if the sequencing went well which based on your other presented data was logical.

Reviewer #2: The manuscript PONE-D-25-26477-R1, entitled "Virus and viroid diversity in hops: Investigating the German hop virome", has been revised according to the reviewers' suggestions. I have no further comments and therefore recommend that the revised manuscript be accepted for publication.

**********

what does this mean? ). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy

Reviewer #1: No

Reviewer #2: No

**********

[NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.]

While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/ . PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org

PLoS One. 2025 Aug 7;20(8):e0329289. doi: 10.1371/journal.pone.0329289.r004

Author response to Decision Letter 2


10 Jul 2025

Reviewer #1:

On more thing needs to be addressed, in the supplementary table S4, number of reads after QC is very low, which is unexpected. Did you maybe preformed host plant genome subtraction and then you reported the number of reads after that? If that is true please state it in the table and in the manuscript where you describe bioinfo pipeline. If this is not the case, please re-check the data you provided in the supplementary table S4, because it is really suspicious that after QC sometimes you have only about 5% of reads left, this shouldn't be the case if the sequencing went well which based on your other presented data was logical.

We also noticed the low number of reads in several datasets after quality control, as presented in S4 Table. We would like to clarify that we did not perform host plant genome subtraction during the data analysis. The low number of retained reads after quality control is can be attributed to two factors:

1- Duplicate reads from library re-sequencing:

As stated in the manuscript, we initially requested that the service provider to generate approximately 10 million paired-end reads per library. According to the service provider, in some cases, fewer reads were obtained initially, so the service re-sequenced the same library to reach the requested number. However, this re-sequencing introduced a high number of technical duplicate reads, which increased the total number of raw reads artificially.

We investigated this issue by analyzing some of our datasets in Geneious Prime with the Dedupe tool vs. 38.84 “Duplicate Read Remover” using the default settings. The results confirmed the presence of a substantial number of duplicate reads, which were subsequently filtered out during normalization with BBNorm alongside other low-quality reads with a Q-score below 20.

2- The implementation of virus/viroid enrichment method:

We performed virus and viroid enrichment (M&M). This method reduces host and microbial RNA that present in the sample. Although this method improves the detection of viruses and viroids, it results in lower total RNA yields. Sequencing providers sometimes misinterpret the low RNA yields as poor quality, so they repeated library sequencing without taking the enrichment strategy into account, and this happened in our case (clarified by the service provider AFTER we obtained the raw reads).

We used only the acquired reads after QC for downstream analysis and found them to be sufficient for detection of partial or full genomes of viruses and viroids. In addition, we were also able to identify other microorganisms and plant sequences. A new column containing the number of “obtained contigs” has been added to S4 Table.

Reviewer #2:

The manuscript PONE-D-25-26477-R1, entitled "Virus and viroid diversity in hops: Investigating the German hop virome", has been revised according to the reviewers' suggestions. I have no further comments and therefore recommend that the revised manuscript be accepted for publication.

Thank you very much for revising our manuscript - we appreciate your valuable feedback.

Attachment

Submitted filename: Rebuttal letter.docx

pone.0329289.s008.docx (21.6KB, docx)

Decision Letter 2

Ahmet Uludag

Virus and viroid diversity in hops, investigating the German hop virome

PONE-D-25-26477R2

Dear Dr. Ziebell,

We’re pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it meets all outstanding technical requirements.

Within one week, you’ll receive an e-mail detailing the required amendments. When these have been addressed, you’ll receive a formal acceptance letter and your manuscript will be scheduled for publication.

An invoice will be generated when your article is formally accepted. Please note, if your institution has a publishing partnership with PLOS and your article meets the relevant criteria, all or part of your publication costs will be covered. Please make sure your user information is up-to-date by logging into Editorial Manager at Editorial Manager®  and clicking the ‘Update My Information' link at the top of the page. If you have any questions relating to publication charges, please contact our Author Billing department directly at authorbilling@plos.org.

If your institution or institutions have a press office, please notify them about your upcoming paper to help maximize its impact. If they’ll be preparing press materials, please inform our press team as soon as possible -- no later than 48 hours after receiving the formal acceptance. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org.

Kind regards,

Ahmet Uludag, Ph.D.

Academic Editor

PLOS ONE

Additional Editor Comments (optional):

congratulations

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

Reviewer #1: All comments have been addressed

Reviewer #2: All comments have been addressed

**********

2. Is the manuscript technically sound, and do the data support the conclusions??>

Reviewer #1: Yes

Reviewer #2: Yes

**********

3. Has the statistical analysis been performed appropriately and rigorously? -->?>

Reviewer #1: N/A

Reviewer #2: Yes

**********

4. Have the authors made all data underlying the findings in their manuscript fully available??>

The PLOS Data policy

Reviewer #1: Yes

Reviewer #2: Yes

**********

5. Is the manuscript presented in an intelligible fashion and written in standard English??>

Reviewer #1: Yes

Reviewer #2: Yes

**********

Reviewer #1: Authors addressed all comments. I do not have any future questions regarding this manuscript for authors to address.

Reviewer #2: I have no further comments and therefore recommend that the revised manuscript be accepted for publication.

**********

what does this mean? ). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy

Reviewer #1: No

Reviewer #2: Yes:  Sebastjan Radišek, Plant Protection Department, Slovenian Institute of Hop Research and Brewing

**********

Acceptance letter

Ahmet Uludag

PONE-D-25-26477R2

PLOS ONE

Dear Dr. Ziebell,

I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS ONE. Congratulations! Your manuscript is now being handed over to our production team.

At this stage, our production department will prepare your paper for publication. This includes ensuring the following:

* All references, tables, and figures are properly cited

* All relevant supporting information is included in the manuscript submission,

* There are no issues that prevent the paper from being properly typeset

You will receive further instructions from the production team, including instructions on how to review your proof when it is ready. Please keep in mind that we are working through a large volume of accepted articles, so please give us a few days to review your paper and let you know the next and final steps.

Lastly, if your institution or institutions have a press office, please let them know about your upcoming paper now to help maximize its impact. If they'll be preparing press materials, please inform our press team within the next 48 hours. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org.

If we can help with anything else, please email us at customercare@plos.org.

Thank you for submitting your work to PLOS ONE and supporting open access.

Kind regards,

PLOS ONE Editorial Office Staff

on behalf of

Dr. Ahmet Uludag

Academic Editor

PLOS ONE

Associated Data

    This section collects any data citations, data availability statements, or supplementary materials included in this article.

    Supplementary Materials

    S1 Table. Samples collected in 2021.

    Description of all plant samples collected from three hopyards, including the sampling location, sample type (hop or non-hop), taxonomic classification, and observed symptoms.

    (XLSX)

    pone.0329289.s001.xlsx (16.4KB, xlsx)
    S2 Table. Samples collected in 2022.

    Description of all plant samples collected from six hopyards including the sampling location, sample type (hop or non-hop), taxonomic classification, and observed symptoms.

    (XLSX)

    pone.0329289.s002.xlsx (26.2KB, xlsx)
    S3 Table. Samples collected in 2023.

    Description of all plant samples collected from six hopyards including the sampling location, sample type (hop or non-hop), taxonomic classification, and observed symptoms.

    (XLSX)

    pone.0329289.s003.xlsx (26.2KB, xlsx)
    S4 Table. Numbers of obtained raw-reads, sequences left after QC including removal of duplicate reads and numbers of assembled contigs from QC-controlled reads.

    (XLSX)

    pone.0329289.s004.xlsx (11.2KB, xlsx)
    S5 Table. Primers used for conventional (RT-)PCR confirmation.

    (XLSX)

    pone.0329289.s005.xlsx (13.1KB, xlsx)
    S6 Table. Viruses and viroids identified in each sequence data pool.

    (XLSX)

    pone.0329289.s006.xlsx (32.2KB, xlsx)
    Attachment

    Submitted filename: Response to Reviewers.docx

    pone.0329289.s007.docx (25.5KB, docx)
    Attachment

    Submitted filename: Rebuttal letter.docx

    pone.0329289.s008.docx (21.6KB, docx)

    Data Availability Statement

    The obtained datasets were archived in Sequence Read Archive (SRA) under Bioprojects: hop virome 2021: PRJNA1165201, hop virome 2022: PRJNA1167474, and hop virome 2023: PRJNA1167495. The obtained datasets were archived in Sequence Read Archive (SRA) under the Bioproject: PRJNA1254465. Variant analysis of the full genome sequence of CBCVd revealed eight CBCVd sequence variants, which were deposited in Genbank under accession numbers: PQ075924, PQ075925, PQ650572, PQ650573, PQ650574, PQ650575, PQ655430, and PQ655431.


    Articles from PLOS One are provided here courtesy of PLOS

    RESOURCES