7/3/2014

The input events to RiverWare now track configuration changes, and the title text for the event will turn red if its configuration has been changed. These events include RiverWare Model, RiverWare DMI, RiverWare Policy and RiverWare MRM. The scenarios that the change in configuration will affect are also shown in red in the Simulate Scenarios and Post-Process Scenarios dialogs. These changes give a visual cue as to what is out of date when input configuration changes are made. When scenarios that are out of date are regenerated, the red highlighting is removed. The user may make changes external to RiverSMART that can make input events out of date, such as changing data files are imported via a RiverWare DMI event. The user can manually indicate this for an event by going to the Edit menu in its configuration dialog and selecting Externally Modified. This causes the same out of date highlighting as a change in configuration does as described above.

The input events to RiverWare also have an option in the Edit menu of the configuration dialog to indicate the event is a placeholder. This means that “None” will be used as an alternative for that type of event when generating scenarios. For example, in the case of DMI events with a Category of Demand, a placeholder event would mean that the demands present in the model would be used and no demand data would be imported for scenarios generated with this placeholder. Indicating an event is a placeholder will disable widgets in the configuration dialog that are not needed (generally all but the name field and, for DMI events, the Category field).

When scenarios are regenerated, a confirmation dialog now will appear indicating which scenarios will be added, deleted, unaffected, or become out of date. The user can then proceed with the regeneration or not. Before, regenerating scenarios removed the state information for the simulation and post-processing of all scenarios; now this is preserved for scenarios that are unaffected by the regeneration.

The processing of the hydrology plugins and the post-processing of scenarios have been moved into separate threads within the software, meaning that the user interface will no longer become inactive during this processing. Particularly for the hydrology plugins, the user interface could become locked for long periods while processing was completed.

An R Plugin event was added to RiverSMART that can be executed as a post-processing event in a study. In its configuration dialog, the user specifies a function within an R script file and specifies the arguments to be passed to the function. This allows the user to accomplish post-processing of data from the study with functions they have written in R. See the help file for the R Plugin for detailed information on this new functionality.