Background on ModuleDataSets organization and the Modflow Module Adapter

Go to:

• #Modules-directory organization
• #ModuleDataSet.zip-files
• #Model states
• #Modflow Module Adapter

Organization of the Modules-directory organization.

The Modules directory is the place where the majority of the data sets are held and where the models are executed. The directory structure is organized as follows:

• At the top level, a distinction is made between the binaries and the models.
• the \bin-directory holds the executables and libraries for Modflow, PCRaster and possibly other codes.
• Each model has its own directory which will hold all relevant model data for Modflow and the recharge model.
• The Modflow directory holds the Modflow data sets organized by scenario type:
  • \Nat is the workspace for the Naturalized run
  • \Hist is the workspace for the Calibrated Historic run and its what-if runs
  • \RecAct is the workspace for the RecentActual run
  • \FulLic is the workspace for the FullyLicenced run
  • \Lta is the workspace for the LongTermAverage run

• Each workspace holds five directories.
  • the \baseData directory holds the Modflow data files which remain fixed for all runs
  • the \fromNGMS directory is used to exchange data from the system towards the Modflow Module Adapter to be converted
  • the \logs directory holds all the log files which are dumped in case of failure
  • the \toNGMS directory is used to hand back data from the Module Adapter towards the NGMS
  • the \workMF directory is the place where e the execution of Modflow is conducted and where the native output is placed.
  • the root holds the instruction-files and MsDos-batch files to run Modflow and the moduelAdapter

• The Modflow-root directory also holds some files for the moduelAdapter:
  • ParameterIds.dat defines the parameters as recognized and used by the moduel Adapter
  • diagnostics_search_strings.dat defines the strings that filter dedicated diagnostics information from the Modflow.OUT file. This data is written to a diagnostics.xml file which can be visualized in the log of NGMS.
  • residual_search_strings.dat defines the strings that filter the residual flow and head convergence information from the Modflow.OUT file. This data will be written to a time series-file.

All model-related directories use abbreviations to keep the path length sufficient short, such that it can be handled by the Modflow-executable.

ModuleDataSet.zip-files.

To ensure that each workflow starts with the original Modflow data files, a mechanism has been defined where the files that may be modified by the Module Adapter (i.e. the BAS, WEL and RCH file) are being refreshed from an original 'source'.

Therefore, the WEL and RCH file are contained in a so-called ModuleDataSet.zip-file. At the start of each workflow, the FEWS-General Adapter module unpacks this file - stored in directory \Config\ModuleDataSetFiles - and places it into the workMF directory.

Model states.

A model state

Modflow Module Adapter

The purpose of Modflow Module Adapter is to convert data from the Modflow native format into the FEWS-Published Interface format (i.e. a set of XML-file defines also referred to as PI) and vice versa.

The exact details of the Modflow Module Adapter are described in a Word-document, but this section highlights the main files needed for its operation:

• the IN file (instructions)
  The IN file provides the instructions to the Module Adapter, as well as pointers to the files and directories it needs to execute its tasks.
  Note 1: the Module Adapter stops executing all commands if it hits a blank line.
  Note 2: the Module Adapter expects a new line after the last command

• the OFS file (offset)
  Since the FEWS software needs geographic and calendar information to hold and visualize the Modflow data, a so-called offset-file (OFS) has been defined which provides this data to the Module Adapter. The OFS file is different for each model (due to the geographic information) and may vary between runs as well (due to the calendar information).
  The IN-file refers to the OFS file that needs to be used.
• the ParameterIDs.dat file
  The ParameterIDs.dat file is required which informs the Module Adapter on the Parameter-Ids to be used in its data exchange.
• the .._search_string.dat file
  The FEWS software can only accept logging information in its diagnostics.xml format. This _search_string.dat file identifies which portions of the Modflow.OUT file should be communicated to the NGMS.