Peer Review History

Original SubmissionMay 15, 2023
Decision Letter - Nikolas Pontikos, Editor
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.

PONE-D-23-14875Kuura - An automated workflow for analyzing WES and WGS dataPLOS ONE

Dear Dr. Fey,

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.

In particular please address the reviewer comments about making your pipeline easy to install and run. Also please address the comment about the performance 

Please submit your revised manuscript by Aug 31 2023 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,

Nikolas Pontikos

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. Please note that PLOS ONE has specific guidelines on code sharing for submissions in which author-generated code underpins the findings in the manuscript. In these cases, all author-generated code must be made available without restrictions upon publication of the work. Please review our guidelines at https://journals.plos.org/plosone/s/materials-and-software-sharing#loc-sharing-code and ensure that your code is shared in a way that follows best practice and facilitates reproducibility and reuse.

3. In your Data Availability statement, you have not specified where the minimal data set underlying the results described in your manuscript can be found. PLOS defines a study's minimal data set as the underlying data used to reach the conclusions drawn in the manuscript and any additional data required to replicate the reported study findings in their entirety. All PLOS journals require that the minimal data set be made fully available. For more information about our data policy, please see http://journals.plos.org/plosone/s/data-availability.

"Upon re-submitting your revised manuscript, please upload your study’s minimal underlying data set as either Supporting Information files or to a stable, public repository and include the relevant URLs, DOIs, or accession numbers within your revised cover letter. For a list of acceptable repositories, please see http://journals.plos.org/plosone/s/data-availability#loc-recommended-repositories. Any potentially identifying patient information must be fully anonymized.

Important: If there are ethical or legal restrictions to sharing your data publicly, please explain these restrictions in detail. Please see our guidelines for more information on what we consider unacceptable restrictions to publicly sharing data: http://journals.plos.org/plosone/s/data-availability#loc-unacceptable-data-access-restrictions. Note that it is not acceptable for the authors to be the sole named individuals responsible for ensuring data access.

We will update your Data Availability statement to reflect the information you provide in your cover letter.

4. We note that Figure 2 in your submission contain copyrighted images. All PLOS content is published under the Creative Commons Attribution License (CC BY 4.0), which means that the manuscript, images, and Supporting Information files will be freely available online, and any third party is permitted to access, download, copy, distribute, and use these materials in any way, even commercially, with proper attribution. For more information, see our copyright guidelines: http://journals.plos.org/plosone/s/licenses-and-copyright.

We require you to either (1) present written permission from the copyright holder to publish these figures specifically under the CC BY 4.0 license, or (2) remove the figures from your submission:

a. You may seek permission from the original copyright holder of Figure 2 to publish the content specifically under the CC BY 4.0 license. 

We recommend that you contact the original copyright holder with the Content Permission Form (http://journals.plos.org/plosone/s/file?id=7c09/content-permission-form.pdf) and the following text:

“I request permission for the open-access journal PLOS ONE to publish XXX under the Creative Commons Attribution License (CCAL) CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). Please be aware that this license allows unrestricted use and distribution, even commercially, by third parties. Please reply and provide explicit written permission to publish XXX under a CC BY license and complete the attached form.”

Please upload the completed Content Permission Form or other proof of granted permissions as an "Other" file with your submission. 

In the figure caption of the copyrighted figure, please include the following text: “Reprinted from [ref] under a CC BY license, with permission from [name of publisher], original copyright [original copyright year].”

b. If you are unable to obtain permission from the original copyright holder to publish these figures under the CC BY 4.0 license or if the copyright holder’s requirements are incompatible with the CC BY 4.0 license, please either i) remove the figure or ii) supply a replacement figure that complies with the CC BY 4.0 license. Please check copyright information on all replacement figures and update the figure caption with source information. If applicable, please specify in the figure caption text when a figure is similar but not identical to the original image and is therefore for illustrative purposes only.

Additional Editor Comments:

Please address the reviewer comments below especially regarding the performance of the pipeline and its installation so that it can be easily installed, ran and tested.

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

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

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

Reviewer #1: The manuscript provides a Nextflow-based pipeline that bioinformaticians can use in their analysis of genetic variants. The pipeline runs as described but the setting up requires some clarification.

Step 3 in line 154 of manuscript, the command used only works in the docker directory and the change of directory needs to be specified in the step.

Files in the GitHub repository are named differently (default.config to standard.config) and a better guide on how to set up the config files would greatly extend the user-friendliness of this pipeline. It would also be beneficial to add supplementary files the repository explaining what each file is or a README file. Users who have not run Nextflow before would appreciate these comments.

The analysis is limited since it does not compare the effectiveness of Kuura to other pipelines based on variants called, time taken for analysis, processing power, etc. Evidence of this comparison would further convince and guide the implementation of this pipeline to existing workflows.

Reviewer #2: This work decribed a whole genome/exome sequencing workflow (Kuura) that consumes fastq files and produces annotated short genetic variants with multiple standard QC reports. It is written in Nextflow, with Docker enabled. The authors are aware of other pipelines such as SeqMule, DNAp, SpeedSeq and GESALL, but it seems their codebases are no longer maintained (most recent change to them was two years ago to SeqMule). Another Nextflow DnaSeq pipeline is Sarek that is still actively maintained and has a relatively large userbase, however its codebase is heavy and its structure is complex.

In contrast, Kuura provides a light-weight solution that requires a minimal setup and is easy to expand functionalities. It can also serve as a backbone for more advanced workflows.

Major concerns:

1. The data presented in Table 3 are surprising. The precisions and recalls are worryingly low. These numbers should be much higher according to Zhao et al., 2020 (https://doi.org/10.1038/s41598-020-77218-4).

Minor concerns:

1. There is no Readme in the github repository. A Readme with a brief desription of the workflow, and instructions to setup and test is necessary.

2. The existing workflow exclusively supports Docker as a solution. However, Docker's incompatibility with many High Performance Computing (HPC) systems hampers its widespread utilization. The authors should consider to include Singularity. (For reference, https://depot.galaxyproject.org/singularity/ has a wide range of images)

3. There are hardcoded parameters in the workflow (e.g. https://github.com/dhanaprakashj/kuura_pipeline/blob/main/dnaseq/main.nf#L96, https://github.com/dhanaprakashj/kuura_pipeline/blob/main/dnaseq/main.nf#L128, https://github.com/dhanaprakashj/kuura_pipeline/blob/main/dnaseq/main.nf#L206). Please make them configurable.

4. The workflow will work best with a small number of exomes. I think it might struggle with large number of exome samples or whole genomes. The authors should discucss this.

**********

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: Yes: Jing Yu

**********

[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

Journal Requirements:

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

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

Response: Thank you for pointing that out. We have corrected the author’s affiliation information to meet the style requirements.

Comment 2. Please note that PLOS ONE has specific guidelines on code sharing for submissions in which author-generated code underpins the findings in the manuscript. In these cases, all author-generated code must be made available without restrictions upon publication of the work. Please review our guidelines at https://journals.plos.org/plosone/s/materials-and-software-sharing#loc-sharing-code and ensure that your code is shared in a way that follows best practice and facilitates reproducibility and reuse.

Response: Thank you for the comment. We added a section “Code Availability and Accessibility” naming the code repository. All code is made publicly available at https://github.com/dhanaprakashj/kuura_pipeline.

Comment 3. In your Data Availability statement, you have not specified where the minimal data set underlying the results described in your manuscript can be found. PLOS defines a study's minimal data set as the underlying data used to reach the conclusions drawn in the manuscript and any additional data required to replicate the reported study findings in their entirety. All PLOS journals require that the minimal data set be made fully available. For more information about our data policy, please see http://journals.plos.org/plosone/s/data-availability.

Response: Thank you for that comment. We added a section “Data availability” detailing the FTP access to the downloaded files.

Comment 4. We note that Figure 2 in your submission contain copyrighted images. All PLOS content is published under the Creative Commons Attribution License (CC BY 4.0), which means that the manuscript, images, and Supporting Information files will be freely available online, and any third party is permitted to access, download, copy, distribute, and use these materials in any way, even commercially, with proper attribution. For more information, see our copyright guidelines: http://journals.plos.org/plosone/s/licenses-and-copyright.

Response: Thank you for pointing that out. We removed all potentially copyrighted parts of figure 2 and uploaded a new image file.

Reviewers' comments:

Reviewer #1:

Comment 1. Step 3 in line 154 of manuscript, the command used only works in the docker directory and the change of directory needs to be specified in the step.

Response: Thank you for spotting that, it is indeed an important step that has been missed. We added a statement to change the directory after downloading the git repository.

Comment 2. Files in the GitHub repository are named differently (default.config to standard.config) and a better guide on how to set up the config files would greatly extend the user-friendliness of this pipeline. It would also be beneficial to add supplementary files the repository explaining what each file is or a README file. Users who have not run Nextflow before would appreciate these comments.

Response: Thank you for pointing that out. We corrected the file names in the github repository and added a README file documenting the basic setup procedure.

Comment 3. The analysis is limited since it does not compare the effectiveness of Kuura to other pipelines based on variants called, time taken for analysis, processing power, etc. Evidence of this comparison would further convince and guide the implementation of this pipeline to existing workflows.

Response: Thank you for the remark. We are aware of that and have seen such comparisons in the literature. However, in our opinion, a comparison of this kind would be short-lived as the specifications of our workflow as well as those of the compared tools, and computing resources change quickly. It would also not accurately reflect the main objective of Kuura which is to provide reproducible end-to-end variant calling with minimal setup as detailed in the manuscript. That is, we do not aim at a particular performance level but rather usability and practical applicability in a reproducible manner.

Reviewer #2:

Major concerns:

Comment 1. The data presented in Table 3 are surprising. The precisions and recalls are worryingly low. These numbers should be much higher according to Zhao et al., 2020 (https://doi.org/10.1038/s41598-020-77218-4).

Response: Thank you for the comment; the validation values were indeed very low, a fact that we were aware of, but we reported those values nonetheless as they represent the unbiased results of our analysis.

To find the cause for the discrepancy between previously published validation values and remedy the concern we repeated the validation with different settings.

Below are the steps we took to to arrive at the now presented outcome:

- We used a completely different set of sequencing data; the new set was sequenced on an Illumina NovaSeq 6000 system (as compared to a llumina HiSeq 2500 before).

- We used a different targets bed file for coverage analysis and hap.py validation (idt_capture_novogene.grch38.bed) matching the validation set experiment.

NB: The bed file used before also matched the experiment (provided by the Garvan institute along with the read files).

- We ran the pipeline separately for both trimming tools on sample NA12878, using cutadapt in one setting and fastp in the other, both yielding similar results to those seen when using the respective other tool (see table in the Rebuttal Letter).

NB: The originally presented results were generated using cutadapt on the Garvan samples and the results presented now were generated using fastp on the NovaSeq samples.

In addition, we ran several tests manually, i.e., outside the pipeline environment, including:

- Complete manual pipeline workflow rerun of the Garvan sample NIST7035_TAAGGCGA using only DeepVariant resulting in the same validation outcome as in the previous version of the manuscript.

NB: When we tested different target bed files on the Garvan samples we noticed an improvement whenever NOT using the Garvan bed file, with the idt_capture_novogene.grch38.bed giving the best results (see table in the Rebuttal Letter).

- Running the exome sequencing case study presented on the DeepVariant github site (starting from BAM files) resulting in comparable validation values.

- Complete manual pipeline workflow rerun of the DeepVariant case study data (HG003_NA24149_father read files) using only DeepVariant arriving at comparable results as presented in the case study.

In addition, when running the tests we notice that, by mistake, all detected variants had been counted instead of only SNPs. That was corrected so all new tables now contain only SNP counts.

As can be seen in the revised table in the manuscript the new data yielded results much closer to those published in recent pipeline comparison papers and case studies. The outcome of abovementioned comparison runs using different settings and input files led us to the conclusion that the originally used Garvan data set is the main cause for the low validation values.

However, since it is not the main goal of this manuscript to evaluate the performance of different variant callers but rather to present an easy-to-use sequencing data analysis pipeline relying on several widely used, validated calling engines, we did not go to the same length in terms of validation before the first submission, obviously missing the potential flaw in the source data. The successful revalidation, though, proves that the pipeline works and further strengthens the point of our proposed consensus call file with high-confidence variants given that different variant callers yield sometimes dramatically different results and may indeed be not applicable to all types of sequencing projects.

Minor concerns:

Comment 1. There is no Readme in the github repository. A Readme with a brief description of the workflow, and instructions to setup and test is necessary.

Response: Thank you for the comment; the README file was indeed forgotten when creating the remote repository and now added.

Comment 2. The existing workflow exclusively supports Docker as a solution. However, Docker's incompatibility with many High Performance Computing (HPC) systems hampers its widespread utilization. The authors should consider to include Singularity. (For reference, https://depot.galaxyproject.org/singularity/ has a wide range of images)

Response: This is a relevant point, and we are aware of the limitations regarding the use of Docker for security reasons. Docker was used initially because we had the most experience with this container software but have worked on a Singularity container which will be added to the repository in a future release of the pipeline. Singularity is able to pull, build from and run Docker containers which might be a solution for more experienced users already now.

Comment 3. There are hardcoded parameters in the workflow (e.g. https://github.com/dhanaprakashj/kuura_pipeline/blob/main/dnaseq/main.nf#L96, https://github.com/dhanaprakashj/kuura_pipeline/blob/main/dnaseq/main.nf#L128, https://github.com/dhanaprakashj/kuura_pipeline/blob/main/dnaseq/main.nf#L206). Please make them configurable.

Response: Thank you for pointing those out, we corrected these parameters.

Comment 4. The workflow will work best with a small number of exomes. I think it might struggle with large number of exome samples or whole genomes. The authors should discucss this.

Response: Thank you for pointing out that concern. We have tested the pipeline on WES as well as WGS data sets and found, apart from the run time and larger requirements in terms of computing resources, that it performs equally well for both.

Attachments
Attachment
Submitted filename: Rebuttal_letter_PONE_231012.docx
Decision Letter - Alvaro Galli, Editor

Kuura - An automated workflow for analyzing WES and WGS data

PONE-D-23-14875R1

Dear Dr. Fey,

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,

Alvaro Galli

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: N/A

**********

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 addressed all my comments. However, as I ran through it again I think that having the option to include compensating set of variants, i.e. variants called by some variant callers, but not all, could be an important improvement, e.g. for finding rare variants underlying Mendelian disorders.

**********

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: Yes: Jing Yu

**********

Formally Accepted
Acceptance Letter - Alvaro Galli, Editor

PONE-D-23-14875R1

PLOS ONE

Dear Dr. Fey,

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

If revisions are needed, the production department will contact you directly to resolve them. If no revisions are needed, you will receive an email when the publication date has been set. At this time, we do not offer pre-publication proofs to authors during production of the accepted work. Please keep in mind that we are working through a large volume of accepted articles, so please give us a few weeks to review your paper and let you know the next and final steps.

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

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

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

Kind regards,

PLOS ONE Editorial Office Staff

on behalf of

Dr. Alvaro Galli

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 .