the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
UPSurgeML (v1.0) – A Machine Learning Workflow for Probabilistic Ensemble Forecast of Tropical Cyclone Storm Surge
Abstract. UPSurgeML is an open-source software package for probabilistic storm surge analysis. The code is written in Python, C, and Fortran, and the codebase complies with the National Centers for Environmental Prediction’s (NCEP) guidelines, making it suitable for deployment on High Performance Computers (HPC) like the Weather and Climate Operational Supercomputing System (WCOSS). By utilizing an unstructured mesh, UPSurgeML refines the prediction of water elevations in complex coastal regions. It provides both deterministic and probabilistic storm surge forecasts driven by a small ensemble of hurricane forecasts. UPSurgeML uses parametric hurricane wind and pressure fields, and astronomical tide forcing with a hydrodynamic ocean model to simulate water elevations. Unlike the current Probabilistic Surge (PSurge) model utilized by the National Hurricane Center (NHC), UPSurgeML employs a machine learning surrogate modeling framework. This approach enables a smaller (order of magnitude reduction) hydrodynamic ensemble size that would otherwise be necessary. Consequently, UPSurgeML provides high-resolution water elevation probability fields and exceedance levels with reasonably low computational cost, and has demonstrated its usability as experimental guidance during the hurricane seasons.
- Preprint
(2245 KB) - Metadata XML
- BibTeX
- EndNote
Status: open (until 11 Nov 2026)
-
CEC1: 'Comment on egusphere-2026-4586 - No compliance with the policy of the journal', Juan Antonio Añel, 23 Sep 2026
reply
-
AC1: 'Reply on CEC1', Fariborz Daneshvar, 28 Sep 2026
reply
Dear Dr. Añel,
Thank you for your prompt review of the manuscript and for guiding us on the journal's Code and Data Policy. To address your specific comments:
-
Third-Party Codes and Data: I published a newer version of code and data on Zenodo (https://zenodo.org/records/23022229) and added the exact versions of SCHISM, PaHM, and StormEvents code and data that were used for this manuscript. These are now explicitly listed in the revised Code and Data Availability section.
-
Machine Learning Training Data: All datasets (including training data) used to develop UPSurgeML are fully included in the primary (https://doi.org/10.5281/zenodo.20801237) and revised Zenodo repositories (https://zenodo.org/records/23022229). This is now explicitly explained in the revised Code and Data Availability section.
Below is the revised Code and Data Availability Statement that incorporates these updates:
"""
Code and Data Availability Statement:
The specific version of the UPSurgeML model used in this manuscript, along with all associated training data, input/output files, and scripts used to generate plots, are permanently archived on Zenodo at https://zenodo.org/records/23022229 (Daneshvar et al., 2026). For active development, the latest version of UPSurgeML is maintained on the NOAA Office of Coast Survey (OCS) GitHub repository (https://github.com/noaa-ocs-modeling/UPSurgeML).
This work relies on third-party models and datasets including SCHISM, Parametric Hurricane Model (PaHM), and StormEvents. The exact source code versions of SCHISM (@7fc47d1), PaHM (@2043c99), and StormEvents (v2.3.7) used in this study have been permanently archived on Zenodo at https://zenodo.org/records/23022229 (Daneshvar et al., 2026) to ensure replicability.
"""Please let us know if these updates satisfy the journal's policy so that our manuscript may proceed to the discussion and peer-review phase. We are happy to make any further adjustments if necessary.
Sincerely,
Fariborz Daneshvar, Ph.D.
Senior Physical Scientist | Ocean Associates Inc
Storm Surge Modeling Team
Coastal Marine Modeling Branch
NOAA National Ocean Service | Office of Coast SurveyCitation: https://doi.org/10.5194/egusphere-2026-4586-AC1 -
CEC2: 'Reply on AC1', Juan Antonio Añel, 29 Sep 2026
reply
Dear authors,
Thanks for addressing this issue. I have checked the repositories and we can consider now the current version of your manuscript in compliance with the code policy of the journal.
Juan A. Añel
Geosci. Model Dev. Executive Editor
Citation: https://doi.org/10.5194/egusphere-2026-4586-CEC2
-
-
AC1: 'Reply on CEC1', Fariborz Daneshvar, 28 Sep 2026
reply
Viewed
| HTML | XML | Total | BibTeX | EndNote | |
|---|---|---|---|---|---|
| 300 | 109 | 33 | 442 | 35 | 28 |
- HTML: 300
- PDF: 109
- XML: 33
- Total: 442
- BibTeX: 35
- EndNote: 28
Viewed (geographical distribution)
| Country | # | Views | % |
|---|
| Total: | 0 |
| HTML: | 0 |
| PDF: | 0 |
| XML: | 0 |
- 1
Dear authors,
Unfortunately, after checking your manuscript, it has come to our attention that it does not comply with our "Code and Data Policy".
https://www.geoscientific-model-development.net/policies/code_and_data_policy.html
The Code and Data Availability section of your manuscript does not contain the repositories for the code and data used in your manuscript. This includes codes such as SCHISM, PaHM, StormEvents, etc. which are cited in the text and references, but not mentioned in the Code and Data Availabilty section. Moreover, they such codes are stored in sites that do not comply with the policy of the journal. It is specially striking that you cite several Git sites -- or even published papers, no repositories--- when the policy of the journal makes clear that Git sites are not acceptable.
Also, it is not clear if the training data that you have used is available in the Zenodo repository that you provide, as the training process for the system presented is not explained in your submitted manuscript. For machine learning works submitted to the journal we request that all the training and output data for the presented models are properly stored in repositories acceptable according to the policy of the journal.
The GMD review and publication process depends on reviewers and community commentators being able to access, during the discussion phase, the code and data on which a manuscript depends, and on ensuring the provenance of replicability of the published papers for years after their publication. Due to the lack of the compliance mentioned above, your manuscript should not be accepted for Discussions and peer review in the journal. Please, therefore, publish your code and data in one of the appropriate repositories and reply to this comment with the relevant information (link and a permanent identifier for it (e.g. DOI) -- a new version of the Code and Data Availability section) as soon as possible. We cannot have manuscripts under discussion that do not comply with our policy.
Later, if the Topical Editor decides to continue with the review or publication process of your manuscript and you are requested to upload a new version of it, then The 'Code and Data Availability’ section of your manuscript must also be modified to cite the new repository locations, and corresponding references added to the bibliography.
I must note that if you do not fix this problem, we cannot continue with the peer-review process or accept your manuscript for publication in GMD.
Juan A. Añel
Geosci. Model Dev. Executive Editor