You are currently reviewing an older revision of this page.
Below are some modeling methods and information for WaterGems beyond what is provided in the product documentation.
The model datastore. 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.
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:
The Working Directory *.wtg.mdb and *.wtg