It is also possible to group several scenarios/scripts (that belong to different Delft-FEWS configurations for example) by using an extra directory level. In the application configuration, a reference to the appropriate scenario/script database can be set, for example ScenarioScriptDatabase/River. Minimize size of LDS through changes to Delft-FEWS configTo minimize the size of the localDataStore, one could separate the import of maps and timeseries into separate modules. This allows for a lower frequency for the import of maps. However, when this is applied, an additional change should be made to the Delft-FEWS configuration (see also application configuration). Also make sure to incorporate the changes to the moduleInstanceId's for the separate import of timeseries and maps in the Delft-FEWS configuration of the filters, spatial display, etc. The scenario/script database When a LDS (localDataStore) scenario is made, the LDS should not contain any information concerning the concerning a WaterCoach session. This information (Information on a selected scenario, script and time ) is stored in the localDataStore LDS whenever we start a session. It makes possible to leave an uncompleted session and start it again to continue. When we decide to copy localDataStore to the scenario/script database folder, we should first remove the session info WaterCoach session. Sometimes users make a LDS for a scenario when they are in a Watercoach session. It is advised to always use a LDS outside of a WaterCoach session as FEWS is storing the session information in a LDS table. It is therfore advised to remove information on an uncompleted WaterCoach session from the LDS before it is copied to the scenario folder. This can be done with the Explorer F12 menu P database - > delete WaterCoach session info. This should be done when the LDS is opened in a Delft-FEWS Stand Alone. |