The following changes were made in RiverSMART 8.3

RiverSMART enables you to place text boxes on the workspace. Previously, if you edited text in a text box, pressing the Delete key deleted the entire text box, not the selected text. RiverSMART was enhanced so the Delete key behaves as expected, deleting the selected text, or the next character if no text is selected.

Distributed multiple runs can be configured to terminate the multiple runs after a specified number of traces have failed. Previously, if RiverSMART started a distributed multiple run and a failure occurred, you were not notified which traces failed and, consequently, had to search multiple log files to identify the failed traces. RiverSMART has been enhanced to notify of the specific traces that have failed, so you can go directly to the appropriate log files to identify the source of the failures.

RiverSMART now supports per-trace Excel output DMIs during distributed multiple runs. The following changes were made to support these DMIs:

When re-generating scenarios, the wording for scenarios that will have their results invalidated changed from:

“Check scenarios to re-simulate their results”

to:

“Check boxes to clear the simulation status of scenarios”

In previous versions, RiverWare MRM was enhanced to allow you to configure how many traces could fail before a run was terminated. When traces fail, the RiverWare and distributed MRM controller user interfaces provide an indication to the user. In RiverSMART, however, the distributed MRM controller user interface would close after a scenario simulated with no indication that traces had failed.

To remedy this, the RiverSMART scenario status “Succeeded With Warnings” was added; the scenario status icon associated with this status displays an orange hue, rather than green. Users can expand a scenario’s tree view item to identify the traces that failed.

Beginning with release 8.0, RiverSMART and RiverWare release version numbers are synchronized, and RiverSMART requires the same version of RiverWare. For example, RiverSMART 8.2 requires RiverWare 8.2; the patch levels may differ.

To support this requirement, the RiverWare batch mode command “RiverSMARTVersion <major>.<minor>” was added to RiverSMART. RiverSMART adds the command to the batch script that configures the RiverWare model file for a scenario; if the RiverWare version does not match, the command fails with a meaningful error message. This eliminates the possibility of errors caused by version mismatches, which can be difficult for a user to understand.