Page History

...

• installation of SOBEK (incl license) in the root of the same partition of your hard disk (e.g. c: or d: ) as where FEWS is run.
• Wiki MarkupSOBEK project (*.lit folder) in /Modules/SOBEK/\[application name\]/ \ *.litunmigrated-wiki-markup
• SOBEK adapter: /Modules/SOBEK/\[application name\]/ SOBEK_Adapter.xml
• general adapter file: Config/ModuleConfigFiles/SOBEK_Forecast and SOBEK_Historical

...

1. run the simulation task
2. cancel the simulation once started
3. Wiki Markuppress \ [Show permanent\] button on error message box
4. delete all next files in work directory of the case
   1. out;.his;.map;.stu;.pst;.hia;.log;.prn;.hia;.inc;.asc;.mon;.lst
   2. 2DAREA.DAT
   3. 2DFLOW.DAT
   4. 2DSOBEK.CHZ
   5. 2DVELOC.DAT
   6. 2DVOLUME.DAT
   7. 2DPOINT.DAT
5. remove rubish data from the project directory
   1. boundary subdir
   2. data subdir
   3. initial S subdir
   4. Network subdir
   5. Many files in fixed subdir
   6. Many files in Bathymetry subdir

...

The case must be saved before copying with at least the \ [Schematisation\] task green. !image008.jpg!
Image Added

Schematisation
Note that the boundaries, laterals and controllers which data is being updated by FEWS should already been defined as time tables, both for Flow and WAQ modules!**

...

• comment: has no meaning, can be any string just for your reference
• description: Description of sub parameter, previously used as Sobek object ID
• sobekObjectId,  like laternal node ID, boundary node ID, controller ID
  If not defined the description element is used (as it was in the older days)
• locationID : is the location ID as used in the PI XML time series file
• parameterID : is the parameter ID as used in the PI XML time series file
• type: type of data or time series. See the table below to select the type of parameter to select.

...

The first option is the preferred one as it guarantees that all Case Management is correct. However, it requires quite a lot of configuration as all the possible workingdirectories have to be pre-configured. Instead of one, for all the ensemble members a working directory should be prepared. In the General Adapter you should link to these directories by using
<rootDir>$REGION_HOME$/Modules/Sobek/Singapore_%ENSEMBLE_MEMBER_INDEX%</rootDir>.
See also 19 Parallel running of ensemble loops.

Wiki MarkupThe second option is more advanced but faster and especially useful for small models where the CMT activities are a significant part of the simulation time. Next to that the configuration is much easier as only one temp directory has to be specified.
In the General Adapter you specify only <rootDir>%TEMP_DIR%</rootDir> where the TEMP_DIR will be defined as the system TEMP_DIR (or defined in the global.properties) and an added unique subdirectory. In case your system TEMP_DIR variable is "c:\windows\Temp" the General Adapter will use as TEMP_DIR in each particular instance of the General Adapter (i.e. per ensemble member) TEMP_DIR = "C:\windows\temp\<FSS>_<ModuleInstance>_<ENSEMBLE_MEMBER_INDEX>_<threadId>."
In this configuration it is quite useful to have no CMT activities anymore. Therefore define in the SBKBATCH.INI the key \ [General\]RunFromTempDirWithoutCMT=-1. Then you need to configure:

• a CMTWORK and WORK directory where all the files are available already
• FNM files in the CMTWORK that has only relative paths or links to files that are not specific to the actual run (like language files)unmigrated-wiki-markup
• use as \ [General\]SimulateCall and \ [General\]SimulateCallRtnFile directly the required program or a batch file that runs multiple programs. For example if you need to run only the RR module, you define:

  Code Block
  [General} SimulateCall=\Sobek212\Programs\3b\sobek_3b.exe sobek_3b.fnm sobek_3b.rtn SimulateCallRtnFile=sobek_3b.rtn

• save the whole setup in a moduleDataSet that will be exported before starting the simulation

...