Methods to improve run time of hydrologic models: opportunities and challenges in the machine learning era

Supath Dhital
8/5/2024
cs.LG

No confident code implementation found for this paper.

Abstract

The application of Machine Learning (ML) to hydrologic modeling is fledgling. Its applicability to capture the dependencies on watersheds to forecast better within a short period is fascinating. One of the key reasons to adopt ML algorithms over physics-based models is its computational efficiency advantage and flexibility to work with various data sets. The diverse applications, particularly in emergency response and expanding over a large scale, demand the hydrological model in a short time and make researchers adopt data-driven modeling approaches unhesitatingly. In this work, in the era of ML and deep learning (DL), how it can help to improve the overall run time of physics-based model and potential constraints that should be addressed while modeling. This paper covers the opportunities and challenges of adopting ML for hydrological modeling and subsequently how it can help to improve the simulation time of physics-based models and future works that should be addressed.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{dhital2024methods,
  title  = {Methods to improve run time of hydrologic models: opportunities and challenges in the machine learning era},
  author = {Supath Dhital},
  year   = {2024},
  eprint = {2408.02242},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2408.02242v2}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2408.02242.svg)](https://codeofpaper.com/paper/2408.02242)

Discussion