The following section provides an explanation of all the columns in the filters sheet which is part of the Display generation spreadsheet:
Column Name | Explanation of contents | |||
|---|---|---|---|---|
TYPE | This column specifies the structure of the filters. The type can either be a parent, a child or a timeseries (tms). The tms define the actual data to be displayed and the childs and parents define the order of the filter in that row (a child can be a parent at a lower level) | |||
FILTERID | This column contains the Id of the filter. This is used to make each filter unique to be able to nest filters within filters |
| FILTERID |
|
NAME | This is the name of the Filter. It is only used at the parent level and where the TimeSerieSet itself is specified | |||
MI_PREFIX | The ModuleInstance prefix is the model abbreviation and is applied referring to all elements in the configuration files where the model prefix is used (file names, etc) the first part of the ModuleInstanceId which was used to create and store the data. Together the columns MI_PREFIX, MI_SOURCE and MI_EXT create the complete ModuleInstanceId | |||
MI_SOURCE | This is the ModuleInstance source and refers to a unique middle part of the ModuleInstanceId which is used to store the dataModuleInstance source. It should refer to the ModuleInstanceId processing step which was used to create the original data. Together the columns MI_PREFIX, MI_SOURCE and MI_EXT create the complete ModuleInstanceId | |||
MI_EXT | This is the ModuleInstance source and refers to a unique last part of the ModuleInstanceId which is used to store the data. It should refer to the ModuleInstanceId Scenario name, which was used to create the original data (or to 'observed' in case of observed data). Together the columns MI_PREFIX, MI_SOURCE and MI_EXT create the complete ModuleInstanceId | |||
PAR | This column contains a reference to the input parameter to be processed. The name of the parameter should be taken from the parameters.xml | |||
LOCSET | This column is referring to the locationSet of the data which is input for the interpolation. Locations and LocationSet are mutually exclusive. Either one or the other should be filled indisplayed through the filter | |||
TMSTYPE | This TimeSeriesType is specified for each TimeSeries and should be the same as what has been used when the data was created. Three types (of the 4 available) are used in NGMS: external historical (observed data), simulated historical (used in ref scenario) and simulated forecasting (used in whatif scenario) | TMSTYPE_in |
| |
TIMESTEP | This is referring to the the TimeStep used for the data being created. It can either be nonequidistant or DaysOfMonth |