HEC-ResSim Version 4.1.2 is a patch release to address a few critical issues found during HEC-RTS testing. See the HEC-ResSim Version 4.1 Release Notes, Known Issues, and Updated Content for all other information on this version. Note that release noted for 4.1.2 includes two issues fixed for 4.1.1 (RSS-1505 and RSS-1506).
Changes in ResSim 4.1.1 and 4.1.2
Type
Release Title
Release Notes
Resolution
Ref
Bug Fix
Creating new RTS forecast failed with global variables, action buttons would not load.
Fixes bug where creating a new RTS forecast with a model that uses Global Variables creates a corrupted copy of the model. As a result, action buttons were not loading correctly and the model would not compute.
Done
RSS-1521
Bug Fix
Saving Network Files to Correct Location when Creating a New 4.x Watershed
This bug fix addressed an issue that occurred during the initial creation of a new watershed in 4.0 or 4.1. The network files were initially being saved to the old location and the /networks/ folder was not being created until later in the process. Now new networks are saved in the rss/network/<network name> folder from the initial creation.
Done
RSS-1517
Small Tasks & Subtasks
Allow Reservoir to have no Guide Curve
In ResSim versions prior to 4.0, it was possible to have no Guide Curve set, but in 4.1, a check was added to ensure a Guide Curve had been set at all reservoirs. For the 4.1.1 release it was identified that this check was unnecessary and it was turned back off.
Done
RSS-1506
Small Tasks & Subtasks
Remove Check for Coincident Zones
An improvement made for ResSim 4.0 was to run a datacheck to ensure that no two zones had the same starting elevation. If two zones were found to be coincident on 01Jan, ResSim 4.0 would show an error and force the user to adjust the zone elev/storage before computing. While zones SHOULD NOT be coincident, it is planned for ResSim to use the Zone Sort Elevation to determine zone order for a 01Jan conflict. We learned from CWMS testers that many of their watersheds had cases where the coincident zone law was being violated due to special modeling techniques, but this was causing no compute issue. Rather than force users to update their watersheds, we removed the datacheck and will improve the Zone Sort Elevation for the next release.