scrollbar |
---|
...
Section | ||
---|---|---|
| ||
|
The SampleRegion contains a pre-defined folder structure as well as a set of basic configuration files for the NGMS. Some files need to be updated manually (mainly so-called instanceDesciptorsInstanceDesciptors, this step), while other files or directories will directories will be updated in later steps.
To be updated in step 3
...
. Go to the #info section for more details.
Anchor | ||||
---|---|---|---|---|
|
Step 3.a. Update ModuleInstanceDescriptors.xml file
Purpose: this file informs the system software on the existence of the ModuleInstances that conduct data processing. It relates the ModuleConfigFiles (holding a specific set of the instructions) to the data processing software components as identified in the ModuleDescriptors.xml-file.
Note: The system will report an error if any configuration file refers to a ModuleInstanceId which has not been identified in this file. A mismatch between ModuleInstances identified in this descriptors-file, and the contents of the ModuleConfigFiles-folder is only detected if a workflow is dispatched which calls the moduelInstance.
Configuration instructions
- remove ModuleInstanceDescriptors (i.e. scenario types) which are not relevant to the model
- replace XXX_ bij model abbrevation e.g XXX_ by WMW_ for West Midlands Worfe module instances
- replace YYY bij model name e.g YYY by WestMidlandsWorfe
- check if proper Modflow version is mentioned in description
Anchor | ||||
---|---|---|---|---|
|
Step 3.b. Update ModuleInstanceSets.xml file
Purpose: this file groups ModuleInstanceIds into sets being reused in the plot-definition of the DisplayGroups.xml-file (i.e. the file which defines the shortcuts in the TimeSeries Display).
Note: Plots may miss the data generated by some ModuleInstances if they are not properly listed in the ModuelInstanceSet. No error is reported.
Configuration instructions
- remove ModuleInstanceDescriptors (i.e. scenario types) which are not relevant to the model
- replace XXX_ bij model abbrevation e.g XXX_ by WMW_ for West Midlands Worfe module instances
Anchor | ||||
---|---|---|---|---|
|
Step 3.c. Update WorkflowDescriptors.xml file
Purpose: this file identifies the workflows which can be executed by the system. Each Workflow file holds a sequence of data processing steps (defined by ModuleInstances) to be called after each other.
Note: Workflows as listed in this file appear in the following displays:
- ManualForecast display (workflows listed for dispatching)
- ForecastManager display (workflows listed in overview of data sets available for download/opening)
- Explorer (data set opened)
Configuration instructions (starting from sample)
- replace XXX_ bij model abbrevation e.g XXX_ by WMW_ for West Midlands Worfe module instances
- replace YYY bij model name e.g YYY by WestMidlandsWorfe
- remove scneario types not utilized
- check model descriptions (e.g. modflow version)
- update dates of model states (if appropriate)
Anchor | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
To be updated in step 3
|
...
|
...
|
...
...
Updated in other steps
Update is optional (if better materials available)
|
...
No update needed
|
...
Purpose: this file informs the system software on the existence of the ModuleInstances that conduct data processing. It relates the ModuleConfigFiles (holding a specific set of the instructions) to the data processing software components as identified in the ModuleDescriptors.xml-file.
Note: The system will report an error if any configuration file refers to a ModuleInstanceId which has not been identified in this file. A mismatch between ModuleInstances identified in this descriptors-file, and the contents of the ModuleConfigFiles-folder is only detected if a workflow is dispatched which calls the moduelInstance.
Configuration instructions
...