Below are some modeling methods and information for WaterGEMS beyond what is provided in the product documentation.
The model datastore in a Jet format (as used by MS Access). It contains one model dataset and all the data for the modeling elements. It is a self-contained file that contains all the data required to make a model run. All other file types can be deleted without harming the datastore, and the model will still function.
A WaterGEMS Project file containing project data in an XML format. There are many components to it, however some of the more important ones are:
A WaterGEMS drawing file. It's primary purpose is to speed up the opening of model files inside the Stand-alone envrionment with pre-saved drawing data. It contains the last saved model element drawing display coordinates, symbology (eg. Color, Line Thickness Multipliers) and decorations (eg. Flow Arrows). In this fashion, WaterGEMS does not need to refresh the drawing during the opening of a model. Its contents are read directly into memory, and does not participate in the active session itself.
Saving a WaterGEMS file in the Stand-Alone environment triggers this file to be regenerated, and is usually the slowest part of the save process.
During a model open, if WaterGEMS detects that the DWH is out-of-sync with Project, or is not present at all, this will trigger WaterGEMS to refresh the entire drawing, and a dialog for the Synchronise Drawing process will appear during the model open.
This is a results report file, which contains the information seen in the Calculation Summary Dialog.
A standard calculation output file from Hydraulic or Water Quality model simulation types. This contains a data table that lists the corresponding results for each modelling element, for each model timestep. The size and contents of these files are governed by the selected Calculation Options, particularly:
Note that simulation types other than Hydraulic or Water Quality simulation types use different file extensions.
Most WaterGEMS user settings and customisations are contained in XML files. These contain things such as:
See WaterGEMs XML Guide
When a WaterGEMS model is opened, the following actions occur:
When a WaterGEMS model is being edited:
When a WaterGEMS model is saved, the following actions occur:
Result files are treated similarly to model data files, but with some subtle differences:
Sometimes a runtime error will occur during the model save process, and the model will "appear" to not have saved, with no apparent way of saving the model. Generally these errors occur during the generation of the *.dwh file in the Project Directory. However, the copy and paste operation of the *.wtg.mdb and *.wtg files from the Working Directory to the Project Directory generally always completes, which is the only thing important in these instances.
The important files, the *.wtg.mdb, and *.wtg files have saved, although the *.dwh file is often corrupted in these instances. After a "failed" save, the user can simply close the model (choosing not to save in the 2nd instance), delete the *.dwh file from the Project Directory, and reopen the model.
For added assurance, a user can compare the timestamps between the Working Directory and Project Directory copies of the *.wtg.mdb and *.wtg files to ensure they are the same. If they are not, the user can manually copy, paste and rename the files from the Working Directory to the Project Directory.
There are two problems in these instances, one obvious, and one not obvious:
The solution can treat both symptoms. Model edits are recoverable because the Working Directory copies of the model files are updated as and when edits are made. The user can go into the Working Directory and manually copy, paste and rename the files into the Project Directory to retrieve his/her model edits.
This error indicates a lack of space of the volume (usually C:) that contains the WaterGEMS Working Directory. Often, this is caused by an accumulation of WaterGEMS abnormal application terminations. This progressively accumulates copies of models in the Working Directory, eventually causing a lack of free space.
Close any open WaterGEMS session, and go into the Working Directory (not the Project Directory). Clean all files out of this directory.
In this case, it is likely that the element is still present in the Drawing, and the user can still do a Find for the element ID/Label, but there is no corresponding record for the element in the model data store. In this case, the model will not be able display data for an element that does not exist in the model data store.
Run the Tools->Database Utilities->Synchronise Drawing menu command to update the drawing to show elements in the model data store.
This is another variation on the WaterGEMS Drawing being out-of-sync with other model files. Usually this occurs with results files. Either:
The corresponding solutions are:
In this case, although the *.out file is present, the *.rpc file is missing.
The safest solution is to close the model, and delete *.out files that have no corresponding *.rpc files, re-open and re-run the model. In addition, this problem is more prevalent when older copies of the model are still present in the Working directory, and the user should delete these copies.