To understand the application of NGMS, a few concepts need to be highlighted. Most important are the terms related to the #run-identification, the #time handling and the #data synchronization.
Run-identification
relational picture needed
Models and Module Adapter
Models are an essential component of NGMS as they generate the data which is being visualized and processed.
Data exchange between the NGMS software and the model-executable is managed by the Module Adapter. This Module Adapter converts output from NGMS into the native model data format and it converts model output into the NGMS data exchange format.
Whatif-scenario
A scenario or what-if scenario refers to the specification of the adjustment of the model (input) data.
Workflows
A workflow is a sequence of data processing steps. Within NGMS, these steps are typically pre-processing (if any), model execution and post-processing.
Within NGMS, various workflows are distinguished as not all runs require that all activities are executed.
E.g. a default run, such as the Calibrated Historic, or Naturalized run, just involves the execution of Modflow, with a set of input files, and the associated post-processing. However, to run a modified scenario, some additional pre-processing activities are needed - to modify the Modflow input files - before the Modflow executable can be started.
Runs
A run (alias task run or forecast) refers to the output of a workflow (i.e. set of data processing activities), given a specific initial state (starting condition) and a whatif-scenario (a specification of the input modification)
Time handling
The FEWS software which typically is used in real-time data processing. The default behaviour of the system is to automatically move forward in time. Displays show data relative to this 'current system time' unless the user changes the 'Display' time in the Dialog.
Within NGMS, the 'current system time' can be manipulated by the user, thus allowing to look back.
When executing a default run, the time-zero (T0) should be properly aligned with the representative period of the model data as all data processing is calendar based using a relative time shift based on T0.
When executing a modified scenario, the associated display manages proper handling of the initial state chosen and the associated T0.
Data synchonization / downloading data
Within the NGMS, the central database holds all the data of all the runs. The user can download (synchronize) this data to its local computer. dependent on its login profile (i.e. login mode), the user can obtain more or less data from the central database.
Synchronization
Synchronization refers to the data transfer process from the central server to your local client (or vice versa). This process ensure that your local datastore contains exactly the same data as the central database.
Various levels of data exchange are supported as each data set has been associated to a so-called 'synchLevel'. The user can log on with different profiles (see below), where each profile synchronizes the data of one or more synchLevels.
Login profiles in NGMS
- minimal: downloads all point data as well as longitudinal profiles (i.e. accretion profiles)
- synchLevel=0
- custom: allows the user to extend the minimal download up till the full data set. The user can select to include:
- Merged grids: aquifer properties, all surface water grids, recharge, the upper groundwater table, the combined horizontal flows, the accumulated vertical flow (synchlevel=21)
- Head details: heads for all model layers (synchLevel=22)
- Cell-flow details: horizontal and vertical groundwater flows for all model layers (synchLevel=23)
- full: downloads all available data
- synchLevel = 0,21,22,23
