Currently, in the WMT client's ParameterTable class, when a parameter has a key named "separator", it's rendered as a separator between groups of parameters. For example, in Hydrotrend, this parameter
A better description for this behavior is a header. Such parameters should be refactored so that
a new type, 'header" is used;
the parameter key should describe the section -- e.g., a set of temperature parameters would have the key temperature_section, or something of the sort.
Currently, in the WMT client's
ParameterTable
class, when a parameter has a key named "separator", it's rendered as a separator between groups of parameters. For example, in Hydrotrend, this parameteris rendered as
A better description for this behavior is a header. Such parameters should be refactored so that
temperature_section
, or something of the sort.For example:
This will require some refactoring, both of model BMIs and the
ParameterTable
code. However, it also presages a "subheader" type.