Versions Compared

Old Version 6

changes.mady.by.user Peter Gijsbers

Saved on

compared with

New Version 7

changes.mady.by.user Peter Gijsbers

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • \Config\RegionConfigFiles
    • Step 3. update the contents of the sample Descriptor files.ModuleInstanceDescriptors.xml-file identifies ModuleInstances specified in \Config\ModuleConfigFiles-folder
    • ModuleInstanceSets.xml-file groups ModuleInstance for use in the timeseries plot definition
    • WorkFlowDescriptors.xml-file identifies the Workflows of this application, as specified in \Config\WorkflowFiles-folder

...

No update needed

  • \Config\MapLayerFiles
    • Folder is Folder is populated with GIS-layers. Shp-files have been compressed in native ssl format. Shape files are available in step 2 as seperate attachements.
  • \Config\RegionConfigFiles
    • ColdModuleInstanceStateGroups.xml-file holds Ids of ColdStates as used in he NGMS-configuration conept. No update needed
    • UnitConversionsDescriptors.xml-file identifies to UnitConversionsFiles held in folder \Config\UnitConversionsFiles. No update needed
  • \Config\SystemConfigFiles
    • DisplayDescriptors.xml-file identifies software components providing display functionality
    • DisplayInstanceDescriptors.xml-file identifies DisplayInstances as used in the configuration
    • LocationIcons.xml-file links icon-files to location sets
    • ModuleDescriptors.xml-file identifies software components conducting data processing
  • \Config\UnitConversionsFiles
    •  Folder Folder contains fixed UnitConversionFiles. No update needed 

Anchor
ModuleInstanceDescriptors
ModuleInstanceDescriptors
h2. 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 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.

...

  1. remove ModuleInstanceDescriptors (i.e. scenario types) which are not relevant to the model
  2. replace XXX_ bij model abbrevation e.g XXX_ by WMW_ for West Midlands Worfe module instances
  3. replace YYY bij model name e.g YYY  YYY by WestMidlandsWorfe
  4. check if proper Modflow version is mentioned in description