scrollbar |
---|
Step 2.a. Define a root-directory for the application
Assumption:
- The <NGMS-root> directory is located at D:\NGMS-root
- The \bin-directory contains the FEWS-binary, located D:\NGMS\bin
- the \jre-directory contains the Java RunTime Environment (version 1.5.0_11), located in D:\NGMS\jre
Sample names:
- the <Region>-directory is named <Region> and is located in D:\NGMS\<Region>
- the model abbreviation is named XXX
- the full model name is YYY
Step 2.b. Populate the directory
unzip SampleregionUnzip SampleRegion.zip into the root directory
create associated executable for testing
Step 1. create Region.exe
the region directory.
Note: the SampleRegion only contains FEWS-compressed GIS-layers. For backtracking purposes the associated ESRI-shape files are available as attachments to this page (national shapes, regional shapes).
Step 2.c. Add most recent 'standard' xml files
This page contains the most recent version of some of the 'standard' configuration files which are still subject to change.
The following files should be added to the directory structure. The files are structured per directory name. The example files provided are from the WMW model in Midlands.
DisplayConfigFiles
ScenarioEditor , this file should be updated to reflect your region and the scenarios to be modified for your region.
ModuleConfigFiles
WMW_extract_staticmodeldata, this file should be updated to reflect your region. It is not used operationally. It is only used to create the aquifer thinkness and transmissivity layers for the Spatial Plots.
WMW_import_observed, this file should be updated to reflect your region.
WMW_merge_staticmodeldata, this file should be updated to reflect your region. It is not used operationally. It is only used to create the aquifer thinkness and transmissivity layers for the Spatial Plots.
RegionConfigFiles
Parameters, this file can be used directly.
ModuleInstanceSets, this file should be updated to reflect your region.
SystemConfigFiles
Explorer, this file should be updated to reflect your region. It needs a model boundary for your region and optionally some model specific MapLayers.
TimeSeriesDisplayConfig, this file should be updated to reflect your region. The section covering the moduleInstanceIdMappings should be updated.
WorkflowFiles
WMW_default_scenarios, this file should be updated to reflect your region.
WMW_import, this file should be updated to reflect your region.
WMW_modified_Historic, this file should be updated to reflect your region.
WMW_ref(Historic), this file should be updated to reflect your region.
WMW_ref(Naturalized), this file should be updated to reflect your region.
Step 2.d. Create associated executable for testing purposes
- Unzip MyRegion.jpif.zip to the \bin-directory.
- Rename MyRegion.exe to <Region>.exe
- Rename MyRegion.jpif to <Region>.jpif
- Open the jpif-file and replace the last line by the Region-directory. The content should be as follows:
..\jre
-mx1024m
-cp
$JARS_PATH$
nl.wldelft.fews.gui.explorer.Application
<Region>Step 2. create region.JPIF