Peer Review History

Original SubmissionFebruary 20, 2025
Transfer Alert

This paper was transferred from another journal. As a result, its full editorial history (including decision letters, peer reviews and author responses) may not be present.

Decision Letter - Adriana Calderaro, Editor

PONE-D-25-08885Evaluation of shotgun metagenomics as a diagnostic tool for infectious gastroenteritisPLOS ONE

Dear Dr. Haugum,

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.

Please submit your revised manuscript by Jul 29 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.

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: 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,

Adriana Calderaro

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. We note that the grant information you provided in the ‘Funding Information’ and ‘Financial Disclosure’ sections do not match.

When you resubmit, please ensure that you provide the correct grant numbers for the awards you received for your study in the ‘Funding Information’ section.

3. Your ethics statement should only appear in the Methods section of your manuscript. If your ethics statement is written in any section besides the Methods, please move it to the Methods section and delete it from any other section. Please ensure that your ethics statement is included in your manuscript, as the ethics statement entered into the online submission form will not be published alongside your manuscript.

4. Please amend your list of authors on the manuscript to ensure that each author is linked to an affiliation. Authors’ affiliations should reflect the institution where the work was done (if authors moved subsequently, you can also list the new affiliation stating “current affiliation:….” as necessary).

5. We note that you have included the phrase “data not shown” in your manuscript. Unfortunately, this does not meet our data sharing requirements. PLOS does not permit references to inaccessible data. We require that authors provide all relevant data within the paper, Supporting Information files, or in an acceptable, public repository. Please add a citation to support this phrase or upload the data that corresponds with these findings to a stable repository (such as Figshare or Dryad) and provide and URLs, DOIs, or accession numbers that may be used to access these data. Or, if the data are not a core part of the research being presented in your study, we ask that you remove the phrase that refers to these data.

[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

**********

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

Reviewer #1: N/A

**********

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

**********

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

**********

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: In this manuscript, the author compared the applicability of shotgun metagenomic and PCR for the diagnosis of infectious gastroenteritis. This is very relevant and will help improve diagnostic protocols and routines. The experimental setup appears reasonable, and the authors present their findings effectively. There are some points that I would like to discuss before making any decision.

• In this work, misclassification is closely linked to mobile genetic elements, which may be one reason. However, it is not the only one. Another possible reason may be the microbial abundance in metagenomics. Regardless of the reason, there is insufficient evidence in this manuscript to support mobile genetic elements as a cause of misclassification, and I believe this assertion is too strong to be made.

• The authors emphasize that bioinformatics analyses could impact the metagenomic results. This is true. However, I believe the manuscript does not provide sufficient evidence to support this claim. For instance, both the assembler and the binner could have a significant impact. In this manuscript, the authors chose to test only Megahit and Metabat2. It has been shown that both assembler and binner behaviour differ when they are used for low and high coverage data. So, preferring one over the other is very challenging in metagenomics. Indeed, many publications have suggested a multi-tool approach. Additionally, there are many different taxonomy tools; however, only Kraken2 and its associated tools were tested. Thus, although the statement is correct, the evidence is insufficient.

• I believe the manuscript will benefit from constructing a confusion matrix that includes both the false positive and negative rates for sequencing as a potential diagnostic method compared to the traditional routine method.

• What is missing from the discussion is the applicability of long-read sequencing to overcome the limitations in the field of metagenomic assembly, especially when it comes to mobile genetic element and their repetitive regions.

Please provide a percentage of unclassified reads for Kraken.

Please provide the percentage of unique mapped reads, depth of coverage, and breadth of coverage after mapping the reads back to assemblies (some of these values are provided but not in percentages).

The authors declared that they mapped the sequencing reads against the host genome where any actual maps were removed. This sounds like a correct approach; however, the authors did not specify the percentage of the host genome contamination.

L 415 / L 421: final spiked concentration is contrasting; please double-check.

L 440: One of the discussed points in this manuscript was the DNA extraction technique and its effectiveness. While I agree with the authors, unfortunately, the current work only presents DNA concentration and A260/A280 ratios. It would be nice to show the A260/A230 as well.

L 493 and L502: any reason to only use Megahit and Metabat2? It is hard to prefer one over the other, specifically for assemblers. Some assemblers performed better for low coverage data.

L 495: Why are authors considered co-assembly?

L 503: At this stage, it is uncertain whether the authors considered all the MAGs for downstream analyses or only selected medium and high-quality MAGs. Please also provide statistics on the quality of the MAGs.

L 508: Why did the authors suddenly decide to use GTDb-Tk for the taxonomy classification of MAGs?

L 526: What was the justification to shift to SPAdes for assembly?

L 527: How is percentage coverage calculated? The method is not consistent across the literature, so please provide more details.

**********

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

**********

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

Revision 1

Haugum et al. - Response to Reviewers

Manuscript number: PONE-D-25-08885

Title: Evaluation of shotgun metagenomics as a diagnostic tool for infectious gastroenteritis

We thank Reviewer #1 for reviewing and commenting on our manuscript “Evaluation of shotgun metagenomics as a diagnostic tool for infectious gastroenteritis”. We have now worked through the manuscript and have, to the best of our knowledge, taken the comments from the Reviewer into consideration. Please see below for details.

Comment to Journal Requirements:

Response to comment 5: We recognize PLOS ONE’s policy regarding the use of the phrase “data not shown”. In this instance, the phrase 'data not shown' was somewhat redundant. It was included to indicate that referencing these specific results was unnecessary, as the outcomes from the second assembly approach using Haploflow are presented in Table 3. As such, in our opinion, the phrase can be removed while the rest of the text remain unchanged. The phrase “data not shown” is removed from line 531.

Review Comments to the Author

Reviewer #1:

• In this work, misclassification is closely linked to mobile genetic elements, which may be one reason. However, it is not the only one. Another possible reason may be the microbial abundance in metagenomics. Regardless of the reason, there is insufficient evidence in this manuscript to support mobile genetic elements as a cause of misclassification, and I believe this assertion is too strong to be made.

Response to reviewer: We thank the reviewer for this comment, and recognize that that other reasons for misclassification exist.

We have now included S3 Table in the manuscript. In this table, we show results from BLAST searches of the ten largest contigs assembled from C. jejuni and C. difficile reads from each of the four non-spiked BP negative samples (i.e. donor faeces without pathogens added). The results showed that the majority of the BLAST hits are related to mobile genetic elements and we therefore suggest there is evidence that mobile genetic elements may contribute to misclassification. Furthermore, we have rephrased the text to clarify, please see lines 333-335, and lines 478-481.

• The authors emphasize that bioinformatics analyses could impact the metagenomic results. This is true. However, I believe the manuscript does not provide sufficient evidence to support this claim. For instance, both the assembler and the binner could have a significant impact. In this manuscript, the authors chose to test only Megahit and Metabat2. It has been shown that both assembler and binner behaviour differ when they are used for low and high coverage data. So, preferring one over the other is very challenging in metagenomics. Indeed, many publications have suggested a multi-tool approach. Additionally, there are many different taxonomy tools; however, only Kraken2 and its associated tools were tested. Thus, although the statement is correct, the evidence is insufficient.

Response to reviewer: We thank reviewer for the comment, and do agree on noted points. We did not aim to extensively test many bioinformatics tools in this study. The tools were chosen for their suitability to our data, as demonstrated by their performance in peer-reviewed literature. We have now added more references to reflect this (line 189 and 199). We have in addition changed the text to apply to comment regarding use of Kraken, please see line 479.

• I believe the manuscript will benefit from constructing a confusion matrix that includes both the false positive and negative rates for sequencing as a potential diagnostic method compared to the traditional routine method.

Response to reviewer: We thank the reviewer for the comment and have now included results for the suggested confusion matrix as Table 2. Please also see lines 294-296 for further information.

• What is missing from the discussion is the applicability of long-read sequencing to overcome the limitations in the field of metagenomic assembly, especially when it comes to mobile genetic element and their repetitive regions.

Response to reviewer: We appreciate the reviewer's comment and agree with the noted point. We have implemented a sentence reflecting this; please see lines 481-485.

• Please provide a percentage of unclassified reads for Kraken.

Response to reviewer: Information regarding unclassified reads is now included in the results, lines 267-269, and in the S2 Table.

• Please provide the percentage of unique mapped reads, depth of coverage, and breadth of coverage after mapping the reads back to assemblies (some of these values are provided but not in percentages).

Response to reviewer: We have now added percentage of unique mapped reads to the S4 Table. In the same table, depth of coverage and breath of coverage are in addition included.

• The authors declared that they mapped the sequencing reads against the host genome where any actual maps were removed. This sounds like a correct approach; however, the authors did not specify the percentage of the host genome contamination.

Response to reviewer: Information regarding human contamination is now included in the results, lines 267-269.

• L 415 / L 421: final spiked concentration is contrasting; please double-check.

Response to reviewer: We recognize that the text in these two sentences can be confusing. In line 415 (now line 112) we refer to the starting concentration of 2.0 x 108 CFU/mL. This is diluted in 1 ml with 100 µL, giving the final concentration of 2.0 x 107 CFU/mL (line 421, now line 117). We have rewritten the text to clarify this, please see line 117-118.

• L 440: One of the discussed points in this manuscript was the DNA extraction technique and its effectiveness. While I agree with the authors, unfortunately, the current work only presents DNA concentration and A260/A280 ratios. It would be nice to show the A260/A230 as well.

Response to reviewer: Thank you for commenting on this. A260/A230 was also measured, and revised text is now included in line 137.

• L 493 and L502 (L 189 and 199): any reason to only use Megahit and Metabat2? It is hard to prefer one over the other, specifically for assemblers. Some assemblers performed better for low coverage data.

Response to reviewer: In this study, we selected the assembler and binner that were best suited for our data, based on their performance as reported in peer-reviewed literature as mentioned above. We agree with the reviewer that different assemblers and binning tools perform differently. However, as the aim was not to compare or benchmark many bioinformatics tools, more tools were not used. While using additional or different assemblers/binners might have provided more comprehensive data, we have addressed this in lines 189 and 199, with adding more references for the tools. Please also see line 491 in the manuscript.

• L 495 (L 191): Why are authors considered co-assembly?

Response to reviewer: We thank reviewer for this comment. In this study, co-assembly was performed to improve genome assembly, by increasing read depth and thus aiming at improving the recovery of low-abundance species, as well as to generate genomes as finished/complete as possible. Thereafter, reads from each sample were individually mapped to quantify completeness and coverage of these reads. To avoid confusion, we have added a sentence regarding this in the manuscript; please see line 191-192.

• L 503 (L 200): At this stage, it is uncertain whether the authors considered all the MAGs for downstream analyses or only selected medium and high-quality MAGs. Please also provide statistics on the quality of the MAGs.

Response to reviewer: Thank you for the comment. Here all bacterial MAGs (line 200) were imported into anvi´o, and result with statistics are provided in Table 4. For virus MAGs, no further work was done. If any quality statistics are missing, we would be happy to provide this information upon request.

• L 508 (L 204): Why did the authors suddenly decide to use GTDb-Tk for the taxonomy classification of MAGs?

Response to reviewer: We thank the reviewer for the comment. Our initial strategy to use Kraken for taxonomix assignment was based on the use of reads to classify pathogens (and other microbes). However, Genome Taxonomy database Toolkit (GTDb-Tk) is a commonly used tool for taxonomic assignment after assembly and binning. Additionally, we used Kraken for taxonomic assignment on contigs.

• L 526 (L222): What was the justification to shift to SPAdes for assembly?

Response to reviewer: All reads were first assembled with Metabat. Due to very few reads for Giardia spp. using this approach, we changed to the species-specific approach for Giardia detection, where reads that mapped to Giardia were extracted and assembled with SPAdes. The reason for using SPADes is that it is widely recognized in the literature as one of the best assemblers for reads derived at the species level.

• L 527 (L 223): How is percentage coverage calculated? The method is not consistent across the literature, so please provide more details.

Response to reviewer: We thank the reviewer for making us aware of this. “Percent coverage” is changed to “alignment length” based on BLAST search in the text, please see line 223.

Attachments
Attachment
Submitted filename: Response to reviewers.docx
Decision Letter - Adriana Calderaro, Editor

Evaluation of shotgun metagenomics as a diagnostic tool for infectious gastroenteritis

PONE-D-25-08885R1

Dear Dr. Haugum,

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. For questions related to billing, please contact billing support .

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,

Adriana Calderaro

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 #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 #2: Yes

**********

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

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 #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 #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 #2: The authors have satisfactorily addressed all reviewer comments in the revised manuscript. I therefore recommend the manuscript for acceptance.

**********

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 #2: No

**********

Formally Accepted
Acceptance Letter - Adriana Calderaro, Editor

PONE-D-25-08885R1

PLOS ONE

Dear Dr. Haugum,

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.

You will receive an invoice from PLOS for your publication fee after your manuscript has reached the completed accept phase. If you receive an email requesting payment before acceptance or for any other service, this may be a phishing scheme. Learn how to identify phishing emails and protect your accounts at https://explore.plos.org/phishing.

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

MD, PhD, Full Professor Adriana Calderaro

Academic Editor

PLOS ONE

Open letter on the publication of peer review reports

PLOS recognizes the benefits of transparency in the peer review process. Therefore, we enable the publication of all of the content of peer review and author responses alongside final, published articles. Reviewers remain anonymous, unless they choose to reveal their names.

We encourage other journals to join us in this initiative. We hope that our action inspires the community, including researchers, research funders, and research institutions, to recognize the benefits of published peer review reports for all parts of the research system.

Learn more at ASAPbio .