Peer Review History
| Original SubmissionOctober 3, 2024 |
|---|
|
PONE-D-24-43959Can you hear me? Playback experiment highlights porpoise detection range differences between commonly used PAM devices: C-POD, F-POD, and SoundTrap.PLOS ONE Dear Dr. Todd, 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 Jan 17 2025 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org . When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file. Please include the following items when submitting your revised manuscript:
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, Vitor Hugo Rodrigues Paiva, 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 2. In your Methods section, please provide additional information regarding the permits you obtained for the work. Please ensure you have included the full name of the authority that approved the field site access and, if no permits were required, a brief statement explaining why 3. Thank you for stating the following financial disclosure: “This work was funded by the Irish Research Council Government of Ireland Postgraduate Scholarship Scheme (Project ID: GOIPG/2019/2173).” 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 the Acknowledgments Section of your manuscript: “This work was funded by the Irish Research Council Government of Ireland Postgraduate Scholarship Scheme (Project ID: GOIPG/2019/2173). We would like to thank Nick Tregenza for the loan of the F- POD that supported this project and the technical support provided by the Chelonia team. All those who provided discussions during the conception of this study including Ollie Boisseau, Mats Amundin, Hanna Nuuttila, Jamie MacAulay, Magnus Wahlberg and Luke Rendell. We would also like to thank Sam Cox for providing the SoundTrap for this experiment. We are grateful to Michael Collins skipper of the Kestrel, and for various field assistants for facilitating the fieldwork in Roaringwater Bay. Open access funding provided by IReL.” We note that you have provided funding information that is not currently declared in your Funding Statement. However, funding information should not appear in the Acknowledgments section or other areas of your manuscript. We will only publish funding information present in the Funding Statement section of the online submission form. Please remove any funding-related text from the manuscript and let us know how you would like to update your Funding Statement. Currently, your Funding Statement reads as follows: “This work was funded by the Irish Research Council Government of Ireland Postgraduate Scholarship Scheme (Project ID: GOIPG/2019/2173).” Please include your amended statements within your cover letter; we will change the online submission form on your behalf. 5. 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. [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: Yes 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: This is a useful article especially to researchers conducting long-term monitoring using different devices, with good insights on EDR/EDA implications. As I mentioned, the duration of the recording itself (or recording type) could be a factor in the reception of the signal by the PAM device, and therefore should be investigated if it is a relevant factor. It is well-written and the structure is clear and concise, but I suggest improving the figures and adding the figure from the supplementary to the article (see my comment in the pdf). I would also like to see more details on the results of model selection. Reviewer #2: Dear Authors Thank you for conducting the research and preparing this manuscript comparing the detection performance of commonly used acoustic recorders. I found the manuscript to be well written, concise, and interesting. I think this manuscript will be of great interest to the audience of this journal. I don't have a lot comments except for the few in the marked up document. ********** 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 |
|
PONE-D-24-43959R1Can you hear me? Playback experiment highlights porpoise detection range differences between commonly used PAM devices: C-POD, F-POD, and SoundTrap.PLOS ONE Dear Dr. Todd, 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 Feb 28 2025 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org . When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file. Please include the following items when submitting your revised manuscript:
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, Vitor Hugo Rodrigues Paiva, 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. [Note: HTML markup is below. Please do not edit.] 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 Reviewer #3: (No Response) ********** 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 Reviewer #3: Partly ********** 3. Has the statistical analysis been performed appropriately and rigorously? Reviewer #2: Yes Reviewer #3: I Don't Know ********** 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 Reviewer #3: 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 Reviewer #3: 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: Thank you for the revised manuscript. My comments and suggestions were properly addressed, and I have no further comments. Reviewer #3: General comments I think this is a very useful experiment and paper but it could use more detail and clarification. I realize this is not the first set of review comments and in the detailed comments below I have made an effort to be explicit about what information would be helpful. An additional sentence or two in the identified paragraphs should provide the necessary information. If the results from one of the gain settings were excluded, this needs to be explained and the total number of playbacks included in the analysis should be consistent. If the results from both settings were used, I would suggest explaining why they were combined in the results. The rationale behind and composition of the playback methods, especially where the method differs from those in the cited methods papers, should be justified. For example, Nuuttila et al. (2018) reported EDR results for both artificial and recorded harbour porpoise calls and by detected versus classified click trains (Figure 4). The selection of the five recordings is not explained. A previous reviewer questioned the duration of the recordings, and from the manuscript it is not clear how the 0.55 - 2.8 sec clips were combined into a one minute playback, how many times the clips were played, or at what gain. I understand a bit better after reviewing the playback2.2.csv file on your Github, but this information needs to be in the manuscript. A diagram of how the playbacks were composed would help the reader and even a condensed version of the results spreadsheet could be included in an appendix. I would like more information to understand how your analysis supports the comparison of EDR for the recorded buzzes versus clicks. My understanding is that you have calculated the source level of the playback but are assuming the difference in these values could represent the difference in true source levels. However, this seems like a coincidence as in theory the buzz could have been detected at a higher received level than the click train (in the pool) depending on the distance and orientation of the captive harbour porpoise from the receiver. You reference the 8dB difference in the discussion, but I would recommend briefly explaining your rationale and assumptions in the methods. The other differences between the recordings (duration, number of clicks, frequency) and how this might impact detection range should also be discussed. It should be clear throughout the manuscript that you have estimated detected range of the playbacks and not of harbour porpoise, given the source levels of the playbacks are much lower than the maximum source levels referenced. The title of the manuscript might imply that the values reported represent harbour porpoise detection ranges, but the emphasis should be on comparing the devices. I would suggest you review the use of the word “their” (when referencing the instruments) and the term “vocalisations” throughout the manuscript. I realize this is a common practice, but as clicks are not produced using vocal cords, some odontocete scientists prefer to use “clicks”, “acoustic signals” or “calls”. Detailed comments Line 54-55: beaked whale researchers are transitioning from “Cuvier’s” to “goose-beaked” Line 65: change “their successor” to “its successor” Lines 92-96: Does the literature suggest why FPODs and SoundTraps detected more than C-PODs other than ambient noise? Here or in the methods would be a good place to provide a bit more information about how the click train detectors work on C-PODs and F-PODs as this likely has a significant impact on what would be detected in a long term monitoring study. Line 97: change “...their detection ranges…” to “its detection range” or “the detection range” Line 100-101: would suggest a less broad statement such as “assessing the effect of porpoise call type including echolocation clicks and foraging buzzes” and I still recommend that more information is needed about why the recordings selected can be representative of these two types of echolocation. Line 114: What frequency was the high pass filter set to? Line 131-148: An explanation of how / why the five recordings were selected would be helpful, and why artificial signals were not used. You could also explain how / why Rec3 and Rec5 are representative of the two echolocation types. Line 140-142: Here general observation clicks are defined as being regular echolocation clicks but in Table 1 these recordings include buzzes. I would suggest updating the paragraph or the table for consistency. Line 144-145: Does off axis echolocation refer to a signal being emitted off centre or the recording of a signal outside of the beam? This sentence could be improved with some rephrasing. Line 155: I assume dBpp refers to peak to peak but it is helpful to state that clearly when it is first referenced as sometimes dBpp is used to denote zero to peak. Lines: 154-159: I would recommend briefly addressing these points again in your discussion. (1) The source levels of the playbacks were much lower than maximum porpoise source levels. A brief discussion of how this does or does not impact your results would be helpful. (2) The source levels of the captive porpoise was not calculated. How is the source level of the playback relevant to the comparison of the different click types? (2) Click characteristics from these recordings might be different than those in the wild. Does this impact your results and conclusions? Is there any information about how C-POD and F-POD detectors perform with captive animal signals? It would be helpful to see that you have considered these factors in your interpretations and conclusions. Line 164-165: It would be helpful if you explained how you decided on the bearings of the two transects. Line 186: I would suggest replacing “circa” with “approximately” Line 188-190: This should be reworded for clarity. It is not clear how the playbacks were composed and it is difficult to follow the numbers referenced here and in the results. In addition, if each recording (n = 5) was played at two gain settings, the use of the gain and how it impacts the results should be clarified. Why were those gain settings selected? Line 190 states there were 10 playbacks per station but in the results (Table 2) it is reported that there were 8 playbacks per recording and 40 playbacks at each station. Was each of the 5 recordings played 4 times at each station (given there were two replicates)? Was the sequence of recordings (Rec1, Rec2, Rec3, Rec4, Rec5, Rec1, Rec2, … etc.) repeated 4 times within one minute? What was the buffer (time gap) between the recordings? How were the two gain values used? From the playback2.2.csv file on your Github it seems that a recording was repeated a certain number of times to make up one minute, and this repeated sequence was played sequentially. This needs to be explained in your methods. It is difficult to evaluate the results from the CPOD or FPOD click detector or the manual review of the sound data in Audacity without understanding how these recordings were compiled and how the playbacks were conducted. A diagram or spectrogram of how the recordings were composed - i.e. what was played at each station - would be helpful. Line 205-208: Given signals were transmitted from a transducer using two different gain settings, I would expect a mean source level or two different estimates of source level. In the playback2.2.csv file on your Github, source levels for playbacks at the 50 dB gain settings are reported. If you excluded the results from one of the gain settings, this needs to be explained - there are 240 rows in your results spreadsheet, if half were excluded the total number of playbacks should add up to 120 (your results report 240 playbacks)? Also, please explain why one SPL measurement was taken across the full spectrum, as often the focus should be on the peak frequencies of interest. Please clarify how you measured and calculated SPL and SL from one or more playbacks of the five different recordings. Line 208: Needs a period Line 214-215: Can you provide more detail about how you defined a “valid detection”. Nuuttila et al. (2018) provide details that would be helpful here, e.g., they recorded the number of clicks detected and whether only part of the sequence was recorded. They also divided C-POD results based on whether clicks were detected in the raw files, by the click train detector, or as porpoise click trains. Use of results from only raw files should be explained as this is relevant to how well a C-POD or F-POD will perform in long term studies - when the click detector and classification as NBHF will be relied on. Line 221-225: Similar to my questions above, how was a detection validated? Did the entire one minute recording have to be detected or did partial recordings count? Line 234: Was the replicate or gain used on the transducer not relevant? Line 261: Should “wheras” be “wherein” or “within which”? Line 263: Missing a “)” Line 284-288: The detection of these two recordings, especially on the F-POD and C-POD, could differ due to factors such as frequency, duration, number of clicks, and amplitude. A justification for why those recordings were selected as representative of two echolocation behaviours would be helpful. In addition, if the assumption is that the difference in playback source level is representative of the difference in source level of an echolocation click train versus buzz click train, this needs to be explained and justified by literature. Line 295: This section and the title of Table 2 contains some information that would be helpful in the methods when explaining how the playbacks were designed and conducted. In the methods (Line 188) states that each playback is the transmission of each recording per gain setting. There is no reference to the different gain settings in the results. This should be clarified in the methods and results. The playback2.2.csv file on your Github shows that the engine as one for the start of your playbacks. Even if this does not impact results, it should be noted. Furthermore, for both tracks 1.1 and 1.2 the measured distance (“true distance” column) from the mooring for stations at 100 and 200 m are recorded as 128.75 m and 225.97 m. This should be explained. Did your include these true distances in your distance analysis or models? If not, you could explain why you assumed it would not alter your results. Line 300: The F-POD detected 90/240 playbacks, 18 were marked as click trains, and two as NBHF. This represents fairly poor performance by the F-POD; I would expect due to the source level, short duration of the recordings and limited number of clicks. A brief discussion of this and some more details on how the click train detector and NBHF classifier works would be helpful - does it rely on a certain number of clicks to identify a click train? I think it is relevant to know which of the recordings were identified as click trains and which of those were identified as NBHF. This is also why it would be helpful to understand the rationale behind the recordings selected and experiment design. I suggest this is relevant because for long term monitoring I expect the click detector and NBHF classifier would be relied on, as opposed to manual review used to find the 90 detections. Table 2: Including percentages would be helpful as it is difficult to determine how many playbacks were detected out of the total played for each recording and each station (distance). For example, 100 playbacks were detected by the SoundTrap, which is ~42%. If two gain settings were used, that information should also be in the table. Line 327: I would suggest including a sentence that reports the EDV values before comparing them as percentages. Line 434: Replace the “&” with “and” Line 348: suggest replacing “therein” with another word as it’s not the correct use Line 350: change “...their detection rates…” to “... detection rates…” Line 354: change use of “their” Line 359: suggest adding a period after C-POD and making this two sentences Line 360: Is “precision” the correct word here? Line 361-363: The two recordings used as representative of call types had different source levels, but this has not been linked to the source level of the captive porpoise. If you are assuming that the difference in source levels, as well as other characteristics that impact detection on the devices, is representative of the difference in clicks and buzzes, this needs to be explained. In addition, it should be clear that you have estimated detected range of the playbacks and not of harbour porpoise given the source levels of the playbacks are much lower than the maximum source levels referenced. Given you should have source level and received level values, you could calculate transmission loss and estimate detection range with the theoretical maximum source level. Line 393: “subsequently” means “afterward”, I would suggest selecting a different word here Line 400-401: Detection range of wild porpoise could also be greater than experimental estimates depending on environmental conditions, devices, and source levels. You reference this at line 381. Line 406: Line 397 states that EDR has varied considerably between devices, was this due to a calibration issue? Line 418: Does this reference the calculated source level of the different recordings or the change in gain used for the transducer? Line 422: Wouldn’t amplitude of a signal be related to source level? Line 425: I’m not sure the difference in bearing between the two transects provides enough information to make conclusions about how the orientation of the devices impacted detection. I assume the devices might rotate or turn while in the water column? Line 442-445: I suggest a brief explanation for why the difference in source level of these two playbacks was assumed representative of the difference between click and buzz source level be provided in the methods. Other than the reduced source level, is it possible the frequency, duration, or number of clicks impacted whether these two recordings were detected? If not, why? Line 453-455: Do you have a reference for this? Directionality of the echolocation beam impacts detection range but is it more an issue of detection probability? ********** 7. PLOS authors have the option to publish the peer review history of their article (what does this mean? ). If published, this will include your full peer review and any attached files. If you choose “no”, your identity will remain anonymous but your review may still be made public. Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy . Reviewer #2: No Reviewer #3: 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 2 |
|
Can you hear me? Playback experiment highlights detection range differences between commonly used PAM devices: C-POD, F-POD, and SoundTrap. PONE-D-24-43959R2 Dear Dr. Todd, We’re pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it meets all outstanding technical requirements. Within one week, you’ll receive an e-mail detailing the required amendments. When these have been addressed, you’ll receive a formal acceptance letter and your manuscript will be scheduled for publication. An invoice will be generated when your article is formally accepted. Please note, if your institution has a publishing partnership with PLOS and your article meets the relevant criteria, all or part of your publication costs will be covered. Please make sure your user information is up-to-date by logging into Editorial Manager at Editorial Manager® and clicking the ‘Update My Information' link at the top of the page. If you have any questions relating to publication charges, 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, Vitor Hugo Rodrigues Paiva, Ph.D. Academic Editor PLOS ONE Additional Editor Comments (optional): Reviewers' comments: |
| Formally Accepted |
|
PONE-D-24-43959R2 PLOS ONE Dear Dr. Todd, 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. Vitor Hugo Rodrigues Paiva 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 .