Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

The GridDisplay can be generated using the provided tools and the information below to fill in the spreadsheet. After producing the GridDisplay configuration file it is necessary to update this file using with references to the Thickness and Transmissivity parameters of the model. The layers thickness and transmissivity should be put in the GridDisplay as a fixed layer (ASCIIGridLayer) instead of a dynamic layer. This is relatively new and an example configuration file can be provided. To get the data displayed the time step of the extract and merge ModuleConfigFiles should change to nonequidistant and the GridDisplay to display the resulting series for thickness and transmissivity as well. Running the Import workflow will produce the thickness and transmissivity data which is still in the database. This data should be exported form the spatial plots as an ASCII grid (using the right mouse button when the specific parameter is selected) and then put the resulting file in the MapLayersFiles.

The following section provides an explanation of all the columns in the
filters gridDisplay sheet which is part of Display generation spreadsheet:

Column Name

Explanation of contents

TYPE

This column specifies the structure of the plots. The type can either be a level 1 to level 4, loc, locset, contour or uv. The types loc and locset specify whether the data is linked to one location or a locationset, the uv and contour types define a specific type of plot (using different settings) and the levels

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)

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

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

GROUPID

This column contains the Id of the plotgroup. Each plotgroup should have a unique name

GROUP_NAME

This column contains the name of the plotgroup. This is used to specify the name of a group of plots

PLOT_NAME

This is the name of the plot. It is only used at the level of the plot where the TimeSerieSet itself is specified

PAR 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

NAME MI_SOURCE

This is the name middle part of the InterpolationSetModuleInstance source. This element should be unique for each interpolationSet in the file. 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

LOC_in

This column is referring to the locationID 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

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_EXT 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

This column is referring to the locationID of location used to display 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 displayed through the interpolationplot. Locations and LocationSet are mutually exclusive. Either one or the other should be filled in

VALTYPE_out TMSTYPE

This refers to the type of data produced as output from the interpolation. The options are scalar, polygon, grid and longitudinalprofile

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 (ModuleConfigfilesTimeSeriesType 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)

TIMESTEP

This is referring to the the TimeStep used for the data being createddisplayed. It can either be nonequidistant or DaysOfMonth

VIEWPERIOD_UNIT

This column is referring to the unit of the period for which you want to display data. Typically we specify the display period in weeks. It is only used for the rows where you specify the data to be displayed

VIEWPERIOD_START

This column is referring to the start of the period for which you want to display data. Typically the start of the display period should be 0. It is only used for the rows where you specify the data to be displayed

VIEWPERIOD_END

This column is referring to the end of the period for which you want to display data. Typically the end of the display period should be the end of the simulation. It is only used for the rows where you specify the data to be displayed

MULTIPLIER

Defines a multiplier to be applied in the processing step to convert positive values to negative and visaversa