Peer Review History

Original SubmissionSeptember 3, 2020
Decision Letter - Ludmila Prokunina-Olsson, 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-20-27691

PEREGRINE:  A Genome-wide Prediction of Enhancer to Gene Relationships Supported by Experimental Evidence

PLOS ONE

Dear Dr. Mi,

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 Dec 04 2020 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org. When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file.

Please include the following items when submitting your revised manuscript:

  • A rebuttal letter that responds to each point raised by the academic editor and reviewer(s). You should upload this letter as a separate file labeled 'Response to Reviewers'.
  • A marked-up copy of your manuscript that highlights changes made to the original version. You should upload this as a separate file labeled 'Revised Manuscript with Track Changes'.
  • An unmarked version of your revised paper without tracked changes. You should upload this as a separate file labeled 'Manuscript'.

If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter.

If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: http://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols

We look forward to receiving your revised manuscript.

Kind regards,

Ludmila Prokunina-Olsson, PhD

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

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

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. Is the manuscript technically sound, and do the data support the conclusions?

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

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

Reviewer #1: I Don't Know

Reviewer #2: Yes

**********

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

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

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

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

Reviewer #1: Yes

Reviewer #2: Yes

**********

5. Review Comments to the Author

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

Reviewer #1: The authors describe an online resource PEREGRINE they’ve developed that examines enhancer-gene links based on the available eQTL data, HiC and ChiaPET data. Through the Panther web interface, users can search for genes and retrieve a list of candidate enhancers. The authors generated a list of putative enhancers using four large databases and then identified enhancers that physically interacted with promoters (HiC and ChIA-PET) or contained an eQTL and the corresponding gene(s). They highlight three examples of previously experimentally validated enhancers and the concordance among the newly developed PEREGRINE database. The authors highlight the limitations of this database, such as statistical validation of the predicted enhancer-gene links and acknowledge the need to develop such standards.

The PEREGRINE tool developed by the authors will be a valuable resource for scientists to identify likely enhancers for their favorite gene(s) or identify genes that a particular non-coding region may regulate prior to functional work. Overall, the paper is well written. Including experimentally validated examples from the literature strengthens the paper and supports the validity of the database.

Minor Revisions:

• The authors define in the introduction what typically denotes an enhancer region, but the criteria used in the individual datasets to classify a non-coding element as an enhancer. i.e., H3K27ac, DHS, H3K4me1, TF binding, etc, should be acknowledged in the methods as there might be variation amongst the datasets.

• It is unclear how the expected number of links was determined for the GO analysis?

• Line 209: Table 4 caption indicates that the most target genes an enhancer has is 17, but the table indicates 34.

• Lines 210-211: Table 4 caption states that over 77% of enhancers are linked to only 1 gene, but the table and text suggest 56% of enhancers have 1 gene, 78% of enhancers have either 1 or 2 genes linked to it.

• Line 211-212: Table 4 caption states >97% of enhancers have 4 or less target genes, this is not what is represented in the text or table. 93% of enhancers have 4 or less target genes, 97% of enhancers have 6 or less target genes.

• Figure 5 is hard to distinguish the genes from the enhancers. Additionally, in the UCSC Genome Browser, the browser image can be viewed by right clicking the browser and saved rather than a browser screen shot.

• Lines 263-266: Figure 5 caption b) does not match the figure, it should be chromosome 14

• It is not clear to this reviewer what is gained by Figure 6 as it is the same data in figure 4 but in bins of 5.

• Please ensure that the appropriate nomenclature is used for gene and protein names.

• Figure 9, the label position for the non-PEREGRINE enhancer datasets is poorly placed inside the PEREGRINE enhancer circle. In this reviewer's opinion, it made interpretation confusing.

Reviewer #2: The authors present a comprehensive database of experimentally validated enhancer-gene links. This database aims to bridge the gap between sources which compile information regarding candidate enhancer regions which are agnostic to the enhancer’s target gene and sources which implicate target genes. Assignment of regulatory regions to their target genes often takes a ‘nearest gene’ approach. The authors frequently give well researched examples of variants identified in GWAS and how they may relate to various putative target genes. The identification of target genes (and therefore nomination of pathways etc.) facilitates a far greater understanding of pathological mechanisms than enhancer data alone.

The PANTHER database is a well-regarded and commonly used tool and an extension such as this fits well with the rest of the database and the types of statistical analyses which are undertaken.

The authors make a compelling case for the database in comparison to other tools. They rightly make the case that statistical validation is difficult and remain open to the possibility that spurious gene-enhancer links may well be included. Future work aims to make progress in this area.

While for the most part the manuscript is technically sound, there are instances throughout where table and figure legends do not agree with the data in the table or figure (e.g. Table 4). Multiple figures and tables which largely show the same data seems unnecessary and could be condensed (fig 2, 3 and table 4). Screenshots of UCSC genome browser views are not the most appropriate figure when the same tool allows for the output of figures as PDF without any of the online user interface as part of the final figure.

**********

6. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy.

Reviewer #1: No

Reviewer #2: No

[NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.]

While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/. PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org. Please note that Supporting Information files do not need this step.

Revision 1

Dear Dr. Ludmila Prokunina-Olsson and reviewers,

We thank you and the reviewers very much for the thorough reading of our manuscript and for the helpful critiques. Enclosed please find our revised manuscript. Since the manuscript was originally submitted to PLOS Computational Biology, it was formatted according to its guidelines. In this revision, the following format updates were made to meet the guidelines of PLOS One.

1. The “Author summary” section was deleted.

2. The “Materials and methods” section was moved up to right after the “Introduction” section.

3. The “Results” and “Discussion” sections in the original manuscript were combined into the “Results and discussion” section in the revised manuscript.

4. A “Conclusion” section was added.

Due to the reformat, as well as other updates suggested by the reviewers, the figure, table and line numbers are different in the revised manuscript compared to the original one. In our response below, I will make sure to specify the version of manuscript used, and if needed, use numbers from both versions.

Below are the specific responses to each of the reviewers’ comments. The modified texts are highlighted in red in the “Revised Manuscript with Track Changes”.

Reviewer #1:

Minor Revisions:

• The authors define in the introduction what typically denotes an enhancer region, but the criteria used in the individual datasets to classify a non-coding element as an enhancer. i.e., H3K27ac, DHS, H3K4me1, TF binding, etc, should be acknowledged in the methods as there might be variation amongst the datasets.

We thank the reviewer for pointing it out. We clarify this by modify the description in the Materials and methods section (line 159-163 in the revised manuscript) as below:

“These enhancer coordinates were the result of experiments performed across various tissues by their respective sources, which differed somewhat according to each enhancer source. We did not filter out any enhancers from these sources, instead opting to utilize their differing enhancer calling pipelines simultaneously to maximize the chance of capturing the highest number of enhancers.”

• It is unclear how the expected number of links was determined for the GO analysis?

We appreciate reviewer’s comment here. We clarified the meaning of “expected” under the subsection of “Statistical Analysis” in “Materials and Methods” section (line 248-249 in the revised manuscript) by rephrasing the sentence as below:

“We performed enrichment analysis using Gene Ontology Biological Processes if there were any gene pathways enriched by having more or less than the expected number of linked enhancers per gene under the null hypothesis of the Mann Whitney U test that the two samples come from the same distribution via the PANTHER web interface.”

• Line 209: Table 4 caption indicates that the most target genes an enhancer has is 17, but the table indicates 34.

We apologize for the mistakes here. We corrected the number to 34 in line 306 in the revised manuscript.

• Lines 210-211: Table 4 caption states that over 77% of enhancers are linked to only 1 gene, but the table and text suggest 56% of enhancers have 1 gene, 78% of enhancers have either 1 or 2 genes linked to it.

We corrected the number to 56% in line 306 in the revised manuscript.

• Line 211-212: Table 4 caption states >97% of enhancers have 4 or less target genes, this is not what is represented in the text or table. 93% of enhancers have 4 or less target genes, 97% of enhancers have 6 or less target genes.

We corrected the text to “97% of enhancers here were found to have six or less target genes” in line 308 in the revised manuscript.

• Figure 5 is hard to distinguish the genes from the enhancers. Additionally, in the UCSC Genome Browser, the browser image can be viewed by right clicking the browser and saved rather than a browser screen shot.

We thank the reviewer for the suggestion. The figures (Figure 3 in the revised manuscript) were regenerated with the suggested method.

• Lines 263-266: Figure 5 caption b) does not match the figure, it should be chromosome 14

We corrected the caption for Figure 5b to “chromosome 14” in line 348 of the revised manuscript.

• It is not clear to this reviewer what is gained by Figure 6 as it is the same data in figure 4 but in bins of 5.

We take the reviewer’s advice and removed the figure from the manuscript.

• Please ensure that the appropriate nomenclature is used for gene and protein names.

We appreciate reviewer’s comment. Under the subsection of “Utilizing the PEREGRINE data in PANTHER”, examples of genes and their relationships to the enhancers were described. All the gene names on page 21-23 of the revised manuscript are italicized according to the gene nomenclature guideline.

• Figure 9, the label position for the non-PEREGRINE enhancer datasets is poorly placed inside the PEREGRINE enhancer circle. In this reviewer's opinion, it made interpretation confusing.

The figure (Figure 6 in the revised manuscript) labels were updated to make it more clear about the non-PEREGRINE sections.

Reviewer #2:

While for the most part the manuscript is technically sound, there are instances throughout where table and figure legends do not agree with the data in the table or figure (e.g. Table 4).

We thank reviewer’s comment. We updated the legends for Table 4 and Figure 3 in the revised manuscript (Figure 5 in the original version) (see our response to reviewer 1 above). We also reviewed all the other figure and table legends to make sure that the descriptions are accurate.

Multiple figures and tables which largely show the same data seems unnecessary and could be condensed (fig 2, 3 and table 4).

This is a good suggestion. We combined Figures 2, 3, 4 in the original manuscript to one figure, Figure 2 in the revised one.

Screenshots of UCSC genome browser views are not the most appropriate figure when the same tool allows for the output of figures as PDF without any of the online user interface as part of the final figure.

The figure (Figure 5 in the original manuscript, and Figure 3 in the revised one) was regenerated according to the suggested method.

We thank you and the reviewers again for the helpful suggestions and comments.

Sincerely,

Huaiyu Mi, Ph.D.

Department of Preventive Medicine

Keck School of Medicine

University of Southern California

Attachments
Attachment
Submitted filename: Response to Reviewers.docx
Decision Letter - Ludmila Prokunina-Olsson, Editor

PEREGRINE:  A Genome-wide Prediction of Enhancer to Gene Relationships Supported by Experimental Evidence

PONE-D-20-27691R1

Dear Dr. Mi,

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,

Ludmila Prokunina-Olsson, PhD

Academic Editor

PLOS ONE

Additional Editor Comments (optional):

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

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

Reviewer #1: All comments have been addressed

Reviewer #2: All comments have been addressed

**********

2. Is the manuscript technically sound, and do the data support the conclusions?

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

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

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

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

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

Reviewer #1: Yes

Reviewer #2: Yes

**********

6. Review Comments to the Author

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

Reviewer #1: This manuscript is well written and the dataset the authors have developed will be a useful resource for scientists seeking to understand enhancer biology and the genes they regulate. The authors addressed all of the reviewer concerns. There are 2 very minor details that don't affect the manuscript's conclusions but should be addressed before final publication.

Figure 2 A & B legends are switched based off the figure order presented.

Screenshot for Figure 4 shows the "Press F11 to exit full screen" notification.

Reviewer #2: The authors have adequately addressed the comments raised in the previous round of review and the manuscript is now suitable for publication.

**********

7. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy.

Reviewer #1: No

Reviewer #2: No

Formally Accepted
Acceptance Letter - Ludmila Prokunina-Olsson, Editor

PONE-D-20-27691R1

PEREGRINE:  A Genome-wide Prediction of Enhancer to Gene Relationships Supported by Experimental Evidence

Dear Dr. Mi:

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. Ludmila Prokunina-Olsson

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 .