the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
PLSTM-Reg v1.0: A regional physics-encoded LSTM model for simulating reservoir operations under data scarcity
Abstract. Representing reservoir operations in large-scale hydrological models remains difficult due to complex release decisions and scarce operational records. Here, we develop PLSTM-Reg v1.0, a regional deep learning framework with physics encoded to simulate reservoir operations across diverse systems. The framework is evaluated using 256 representative reservoirs across the Contiguous United States, focusing on three core capabilities: temporal generalization to unseen periods, spatial transfer to unseen reservoirs, and historical data reconstruction. Under temporal testing, the regional model improves 1-day-ahead release forecasts from a median Kling–Gupta Efficiency (KGE) of 0.83 to 0.96 relative to local counterparts, and reduces poorly simulated cases (KGE < 0.8) from 41.8 % to 2.3 %. For long-term simulation, storage performance reaches a median KGE of 0.79, a modest gain over local models (0.76) but with notable robustness for reservoirs with large capacity. When transferred to unseen reservoirs, the model substantially outperforms widely used rule-based schemes: median KGE rises from 0.55 (best benchmark) to 0.73 for release and from 0.22 to 0.59 for storage, and the proportion of usable simulations (KGE > 0.5) increases from 56.6 % to 89.8 % for release and 14.4 % to 61.7 % for storage. In historical storage reconstruction, incorporating monthly satellite-derived surface area strengthens storage estimates and enables reconstruction accuracy comparable to models trained with local records. These results demonstrate that cross-reservoir deep learning combined with physical knowledge provides a scalable scheme for representing human water management within large-scale hydrological and land surface models under widespread data scarcity.
- Preprint
(5390 KB) - Metadata XML
-
Supplement
(4769 KB) - BibTeX
- EndNote
Status: open (until 13 May 2026)
-
CEC1: 'Comment on egusphere-2026-1098 - No compliance with the policy of the journal', Juan Antonio Añel, 28 Mar 2026
reply
-
CC1: 'Reply on CEC1', Bin Yu, 29 Mar 2026
reply
Publisher’s note: the content of this comment was removed on 31 March 2026 since the comment was posted by mistake.
Citation: https://doi.org/10.5194/egusphere-2026-1098-CC1 -
AC1: 'Reply on CEC1', Yi Zheng, 29 Mar 2026
reply
Please see attachment.
-
CEC2: 'Reply on AC1', Juan Antonio Añel, 30 Mar 2026
reply
Dear authors,
Many thanks for your quick reply. Unfortunately, it does not solve all the issues pending with the data in your manuscript. We can not accept Hydroshare.org or Nasa.gov sites as permanent repositories to store the assets used to perform the work described in a manuscript. Therefore, you must store in one of the repositories that we can accept the data that you have made available through them.
Please, reply to this comment with the information for the new repositories containing the mentioned datasets, and a modified Code and Data Availability section that complies with the policy of the journal.
Juan A. Añel
Geosci. Model Dev. Executive Editor
Citation: https://doi.org/10.5194/egusphere-2026-1098-CEC2 -
AC2: 'Reply on CEC2', Yi Zheng, 30 Mar 2026
reply
Please see attachment.
-
CEC3: 'Reply on AC2', Juan Antonio Añel, 30 Mar 2026
reply
Dear authors,
Again, thanks for addressing this issue so quickly. 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-1098-CEC3
-
CEC3: 'Reply on AC2', Juan Antonio Añel, 30 Mar 2026
reply
-
AC2: 'Reply on CEC2', Yi Zheng, 30 Mar 2026
reply
-
CEC2: 'Reply on AC1', Juan Antonio Añel, 30 Mar 2026
reply
-
CC1: 'Reply on CEC1', Bin Yu, 29 Mar 2026
reply
Viewed
| HTML | XML | Total | Supplement | BibTeX | EndNote | |
|---|---|---|---|---|---|---|
| 93 | 27 | 15 | 135 | 16 | 8 | 8 |
- HTML: 93
- PDF: 27
- XML: 15
- Total: 135
- Supplement: 16
- BibTeX: 8
- EndNote: 8
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
First, you have archived your code on a Zenodo private repository, something we can not accept. 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. Therefore, you must public openly and without restrictions the code used in your manuscript to continue the Discussions and peer review process.
In addition, to access the data used and produced in your work you cite several sites; however, the cited sites do not fulfil GMD’s requirements for a persistent data archive because:
* They do not appear to have a published policy for data preservation over many years or decades (some flexibility exists over the precise length of preservation, but the policy must exist).
* They do not appear to have a published mechanism for preventing authors from unilaterally removing material. Archives must have a policy which makes removal of materials only possible in exceptional circumstances and subject to an independent curatorial decision,
* They do not appear to issue a persistent identifier such as a DOI or Handle for each precise dataset.
If we have missed a published policy which does in fact address this matter satisfactorily, please post a response linking to it. If you have any questions about this issue, please post them in a reply. There is a site in the case of your manuscript that could almost be considered in compliance with our policy, the Texas Data Repository; however, after reading their policy, it seems that the service for hosting and curating the data are not provided directly by the Texas Digital library, but by AWS, which is a private company, and therefore we can not accept as a long-term repository valid for scientific publication.
Please, therefore, publish all the code and data used in your work and necessary to replicate it in one of the appropriate repositories according to the policy of the journal, and reply to this comment with the relevant information (link and a permanent identifier for it (e.g. DOI)) as soon as possible. We cannot have manuscripts under discussion that do not comply with our policy.
The 'Code and Data Availability’ section 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