Release Notes RiverSMART 1.4

RiverSMART Help : Prior Release Notes : Release Notes RiverSMART 1.4

RiverSMART Now Accesses Names From RiverWare

Note: This change requires RiverWare 7.0. Until that is released, the following change won’t make a difference, but won’t have an adverse effect.

There is a tight connection between studies and RiverWare model files. Study event and file configurations contain the names of entities in the model file, including:

• Dataset names and, for Excel datasets, their workbook and sheet.

• DMI names and:

– For direct connect DMIs, their Excel datasets.

– For control file / executable DMIs, their executable.

– For trace directory DMIs, their top-level directory and control file.

• MRM configuration names; their descriptors (keyword / value pairs); and their RDF, NetCDF and CSV output files.

Previously, users had to know the names of the entities and enter them in the event and file configuration dialogs. Now, RiverSMART can look into the RiverWare model file to get the names of the entities. For example, the DMI event configuration dialog has a combo box where users can select a DMI in the model file, rather than a text field where users would enter a DMI name.

Status Bar

A new Status Bar was added to the RiverSMART workspace. This contains:

• The study status (blue background), for example “Executing event RiverWare”.

• The event status (green background), for example “Simulating scenario dry,demand2,IG”.

• The event progress bar.

• The diagnostic window button.

Non Distributed Runs

Originally RiverSMART required distributed multiple runs; it now supports non-distributed multiple runs.

Note: A non-distributed multiple run in the model file is made into a distributed multiple run using the default number of cores for the computer.

Bug Fixes

Table 1.11 Issues addressed
Number	Summary
	A lag could occur when RiverSMART was run over a remote desktop.
	The diagnostics window was always on top of the workspace and had to be moved aside to prevent it from obscuring the workspace. The diagnostics window can now be below the workspace.
	Loading a study which uses a missing plugin crashed.
	Reordering columns in the scenario dialogs sometimes caused the folder buttons (to launch Windows Explorer in the scenario’s directory) to be displayed in strange locations (for example, in the middle of other columns).
	Closing the file configuration dialog by clicking the “X” didn’t accept the changes.
	Marking a scenario as (not) post-processed crashed.
	Setting and saving of placeholder events caused a crash.
	“Escaping” from an event configuration dialog sometimes left the event in an inconsistent state. Escape now cancels changes. Clicking the “X” accepts the changes.

Revised: 07/03/2024