This repository contains the official MESH development code, which is the basis for the 'tags' listed under the MESH-Releases repository. The same tags are listed under this repository. Legacy branches and utilities have also been ported from the former SVN (Subversion) repository. Future developments must create 'forks' from this repository.
I have a suggestion for the development of the MESH model in terms of reading climate forcing files. Instead of reading one big chunk of climate forcing data for the entire period of simulation (e.g., 1980-2020), it is convenient for MESH to have the capability to read forcing data month-by-month from a list of extracted climate forcing, like 198001, 198002, 198003, and so on. This implementation can be applied within the MESH code. A short-term solution for this implementation externally is to write a bash script to run MESH month-by-month by modifying the MESH_input_run_options file after finishing one month of the run where the name of the climate forcing file, start and end time of simulation, as well as the resume/saveresume flags of the MESH_input_run_options are updated.
I have a suggestion for the development of the MESH model in terms of reading climate forcing files. Instead of reading one big chunk of climate forcing data for the entire period of simulation (e.g., 1980-2020), it is convenient for MESH to have the capability to read forcing data
month-by-month
from a list of extracted climate forcing, like 198001, 198002, 198003, and so on. This implementation can be applied within the MESH code. A short-term solution for this implementation externally is to write a bash script to run MESHmonth-by-month
by modifying theMESH_input_run_options
file after finishing one month of the run where the name of the climate forcing file, start and end time of simulation, as well as the resume/saveresume flags of theMESH_input_run_options
are updated.