The purpose of this repository is to provide a place for sharing and improving scripts for pre- and post-processing data, MESH vector-based workflow, as well as running, the MESH Hydrology Land-Surface model.
R is the primary language of development for MESH pre- and post-processing scripts, and some useful tools (listed below) have already been developed. However, scripts and functions in any programming language are welcome on this repository.
Key R-Language Packages:
- R Packages developed at the Centre for Hydrology, University of Saskatchewan
- MESHr - R package containing functions for pre- and post- processing MESH models.
- CRHMr - R package for the CRHM model, but also contains functions for gap removal, infilling and imputation of time series data, which may be useful for MESH.
- tidyhydat - an R package managed by the BCMOE with functions for accessing and plotting hydrometric data from the Water Survey of Canada.
- HYDAT - R package to interface to Canadian Hydrometric Data (HYDAT) published by Water Survey of Canada
- WISKIr - R package containing functions for retrieving data from a Wiski database
- Canadian Society for Hydrological Scieces (CSHS) hydRology package CSHShydRology contains functions useful to Canadian hydrologists, such as statistical hydrology, data manipulation, visualization, spatial hydrology, and streamflow analysis.
- weathercan R package for searching and downloading multiple months/years of historical weather data from Environment and Climate Change Canada's (ECCC) website.
- CRAN Task View for Hydrology Information about R packages broadly relevant to hydrology.
- The Photobiology package which contains the function water_vp_sat to calculate saturation vapour pressure using either the Tetens, Magnus, Wexler, or Goff-Gratch approximations.
- The humidity package for R (CRAN) which contains useful functions for calculating water vapour pressure (ea) and specific humidity (ie. see functions WVP2, and SH, as well as C2K or K2C for temperature conversions).
Code in this repository is organized according to function, as listed below:
- Pre-processing
- Driving_data
- Drainage_database
- Input_files
- Run_MESH (bash command line, running on servers (Plato, Graham, etc.), etc.)
- Post-processing
Within each main folder, each script should be in its own appropriately-named sub-folder. The script folders should including the code file(s) and a "how-to" document (markdown format preferred) outlining instructions for use such as language used, dependent packages, data / format requirements, how to use the script/functions, outputs produced, and any relevant reference documentation.