5.32 Beta Release (March 2024)

The changes in this beta will also be available in the next Source production release due out at in May 2024.

This release includes:

  • Debugger - a tool to diagnose and evaluate a run.

  • Trade Manager recorders to understand the water trade in a model.

  • Farm Dams enhancements to include Minimum storage & voluntary release to the onstream farm dam node.

  • Other enhancements and bug Fixes

 

Debugger

Debugger is a diagnostic tool that allows pausing during a run and displaying current model values (using something similar to modeled variables to do so). It has been developed to help modelers understand the internals of the Environmental Flow node / manager and Resource Assessment. But it can be used for all aspects of Source and will provide a really useful for modelers to debug and understand what is happening with their scenarios and projects.

We can find the user guide for the Debugger tool here Debugger User Guide.

 

To allow initial evaluation of the debugger concept inspection abilities, the UI is provided to select individual properties on models for display.

It allows a basic selection of aspects of models as follows:

and show the values of the properties as the appropriate breakpoints.

 

Farm Dams Enhancements

 

  1. Minimum storage field: A threshold below which water will not be extracted to satisfy demand.  

    UI - Added a field in the “Dam Information” screen of “Onstream Farm Dam” node to specify a dead storage or minimum storage with values – Constant/Timeseries Input File/Function 

  2. Voluntary Release field: Added new functionality to release water even when the dam is not at capacity. This is needed to model different forms of release from farm dams. 

UI - Added a field in the “Dam Information” screen of “Onstream Farm Dam” node to specify a “Release” field with values – Constant/Timeseries Input File/Function 

  1. Added additional input formats to the existing Bypass flow node to allow Monthly pattern, Data Source and Function along with the constant input value.

 

Trade Manager Enhancements

Building on our work for Beta 5.31, we have continued to refine the new Trade Manager functionality, including new Recorders specifically for the Trade Manager and updates to the Resource Assessment Recorders to include the trade logic.

  1. Specialist Trade Manager Recorders have been added to provide insight on the model performance with respect to the trade logic and to support reporting.

 

UI looks like the below screenshot:

 

  1. Resource Assessment is modified to accommodate trade logic.

    1. 'Account Adjustment’ recorder in RA does not include trade by default.

    2. ‘Net trade' recorder is now added to 'RA-> Account Host’.

 

Enhancements &. Bug Fixes:

Minor enhancements and Bug fixes include:

  • Timeseries Aggregation Doesn't Work.

  • Change Screen width to be wider to accommodate working on large complex projects. Now we can see all the columns

  • Correct the "License expiry date" message on splash screen.

  • Min and Max button are not visible in the Run configuration window.

  • Issue with run name for Linked Scenarios. No duplicate names are displayed now.

  • Editing certain values for Storage Node in Feature Table causes Source to crash. User is able to edit parameters for storage node in the Feature Table.

  • The overridden value in the gauge release does not persist when changed in operations mode.

  • Issue exporting functions from set of active recorders in Tabular editor.

  • Projects created before v4.2.9 (October 2017) cannot be opened in v5.14 or later. Fixed on Version: Source 5.32.0.13017

  • Deleting last run from Dora tree also deletes the Latest Run.

  • The Source project crashes when attempting to import a scenario into an project file.

  • Issue in importing function recorder in Tabular Editor recorders.

  • Off Allocation recorder appears to be off by a factor of 4.

  • Ops project disables Gauged Release after run.

  • Gauged Release Value in the UI is being overridden by the Owner Releases value after the run.

  • Create an Assurance Rule to warn users if they have renamed a csv column when loading by position. Fixed but Note that the solution for a renamed CSV column when loading by position is only for reloading on the run, and there is no method to provide a warning when manually reloading the file.

  • The no account host does not work in the transfer trigger.

  • Investigate execution order of functions on same element and Time of Evaluation.

  • Duplicate run names when using saved run.

 

Regression Testing

There is no tolerance in our regression test suite to allow for earlier identification of results being different on different machines or versions of operating systems. 

See: 5.32 Regression Test Changes

 

Full Release Documentation