Peer Review History

Original SubmissionJune 17, 2025
Decision Letter - Jamil Alexandre Ayach Anache, Editor

PLOS ONE

Dear Dr. Sanguankiattichai,

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 Oct 18 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:

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

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

If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols . Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols .

We look forward to receiving your revised manuscript.

Kind regards,

Jamil Alexandre Ayach Anache

Academic Editor

PLOS ONE

Journal requirements:

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

1. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at

https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and

https://journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf

2. If the reviewer comments include a recommendation to cite specific previously published works, please review and evaluate these publications to determine whether they are relevant and should be cited. There is no requirement to cite these works unless the editor has indicated otherwise. 

Additional Editor Comments:

Dear authors, I received two reviews to your papers. All comments are relevant and must be adressed.

Best regards,

Academic editor

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

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

Reviewer #1: Yes

Reviewer #2: N/A

**********

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

The PLOS Data policy

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

Reviewer #1: Yes

Reviewer #2: Yes

**********

Reviewer #1: The authors have made a valuable contribution to the crop modeling and natural resource management community by developing a comprehensive set of tools for visualizing and analyzing AquaCrop outputs. These tools include a Windows GUI, a ShinyApp, and an R package. Additionally, the paper presents a case study conducted across three locations under different climate change scenarios. The manuscript is generally well-structured, clearly written, and follows a logical progression that is easy to follow. However, I have some concerns and suggestions that I provide detailed comments below.

Comment 1: In the introduction, the authors present the importance and implications of developing an application for visualizing and analysing AquaCrop, which is well-done. However, the authors should bear in mind that there will be two kinds of readers: the ones that are acquainted with AquaCrop and understand all the equations and how the physical processes are represented in the model and the ones that will be firstly introduced by AquaCrop by this paper. While I understand that the main target group can potentially be the reader that is acquainted with AquaCrop, I think that giving more details of AquaCrop is of utmost importance. This includes, but it is not limited to, details of the input data that is required and the units (maybe a table?), the main equations and physical principles, and limitations of the model.

Comment 2: The citation and reference of the packages used in to develop the R application is essential, however, it is important to explain what is the purpose of using a given package. The authors have done this by explaining that Tudyverse and furr were used for analysis pipelines. A similar explanation should be given for shinydashboard, shinyjs, shinyBS, and DT.

Comment 3: The authors have done an excellent job in providing all the relevant links for accessing all the extensive resources related to AquaCropPlotter (github and Mendeley repositories, links for download and technical documentation). All links are working correctly, nonetheless, I strongly suggest presenting them as a citation and put the links in the reference.

Comment 4: Maybe one of the most critical aspects of AquaCropPlotter is the ingestion of the data into the application. As the authors stated "AquaCropPlotter takes project files and output files from AquaCrop simulation as its input". I think the authors should provide more information on the differences of the Standard "GUI" and the stand-alone "Plug-in", e.g., in what cases each one of them are used? Also, the output files from each type of interface should be better explained. The standard GUI saves 10 files and the reader should learn in the text about what to expect to be written in each one of these files. For example, I can infer that the project file [.PRM] stores all the project settings, however, for the file CompEC.OUT I cannot make any inference if I'm not an experienced user of AquaCROP. The same reasoning applies to the outputs of the "Plug-in".

Comment 5: In the Step 4: Analysis, the authors provide an explanation that "AquaCropPlotter offers two simple statistical analysis options for gaining more insights into the data". The first one is a window summary function that is not clear to me what it is exactly. The authors are encouraged to give more details about how the summary and trend of variables are computed in the application. Moreover, they should present one example for each analysis in the case study.

Reviewer #2: The manuscript is very well written and is a substantial improvement as an option to the traditional AquaCrop model software. However, the figures need to be improved because they are of poor quality (blurry).

**********

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: Yes:  Marcos Roberto Benso

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

Response to reviewers

Reviewer #1: The authors have made a valuable contribution to the crop modeling and natural resource management community by developing a comprehensive set of tools for visualizing and analyzing AquaCrop outputs. These tools include a Windows GUI, a ShinyApp, and an R package. Additionally, the paper presents a case study conducted across three locations under different climate change scenarios. The manuscript is generally well-structured, clearly written, and follows a logical progression that is easy to follow. However, I have some concerns and suggestions that I provide detailed comments below.

- Comment 1: In the introduction, the authors present the importance and implications of developing an application for visualizing and analysing AquaCrop, which is well-done. However, the authors should bear in mind that there will be two kinds of readers: the ones that are acquainted with AquaCrop and understand all the equations and how the physical processes are represented in the model and the ones that will be firstly introduced by AquaCrop by this paper. While I understand that the main target group can potentially be the reader that is acquainted with AquaCrop, I think that giving more details of AquaCrop is of utmost importance. This includes, but it is not limited to, details of the input data that is required and the units (maybe a table?), the main equations and physical principles, and limitations of the model.

Response: We have added more information about AquaCrop including the principles, inputs, outputs, and limitations (Line 58 - 110). We feel that listing all the inputs and their units might be quite detailed for the purpose of this manuscript, since there are many inputs that are not straightforward and there can be multiple units for a single variable, e.g. for the climate inputs. We think that providing the concepts and summary of the required inputs may be sufficient for understanding AquaCrop within the scope of this manuscript. More details of inputs can be found better explained in detail in the original AquaCrop publications cited.

- Comment 2: The citation and reference of the packages used in to develop the R application is essential, however, it is important to explain what is the purpose of using a given package. The authors have done this by explaining that Tudyverse and furr were used for analysis pipelines. A similar explanation should be given for shinydashboard, shinyjs, shinyBS, and DT.

Response: We have added more explanation for the packages used (Line 158 - 164).

- Comment 3: The authors have done an excellent job in providing all the relevant links for accessing all the extensive resources related to AquaCropPlotter (github and Mendeley repositories, links for download and technical documentation). All links are working correctly, nonetheless, I strongly suggest presenting them as a citation and put the links in the reference.

Response: We have put the links in the references and cited them in the text (Line 166-178).

- Comment 4: Maybe one of the most critical aspects of AquaCropPlotter is the ingestion of the data into the application. As the authors stated "AquaCropPlotter takes project files and output files from AquaCrop simulation as its input". I think the authors should provide more information on the differences of the Standard "GUI" and the stand-alone "Plug-in", e.g., in what cases each one of them are used? Also, the output files from each type of interface should be better explained. The standard GUI saves 10 files and the reader should learn in the text about what to expect to be written in each one of these files. For example, I can infer that the project file [.PRM] stores all the project settings, however, for the file CompEC.OUT I cannot make any inference if I'm not an experienced user of AquaCROP. The same reasoning applies to the outputs of the "Plug-in".

Response: We have added more information about

• the differences of the standard GUI and plug-in versions (Line 116 - 121)

• information on each of the output files from the standard GUI and plug-in versions (Line 190-222)

• details of output files and variables are also listed in a table provided as supplementary material Table S1.

- Comment 5: In the Step 4: Analysis, the authors provide an explanation that "AquaCropPlotter offers two simple statistical analysis options for gaining more insights into the data". The first one is a window summary function that is not clear to me what it is exactly. The authors are encouraged to give more details about how the summary and trend of variables are computed in the application. Moreover, they should present one example for each analysis in the case study.

Response: We have added more information about the analysis functions (Line 276-292) and include an example in the case study (Line 338-344, 362-365, 380-383).

Reviewer #2: The manuscript is very well written and is a substantial improvement as an option to the traditional AquaCrop model software. However, the figures need to be improved because they are of poor quality (blurry).

Response: The figures seem to be blurry when the submission system auto-generates the pdf file of the manuscript for reviewers. We have double checked our figure files and make sure the final version uploaded is not blurry.

Attachments
Attachment
Submitted filename: _AquacropPlotter_PlosOne_response to reviewers.docx
Decision Letter - Jamil Alexandre Ayach Anache, Editor

AquaCropPlotter: a Shiny app for visualizing and analyzing AquaCrop simulation results

PONE-D-25-32827R1

Dear Dr. Sanguankiattichai,

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,

Jamil Alexandre Ayach Anache

Academic Editor

PLOS ONE

Additional Editor Comments (optional):

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

Reviewer #1: All comments have been addressed

**********

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

Reviewer #1: Yes

**********

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

Reviewer #1: Yes

**********

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

The PLOS Data policy

Reviewer #1: Yes

**********

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

Reviewer #1: Yes

**********

Reviewer #1: I appreciate the effort made by the authors in responding to the comments and suggestions I have made. After carefully evaluating the author's response, I believe that the manuscript is ready to be published in PLOS One.

I would like to thank the authors for creating a useful and interesting tool for crop modeling, which I believe will be greatly appreciated by the research and technical community. Moreover, I truly believe that the readership of PLOS One will be interested in reading the manuscript.

Regards

**********

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: Yes:  Marcos Roberto Benso

**********

Formally Accepted
Acceptance Letter - Jamil Alexandre Ayach Anache, Editor

PONE-D-25-32827R1

PLOS ONE

Dear Dr. Sanguankiattichai,

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. Jamil Alexandre Ayach Anache

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 .