Peer Review History
| Original SubmissionMarch 28, 2025 |
|---|
|
PONE-D-25-14715Exploratory trajectory inference reveals convergent lineages for CD8 T cells in chronic LCMV infectionPLOS ONE Dear Dr. Claassen, 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 Jun 05 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, Xianmin Zhu 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. Thank you for stating the following financial disclosure: “This work was supported by the ETH Z üurich (grant no. 470 ETH-39 14-2 to M.C. and A.O.) and the Novartis Foundation for Biomedical Research, 471 DFG CL 792/1-1 and the Center for Personalized Medicine (ZPM) and DFG EXC 2180.” 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. 3. Thank you for stating the following in the Acknowledgments Section of your manuscript: “We thank Franziska Wagen and Nathalie Oetiker for great technical support. We are 466 grateful for the constructive input of the members of the Claassen, Oxenius, Joller 467 and Sallusto Group during discussions and group meetings. The authors thank the 468 International Max Planck Research School for Intelligent Systems (IMPRS-IS) for 469 supporting J.T.S. Funding: This work was supported by the ETH Z¨urich (grant no. 470 ETH-39 14-2 to M.C. and A.O.) and the Novartis Foundation for Biomedical Research, 471 DFG CL 792/1-1 and the Center for Personalized Medicine (ZPM) and DFG EXC 2180.” We note that you have provided funding information that is 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 supported by the ETH Z üurich (grant no. 470 ETH-39 14-2 to M.C. and A.O.) and the Novartis Foundation for Biomedical Research, 471 DFG CL 792/1-1 and the Center for Personalized Medicine (ZPM) and DFG EXC 2180.” Please include your amended statements within your cover letter; we will change the online submission form on your behalf. 4. We notice that your supplementary figures are included in the manuscript file. Please remove them and upload them with the file type 'Supporting Information'. Please ensure that each Supporting Information file has a legend listed in the manuscript after the references list. [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 Reviewer #3: No ********** 2. Has the statistical analysis been performed appropriately and rigorously? Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: No ********** 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 Reviewer #3: 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 Reviewer #3: 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: In this paper, Revant proposes a new method called Cytopath to infer trajectories in scRNA-seq data by leveraging RNA velocity information. They present an in-depth analysis of a chronic LCMV infection dataset and support their findings with flow cytometry experiments. The proposed method appears promising, and the accompanying biological analyses are compelling. However, I have a few concerns: 1. Some aspects of Cytopath remain unclear. For instance, the hierarchical clustering based on the simulated sequences is not well explained. What features are used in the clustering—only gene expression, or also information derived from the simulated trajectories? Does Cytopath require prior knowledge such as cell type or state labels? How does the method determine or control the number of inferred trajectories? Clarifying these points in the Results and Methods sections would greatly aid readers in understanding the approach. 2. It is well known that different RNA velocity inference methods can yield substantially different results [1]. It would be helpful if the authors could explore how such variation in RNA velocity affects the performance and output of Cytopath. 3. The stability of Cytopath needs further discussion. Since the method involves simulation, it would be important to know whether multiple runs on the same dataset yield consistent trajectories. 4. Finally, a discussion on Cytopath’s computational efficiency—including time and memory usage—would be valuable for potential users. References: [1] Zheng, S.C., Stein-O’Brien, G., Boukas, L. et al. Pumping the brakes on RNA velocity by understanding and interpreting RNA velocity estimates. Genome Biol 24, 246 (2023). https://doi.org/10.1186/s13059-023-03065-x Reviewer #2: The authors proposed a novel framework termed exploratory trajectory inference to address limitations in resolving complex lineage topologies, particularly convergent differentiation trajectories, from single-cell RNA sequencing (scRNA-seq) data. By applying this approach to an original dataset of CD8 T cell responses in chronic LCMV infection, the authors identified several distinct yet converging developmental paths to T cell exhaustion. The inferred trajectories are experimentally supported through adoptive transfer studies. I find the framework proposed in the paper interesting, and the experimental validation is convincing. However, I think the authors should provide more clarification regarding the advances over their previous studies, as well as include additional simulation benchmarking results to better demonstrate the performance of the approach. Here are my specific comments: 1. The proposed framework, exploratory trajectory inference, appears to be based on cy2path (Ref. 35), which seems closely related to Cytopath (Ref. 14). Given the strong methodological overlap among these works, could the authors clarify how the current manuscript advances beyond these prior studies? Specifically, it would be helpful to delineate which aspects of the methodology are novel in this manuscript, and how it extends or differs from cy2path and/or Cytopath. For example, the description in the Exploratory Trajectory Inference subsection of the Methods section could more clearly highlight the conceptual differences. 2. RNA velocity methods like scVelo are based on abundance quantification and involve numerous steps and parameters, which can lead to variability in results (https://doi.org/10.1371/journal.pcbi.1008585; https://doi.org/10.1371/journal.pcbi.1010492). This variability can propagate downstream through the state transition matrix, potentially affecting trajectory inference outcomes. Can the authors provide some explanation or further analysis on whether exploratory trajectory inference is sensitive to these factors? 3. The authors mention around line 180 that "we did not enforce simulations to reach predefined endpoints. Instead, we simulated 1000 cell state sequences with a predetermined, automatically chosen number of steps," and on line 413 that "The number of steps for Markov chain sampling was set to 228 based on convergence." I am a little confused about how the number of steps was determined. Could the authors clarify how both the number of sequences and the number of steps were chosen, and provide analysis on whether exploratory trajectory inference is sensitive to these parameters? 4. Can this framework handle cyclical processes? Please clarify which types of topologies the proposed method is capable of inferring. 5. Does the computational cost of exploratory trajectory inference increase more than linearly with the number of cells? If so, could the authors evaluate the computational efficiency of the method on datasets with larger cell numbers? 6. Minor points about the figures: a. Please check whether the title of Figure 1 is correct. b. On line 99, should the reference to Fig. 1C be Fig. 2B instead? c. On lines 210, 214, 218, and 223, the word "Fig" appears to be missing. Reviewer #3: In their study, “Exploratory trajectory inference reveals convergent lineages for CD8 T cells in chronic LCMV infection”, the authors describe a methodology for inferring trajectories between cells in scRNA-seq data by aggregating simulations of cell state transition dynamics without an imposed external structure/geometry, to propose potentially novel trajectories. They apply this methodology, termed ‘exploratory trajectory inference’, to time-series scRNA-seq data and highlight convergent cell state transitions where terminally exhausted CD8 T cells can develop from memory-like or non-memory-like exhausted CD8 T cells. Overall, the concept of using ensembles of simulated cell state transitions for more generalizable trajectory inference is interesting but the study is lacking simulated or data-based controls as well as other measures of accuracy or robustness to assess the properties of the proposed methodology. Without such baselines and applications, it is difficult to understand how one should apply this approach and interpret or trust the results. The experimental validation, though interesting, does not address the capabilities of the analysis methods themselves, e.g., if or how easily ‘incorrect’ or nonexistent paths could be produced in the analysis even if ‘correct’ paths also appear. Major Comments: 1. A major issue in RNA velocity analyses is the impact of the chosen dimension reduction/embedding method on the inferred velocity values and transition probabilities [1,2]. This can lead to bias and/or arbitrary final velocity values warped by the placement of cells in the 2D visualizations. Thus it is necessary to understand if the UMAP embedding used here affects the resulting trajectories in any way. - Both the hyperparameters of the UMAP algorithm and the choice of k-nearest neighbors to smooth over in other steps of the velocity pipeline (such as calculating the gene moments) impact the definition of cell neighborhoods and their placement in 2D [1,2]. Thus the trajectory inference results should be shown to be robust to a range of reasonable hyperparameters. Likewise, cells at particular times or types can be removed to see if arbitrary trajectories are induced based on this change in locations of cells in embedding space. 2. As the authors describe in the Cytopath paper [3], the use of RNA velocity values is not necessary to construct the transition matrix used, which highlights a control/baseline that is missing from here. The same cosine distance/similarity calculated between velocity vectors can be calculated between cells (preferably using both unspliced and spliced counts as this is the information used in velocity) to create a transition matrix not reliant on inferred velocity values which provides a point of comparison for both the broader utility of this approach and the potential instabilities induced by the RNA velocity inference pipeline. 3. The output of the exploratory inference methodology additionally provides no metrics of uncertainty or confidence in the inferred trajectories, making it difficult to assess the believability of potentially novel paths. For example, obtaining statistics on the variance of the various trajectory coordinates would be helpful as these are then averaged over for the final trajectories visualized. The definitions of trajectory 'segments' and 'coordinates' can also be further clarified (e.g., what calculations are used to obtain 'segments', what space/dimension are these in)? - A scrambled transition matrix may also provide a baseline for comparison/confidence. - Potentially the frequency of a particular path is also something that could be visualized and used as a qualitative assessment. 4.Generally the question of how spurious the trajectories inferred by this exploratory methodology are is not addressed, beyond the comparison of trajectories obtained by cutting the hierarchical clustering dendrogram at different levels. To demonstrate if the method is relatively robust and accurate, comparisons need to be made to control settings (potentially through simulations as well as data) which encompass settings without continuous relationships between cells (negative control) and settings with 'ground truth' trajectories. These will demonstrate how easily trajectories are inferred when they should or shouldn't be present, providing a baseline and external context for the result on the CD8 T cells. 5.As currently written, it is unclear what the advantage or novel finding of the cy2path/‘exploratory’ methodology (Fig. 5C,D) is over the Cytopath results in Fig 4A. In Fig. 4A the path from early to exhausted memory T cells to terminally exhausted cells is present in the results obtained from Cytopath analysis, with the width of the arrows potentially suggesting more or less likely transitions. The proposed exploratory method, following the Cytopath section, shows the same trajectories (Fig. 5C,D), but without any width differences, i.e., no visual difference in how 'likely' either trajectory is. It seems that both approaches show this main finding, and thus it is unclear what the cy2path/exploratory approach adds in terms of novel path discovery. - The study should also compare to other existing methods that use transition probability matrices or random walks to infer trajectories between cells (e.g., CellRank, VIA) [4,5]. Minor Comments: 1. There are several statements that refer to validation of 'continuous' relationships between cells based on the qualitative UMAP space, which is known to create or distort quantitative cell-cell relationships [1,2,6]. Thus this space does not qualify as a measure of continuity or a validation of a real developmental lineage. 2. Two different clustering approaches are used on the outputs of the Cytopath and the cy2path/exploratory methodologies. It would be good to see a rationale for why different approaches were used in these cases. References: 1. Zheng, S. C., Stein-O’Brien, G., Boukas, L., Goff, L. A. & Hansen, K. D. Pumping the brakes on RNA velocity by understanding and interpreting RNA velocity estimates. Genome Biol. 24, 246 (2023). 2. Gorin, G., Fang, M., Chari, T. & Pachter, L. RNA velocity unraveled. PLoS Comput. Biol. 18, e1010492 (2022). 3. Gupta, R., Cerletti, D., Gut, G., Oxenius, A. & Claassen, M. Simulation-based inference of differentiation trajectories from RNA velocity fields. Cell Rep. Methods 2, 100359 (2022). 4. Lange, M. et al. CellRank for directed single-cell fate mapping. Nat. Methods 19, 159–170 (2022). 5. Stassen, S. V., Yip, G. G. K., Wong, K. K. Y., Ho, J. W. K. & Tsia, K. K. Generalized and scalable trajectory inference in single-cell omics data with VIA. Nat. Commun. 12, 5528 (2021). 6. Kharchenko, P. V. The triumphs and limitations of computational methods for scRNA-seq. Nat. Methods 18, 723–732 (2021). ********** 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 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 1 |
|
PONE-D-25-14715R1Exploratory trajectory inference reveals convergent lineages for CD8 T cells in chronic LCMV infectionPLOS ONE Dear Dr. Claassen, 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 Aug 15 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, Xianmin Zhu 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 #1: All comments have been addressed 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 #1: Yes Reviewer #2: Yes Reviewer #3: Partly ********** 3. Has the statistical analysis been performed appropriately and rigorously? Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: 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 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 #1: Yes 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 #1: (No Response) Reviewer #2: (No Response) Reviewer #3: Thank you to the authors for addressing the comments and for the additional analyses and controls now incorporated into the paper. There are a few remaining comments regarding some of the more qualitative robustness analyses, and clarifications on the uncertainty analysis and metrics for users to determine if an input is less suitable for trajectory inference. 1. To show stability of root/terminal cell probabilities parameters over a range of nearest neighbors (Figure S12, S13) please plot the results in a more quantitative manner (e.g., pairwise correlations between root/terminal probabilities across hyperparameters, or the distributions of these probabilities over the hyperparameters). Otherwise readers need to interpret the grid of embeddings in a qualitative manner. 2. I believe the term ‘diffuse’ is used to define widely distributed root cell probabilities which may lead to harder to interpret trajectories. However, further (quantitative) discussion would be beneficial to make this property of use to users, to be able to assess their data. For example, is there some property of the transition matrix that demonstrate this diffuseness, or can this be plotted in the width/variance of inferred root cell probabilities? 3. Apologies for the potential confusion regarding the comment asking for uncertainty analysis of the trajectories generated over multiple runs. The intent was to assess the variance in the multiple realizations of trajectories in the system, which should be computed in whatever space the trajectories are created in (and clustered etc), which I believe is the 50d PCA space. Assessing variance in the UMAP coordinates adds the layer of a non-deterministic, nonlinear transformation and thus analysis of variance/noise also induced by that process not just through the variance in the trajectories themselves. Thus this analysis should be performed in the original trajectory space (and be easily available for users to check). It would also help to visualize variance in these paths in Figure S14, particularly if in scenarios where paths are not recovered correctly and we see more variance/uncertainty in the produced trajectories, i.e., if there is anything a user could use to tell how much to trust or choose between those outputs. 4. For the simulations of the different topologies, please provide details on how many cells/observations were sampled from this model. This Gaussian model also does not represent sparse single-cell count data so the authors should comment on these assumptions (how this may influence results) and demonstrate that the generated points provided to scVelo resemble at least the magnitude of values usually provided in single-cell data. Additionally, why was a count-based simulator, like dyngen https://github.com/dynverse/dyngen for example, not used here to generate different topologies that also provide ‘realistic’ RNA counts (the usual input to scVelo)? ********** 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 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 |
|
Exploratory trajectory inference reveals convergent lineages for CD8 T cells in chronic LCMV infection PONE-D-25-14715R2 Dear Dr. Claassen, 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. For questions related to billing, please contact billing support. 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, Xianmin Zhu Academic Editor PLOS ONE Additional Editor Comments (optional): Reviewer #3: 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 #3: 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 #3: Yes ********** 3. Has the statistical analysis been performed appropriately and rigorously? Reviewer #3: 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 #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 #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 #3: The authors have sufficiently addressed the reviewer comments and provided thorough evaluations of the outputs of their method with quantitative metrics for user interpretation of inference results. ********** 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 #3: No ********** |
| Formally Accepted |
|
PONE-D-25-14715R2 PLOS ONE Dear Dr. Claassen, 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 You will receive further instructions from the production team, including instructions on how to review your proof when it is ready. Please keep in mind that we are working through a large volume of accepted articles, so please give us a few days 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. You will receive an invoice from PLOS for your publication fee after your manuscript has reached the completed accept phase. If you receive an email requesting payment before acceptance or for any other service, this may be a phishing scheme. Learn how to identify phishing emails and protect your accounts at https://explore.plos.org/phishing. 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. Xianmin Zhu 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 .