DSM2 New Version
October 25, 2005
The new version of DSM2 has these changes from the text version:
· Fixed data now reads from a relational database, not from text files. This allows for better control of data and a greater likelihood that different studies using the same Delta design elements (e.g. permanent gates or a Through-Delta facility) will use identical parameters. It also allows for an easier implementation of a GUI, addition of metadata to studies, and standardization in general.
· Graphical User Interface. The GUI enables far easier review of changes from an initial study (i.e.. base case) to a plan study. It is not intended to run the model or examine time-varying data, but to allow examination and manipulation of the fixed data in the database (adding new data and editing and deleting existing data).
· HDF5 for the tidefile. HDF5 is used instead of a simple Fortran unformatted tidefile to store hydrodynamic information needed by Qual and PTM. HDF5 is a standard storage format used in high-performance computing, has a public domain viewer and editor, and results in smaller file sizes. It will allow us to include more fixed data and metadata in the tidefile.
· Increased Gate Capabilities. Gates now are collections of devices. The devices contain the physical dimensions and parameters of what we now call gates, so a single gate may contain several independent devices. Furthermore, gates can now be operated by several criteria or triggers during a model run. Reservoirs can now have true gates attached to them, as well as the previous simple reservoir connection. The nonlinear numerical solver for both gate and reservoir connections has been improved, and messages about reaching maximum iterations (for example, “Note: at 20MAY1975 0100 network iterations at maximum ( 20).”) are now meaningful and much less common. As a result, Hydro runs about 20% faster.
· Little Language for Operating Rules. A simple interpretive language has been developed which allows users to specify actions to take place on triggers. An action can be a change of gate state (open/close), or pumping or inflow change. A trigger is a value of stage, flow or time that reaches a specified value. This allows the model to make decisions during a run in response to environmental values.
Status of tasks needed before the new version of DSM2 is ready for production use.
· Validation using historic run. This repeats the historic-data run and compares the new gate devices and reservoir connections using gates at Clifton Court to the text version of DSM2. No operating rules used except at the Suisun Marsh Salinity Control Structure on Montezuma Slough (all device operations are from observed data). No improvement is sought over previous calibration.
· Status: Work finished by Tawnly Pranger in September. Only minor differences noted in stage, flow, and salinity between versions of DSM2 which is attributed to different numerical convergence criteria and treatment of gates. No adjustment of channel friction coefficients or gate parameters needed.
· Finish DSM2/DB/GUI work.
· Finish bug fixes.
· Adopt PTM to use DB.
· Change GUI to handle non-conservative constituent input.
· Initial conditions: Verify restart file preserves trigger and action state.
· Some work on GUI Help system. A basic Help should be ready when new DSM2 is released for production.
· Other operating rule enhancements. Extensions to current rules will be driven by user needs as they are discovered.
· Status: Flow transfers (object-to-object) are repaired in new version (they are unreliable in the text version) and are controllable using either DSS input or operating rules. Source tracking (multiple conservative constituents) works by specifying groups. Output may now be written directly to DSS files instead of using scratch files during the run, which allows output to be examined during a run. DWR is using Condor (a distributed high-throughput computing system) to speed runs. Multiple, unlikely reservoir flow coefficients through Clifton Court gates discovered in text version and should be corrected.
· Finish development of planning runs, one for temporary barriers, another for permanent gates. Explore operating rules for planning runs. Need to acquire experience and rules-of-thumb in how the feature can be used.
· Status: This testing has just begun with the Clifton Court and South Delta permanent gates.
· Implement Informix replication to MS Access database using BDAT datasharing method so non-DWR users can copy the latest DWR data and share their updates.