Peer Review History

Original SubmissionJuly 28, 2022
Decision Letter - Neelesh Dahanukar, Editor

PONE-D-22-21262Mitogenome of Notobitus montanus (Hemiptera: Coreidae) and a phylogenetic analysis of CoreoideaPLOS ONE

Dear Dr. Chen,

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

Both the reviewer and the academic editor have found your manuscript interesting. However, both have comments on manuscript preparation and authors will have to revise the manuscript substantially based on the comments provided at the bottom of this email. 

Please submit your revised manuscript by Nov 12 2022 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,

Neelesh Dahanukar, 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. 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. Thank you for stating the following financial disclosure: 

"This research was funded by National Natural Science Foundation of China, grant number 32060124; Guizhou Normal University, grant number Qianshixinmiao[2021]A11"

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

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

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

4. Thank you for stating the following in your Competing Interests section:  

"The authors declare no conflicts of interest."

Please complete your Competing Interests on the online submission form to state any Competing Interests. If you have no competing interests, please state ""The authors have declared that no competing interests exist."", as detailed online in our guide for authors at http://journals.plos.org/plosone/s/submit-now 

 This information should be included in your cover letter; we will change the online submission form on your behalf.

5. Please include your full ethics statement in the ‘Methods’ section of your manuscript file. In your statement, please include the full name of the IRB or ethics committee who approved or waived your study, as well as whether or not you obtained informed written or verbal consent. If consent was waived for your study, please include this information in your statement as well.

6. Please include captions for your Supporting Information files at the end of your manuscript, and update any in-text citations to match accordingly. Please see our Supporting Information guidelines for more information: http://journals.plos.org/plosone/s/supporting-information.

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

Additional Editor Comments:

Authors have provided complete mitogenome of the Leaf-footed bug Notobitus montanus and its analysis. Apart from routine analysis, authors have also provided some comparative genomics and phylogenetics. Although the study is interesting and the analysis is performed appropriately, the manuscript is not presented well and authors will have to revise it carefully before a final decision can be made. I have made the concerns clear below.

Major comment

In several cases authors draw major conclusions without providing data or analysis. Most of this conclusion could also be because authors are not aware of several basic concepts in molecular genetics of mitochondria. Authors should know that, while making any big statement they should provide evidence or arguments based on earlier studies to support the claims.

The first claim authors make is that “Most amino acids preferred to use tRNAs encoded by nuclear genome.” It is unclear how authors came to this conclusion. The tRNAs for all 20 amino acids (including the two separate starting codons for leucine and serine) are present in the mitochondrial genome so why do authors mention that the mitochondria is using nuclear tRNAs. If this conclusion is drawn based on the mismatch between the third codon position in the CDS and tRNA anticodon arm, then authors should know that the third codon position is a wobble position.

The second claim authors make is regarding the overlap between the genes. Authors mention, “The presence of polycistron might contribute to generating overlaps between PCGs.” Authors cite reference [32] for this statement; however, the reference does not make any such claim. This statement is an ignorance of basic molecular biology of mitochondrial genome. First, polycistron has nothing to do with overlap in the genes. Most polycistron exists without overlap in the genes. In the case of mitochondria, the mitochondrial genes are generally transcribed as two large precursor polycistronic transcripts. These transcripts are subsequently cleaved to generate individual mRNAs, tRNAs and rRNAs. So polycistron does not explain the overlapping genes because even the genes that do not have overlap are transcribed from polycistronic transcripts.

Minor comments: Authors will need to improve manuscript writing substantially.

(1) Authors can add the common name “Leaf-footed bug” before Notobitus montanus to make it more accessible to non technical readers. Suggested title: Mitogenome of the leaf-footed bug Notobitus montanus (Hemiptera: Coreidae) and a phylogenetic analysis of Coreoidea

(2) As per the zoological nomenclatural rules, authority of scientific names that are written as per their original combination are not in parenthesis. Notobitus montanus is the original combination in which the species was described. So the authority and year cannot be in parenthesis. This should be - Notobitus montanus Hsiao, 1963. Make this change in abstract and remaining text.

(3) Abstract is not drafted properly. Authors unnecessarily provide details on the start and stop codons of coding genes when most of this is common in other organisms as well. In the manuscript authors talk about RSCU, compare codon usage with other species, they also provide comparison of D-loop of several species but none of this analysis is mentioned in the abstract. An abstract is a vital part of the manuscript and should be presented properly with a proper flow. There should be one or two lines providing the background of the study and its importance. One or two lines describing the methods use (also mention you determined secondary structure of tRNAs, compared genomes for codon usage and performed phylogeny). Important results in a few lines and implications of this study in understanding ecology and evolution of the species as a conclusion.

(4) The word “taxology” is normally not used in the field. What authors are referring to is called “taxonomy”.

(5) Introduction does not provide any information on the taxa under study Notobitus montanus and why it is important to study its mitogenome.

(6) As a rule, authors should use present tense when they are referring to established facts published earlier or any other facts. For example, second last line in first paragraph of results and discussion, “These two overlaps were popular in arthropods [19, 20]” should be “……. overlaps are popular in arthropods…”. Last line in third paragraph of results and discussion, “Incomplete stop codons were usually used in metazoan [18]” should be “Incomplete stop codons are usually used in metazoan [18]”. Similarly, in figure caption of figure 6, “The posterior probabilities were labeled at each node” should be “The posterior probabilities are labeled at each node”.

(7) The results are not stated properly and discussed at length. It is actually better to separate results and discussions. Authors can explain all the results in the results section and in the discussion discuss the results with respect to other mitogenomes and also discuss the implications of the results with respect to understanding ecology and evolution of the focal taxa. Authors have provided some analysis with respect to the published genomes of related taxa but the implications of the results are not clear.

(8) Figure legends should be self-explanatory and readers should understand the figure from figure legends without referring to the main text. For example, authors use several colours, numbers, etc. in figure 5 but the figure legend does not explain any of these. Similarly, for figure 6, there are two classification schemes shown in the figure but these are not explained in the figure legend. Figure legend of figure 6 also does not explain what data was used for the phylogenetic analysis, both coding and non-coding genes or just the coding genes. Although this is mentioned in the main text, as stated earlier, figure legends should be in details and self-explanatory.

(9) Supplementary information should be referred to as Fig. S1, Fig. S2, Table S1, etc. and not S1 Fig., S2 Fig., S1 Table, etc. Also, revise the figure captions to make them self-explanatory.

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

**********

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

This manuscript focuses on sequencing a mitogenome of Notobitus montanus (Hemiptera: Coreidae) - the first mitogenome of Notobitus to investigate the mitogenome structure and phylogeny analysis. Their results were consistent with Dong et al. 2022 and didn't get any innovative results but one mitogenome of a species. I have some key points that I will address here if you think it was deserved to publication.

Reference

Dong X, Wang K, Tang Z, Zhang Y, Yi W, Xue H, et al. Phylogeny of Coreoidea based on mitochondrial genomes show the paraphyly of Coreidae and Alydidae. Archives of Insect Biochemistry and Physiology. 2022;110(1):e21878.

Comments to Author:

Major questions:

Q1: Coreoidea consists of five extant families, but mitochondrial genomes in your manuscript only covered four families (Hyocephalidae not included). You should state clearly the group used for phylogeny reconstruction in all related description. Such as this sentence “The phylogenetic tree of Coreoidea was constructed with the new mitogenome and 30 mitogenomes extracted from NCBI.”

Q2: The methods for genome extraction, sequencing and mitochondrial genome assembly are inaccurate in materials and methods. “DNA was isolated from…. Mitogenomic DNA was fragmented, then ~500 bp DNA was recycled. Paired-end libraries were constructed with the Illumina platform. The mitogenome was sequenced using the…”. It confused me for obtaining the mitogenome between genomic DNA extraction and sequencing or assembly. There is more than one way to get to the mitogenome (sequence genomic DNA and then to isolate mitogenome after sequencing; enrich the mitogenome prior to sequencing and other approach).

Q3. In the Transfer RNA and ribosomal RNA genes results, you described the amino acid preferences about the use of tRNAs. “…….preferred to use tRNAs encoded by the mitogenome or nuclear genome”. How do you determine the use in the nuclear genome? And you operate only for Notobitus montanus, cannot represent the whole large group, whether there are relevant references to justify?

Q4: I think that authors should give a detailed and accurate description in results and discussion part about phylogenetic relationship. For example, you cited the reference but inaccurate. “However, based on nucleotide sequences of 13 PCGs and two rRNAs, some studies considered Alydidae and Coreidae were monophyletic [40].” It clarified the sister group of Rhopalidae with Alydidae + Coreidae but not revealed the monophyly of Alydidae and Coreidae because one subfamily of Alydidae were not covered.

Minor comments:

Q1. You used many analyses software in materials and methods, but not all of them has corresponding version number. Determine the software version you are using.

Q2. In phylogenetic analysis part, I don’t understand the operation for PCGs in Phylosuite. “These mitogenomes were imported into PhyloSuite. After standardization of sequences, the nucleic acid sequences of 13 PCGs were extracted from these mitogenomes.” I wonder what’s meaning and how to standardize in Phylosuite. That is, what is being done to the sequences.

**********

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

We have carefully read the comments from the editors and reviewers. The comments and suggestions are very valuable for us to improve this manuscript. Please see manuscript and Response to Reviewers for specific revision!

Attachments
Attachment
Submitted filename: Response to Reviewers.docx
Decision Letter - Neelesh Dahanukar, Editor

PONE-D-22-21262R1Mitogenome of the leaf-footed bug Notobitus montanus (Hemiptera: Coreidae) and a phylogenetic analysis of CoreoideaPLOS ONE

Dear Dr. Chen,

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. Revised manuscript is a substantial improvement over the earlier draft. However, there are some minor issues that authors will have to resolve before the manuscript can be finally accepted. Specific comments are made in the attached manuscript file.

Please submit your revised manuscript by Feb 05 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,

Neelesh Dahanukar, Ph.D.

Academic Editor

PLOS ONE

Journal Requirements:

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

Additional Editor Comments:

Revised manuscript is a substantial improvement over the earlier draft. However, there are some minor issues that authors will have to resolve before the manuscript can be finally accepted. Specific comments are made in the attached manuscript file.

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

Reviewers' comments:

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

Attachments
Attachment
Submitted filename: Manuscript with comments.docx
Revision 2

We have carefully read the comments from the editor and revised the manuscript according to the comments.

Attachments
Attachment
Submitted filename: Response to Reviewers.docx
Decision Letter - Neelesh Dahanukar, Editor

Mitogenome of the leaf-footed bug Notobitus montanus (Hemiptera: Coreidae) and a phylogenetic analysis of Coreoidea

PONE-D-22-21262R2

Dear Dr. Chen,

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,

Neelesh Dahanukar, Ph.D.

Academic Editor

PLOS ONE

Formally Accepted
Acceptance Letter - Neelesh Dahanukar, Editor

PONE-D-22-21262R2

Mitogenome of the leaf-footed bug Notobitus montanus (Hemiptera: Coreidae) and a phylogenetic analysis of Coreoidea

Dear Dr. Chen:

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. Neelesh Dahanukar

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 .