Support
ParaMESH support is continually being expanded. Review the Documentation
section for more information about the modelling environments that are being
supported by ParaMESH.
Explore:
Support > Documentation
An administrative manual is not available at this time.
Please be patient while documentation is updated for the
current version of ParaMESH.
Please contact the ParaMESH administrator if additional
documentation is required.
MESH 1.3
Running MESH with ParaMESH--For Users with an Existing MESH Directory
Updated: September 11, 2009
Follow this tutorial to load an existing MESH directory with ParaMESH. This
tutorial is applicable to the "Classic View" of all versions of ParaMESH 1.2
and above that are configured for the MESH environment.
The parameter definitions for MESH 1.3 have been defined based on CLASS
and MESH documentation, and private consultation with Dr. E. D. (Ric) Soulis
of the University of Waterloo (Ontario, CA), B. Davison of the National
Hydrology Research Centre of Environment Canada (Saskatchewan, CA), and
D. Verseghy of Environment Canada (Ontario, CA).
Use the integrated application below to review the parameter definitions
that have been defined for MESH 1.3 by their associated parameter file.
Notes: The "File: ..." drop-down box will not be visible if
JavaScript has been disabled. The integrated application provides live access
to the ParaMESH repository. Please wait a few minutes and try again if response
is slow. The integrated application has been tested with Microsoft Internet
Explorer (7+), Mozilla Firefox (3.5.2+), and Google Chrome (3.5.x+).
Advanced parameter verification is performed using the bounds and range
sets that have been defined for numeric parameters (of "Integer" or "Double"
type) for MESH 1.3. These values can viewed by loading the parameter definitions
in the "Parameter Definitions" sub-section above.
ParaMESH checks that a parameter value is greater than or equal to the
first bound and less than or equal to the last bound in a "Continuous" range
set, that a parameter value is equal to any given bound in a "Discontinuous"
range set, that a parameter values is less than or equal to the first bound
in a "Less Than Or Equal To" range set, and that a parameter value is greater
than or equal to the first bound in a "Greater Than Or Equal To" range set.
ParaMESH does not check a parameter value when "No Range Set" has been defined.
Extended parameter verification is performed using a set of "Quick Fixes"
and "Special Checks" that have been defined for MESH 1.3. Review these definitions
below. Note that they refer to parameter ID's, and that a definition associated
with a parameter ID can be viewed by loading the parameter definitions in
the "Parameter Definitions" sub-section above.
ParaMESH performs the following quick fixes for MESH 1.3:
- Adjust DEGLAT if it is greater than {90}. Subtract {90} if the value
is using the {0} to {180} data convention.
- Adjust DEGLON if it is less than {0}. Add {180} if the value is
using the {-180} to {180} data convention.
- Change the value of MetStartHour to {0} if MetStartHour is equal
to {24}.
- Change the value of GRU to include its default value and order (i.e.:
"GRU" and {1}) if the value does not exist.
- Set FARE equal to {1} for compatibility reasons. FARE has been depreciated
by modern versions of MESH.
- Ignore erroneous values of SAND that are equal to {-2}, {-3}, or
{-4}. These are special SAND flags that are accepted by CLASS.
- Ignore erroneous values of ORGM that are equal to {1}, {2}, or {3}.
These are special ORGM flags that are accepted by CLASS.
- Flag all SIM_START(x) and SIM_STOP(x) values to be shown if any
SIM_START(x) or SIM_STOP(x) values are erroneous. The user may wish
to set all values to {0} to accept MESH defaults or change all values
to become representative of their forcing data.
ParaMESH performs the following special checks for MESH 1.3:
- Check that all values of FCAN sum to {1} for a given grouped response
unit.
- Check that HourlyStartDay is less than {366} if HourlyStartYear
is not a leap-year.
- Check that HourlyStopDay is less than {366} if HourlyStopYear is
not a leap-year.
- Check that HourlyStartYear is less than or equal to HourlyStopYear.
- Check that DailyStartDay is less than {366} if DailyStartYear is
not a leap-year.
- Check that DailyStopDay is less than {366} if DailyStopYear is not
a leap-year.
- Check that DailyStartYear is less than or equal to DailyStopYear.
- Check that SimStartDay is less than {366} if SimStartYear is not
a leap-year.
- Check that SimStopDay is less than {366} if SimStopYear is not a
leap-year.
- Check that SimStartYear is less than or equal to SimStopYear.
- Check that MetStartDay is less than {366} if MetStartYear is not
a leap-year.
- Check that MetStartYear is greater than or equal to SIM_STARTYEAR
and that MetStartYear is less than or equal to SIM_STOPYEAR.
- Check that LAMN is less than or equal to LAMX for a given canopy
type and grouped response unit.
- Check that THLQ is equal to {0.04} and THIC is greater than {0}
if TBAR is less than or equal to {0} for a given soil layer and grouped
response unit to be representative of a frozen soil layer.
- Check that THLQ is greater than {0.04} and THIC is equal to {0}
if TBAR if greater than {0} for a given soil layer and grouped response
unit to be representative of a thawed soil layer.
- Check that RHOS is greater than {0} if SNO is greater than {0} for
a given grouped response unit to ensure that a snow density has been
defined if a snow depth has been given.
- Warn that ZBLD should not be less than the vegetation height of
the canopy.
- Check that the sum of SAND and CLAY is less than or equal to {100}
for a given soil layer and grouped response unit.
- Warn that values of SAND and CLAY should equal {0} if the value
of ORGM is equal to {100} for a given soil layer and grouped response
unit to be representative of a completely organic (peaty) soil layer.
- Check that SIM_STARTDAY is less than {366} if SIM_STARTYEAR is not
a leap-year.
- Check that SIM_STOPDAY is less than {366} if SIM_STOPYEAR is not
a leap-year.
- Check that SIM_STARTYEAR is less than or equal to SIM_STOPYEAR.
- Check that all values of SOIL_DEPTH(x) sum to SDEP or {4.1}.
Support > Known
Issues
No known issues have been discovered with ParaMESH 1.2.2.
Support > Future
Developments
The next version of ParaMESH will include:
- An automated parameter calibration scheme.
- Dynamic support for multiple environments.
- Backwards compatibility with all versions of
MESH.
ParaMESH is being developed to support the following software:
- The
OSTRICH optimization software toolkit.
Updated: Nov. 3, 2009