Skip to main content
PLOS One logoLink to PLOS One
. 2021 Mar 12;16(3):e0248418. doi: 10.1371/journal.pone.0248418

BlueFeather, the singleton that wasn’t: Shared gene content analysis supports expansion of Arthrobacter phage Cluster FE

Stephanie Demo 1,#, Andrew Kapinos 1,#, Aaron Bernardino 1, Kristina Guardino 1, Blake Hobbs 1, Kimberly Hoh 1, Edward Lee 1, Iphen Vuong 1, Krisanavane Reddi 1, Amanda C Freise 1, Jordan Moberg Parker 1,*
Editor: Eric Charles Dykeman2
PMCID: PMC7954295  PMID: 33711060

Abstract

Bacteriophages (phages) exhibit high genetic diversity, and the mosaic nature of the shared genetic pool makes quantifying phage relatedness a shifting target. Early parameters for clustering of related Mycobacteria and Arthrobacter phage genomes relied on nucleotide identity thresholds but, more recently, clustering of Gordonia and Microbacterium phages has been performed according to shared gene content. Singleton phages lack the nucleotide identity and/or shared gene content required for clustering newly sequenced genomes with known phages. Whole genome metrics of novel Arthrobacter phage BlueFeather, originally designated a putative singleton, showed low nucleotide identity but high amino acid and gene content similarity with Arthrobacter phages originally assigned to Clusters FE and FI. Gene content similarity revealed that BlueFeather shared genes with these phages in excess of the parameter for clustering Gordonia and Microbacterium phages. Single gene analyses revealed evidence of horizontal gene transfer between BlueFeather and phages in unique clusters that infect a variety of bacterial hosts. Our findings highlight the advantage of using shared gene content to study seemingly genetically isolated phages and have resulted in the reclustering of BlueFeather, a putative singleton, as well as former Cluster FI phages, into a newly expanded Cluster FE.

Introduction

Bacteriophages are ubiquitous biological entities with an estimated 1031 phage particles on Earth. Assuming an average length of 200 nm, they would extend 200 million light years if stacked head-to-tail [1]. Phages are found in all ecosystems in which bacteria exist and function as drivers of bacterial evolution [2]. They exhibit horizontal gene transfer (HGT) with each other and with bacteria, resulting in the diverse and mosaic nature of phage genomes [3]. Despite their incredible prevalence in the environment, phages remain largely understudied [4].

Previous research on mycobacteriophages concluded that phages may exhibit a continuum of diversity, wherein genes are constantly being shuffled amongst the phage population, resulting in shared genes and sequences between different clusters [5]. The immense and ever-expanding diversity of phage genomes has historically been categorized in terms of nucleotide sequence conservation, with a minimum 50% nucleotide identity and 50% span length to at least one phage in a cluster to warrant membership [6, 7]. A mass scale study on Gordonia phages also identified a spectrum of genetic diversity, as clusters did not have clear boundaries [8]. Numerous phages lacked the requirement of 50% nucleotide identity but shared many genes, suggesting a relatedness not captured by nucleotide comparisons alone. This relatedness was confirmed with a gene content network phylogeny, and subsequently the cluster assignment parameter for Gordonia phages [8], and later for Microbacterium phages [9], was adjusted to 35% shared gene content with at least one phage in a cluster. Mycobacteriophages, as well as Gordonia and Microbacterium phages, exhibited this spectrum; however, the extent of diversity varies depending on the current known phage population, which in turn affects how clustering is carried out. Arthrobacter phages were previously found to exchange genes more slowly than Gordonia phages, and the 50% nucleotide clustering parameter was considered sufficient at the time [8]. Further studies on Arthrobacter phages found these phages to be genetically isolated with highly variable gene content for phages that can infect a range of host species. With this great diversity, nucleotide identity was used to separate Arthrobacter phages into 10 distinct clusters and 2 singletons [7], and this parameter has been considered sufficient to categorize the limited number of Arthrobacter phages until recently.

Singleton phages can serve as the seeds to start new clusters or be extremely distinct, as they lack the nucleotide identity and/or shared genes required for clustering with known phages. In this study, the genome of novel Arthrobacter phage BlueFeather was examined for nucleotide and amino acid identity with other known phages. BlueFeather lacked sufficient nucleotide conservation for clustering according to nucleotide-based parameters, and was thus designated a putative singleton. Phage BlueFeather did, however, have notable amino acid conservation and shared gene content with other Arthrobacter phages previously assigned to Clusters FE and FI, suggesting it may not be as isolated as its putative singleton status implied. The outcomes of this research on phage BlueFeather provided evidence for the reclustering of phage BlueFeather, as well as phages formerly assigned to Cluster FI, into a newly expanded Cluster FE.

Materials and methods

Sample collection and direct isolation

Soil was collected from Los Angeles, CA in a residential area located at 34.05638889° N, 118.445010000° W. Direct isolation of phages was performed by shaking a soil sample and 2X PYCa broth (Yeast Extract 1 g/L, Peptone 15 g/L, 4.5mM CaCl2, Dextrose 0.1%) in conical tubes at 250 RPM at 25°C for 1.5 hours. After incubation, the solution was filtered through a 0.22 μm syringe and spotted onto Arthrobacter globiformis B-2979 (A. globiformis). Plaque purifications were performed as described previously and a high titer lysate was filter-sterilized to be used in subsequent characterization experiments [10]. Representative plaques were measured using ImageJ [11] and average plaque diameter was calculated.

Transmission electron microscopy

Transmission electron microscopy (TEM) was performed on BlueFeather lysate. The sample was placed onto a carbon-coated electron microscope grid and stained with 1% uranyl acetate. Phage particles were visualized using the CM120 Instrument (Philips, Amsterdam, Netherlands), and micrographs were captured. Phage head and tail lengths were measured using ImageJ [11].

Genome sequencing and assembly

Viral DNA was isolated with the Wizard® DNA Clean-Up System (cat # A7280, Promega, WI, USA). Sequencing libraries were constructed with the NEBNext® Ultra II DNA Library Prep kit (New England Biolabs, MA, USA), and sequenced by Illumina-MiSeq at the Pittsburgh Bacteriophage Institute to an approximate shotgun coverage of 3538x. Genome assembly and finishing were performed as previously described [12].

Gene annotation

Genomes were annotated as described previously [13] using DNA Master (http://cobamide2.bio.pitt.edu/) and PECAAN (https://pecaan.kbrinsgd.org/) for auto-annotation. GLIMMER [14] and GeneMark [15] were used to predict protein-coding regions along with their start and stop sites. Manual annotation was performed using Phamerator [16], Starterator [17], and host-trained and self-trained GeneMark coding potential maps to support or refute auto-annotation predictions [15]. Gene functions were determined using PhagesDB BLAST (https://phagesdb.org/blastp/), NCBI BLAST [18], HHpred [19] and CDD [20]. The presence of transmembrane proteins was determined using TMHMM [21] and TOPCONS [22]. The annotated complete genome was deposited to GenBank under the accession number MT024867.

Gene content comparisons

Phage genomes used in this study are available from phagesdb.org [23]. Gepard was used to perform sequence analysis to identify regions of homology between nucleotide sequences or amino acid sequences of different phages [24]. Concatenated whole genome nucleotide and whole proteome amino acid sequences were used to create dot plots with word sizes of 15 and 5, respectively.

SplitsTree was used to generate a network phylogeny in order to reveal the genetic distance between Arthrobacter phages [25]. BlueFeather and up to 10 representative phages from each Arthrobacter cluster were selected from the Actino_Draft database (version 366) for comparison.

The gene content calculator on PhagesDB (https://phagesdb.org/genecontent/) was used to calculate Gene Content Similarity (GCS), the percentage of shared genes in phams (groups of genes with related sequences), between BlueFeather, Cluster FE, and former Cluster FI phages [16]. Gene Content Dissimilarity (GCD) and maximum GCD gap (MaxGCDGap) were calculated using scripts described previously [8]. Heatmaps and scatter plots were created using Prism 8.0.0 (GraphPad Software, San Diego, California, USA) and were used for quantitative analysis and visualization of GCS and GCD values.

PhagesDB Pham View was used to gather information about phages with genes in the same phams as BlueFeather’s [23]. PECAAN was used to obtain the nucleotide sequences for each BlueFeather gene (https://discover.kbrinsgd.org). The BiologicsCorp online GC content calculator was used for each gene in the genome (https://www.biologicscorp.com/tools/GCContent/).

Results

BlueFeather is a siphovirus with a short genome

Phage BlueFeather was isolated from a soil sample via direct isolation on A. globiformis B-2979 at 25°C and had a mixed plaque size, ranging from 2–5 mm in diameter (average plaque size of approximately 3.5 mm). Plaque morphology was also inconsistent, with some bullseye plaques containing 1 mm center clearings with varying degrees of turbidity (Fig 1A). Transmission electron microscopy (TEM) at 67,000X magnification showed an average phage capsid diameter and tail length of 48 ± 8 nm and 156 ± 53 nm, respectively (Fig 1B). The long, flexible, non-contractile tail suggested BlueFeather’s classification as a Siphoviridae [26].

Fig 1. BlueFeather is a siphovirus.

Fig 1

A. Plaque morphology was inconsistent with some bullseye plaques containing 1 mm center clearings with varying degrees of turbidity. Plaque sizes ranged from 2–5 mm in diameter, with an average plaque diameter of approximately 3.5 mm. B. TEM image of BlueFeather at 67,000X magnification. The capsid was estimated to be 48 ± 8 nm and the tail 156 ± 53 nm.

BlueFeather’s genome had a length of 16,302 bp, 64.30% GC content, and genome ends with 15 base 3’ sticky overhangs (CCACGGTTCCCGTCC). Phages that infect Arthrobacter hosts have genome lengths that range from 15,319 bp (Toulouse) to 70,265 bp (PrincessTrina) [7]. The average Arthobacter phage genome length (as of May 2020) was 46,968 bp with a standard deviation of 20,619 bp and a median length of 53,859 bp, suggesting that most Arthrobacter phages have genomes notably larger than that of BlueFeather. BlueFeather’s genome contained 25 manually annotated genes; 18 were of known function, 6 were orphams–meaning they have not been identified in any other known phage–and 1 was a reverse gene (Fig 2). The left arm of the genome had highly conserved genes amongst siphoviral Arthrobacter phages, such as those encoding terminase, portal protein, head-to-tail adapter, and tail proteins [7]. Tail tube and sheath genes were absent, confirming the classification of BlueFeather as a siphovirus. Genes characteristic of the lytic life cycle, such as lysin A and holin, were identified; however, there were no genes that would indicate BlueFeather’s ability to undergo a lysogenic life cycle, suggesting that BlueFeather is not a temperate phage [27].

Fig 2. BlueFeather genome shares little nucleotide similarity but many phams with Cluster FE and former Cluster FI.

Fig 2

The BlueFeather genome is linear with a relatively small length of 16 kbp. Of the 25 identified ORFs, 18 were of known function, 6 were orphams and 1 was a reverse gene. BlueFeather had little BLASTn homology to its most similar phages, as indicated by the limited orange and yellow shading.

Dot plot comparisons revealed synonymous substitutions in BlueFeather’s genome

Phage BlueFeather was originally classified as a singleton on PhagesDB due to low nucleotide identity with other known phages. Nucleotide and amino acid dot plots were created to qualitatively compare BlueFeather to the most similar Arthrobacter phages, including those in Cluster FE (Corgi, Idaho, Noely) and former Cluster FI (Whytu, Yavru), as identified by BLASTn. Due to the limited number of sequenced Arthrobacter phages, many of the clusters have few members. Of the 28 Arthrobacter clusters on PhagesDB (as of May 2020), 17 clusters have between 2–4 phages (including the former Cluster FI). As expected, phages originally assigned to the same cluster had alignments indicating large regions of nucleotide similarity [28], while comparison of BlueFeather’s genome to phages originally assigned to Clusters FE and FI revealed no homologous sequences (Fig 3A). Unexpectedly, dot plot analysis of concatenated amino acid sequences with a word size of 5 revealed numerous regions of amino acid sequence similarity between these phages (Fig 3B). This reflects, at present, perhaps one of the clearest examples in which a group of phages lack nucleotide identity while sharing considerable amino acid identity.

Fig 3. Dot plots suggest shared amino acids but not nucleotides.

Fig 3

Whole genomes and proteomes for each phage were concatenated and dot plots were created using Gepard. Original cluster information is denoted along the top of each figure, with phage BlueFeather indicated by *. A. A whole genome dot plot with word size of 15 indicates strong intracluster nucleotide similarities with both FE and former FI phages. No intercluster nucleotide similarities were observed, indicating BlueFeather does not share significant nucleotide sequences with any of these phages. B. A whole proteome dot plot with a word size of 5 indicated the same intracluster amino acid similarities seen in the genome dot plot, but there were also amino acid similarities observed between BlueFeather, Cluster FE, and former Cluster FI phages. BlueFeather appeared to have greater amino acid similarity with phages originally assigned to Cluster FI.

Gene similarity demonstrates a close relationship between BlueFeather and phages of Cluster FE and former Cluster FI

Gene Content Similarity (GCS) is a key metric in quantifying phage genetic relationships and is calculated by averaging the number of shared genes between two phages [29]. GCS was calculated for BlueFeather, Cluster FE phages, and phages originally assigned to Cluster FI. BlueFeather shared over 35% of genes with all Cluster FE phages, and over 55% of genes with the former Cluster FI phages. Over 35% of genes were shared in each pairwise comparison performed (Fig 4A). Given that BlueFeather was originally determined to be a singleton, it was surprising to find GCS greater than the recently adopted threshold of 35% for clustering other phage populations [8, 9]. Gene Content Dissimilarity (GCD) is the opposite of GCS and was used to calculate the maximum GCD gap (MaxGCDGap), a metric that represents the degree of isolation between a phage and a selected phage population [8]. GCD was calculated for BlueFeather and all Arthrobacter phages. There was a MaxGCDGap of 41.60% between BlueFeather and Yavru, indicating a relatively high degree of separation between BlueFeather and the rest of the Arthrobacter phage population (Fig 4B). Arthrobacter phages exhibiting pairwise GCD values with BlueFeather of less than 1 were found in Clusters AN, AU, AM, AZ, AV, AL, FE, AO, FH, FF, and former Cluster FI, indicating shared gene content. GCD was then calculated for BlueFeather and all known phages in the PhagesDB Actino_draft database (Fig 4C). Similar to the Arthrobacter GCD plot, phages assigned to Cluster FE and former Cluster FI were the least dissimilar to BlueFeather. It is notable that in this comparison, there were 63 additional phages ranging from 0.959 to 0.975 GCD, meaning BlueFeather shares a low number of genes with many non-Arthrobacter phages. Non-Arthrobacter phages exhibiting pairwise GCD values with BlueFeather of less than 1 were found in Microbacterium phage Cluster EE, Mycobacterium phage Clusters N, I, P, and the singleton IdentityCrisis, as well as Gordonia phage Clusters DT, CW and the singleton GMA4.

Fig 4. BlueFeather shares the most phams with phages originally assigned to Cluster FE and former Cluster FI.

Fig 4

A. Gene Content Similarity (GCS) between BlueFeather, Cluster FE and the former Cluster FI was calculated with the PhagesDB GCS calculator using the number of shared phams. There was high intracluster GCS, and BlueFeather showed higher GCS values with former Cluster FI. B. Gene Content Dissimilarity (GCD) output values of all pairwise comparisons of BlueFeather and all Arthrobacter phages (305), ordered by magnitude. Cluster FE and former Cluster FI were found to be least dissimilar to BlueFeather, with a MaxGCDGap of 41.60%, between BlueFeather and Yavru. (C) GCD output values of all pairwise comparisons of BlueFeather and all phages in PhagesDB (3381). MaxGCDGap remained at 41.60%. There are no non-Arthrobacter phages that are less dissimilar to BlueFeather than Yavru. BlueFeather shares up to 10% of genes with at least 63 non-Arthrobacter phages.

To compare the relationships between the Arthrobacter phage population as whole and the phages assigned to Cluster FE, former Cluster FI, and BlueFeather, a SplitsTree network phylogeny of the phams from each Arthobacter phage cluster was generated to examine the genetic distance between the phages. As expected, BlueFeather was shown to be more genetically similar to phages originally assigned to Clusters FE and FI than to any other Arthrobacter phage clusters (Fig 5). BlueFeather demonstrated a closer pham similarity to former Cluster FI phages Whytu and Yavru than to Cluster FE phages Idaho, Noely and Corgi; however, these phages altogether formed a distinct branch from the rest of the phages sampled and together comprise the newly expanded Cluster FE.

Fig 5. Expanded Cluster FE includes BlueFeather and former FI phages.

Fig 5

A SplitsTree was generated in order to group Arthrobacter phages based on pham similarity. Ten representative phages from each cluster were selected to measure evolutionary relatedness. While there is great diversity of Arthrobacter phages, BlueFeather forms a relatively small branch with phages originally assigned to Cluster FE and the former Cluster FI. These phages, boxed in blue, comprise the expanded FE Cluster.

BlueFeather genome exhibits evidence of horizontal gene transfer

Given that BlueFeather shares genes with phages infecting distinct hosts, we investigated its genome for potential evidence of horizontal gene transfer (HGT). A whole genome heatmap was created using common metrics for evidence of HGT for each gene in the genome. As of March 2020, 4 genes in BlueFeather were considered to have the most convincing evidence for HGT based on GC content and prevalence in phages that infect unique bacterial hosts: genes 2, 15, 19, and 24 (Fig 6).

Fig 6. Evidence of horizontal gene transfer in the BlueFeather genome.

Fig 6

The GC content for each gene in BlueFeather’s genome ranged from 59.30%-70.30%, with an average of 64.30%. The number of unique isolation hosts that were represented in each pham ranged from 1–4. Genes with unexpectedly high values were considered to be the result of horizontal gene transfer. There were four genes with the most convincing evidence, indicated by *.

Typically, viral genes have about the same [30] or slightly lower GC content [31] compared to their bacterial hosts, suggesting that genes with higher GC content may have been horizontally transferred. BlueFeather had an overall average GC content of 64.30% and Arthrobacter globiformis mrc11 was found to have an overall GC content of 65.9% [32]. BlueFeather gene-specific average GC contents ranged from 59.30% to 70.30%, and genes with maximum average GC contents were considered for HGT. This included genes 15 and 24 with GC contents of 70.3% and 70.1%, respectively.

It is increasingly understood that phages infecting different hosts may share considerable gene content through processes such as HGT [8]. For each gene in the BlueFeather genome, we calculated the number of unique isolation hosts for phages possessing a pham found in BlueFeather. Gene 2 belongs to a pham with member genes found in phages that infect Gordonia malaquae BEN700 and Arthrobacter sp. ATCC 21022. Gene 15 belongs to a pham with member genes found in phages that infect A. globiformis B-2979, A. sp. ATCC 21022, Mycobacterium smegmatis mc2155, G. malaquae BEN700, and Gordonia rubripertincta NRRL B-16540. Gene 19 was the only reverse gene in the BlueFeather genome, and this gene was only found in BlueFeather and in phages infecting Microbacterium foliorum NRRL B-24224 SEA and Microbacterium paraoxydans NWU1.

Discussion

Our research was focused on the genomic and evolutionary relationships between the novel Arthrobacter phage BlueFeather and other known phages, particularly those originally assigned to Clusters FE and FI. Previous studies have shown that new clusters can be formed when novel phages are found to be similar to former singletons, as demonstrated by the formation of Cluster AS from Arthrobacter singleton Galaxy [7]. BlueFeather, originally designated as a putative singleton phage, exhibits over 35% GCS with all phages originally in Cluster FE and over 55% GCS with those formerly assigned to Cluster FI. The conservation of amino acids, rather than nucleotides, suggests a history of purifying selection via many synonymous mutations in which deleterious mutations were filtered out [33]. Moreover, this presents some of the clearest evidence to date of highly conserved amino acid sequences despite the absence of significant nucleotide conservation amongst related phages.

There is a high degree of synteny between these phages as well. While BlueFeather’s original designation as a singleton would imply low genomic relatedness to other phages [5], gene similarity between BlueFeather and phages from Cluster FE and former Cluster FI–in excess of 35%–indicates conservation of gene functions and genome architecture despite extensive divergence of nucleotide identity. While Arthrobacter phages have been clustered according to nucleotide identity in the past [7], this study on BlueFeather, Cluster FE, and the former Cluster FI highlights the importance of continually reevaluating clustering parameters, particularly when different parameters may result in different cluster assignments. Moreover, BlueFeather has the smallest genome of all Arthrobacter singletons, and it is possible that clustering parameters may also need to take genome size into account. Given that GCS reflects the number of genes shared as a proportion of the total number of genes for each phage, the same number of shared genes would yield higher GCS in comparisons between smaller genomes.

Gene content dissimilarity demonstrated that BlueFeather has a MaxGCDGap of 41.60% with phage Yavru, which was originally assigned to Cluster FI. BlueFeather was found to be least dissimilar with Cluster FE and former Cluster FI phages; this was supported by a network phylogeny of representative Arthrobacter phages that indicated great diversity between clusters, but revealed that phage BlueFeather forms a distinct branch with Cluster FE and former Cluster FI phages. Additionally, many phages were found to share between 0–10% GCS with BlueFeather. While this is too low to warrant a significant phylogenetic relationship, it reinforced the observed continuum of diversity in phage populations. Previous research found Arthrobacter phage clusters to be very discrete [7]. Even so, this low yet seemingly widespread display of shared genes, as well as BlueFeather’s unexpected relationships with Cluster FE and former Cluster FI phages, provides new insight into the genetic landscape of Arthrobacter phages. Few phages were previously assigned to Cluster FE and the former Cluster FI, representing only 5 of the 306 sequenced and manually annotated Arthrobacter phages (as of May 2020). On the other hand, there are 1,906 sequenced Mycobacterium phages (as of May 2020), which has allowed for a more thorough investigation of the mycobacteriophage continuum of diversity. As more Arthrobacter phages are sequenced, we expect to observe similar trends in these host-dependent genetic landscapes.

Unlike singleton phages that are replete with orphams [5, 7], the BlueFeather genome, originally designated as a putative singleton, is composed predominantly of genes with known functions that have been assigned to phams. BlueFeather has less than half as many genes as current Arthrobacter singletons and contains highly conserved genes required for viral mechanisms. These vital functional genes have been more thoroughly studied and as a result, are more likely to be found in phams with predicted functions [16]. Additionally, given that pham assignments are performed on the basis of amino acid identity, it is unsurprising that many of the phams containing these vital functional genes are shared amongst BlueFeather, Cluster FE, and former Cluster FI phages, despite the lack of significant nucleotide identity in gene encoding sequences.

Markers of horizontal gene transfer (HGT) included unexpectedly high GC content, as well as multiple bacterial hosts on which phages sharing genes with BlueFeather were isolated [5]. BlueFeather shared phams with a multitude of non-Arthrobacter phages from various clusters, which allowed us to identify multiple regions as having evidence for HGT. These potential HGT events serve to magnify phage diversity and promote the phenomenon of genetic mosaicism. BlueFeather serves as yet another example of the highly intricate mosaic relationships which exist among phages and are a common feature of the genetic landscape, making phage taxonomy an increasingly difficult task.

In sum, this research has led to the reclustering of BlueFeather and phages formerly assigned to Cluster FI into a newly expanded Cluster FE. Recent observations in which there appear to be limited nucleotide conservation but high shared gene content, as observed in this newly expanded cluster, support the notion that clustering methods should be continually reevaluated and optimized as more phages are sequenced [8]. This study thus provides valuable insight into the continuum of diversity amongst Arthrobacter phages, while also supporting a 35% shared gene content clustering parameter as was previously adopted for Gordonia and Microbacterium phages [8, 9]. Further investigation into novel phages is essential to understand the complex phage landscape. As more Arthrobacter phages are discovered, it is likely that we will discover many more phages like BlueFeather which belong to clusters whose close relationships become apparent only through the lens of shared gene content.

Acknowledgments

We thank Rebecca A. Garlena and Daniel A. Russell at the Pittsburgh Bacteriophage Institute for genome sequence and assembly; and Travis Mavrich, Welkin Pope, Debbie Jacobs-Sera, and Graham Hatfull with the HHMI Science Education Alliance-Phage Hunters Advancing Genomics and Evolutionary Science (SEA-PHAGES) program for programmatic support. The authors acknowledge the use of instruments at the Electron Imaging Center for NanoMachines supported by NIH (1S10RR23057 to ZHZ) and CNSI at UCLA. We would like to thank the Microbiology, Immunology, and Molecular Genetics Department, and the Dean of Life Sciences Division at UCLA for programmatic support.

Data Availability

All FASTA files are available from the phages.db database and/or GenBank. Accession numbers for the FE cluster phages used for most analyses are as follows: BlueFeather (MT024867), Corgi (MH834607), Idaho (MK757448), Noely (MH834622), Whytu (MT024870), and Yavru (MT889364). Representative phage genome sequences from each Arthrobacter phage cluster were randomly selected and accessed from https://phagesdb.org/ for the SplitsTree analysis.

Funding Statement

The author(s) received no specific funding for this work.

References

  • 1.Wiles S. Monday Micro– 200 million light years of viruses?! In: Sciblogs [Internet]. 8 May 2014 [cited 3 Aug 2020]. https://sciblogs.co.nz/infectious-thoughts/2014/08/05/monday-micro-200-million-light-years-of-viruses/
  • 2.Keen EC. A century of phage research: Bacteriophages and the shaping of modern biology: Cause to reflect. BioEssays. 2015;37: 6–9. 10.1002/bies.201400152 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 3.Pedulla ML, Ford ME, Houtz JM, Karthikeyan T, Wadsworth C, Lewis JA, et al. Origins of highly mosaic mycobacteriophage genomes. Cell. 2003;113: 171–182. 10.1016/s0092-8674(03)00233-2 [DOI] [PubMed] [Google Scholar]
  • 4.Miller-Ensminger T, Garretto A, Brenner J, Thomas-White K, Zambom A, Wolfe AJ, et al. Bacteriophages of the Urinary Microbiome. J Bacteriol. 2018;200. 10.1128/JB.00738-17 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 5.Pope WH, Bowman CA, Russell DA, Jacobs-Sera D, Asai DJ, Cresawn SG, et al. Whole genome comparison of a large collection of mycobacteriophages reveals a continuum of phage genetic diversity. Kolter R, editor. eLife. 2015;4: e06416. 10.7554/eLife.06416 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 6.Hatfull GF, Jacobs-Sera D, Lawrence JG, Pope WH, Russell DA, Ko C-C, et al. Comparative Genomic Analysis of 60 Mycobacteriophage Genomes: Genome Clustering, Gene Acquisition, and Gene Size. J Mol Biol. 2010;397: 119–143. 10.1016/j.jmb.2010.01.011 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 7.Klyczek KK, Bonilla JA, Jacobs-Sera D, Adair TL, Afram P, Allen KG, et al. Tales of diversity: Genomic and morphological characteristics of forty-six Arthrobacter phages. Schuch R, editor. PLOS ONE. 2017;12: e0180517. 10.1371/journal.pone.0180517 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 8.Pope WH, Mavrich TN, Garlena RA, Guerrero-Bustamante CA, Jacobs-Sera D, Montgomery MT, et al. Bacteriophages of Gordonia spp. Display a Spectrum of Diversity and Genetic Relationships. mBio. 2017;8. 10.1128/mBio.01069-17 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 9.Jacobs-Sera D, Abad LA, Alvey RM, Anders KR, Aull HG, Bhalla SS, et al. Genomic diversity of bacteriophages infecting Microbacterium spp. Cloeckaert A, editor. PLOS ONE. 2020;15: e0234636. 10.1371/journal.pone.0234636 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 10.Sarkis GJ, Hatfull GF. Mycobacteriophages. In: Parish T, Stoker NG, editors. Mycobacteria Protocols. Totowa, NJ: Humana Press; 1998. pp. 145–173. [Google Scholar]
  • 11.Schneider CA, Rasband WS, Eliceiri KW. NIH Image to ImageJ: 25 years of image analysis. Nat Methods. 2012;9: 671–675. 10.1038/nmeth.2089 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 12.Russell DA. Sequencing, Assembling, and Finishing Complete Bacteriophage Genomes. In: Clokie MRJ, Kropinski AM, Lavigne R, editors. Bacteriophages: Methods and Protocols, Volume 3. New York, NY: Springer New York; 2018. pp. 109–125. 10.1007/978-1-4939-7343-9_9 [DOI] [PubMed] [Google Scholar]
  • 13.Pope WH, Jacobs-Sera D. Annotation of Bacteriophage Genome Sequences Using DNA Master: An Overview. In: Clokie MRJ, Kropinski AM, Lavigne R, editors. Bacteriophages. New York, NY: Springer New York; 2018. pp. 217–229. [DOI] [PubMed] [Google Scholar]
  • 14.Delcher AL, Harmon D, Kasif S, White O, Salzberg SL. Improved microbial gene identification with GLIMMER. Nucleic Acids Res. 1999;27: 4636–4641. 10.1093/nar/27.23.4636 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 15.Besemer J, Borodovsky M. GeneMark: web software for gene finding in prokaryotes, eukaryotes and viruses. Nucleic Acids Res. 2005;33: W451–454. 10.1093/nar/gki487 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 16.Cresawn SG, Bogel M, Day N, Jacobs-Sera D, Hendrix RW, Hatfull GF. Phamerator: a bioinformatic tool for comparative bacteriophage genomics. BMC Bioinformatics. 2011;12: 395. 10.1186/1471-2105-12-395 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 17.SEA-PHAGES/starterator. SEA-PHAGES Program; 2020. https://github.com/SEA-PHAGES/starterator
  • 18.Altschul SF, Gish W, Miller W, Myers EW, Lipman DJ. Basic local alignment search tool. J Mol Biol. 1990;215: 403–410. 10.1016/S0022-2836(05)80360-2 [DOI] [PubMed] [Google Scholar]
  • 19.Soding J, Biegert A, Lupas AN. The HHpred interactive server for protein homology detection and structure prediction. Nucleic Acids Res. 2005;33: W244–W248. 10.1093/nar/gki408 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 20.Marchler-Bauer A, Derbyshire MK, Gonzales NR, Lu S, Chitsaz F, Geer LY, et al. CDD: NCBI’s conserved domain database. Nucleic Acids Res. 2015;43: D222–D226. 10.1093/nar/gku1221 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 21.Krogh A, Larsson B, von Heijne G, Sonnhammer EL. Predicting transmembrane protein topology with a hidden Markov model: application to complete genomes. J Mol Biol. 2001;305: 567–580. 10.1006/jmbi.2000.4315 [DOI] [PubMed] [Google Scholar]
  • 22.Tsirigos KD, Peters C, Shu N, Käll L, Elofsson A. The TOPCONS web server for consensus prediction of membrane protein topology and signal peptides. Nucleic Acids Res. 2015;43: W401–407. 10.1093/nar/gkv485 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 23.Russell DA, Hatfull GF. PhagesDB: the actinobacteriophage database. Bioinforma Oxf Engl. 2017;33: 784–786. 10.1093/bioinformatics/btw711 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 24.Krumsiek J, Arnold R, Rattei T. Gepard: a rapid and sensitive tool for creating dotplots on genome scale. Bioinformatics. 2007;23: 1026–1028. 10.1093/bioinformatics/btm039 [DOI] [PubMed] [Google Scholar]
  • 25.Huson DH. SplitsTree: analyzing and visualizing evolutionary data. Bioinforma Oxf Engl. 1998;14: 68–73. 10.1093/bioinformatics/14.1.68 [DOI] [PubMed] [Google Scholar]
  • 26.Yuan Y, Gao M. Jumbo Bacteriophages: An Overview. Front Microbiol. 2017;8. 10.3389/fmicb.2017.00403 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 27.Shi Y, Li N, Yan Y, Wang H, Li Y, Lu C, et al. Combined Antibacterial Activity of Phage Lytic Proteins Holin and Lysin from Streptococcus suis Bacteriophage SMP. Curr Microbiol. 2012;65: 28–34. 10.1007/s00284-012-0119-2 [DOI] [PubMed] [Google Scholar]
  • 28.Grose JH, Casjens SR. Understanding the enormous diversity of bacteriophages: The tailed phages that infect the bacterial family Enterobacteriaceae. Virology. 2014;468–470: 421–443. 10.1016/j.virol.2014.08.024 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 29.Mavrich TN, Hatfull GF. Bacteriophage evolution differs by host, lifestyle and genome. Nat Microbiol. 2017;2: 17112. 10.1038/nmicrobiol.2017.112 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 30.Bohlin J, Pettersson JH-O. Evolution of Genomic Base Composition: From Single Cell Microbes to Multicellular Animals. Comput Struct Biotechnol J. 2019;17: 362–370. 10.1016/j.csbj.2019.03.001 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 31.de Melo ACC, da Mata Gomes A, Melo FL, Ardisson-Araújo DMP, de Vargas APC, Ely VL, et al. Characterization of a bacteriophage with broad host range against strains of Pseudomonas aeruginosa isolated from domestic animals. BMC Microbiol. 2019;19: 134. 10.1186/s12866-019-1481-z [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 32.Sahoo D, Devi NJ, Ngashangva N, Momota P, Rojeena Y, Indira Devi S. Draft Genome Sequence of Arthrobacter globiformis mrc11, an Antimicrobial Agent Isolated from a Khangkhui Cave Deposit. Putonti C, editor. Microbiol Resour Announc. 2019;8: e01620–18. 10.1128/MRA.01620-18 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 33.Ngandu NK, Scheffler K, Moore P, Woodman Z, Martin D, Seoighe C. Extensive purifying selection acting on synonymous sites in HIV-1 Group M sequences. Virol J. 2008;5: 160. 10.1186/1743-422X-5-160 [DOI] [PMC free article] [PubMed] [Google Scholar]

Decision Letter 0

Eric Charles Dykeman

10 Dec 2020

PONE-D-20-26741

BlueFeather, the singleton that wasn’t: Shared gene content analysis supports expansion of Arthrobacter phage cluster FE

PLOS ONE

Dear Dr. Moberg Parker,

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.

==============================

Apologies for the long review process. I would be grateful if you could address the comments from both reviewers in the resubmission. Again, sorry for the delay.

==============================

Please submit your revised manuscript by Jan 24 2021 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.

Please include the following items when submitting your revised manuscript:

  • 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 you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter.

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: http://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols

We look forward to receiving your revised manuscript.

Kind regards,

Eric Charles Dykeman, 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 in the Acknowledgments Section of your manuscript:

[This research was funded in part by the Microbiology, Immunology and Molecular Genetics Department, and the Dean of Life Sciences Division at UCLA.]

We note that you have provided funding information that is not currently declared in your Funding Statement. However, funding information should not appear in the Acknowledgments section or other areas of your manuscript. We will only publish funding information present in the Funding Statement section of the online submission form.

Please remove any funding-related text from the manuscript and let us know how you would like to update your Funding Statement. Currently, your Funding Statement reads as follows:

 [The author(s) received no specific funding for this work.]

Please include your amended statements within your cover letter; we will change the online submission form on your behalf.

[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?

The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented.

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

Reviewer #1: N/A

Reviewer #2: Yes

**********

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

The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.

Reviewer #1: Yes

Reviewer #2: Yes

**********

5. Review Comments to the Author

Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters)

Reviewer #1: Dear Editor,

The manuscript entitled “BlueFeather, the singleton that wasn’t: Shared gene content analysis supports expansion of Arthrobacter phage cluster FE” is a very well written paper utilizing current methodologies to characterize the genome of phage BlueFeather and assign it to a cluster. The data are all very solid in support of the authors’ conclusions with regards to the classification of the phage. The in silico analyses seemed to be performed appropriately for what was being investigated. Again, the conclusions are in accordance with the data generated and presented.

In my opinion, however, the conclusion(s) of the paper is not scientifically novel nor important enough to warrant publication in PLOS One. The classification of a single phage to an already existing cluster does not provide sufficient scientific discovery for publication in this journal. A much deeper inquiry into how gene content similarities or dissimilarities would establish new clusters or reorganization of multiple phages would be helpful. Similar papers have classified many phage simultaneously to establish new phage clustering.

Thank you for the opportunity to comment.

Reviewer #2: Review of ‘BlueFeather, the singleton that wasn’t: Shared gene content analysis supports

expansion of Arthrobacter phage cluster FE’

Summary:

Clustering is used to categorize bacteriophages based upon genomic similarity. Previous analyses using nucleotide identity measures designated the novel Arthrobacter phage, BlueFeather, as a singleton indicating that it was not able to be clustered with other phages. This study investigated the use of gene content and amino acid conservation to cluster phage BlueFeather, as its small genome and extensive synteny with clustered phages warranted reevaluation of its designation. Characterization of BlueFeather in terms of plaque and phage morphology is also presented. The authors determined that shared gene content and amino acid conservation between BlueFeather and members of Cluster FI and Cluster FE and phylogenetic analysis using Splitstree warrant reclustering of BlueFeather and the current Cluster FI and Cluster FE phages into one cluster designated Cluster FE.

Due to the mosaic nature of bacteriophage genomes, clustering phages of a particular host can be challenging, especially if there are a limited number of sequenced phage genomes to work with. As the database of phage genomes has grown, the accuracy for clustering has improved, and for Arthrobacter phages, the number of sequenced phages available to evaluate in the initial publication 3 years ago was 46 while today there are 312 Arthrobacter phage genomes sequenced on phagesdb.com. In addition new tools and methods for evaluating genomic relationships have become available besides simply looking at nucleotide identity. Reevaluating cluster assignments is necessary, and in this case merging a singleton, BlueFeather, and Cluster FI phages with the Cluster FE phages is sound.

The authors presentation of their bioinformatic analyses used in this study is clear, and overall the article is well written. This data has not been published elsewhere, and conclusions presented are clear. The conclusions are supported by several different types of bioinformatic analyses making for a strong case for creation of a new Cluster FE and re-clustering of several phages. There are a few minor issues to address such as wording choices and clarification of plaque purifications, but these do not affect the overall conclusions. I recommend this article for publication.

Major issues: There are no major issues to address.

Minor issues: (listed in order of importance)

• Figure 1A: The plaques are difficult to see and are described as being 5mm in diameter though there is a mixture in plaques sizes on this plate. On pg 7, line 153-155, the figure is described as a plate produced from an infection using a picked plaque, so is this from purification steps before the high titer lysate was produced? Perhaps a clearer image of plaques from the lysate would be better and the plaques would be consistent in size. If plaques are variable in size for this phage, that is not uncommon and should be stated.

• Pg 9, line 219: In the text, Idaho has 34.18% shared gene content with BlueFeather while in Figure 4A itself it says that Idaho has 38.5% shared gene content with BlueFeather (though the text in the figure is hard to read in the pdf). These numbers should be consistent. 38.5% GCS would provide an even stronger argument for clustering BlueFeather with Idaho.

• Pg 5, line 96: A reference should be provided for phage purifications or details about the procedure should be included.

• Pg 6, line 126: may I suggest changing ‘whole amino acid sequences’ to ‘whole proteome amino acid sequences’ to clarify that the entire proteome was examined

• Pg 3, line 62: comma needed after phylogeny

• Pg 5, line 103: comma after (Philips, Amsterdam, Netherlands)

• Pg 10, line 228: comma between phages and which

• Pg 10, line 229: comma between 1 and were

• Pg 10, line 235: comma between phages and which

• Pg 10, line 236: comma between 1 and were

• Pg 16, line 373: may I suggest changing this sentence so that it flows better to ‘BlueFeather serves as yet another example of the highly intricate mosaic relationships which exist among phages and are a feature of the genetic landscape, making phage taxonomy an increasingly difficult task.’

**********

6. PLOS authors have the option to publish the peer review history of their article (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. Please note that Supporting Information files do not need this step.

PLoS One. 2021 Mar 12;16(3):e0248418. doi: 10.1371/journal.pone.0248418.r002

Author response to Decision Letter 0


23 Jan 2021

Response to Reviewer 1:

Thank you for the positive feedback regarding the writing, data, and analyses. We respectfully disagree with the reviewer’s suggestion that the conclusion is not scientifically novel or important enough for publication in PLOS ONE. In addition to reclassifying the novel phage BlueFeather from singleton to Cluster FE, this work did also result in the re-organization of the previously distinct Cluster FI into an expanded Cluster FE. Prior to this work, Arthrobacter phages were clustered using nucleotide identity as described by Klyczek et al. (2017), but now the Hatfull lab (which runs phagedb.org) has adopted the parameters we describe for clustering new Arthrobacter phages. We believe our paper has the strong scientific validity, methodology, and ethical standards necessary for publication in PLOS ONE, which doesn’t select articles based on perceived significance.

Response to Reviewer 2 (Minor Issues to Address):

• Figure 1A: The plaques are difficult to see and are described as being 5mm in diameter though there is a mixture in plaques sizes on this plate. On pg 7, line 153-155, the figure is described as a plate produced from an infection using a picked plaque, so is this from purification steps before the high titer lysate was produced? Perhaps a clearer image of plaques from the lysate would be better and the plaques would be consistent in size. If plaques are variable in size for this phage, that is not uncommon and should be stated.

Thank you for the suggestion, we went back and used ImageJ to calculate average plaque diameter (sentence added to methods at lines 99-100). A revised figure 1A has been submitted with an inset showing a magnification of the plaques, and a revised figure legend. The results section has been revised to reflect a more detailed description of plaque size and morphology variations (lines 150-153).

• Pg 9, line 219: In the text, Idaho has 34.18% shared gene content with BlueFeather while in Figure 4A itself it says that Idaho has 38.5% shared gene content with BlueFeather (though the text in the figure is hard to read in the pdf). These numbers should be consistent. 38.5% GCS would provide an even stronger argument for clustering BlueFeather with Idaho.

The GCS calculation was repeated confirming the 38.5% GCS for Phage Idaho (text updated in lines 221-223). The repeated analysis also indicated that the MaxGCDGap was between BlueFeather and Yavru (41.60%), rather than Whytu. The text (line 230), Figure 4b and legend have been revised.

• Pg 5, line 96: A reference should be provided for phage purifications or details about the procedure should be included.

Reference added at line 99.

• Pg 16, line 373: may I suggest changing this sentence so that it flows better to ‘BlueFeather serves as yet another example of the highly intricate mosaic relationships which exist among phages and are a feature of the genetic landscape, making phage taxonomy an increasingly difficult task.’

Thank you for the suggestion, the sentence has been edited.

The following suggested edits have been incorporated:

• Pg 3, line 62: comma needed after phylogeny

• Pg 5, line 103: comma after (Philips, Amsterdam, Netherlands)

• Pg 6, line 126: may I suggest changing ‘whole amino acid sequences’ to ‘whole proteome amino acid sequences’ to clarify that the entire proteome was examined

The suggested edits below change the meaning of the text, so the sentences were changed from “which exhibited” to “exhibiting” to improve clarity (lines 232 and 240).

• Pg 10, line 228: comma between phages and which

• Pg 10, line 229: comma between 1 and were

• Pg 10, line 235: comma between phages and which

• Pg 10, line 236: comma between 1 and were

We would like to thank Reviewer 2 for the detailed feedback, which helped improve the quality of our manuscript.

Attachment

Submitted filename: Bluefeather Manuscript Response to Reviewers.docx

Decision Letter 1

Eric Charles Dykeman

26 Feb 2021

BlueFeather, the singleton that wasn’t: Shared gene content analysis supports expansion of Arthrobacter phage Cluster FE

PONE-D-20-26741R1

Dear Dr. Moberg Parker,

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 for payment will follow shortly after the formal acceptance. To ensure an efficient process, please log into Editorial Manager at http://www.editorialmanager.com/pone/, click the 'Update My Information' link at the top of the page, and double check that your user information is up-to-date. If you have any billing related questions, 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,

Eric Charles Dykeman, Ph.D.

Academic Editor

PLOS ONE

Additional Editor Comments (optional):

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. If the authors have adequately addressed your comments raised in a previous round of review and you feel that this manuscript is now acceptable for publication, you may indicate that here to bypass the “Comments to the Author” section, enter your conflict of interest statement in the “Confidential to Editor” section, and submit your "Accept" recommendation.

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?

The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented.

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.

Reviewer #1: Yes

Reviewer #2: Yes

**********

6. Review Comments to the Author

Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters)

Reviewer #1: Well written paper describing the reclassification of phage based on shared gene content analysis. The data fully support the authors' conclusions and the previous review improved some formatting and descriptive content in the paper.

Minor:

Line 26 delete 'shifting target' for 'challenge' or 'challenging task'.

Line 27 substitute Mycobacterium for Mycobacteria

Line 386 delete 'thus'

Reviewer #2: (No Response)

**********

7. PLOS authors have the option to publish the peer review history of their article (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

Acceptance letter

Eric Charles Dykeman

3 Mar 2021

PONE-D-20-26741R1

BlueFeather, the singleton that wasn’t: Shared gene content analysis supports expansion of Arthrobacter phage Cluster FE

Dear Dr. Moberg Parker:

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

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 plosone@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. Eric Charles Dykeman

Academic Editor

PLOS ONE

Associated Data

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

    Supplementary Materials

    Attachment

    Submitted filename: Bluefeather Manuscript Response to Reviewers.docx

    Data Availability Statement

    All FASTA files are available from the phages.db database and/or GenBank. Accession numbers for the FE cluster phages used for most analyses are as follows: BlueFeather (MT024867), Corgi (MH834607), Idaho (MK757448), Noely (MH834622), Whytu (MT024870), and Yavru (MT889364). Representative phage genome sequences from each Arthrobacter phage cluster were randomly selected and accessed from https://phagesdb.org/ for the SplitsTree analysis.


    Articles from PLoS ONE are provided here courtesy of PLOS

    RESOURCES