-----------------------------------------------------
            SUMMARY OF CHANGES IN RIVERWARE PATCH RELEASE 7.3.1
           -----------------------------------------------------
                        Released September 20, 2018
           -----------------------------------------------------

Reach Well Mixed Salinity
----------------------
The Reach Well Mixed Salt methods were modified as follows:
- An incorrect error condition was stopping the run. This error check was 
  refined.
- When Salt Storage is in use, the reach salinity dispatch methods were 
  not redispatching with the correct previous timestep information. Now 
  the reach will redispatch when previous Salt Storage values change. Note, 
  this fix could change model results for reaches where Salt Storage is in 
  use and flows are small.

Units
----------------------
The following new units were added:
  FlowSquared: kcfs2
  VolumeSquared: kcfs-hr2

Bugs
----------------------
The following bugs were addressed:
6103: When plotting many slots and an error occurs, the error dialog could 
      be shown many times.
6115: Within a Script, the enabled state of actions were not applied 
      correctly with multiple calls to a subscript.
6130: For certain RPL Predefined function diagnostics, the incorrect 
      context could be used.
6134: Multiple Object Viewers could occur at the same time.
6136: An error dialog could be incorrectly shown when generating a chart.
6137: Setting a plot x-axis to constant datetime did not work correctly.
6158: In the CSV Output from Multiple Run Management (MRM), the timestep 
      size field was exported incorrectly.
6159: Within MRM, the RDF to Excel conversion did not work if the output 
      file did not exist.
6162: A crash could occur opening a Mass Balance Summary slot.
6163: Deleting a Balance within a Mass Balance Summary slot could cause a 
      crash.
6164: Within the RiverWare Policy Language, a comment on a CONCAT operator 
      could move to the next expression on save and reload.
6165: RPL editors permitted replacing a comment with an expression.
6172: NetCDF output doesn't support timesteps less than 1 day. Now an 
      error is posted for an MRM configuration with NetCDF output when the 
      run timestep is less than 1 day.


                              --- [end] ---