CADSWES Maintenance Accomplishments -- June 2013 (edit 7-12-2013)

RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Releases and Patches

RiverWare 6.3.1 was released on June 13, 2013.  The release included the following release notes:

SUMMARY OF CHANGES IN RIVERWARE PATCH RELEASE 6.3.1

The following bugs were fixed:
    5324: In the unit scheme manager, a typed unit scale was not correctly taking effect.
    5327: The user could not create a slot named "Evaporation Coefficients" on a data object.
    5328: Under certain situations, the user could not add a rule to a policy group.
    5329: On the open object dialog for an Aggregate Object, the operation to "Insert Element Before" was not working correctly.
    5330: On the slot dialogs, the operation to "Set All to Outputs" was not working correctly.
    5332: RiverWare crashed during exit.
    5335: On the new Series Slot with Periodic Input, the unit type wasn't being preserved when saved in periodic mode.
    5336: The Reach's Available Flow Based Diversion method was modified to recognize when "Available For Diversion" is input or set by a rule on either the slot itself or on the linked slot.

ATTENTION GPAT USERS!
A new version of the Graphical Policy Analysis Tool (GPAT 3.1.1) is now posted on the RiverWare download page. A "Save/Load" tab has been added to the interface that allows graph configurations to be named and saved to a list. This list can be written to a file, which can be reloaded in a subsequent GPAT session. Configurations from the list can then be selected and loaded into the GUI to generate new graphs. In this way commonly used graphs do not have to be reconfigured with each GPAT session, but can be preserved and reloaded via files.

RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Regression Tests

The regression tests continue to be maintained on a daily basis. This involves updating the regression tests to exercise new developments in the code. Also, as new code is added to the development area, the model comparisons performed in the nightly regression tests usually show differences (for example, because a new method category may have been added). When this occurs, the regression tests need to be updated to reflect the current state of the development area so model comparisons do not fail. In addition, every week, the daily history of each regression test is analyzed to determine if the run time or model size has significantly changed because of new development. In June, the regression test procedures were updated so that all combinations of builds/prerel, debug/release and 32/64bit are running successfully overnight.

One of the overnight regression tests began to fail for unknown reasons. CADSWES staff diagnosed the problem (a consequence of code changes to fix bug 5335) and updated the regression tests appropriately.

RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Development Snapshots

RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Download, Installation and Release Process

  1. Updated the version number to 6.4 in the development builds area and in all the regression test files.
  2. Updating the release generation document with all the new and changed procedure due to switching from CVS to git.
  3. Flexera InstallShield:

RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Licensing

  1. Ongoing: Issuing Commercial Licenses.
  2. Ongoing: Maintaining licenses for internal development environment.
     
  3. Issued new CPLEX license for all internal machines and training machines.
     
  4. Reprise RLM:

RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Development Environment

Build Document

Work was completed on the document to summarize the building of libraries and executables associated with RiverWare. These libraries and executables had to be rebuilt with the upgrade from Visual Studio 2008 to Visual Studio 2010, so the procedures were recorded for future reference.  Also descriptions were added for stand-alone executables outside of RiverWare, including the Graphical Policy Analysis Tool, the Demand Input Tool, the RDF Annualizer and the RDF To Excel tool.

Visual Studio 2010

Warning messages about "First chance exceptions" during RiverWare execution in Visual Studio 2010 were investigated. These messages are not indicating a problem with the code, but are given by Visual Studio any time an exception is thrown. If the exception is not caught by the code, it is elevated to a second chance exceptions, which indicates a problem, and the debugger will break on this.  Research into Visual Studio found that these messages can be optionally turned off, as can some other categories of messages related to modules, threads, and processes, to greatly reduce clutter in the debugger output window. This information regarding Visual Studio settings was distributed to the RiverWare development team.

RIVERWARE
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Software Maintenance - Qt4 Port

Qt3-to-Qt4 port of the SCT

Porting of the SCT's series data tables was provisionally completed in May 2013 for RiverWare 6.4. Optional incell display of series timestep flag letters and rule priority numbers had been overlooked. These SCT features were completed in June.

Qt3-to-Qt4 Port Completion

With the exception of the DbDmi and Client/Server libraries (which are underway in July), all RiverWare modules have been ported from Qt3 to Qt4.

Exclusion of use of the Qt3 compatibility library was effected at the C++ module level (i.e. individual C++ files). Disabling the compatibility library at the RiverWare library level will be done after the DbDmi and Client/Server library ports have been completed to the point of removal of all Qt3 widgets. This will probably be completed in July.

[Note: Bill will probably be reporting Qt4 porting work this month (June), in DbDmi and the Client/Server library].

STUDY MANAGER
RELEASES, SOFTWARE MAINTENANCE and DEVELOPMENT ENVIRONMENT
Software Maintenance

Study Manager Help Files

To provide easier access for non-developers, the Study Manager help files were removed from the Study Manager git repository, and were put in a documentation directory under the Study Manager project area. For revision control of the files, they were placed under RCS, which is how the RiverWare help files are maintained. This change means that non-developers will not need to clone a copy of the git repository to get access to the latest version of the Study Manager help.

--- (end) ---