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 | ||
---|---|---|---|
MI_PREFIX | The ModuleInstance prefix is the model abbreviation and is applied to all elements in the configuration files where the model prefix is used (file names, etc) | ||
MI_SOURCE | This is the ModuleInstance source and refers to a unique part of the ModuleInstanceId which is used to store the data. It should refer to the ModuleInstanceId which was used to create the original data | ||
PAR_in | This column contains a reference to the input parameter to be processed. The name of the parameter should be taken from the parameters.xml | ||
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 | ||
NAME | This is the name of the InterpolationSet. This element should be unique for each interpolationSet in the fileFilter. It is also used ot easily identify an interpolationSet | ||
METHOD | This refers to the interpolation method used. The options used in NGMS are: closestdistance, sum and inputAverageTimesOutputArea | ||
only used at the parent level and where the TimeSerieSet itself is specified | |||
MI_PREFIX | The ModuleInstance prefix is the model abbreviation and | LOC_in | This column is referring to the locationID first part of the data which is input for the interpolation. Locations and LocationSet are mutually exclusive. Either one or the other should be filled in |
LOCSET_in | 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 in | ||
VALTYPE_in | This refers to the type of data used as input for the interpolation. The options are scalar, polygon, grid and longitudinalprofile. Typically a grid is used as input | ||
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 middle part of the ModuleInstance source. It should refer to the 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 last part of the ModuleInstanceId. It should refer to the 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 PAR_out | This column contains a reference to the output parameter being createdinput parameter to be processed. The name of the parameter should be taken from the parameters.xml | ||
LOC_out LOCSET | This column is referring to the locationID locationSet of the data which is the output from the interpolation. Locations and LocationSet are mutually exclusive. Either one or the other should be filled in | ||
LOCSET_out | This column is referring to the locationSet of the data which is output from the interpolation. Locations and LocationSet are mutually exclusive. Either one or the other should be filled in | ||
VALTYPE_out | This refers to the type of data produced as output from the interpolation. The options are scalar, polygon, grid and longitudinalprofile | ||
displayed 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 | SYNCH | This column is used to specify the synchronisation level of the data that is being created and stored in the database. More information about the synchronisation levels can be found in Step 7. ModuleInstances (ModuleConfigfiles) |
TIMESTEP | This is referring to the the TimeStep used for the data being created. It can either be nonequidistant or DaysOfMonth | MULTIPLIER | Defines a multiplier to be applied in the processing step to convert positive values to negative and visaversa |