CADSWES Maintenance Accomplishment Report Compilation -- February 2014 (edit 3-14-2014).

This compilation includes the (3) individual maintenance accomplishments reports from: Jessica, David, and Phil.
Mitch, Bill, Neil, Patrick and Tim indicated that they have no February maintenance accomplishments to report.

(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

The following releases were generated this month:

RiverWare 6.4.6 was released on February 25, 2014:

The following bugs were fixed:

Water User Method:

On the Water User, a new method was added to the Diversion and Depletion Request category called Specify Scheduled Requests. This method allows you to specify an initial scheduled amount (as either a series or periodic relationship) and then reduce the schedule to the requests. For more information, see section 25.1.1.10 of the Objects section of the help.

Units -- the following units were added:

Length:
- survey_ft (US Survey Foot)

Volume:
- survey_acreft (US Survey Acre-foot)
- MCM (Million Cubic Meters)
- TCM (Thousand Cubic Meters)
  
Flow:
- survey_acreft/day, survey_acreft/month, survey_acreft/year
- MCM/day, MCM/month, MCM/year,
- TCM/day, TCM/month, TCM/year

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

The following old bugs were analyzed and closed without changes:

The following bugs were fixed:

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

None in February 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. In February, the tests were restarted when they failed to work after a power outage.

(II.E) Download, Install and Release Processes

(II.F) Updates to license software/procedures

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

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

--- (end) ---