CADSWES Maintenance Accomplishment Report Compilation -- November 2014
Edit: 12-09-2014 (Phil)

Report contributors:

(II) RiverWare Software Maintenance

  1. Releases, Patches and Snapshots
  2. Software Updates, Bug fixes (not associated with new development)
  3. Development tool improvements; issue tracking software; modelcomp
  4. Enhancements or changes to regression tests (not part of development tasks)
  5. Download, Install and Release Processes
  6. Updates to license software/procedures
  7. Updates to download/install/configure user documentation
  8. Modification to Web pages for downloads and installs

(II.A) Releases, Patches and Snapshots

RiverWare 6.5.3 release notes:

Bugs
The following bugs were fixed:

  • 5545: On the SCT, slots on objects with dispatching disabled were not showing the crosshatch correctly.
  • 5546: Empty table slots with defined row labels were incorrectly being reduced to one row.
  • 5551: Stopping a script that executed a run was causing a crash.
  • 5552: The Distribution Canal was incorrectly computing negative Available Flow values.
  • 5555: Series Slots with Periodic Inputs were not correctly computing the series values at the start of a run.
  • 5559: The Script Dashboard was not using a specified datetime for the Set Scalar Slot Values action.

Inline Power Plant - Flow Tables Method
As part of a fix to bug 5553 (Incorrect error when the Power Plant Cap Fraction was less than 1.0), the calculation for the Flow Tables method was modified. Now the Power Plant Cap Fraction is applied to both the Turbine Release and the computed Power when the flow is above Max Turbine Release times the Power Plant Cap Fraction. It is not applied when the flow is less than Max Turbine Release times the Power Plant Cap Fraction. This change affects only Inline Power Plants using the Flow Tables method. Contact RiverWare support if you are using this method and/or have questions.

(II.B) Software Updates, Bug fixes (not associated with new development)

(II.C) Development tool improvements; issue tracking software; modelcomp

None reported in November 2014

(II.D) Enhancements or changes to regression tests (not part of development tasks)

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.

(II.E) Download, Install and Release Processes

(II.F) Updates to license software/procedures

(II.G) Updates to download/install/configure user documentation

None reported in November 2014

(II.H) Modification to Web pages for downloads and installs

None reported in November 2014

---