TorchHydro
A PyTorch-based deep learning framework for hydrological modeling. Supports Normal, Transfer Learning, Multi-Task Learning, and Federated Learning modes.
Documentation: https://OuyangWenyu.github.io/torchhydro
Installation
Python 3.10+ required.
pip install torchhydro
or with uv (faster):
uv pip install torchhydro
See the Installation Guide for developer setup.
Quick Start
1. Configure data path
Create hydro_setting.yml in your home directory (~/ or %USERPROFILE%):
storage:
default_source: local
local:
root: 'D:/data/hydrodatasets' # your data directory
cache: 'D:/data/hydrodatasets/cache'
Standard dataset paths (e.g., CAMELS-US) are resolved automatically from this root by the unified data resolver.
2. Run a model
from hydrodataset.hydro_dataset import StandardVariable
from torchhydro.configs.config import cmd, default_config_file, update_cfg
from torchhydro.trainers.trainer import train_and_evaluate
# Build config for LSTM on CAMELS-US
args = cmd(
source_cfgs={"dataset_id": "camels_us"},
model_name="CpuLSTM",
model_hyperparam={"n_input_features": 23, "n_output_features": 1, "n_hidden_states": 256},
gage_id=["01013500", "01022500", "01030500"],
train_period=["2000-10-01", "2001-10-01"],
valid_period=["2001-10-01", "2002-10-01"],
test_period=["2002-10-01", "2003-10-01"],
var_t=[
StandardVariable.PRECIPITATION,
StandardVariable.SOLAR_RADIATION,
StandardVariable.TEMPERATURE_MAX,
],
var_out=[StandardVariable.STREAMFLOW],
dataset="StreamflowDataset",
sampler="KuaiSampler",
scaler="DapengScaler",
)
config_data = default_config_file()
update_cfg(config_data, args)
train_and_evaluate(config_data)
See examples/ for runnable scripts:
examples/lstm_camels_example.py— Standard LSTM on CAMELS-USexamples/dpl_xaj_example.py— Differentiable Xinanjiang (XAJ) model
Features
Models
| Category | Models |
|---|---|
| LSTM variants | SimpleLSTM, CudaLSTM, CNNLSTM, MCLSTM, SPPLSTM, BALSTM, MTSLSTM |
| Seq2Seq / Encoder-Decoder | GeneralSeq2Seq, Transformer, DataFusionModel, SeqForecast |
| Differentiable physical models | DPL-XAJ, DPL-HBV, DPL-GR4J, DPL-MC-Reservoir |
| Graph neural networks | GCN, ResGCN, GCNII, ResGAT, GCGRU, GCLSTM, STGCN |
| Mixture of Experts | DenseMoE, SparseMoE, SwitchMoE, HydrologyTopKMoE, GlobalTopKMoE |
| Generative / spectral | Diffusion, FNO (Fourier Neural Operator) |
| Specialized | WDNE (3D flood), CoupledLSTM, RegulLSTM |
Datasets
Standard datasets resolved via hydrodataset and hydrodatasource:
dataset_id |
Description |
|---|---|
camels_us |
CAMELS-US (671 US basins) |
camelsh |
CAMELS-Hourly |
caravan / grdc_caravan |
Caravan / GRDC-Caravan collections |
camels_aus / camels_br / camels_cl / camels_gb / camels_col |
CAMELS regional datasets |
Custom data sources: selfmadehydrodataset, selfmadeforecastdataset, longtermdataset, floodeventdatasource, stationhydrodataset, tghydrodatasource.
Training modes
- Standard supervised learning — single basin or regional training
- Transfer learning — cross-basin model adaptation
- Multi-task learning — shared backbone, task-specific heads
- Federated learning — decentralized basin-level training
Key capabilities
- Unified data resolver — all dataset paths from one
hydro_setting.ymlconfig - Monthly and sub-daily (hourly) time units
- Cloud-Zarr lazy loading for joint training on remote data
- Lightning Fabric integration for debugging and distributed training
- SHAP-based model interpretability and loss landscape visualization
- Advanced dropout strategies and data augmentation
Guides & Documentation
Examples & Results
- LSTM on CAMELS-US — baseline benchmark and basin-level performance
- Songliao Flood Models — LSTM, MCLSTM, GNN, WDNE flood forecasting
- Sanxia Multi-Site — reservoir and multi-site experiments
- MoE / Diffusion / FNO — advanced model experiments
- Seq2Seq / BALSTM / MTSLSTM — encoder-decoder and spatial-temporal models
Advanced Topics
- Cloud-Zarr Joint Training — lazy loading for large-scale remote data
- Lightning Fabric — debugging and distributed training
- ERA5-Land & GPM — gridded meteorological data experiments
- Model Interpretability — SHAP and loss landscape analysis
API Reference
Models · Datasets · Trainers · Configs · Explainers
Architecture
configs/ config.py, model_config.py, data_resolver.py (unified data layer)
│ drives
├── datasets/ data_sets.py, data_sources.py, sampler.py, scalers.py
├── models/ 20+ architectures registered in model_dict_function.py
├── trainers/ deep_hydro.py (orchestrator), trainer.py, fabric_wrapper.py
├── explainers/ shap.py, loss_landscape/, uncertainty_analysis.py
└── utils/ dist_utils.py (MPI distributed computing)
Why TorchHydro?
- Decoupled data layer — a unified resolver supports 10+ datasets, custom sources, and cloud storage; data tooling is usable even without a deep-learning model
- Flexible learning paradigms — transfer, multi-task, and federated learning are first-class, not afterthoughts
- Deep configuration — fine-grained control over data traversal, normalization, batch sampling, and advanced dropout
- Extensible — configuration is externalized so new data sources and models plug in without modifying core code
Contributing
See the Contributing Guide for development setup, code standards, and pull request workflow.
License
BSD License. See LICENSE.
Acknowledgments
Metadata
Release files for torchhydro 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| torchhydro-0.2.0.tar.gz | 1.1 MB | With provenance | Details for torchhydro-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| torchhydro-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for torchhydro-0.2.0-py3-none-any.whl |
Total release size: 1.5 MB
Release files / torchhydro-0.2.0.tar.gz
| Download URL | torchhydro-0.2.0.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f1ce496345818efe26e362b53358a931ead57ec10174b805ea61f53b508835c
|
|
BLAKE2b-256 checksum How to use checksums |
a45c2bb23240dbd8959f950c633a148ed4d1068d842c127246342c473f09345d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / torchhydro-0.2.0-py3-none-any.whl
| Download URL | torchhydro-0.2.0-py3-none-any.whl |
|---|---|
| Size | 411.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d1862ff83b86e36464dcf386ec76a86e264e0638b93a96ef96ae6d351d5420d
|
|
BLAKE2b-256 checksum How to use checksums |
ff6bdb7fabf5542400a2919443b7f051d4ff079d75908acd7aea111ef0e64689
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logSecurity for torchhydro 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for torchhydro-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.