Peer Review History

Original SubmissionMay 21, 2020
Decision Letter - Sergei L. Kosakovsky Pond, Editor, Mark Alber, Editor

Dear Prof. Vongsangnak,

Thank you very much for submitting your manuscript "MetGEMs Toolbox: Metagenome-scale models as integrative toolbox for uncovering metabolic functions and routes of human gut microbiome" for consideration at PLOS Computational Biology.

As with all papers reviewed by the journal, your manuscript was reviewed by members of the editorial board and by several independent reviewers. In light of the reviews (below this email), we would like to invite the resubmission of a significantly-revised version that takes into account the reviewers' comments.

Ensure that your revisions offer a point-by-point response. We also expect the revision to provide considerably more methodological clarity and detail, and a proper placement of the proposed methodology in the context of existing work.

We cannot make any decision about publication until we have seen the revised manuscript and your response to the reviewers' comments. Your revised manuscript is also likely to be sent to reviewers for further evaluation.

When you are ready to resubmit, please upload the following:

[1] A letter containing a detailed list of your responses to the review comments and a description of the changes you have made in the manuscript. Please note while forming your response, if your article is accepted, you may have the opportunity to make the peer review history publicly available. The record will include editor decision letters (with reviews) and your responses to reviewer comments. If eligible, we will contact you to opt in or out.

[2] Two versions of the revised manuscript: one with either highlights or tracked changes denoting where the text has been changed; the other a clean version (uploaded as the manuscript file).

Important additional instructions are given below your reviewer comments.

Please prepare and submit your revised manuscript within 60 days. If you anticipate any delay, please let us know the expected resubmission date by replying to this email. Please note that revised manuscripts received after the 60-day due date may require evaluation and peer review similar to newly submitted manuscripts.

Thank you again for your submission. We hope that our editorial process has been constructive so far, and we welcome your feedback at any time. Please don't hesitate to contact us if you have any questions or comments.

Sincerely,

Sergei L. Kosakovsky Pond, PhD

Associate Editor

PLOS Computational Biology

Mark Alber

Deputy Editor

PLOS Computational Biology

***********************

Reviewer's Responses to Questions

Comments to the Authors:

Please note here if the review is uploaded as an attachment.

Reviewer #1: This work proposes the MetGEMs as integrative toolbox which can predict the functional capabilities of microbiome from amplicon sequencing data. The proposed method improved over the existing method by applying genome-scale metabolic model as a reference instead of draft genomes which results in the functional prediction improvement. However, there are the comments that are needed to be addressed in the manuscript before publication.

1. There are several functional predictors publicly available, the authors should state the reasons for selection of PICRUSt2?

2. Can the authors discuss for further improvement of MetGEMs e.g., can it be applied by Shotgun datasets?

3. The toolbox seems to be limited with the gut microbiome data or not.

4. Can the authors compare the metabolic results between Pan-, Pan-Weight, Core-, Core-Weight? Which one is the suitable for further functional prediction application?

5. For the better perfume the MetGEMs, is possible to include data in the GitHub as well?

6. Language is needed to be improved, such as “However, there have not yet been used genome-scale models (GEMs) as scaffold toolbox for microbiome analysis at a systematic level.” in the introduction part.

Reviewer #2: In their paper “MetGEMs Toolbox: Metagenome-scale models as integrative toolbox for uncovering metabolic functions and routes of human gut microbiome”, Patumcharoenpol et al. present MetGEMs, a tool for inferring metagenome-wide KEGG Ortholog and Enzyme Commission number abundances by mapping amplicon sequencing data to genome-scale metabolic network reconstructions. They demonstrate an improvement in performance relative to PICRUSt2 based on increased correlation between inferred KO/EC abundances from amplicon sequencing data and paired metagenomics data. While the software appears to be well-written, the methods underlying the software and all of the benchmarking analyses contained in the paper are severely under-described. Increasing the level of detail in the manuscript is very critical to engaging new users of the software, especially because there appears to be no formal documentation for the software in the GitHub repository. Overall, I feel that this is a very valuable contribution, but it will have much higher impact and probability of adoption if the quality and detail of the manuscript is improved.

Major comments

The authors statements of novelty for their method are overstated and should be made more nuanced. Specifically, the authors seem to be communicating that inference of community-level metabolic functionality from 16S rRNA gene sequencing data has never been performed. For example, in lines 70-72, the authors state the AGORA GEMs “... have not yet been used as a scaffold toolbox to infer metagenomic content from 16S rRNA sequenced samples at a systematic level”, but this was done to a small extent in the original AGORA paper (see the last figure in Magnusdottir et al. 2017 for inference of reaction content from both 16 rRNA gene sequencing data and shotgun metagenomics data). The authors of the AGORA paper have also since performed more in-depth versions of this analysis on many occasions (for example, see Baldini et al., BMC Biology 2020, “Parkinson’s disease-associated alterations of the gut microbiome predict disease-relevant changes in metabolic functions”). The authors’ statements describing the need for their method or the innovative aspects should include this context. In my opinion, the true innovation here is that the methodology for performing this analysis is open and packaged as software, whereas previous approaches in the field have not shared code and use obscure methods that would be difficult to reproduce. In other words, the authors have developed a tool for actually performing this analysis.

Methods are described with insufficient detail for the majority of analyses in the paper. We recommend adding more detail to the description of every analysis (including steps of the MetGEM pipeline as well as all of the analyses used to test MetGEM performance). Here is a non-exhaustive list of examples of issues that I cannot find answers to in the manuscript: 1) In the atopic dermatitis analysis, was Core- or Pan-functionality used to compute KO/ECs? 2) No methods are provided for 16S rRNA gene sequence data processing other than the software and databases used. BBDUK, DADA2, and QIIME2 all have many parameters selected by the user, and the authors provide zero parameter values. This needs much more detail to be reproducible. 3) Similar to issue (2), no details for parameters used in HUMAnN2 are provided. 4) Insufficient detail on bootstrapping is provided. Both the number of samples and the *size* of each sample are needed. Furthermore, in the analysis in Fig S1, I can’t tell what the non-bootstrapped line is supposed to be indicating; the authors should describe this.

Minor comments

Figure 2A--what do the green and blue lines represent? It looks like number of reactions, but it isn’t labelled anywhere. Also, the choice to annotate the figure with the correlation coefficient is very odd--it would be clearer to simply add an additional scatter plot showing the data that went into the correlation, and the goodness of fit for the correlation.

Within the results around lines 127-159, no justification is given for the “weighted” versions of the core/pan metrics, and it’s not clear how they are computed. The use of these metrics should be justified when they are introduced here, and their computation should be briefly described (with more detail in the methods).

Figure 1, “Specie” is not the singular form for “species”--both singular and plural forms of the words are “species”. This is unfortunate and confusing, but the authors should correct “Specie” to “Species” to be consistent with English conventions.

References to the 16S rRNA gene sequence should use the complete terminology, e.g., “16S rRNA gene sequencing”, and not “16S rRNA sequencing”, since the *gene*

**********

Have all data underlying the figures and results presented in the manuscript been provided?

Large-scale datasets should be made available via a public repository as described in the PLOS Computational Biology data availability policy, and numerical data that underlies graphs or summary statistics should be provided in spreadsheet form as supporting information.

Reviewer #1: None

Reviewer #2: Yes

**********

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

Figure 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. 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 us at figures@plos.org.

Data Requirements:

Please note that, as a condition of publication, PLOS' data policy requires that you make available all data used to draw the conclusions outlined in your manuscript. Data must be deposited in an appropriate repository, included within the body of the manuscript, or uploaded as supporting information. This includes all numerical values that were used to generate graphs, histograms etc.. For an example in PLOS Biology see here: http://www.plosbiology.org/article/info%3Adoi%2F10.1371%2Fjournal.pbio.1001908#s5.

Reproducibility:

To enhance the reproducibility of your results, PLOS recommends that you deposit laboratory protocols in protocols.io, where a protocol can be assigned its own identifier (DOI) such that it can be cited independently in the future. For instructions, please see http://journals.plos.org/compbiol/s/submission-guidelines#loc-materials-and-methods

Revision 1

Attachments
Attachment
Submitted filename: Answers_reviewers_comments.docx
Decision Letter - Sergei L. Kosakovsky Pond, Editor, Mark Alber, Editor

Dear Prof. Vongsangnak,

We are pleased to inform you that your manuscript 'MetGEMs Toolbox: Metagenome-scale models as integrative toolbox for uncovering metabolic functions and routes of human gut microbiome' has been provisionally accepted for publication in PLOS Computational Biology.

Before your manuscript can be formally accepted you will need to complete some formatting changes, which you will receive in a follow up email. A member of our team will be in touch with a set of requests.

Please note that your manuscript will not be scheduled for publication until you have made the required changes, so a swift response is appreciated.

IMPORTANT: The editorial review process is now complete. PLOS will only permit corrections to spelling, formatting or significant scientific errors from this point onwards. Requests for major changes, or any which affect the scientific understanding of your work, will cause delays to the publication date of your manuscript.

Should you, your institution's press office or the journal office choose to press release your paper, you will automatically be opted out of early publication. We ask that you notify us now if you or your institution is planning to press release the article. All press must be co-ordinated with PLOS.

Thank you again for supporting Open Access publishing; we are looking forward to publishing your work in PLOS Computational Biology. 

Best regards,

Sergei L. Kosakovsky Pond, PhD

Associate Editor

PLOS Computational Biology

Mark Alber

Deputy Editor

PLOS Computational Biology

***********************************************************

Reviewer's Responses to Questions

Comments to the Authors:

Please note here if the review is uploaded as an attachment.

Reviewer #1: The authors have solved my concerns, and thus I think that the current verison can be accepted by PLOSCB.

Reviewer #2: The authors have comprehensively addressed my concerns and I look forward to this tool being used in the field.

**********

Have all data underlying the figures and results presented in the manuscript been provided?

Large-scale datasets should be made available via a public repository as described in the PLOS Computational Biology data availability policy, and numerical data that underlies graphs or summary statistics should be provided in spreadsheet form as supporting information.

Reviewer #1: None

Reviewer #2: Yes

**********

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

Formally Accepted
Acceptance Letter - Sergei L. Kosakovsky Pond, Editor, Mark Alber, Editor

PCOMPBIOL-D-20-00865R1

MetGEMs Toolbox: Metagenome-scale models as integrative toolbox for uncovering metabolic functions and routes of human gut microbiome

Dear Dr Vongsangnak,

I am pleased to inform you that your manuscript has been formally accepted for publication in PLOS Computational Biology. Your manuscript is now with our production department and you will be notified of the publication date in due course.

The corresponding author will soon be receiving a typeset proof for review, to ensure errors have not been introduced during production. Please review the PDF proof of your manuscript carefully, as this is the last chance to correct any errors. Please note that major changes, or those which affect the scientific understanding of the work, will likely cause delays to the publication date of your manuscript.

Soon after your final files are uploaded, unless you have opted out, the early version of your manuscript will be published online. The date of the early version will be your article's publication date. The final article will be published to the same URL, and all versions of the paper will be accessible to readers.

Thank you again for supporting PLOS Computational Biology and open-access publishing. We are looking forward to publishing your work!

With kind regards,

Nicola Davies

PLOS Computational Biology | Carlyle House, Carlyle Road, Cambridge CB4 3DN | United Kingdom ploscompbiol@plos.org | Phone +44 (0) 1223-442824 | ploscompbiol.org | @PLOSCompBiol

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 .