Open mee067 opened 4 months ago
To document the status of this issue:
slope from MESH_Parameters.nc is used to set xslp when MMESH is active only and it is assigned at the tile level - not the sub/grid level as done in MESH_Parameters.r2c
To use it when MMESH is off, the field has to be renamed in the parameter file to be xslp
I didn't think the xslp
of MMESH is connected to that of CLASS. Neither is IntSlope
from the db. I like to see things where a parameters describing the same thing are used consistently, but it isn't the case with these.
I suspect if demslope
is mapped to tile values from MMESH inputs, it would get overwritten with grid-based values from the other parameter files, depending on the order in which those files are read.
I always get confused with all those names for the same thing - or is it the same thing? please define xslp, demslope, and IntSlope.
Looking into MMESH code after posting the note above, MMESH assigns the "slope
" field read from parameteres.nc
to CLASS "xslp
" at the tile level, but that will only occur when MMESH is active.
They are independent variables representing the same thing.
any documentation?
For MMESH, one of the required parameters is slope which named as such and provided as tile-based (in 1860_ME_ZT code). This slope is used in the adjustments of met forcing to the different tiles.
MESH also uses slope (named xslp or demslope or intslope) read from CLASS.ini or as a distributed field at the grid/sub level for the generation/routing of overland and sub-surface runoff components (WATROF) and possibly by other routines.
If MMESH is active, will slope be used for xlsp?
What if we still provide MMESH parameters while deactivating it?