...
When merging two separate configurations for two models in one region it is necessarry to go through the following 10 steps. It is best to start with the configuration of one of the two models to be merged and add one model to the configuration of the other model. The basic configuration files which are not going to be changed (like ModuleDescriptors, DisplayDescriptors, Parameters, etc) are already available and up to date (if not use the most recent version of the files). To simplify
| Tip |
|---|
Before you start to manually amend all the files please note that there is a tool available to simplify the merge activity |
- merge Locations and LocationSets (can be done with the mergemodels tool, see below)
- merge ModuleInstanceDescriptors (can bedone with the mergemodels tool, see below)
- merge WorkflowDescriptors (can be done with the mergemodels tool, see below)
- merge ModuleInstanceSets (can be done with the mergemodels tool, see below)
- merge IdMapDescriptors (can be done with the mergemodels tool, see below)
- merge Branches and Grids (Grids can be merged with the mergemodels tool, see below, branches.xml has to be merged manually!)
- edit ScenarioEditor (can be done with the mergemodels tool, see below)
- edit TimeSeriesDisplayConfig and Explorer (can be done with the mergemodels tool, see below)
- create Filters, GridDisplay, DisplayGroups (Filters and, GridDisplay can be merged with the mergedmodels tool, DisplayGroups.xml hast be merged manually!)
- copy IdMapFiles, MapLayerFiles, ModuleConfigFiles, ModuleDataSetFiles, ModuleParFiles, WorkFlowFiles, ColdStates and Modules (has to be done manually!)
...
| Info |
|---|
Example of mergemodels.inp: |
...