The changes in this beta will be available in the next Source production release due out at the end of December 2022.
This release includes:
- Updates to the Storage Ownership logic.
- Modifications to the Operations Tabular Editor.
- Bug fixes for the Environmental Flow node.
Updates to Storage Ownership logic
In Source 5.14 Beta and Source 5.16 changes were made to allow "Internal spilling to be specified by Owner". This added a new option to 'Ownership' in storage and weir nodes allowing an owner to 'Use Airspace'. Following testing and feedback from those releases, further changes have been made in this release to address a number of identified issues. These changes include:
- A new proportional loss calculation method has been introduced.
- The 'Use airspace' option can be used when internal spilling is disabled.
- The 'Use Airspace' owner can receive water internally spilled from other owners, if it is below its specified capacity share (not allowing this could cause incorrect spill calculations).
- Fixes for negative and close to zero ownership values in storage ownership.
- Improved test coverage of storage ownership.
The new proportional loss calculation method has been separated out into an independent implementation from the original storage ownership methodology to allow for comparison of results between the old and new versions. It is expected that the new method will be adopted as part of the next production release, in December 2022, at which point the dual implementation will be removed.
Details of the changes are outlined in Changes to Ownership in Storages.
...
Recorder Set Filtering Option
A new option has been added to command line execution of Source that allows the output data to be limited to specific recorder sets.
--rs | Which recorder set to return. This can be specified multiple times. | --rs "recordersetname" |
This can be useful when a Source Project run (e.g. in Operations mode) has a number of standard recorders preconfigured, but specialised runs are required to limit the output data to specific recorder sets.
Operations Mode Enhancements
Several changes have been made to provide additional options when working in River Operations Mode.
These changes include:
Data Sources can now be overridden in the Tabular Editor.
- Values overridden in the Data Sources in the Tabular Editor will apply wherever the Data Source is used.
- For example, updates to model inputs such as rainfall/PET will be applied to all nodes where they are relevant. Similarly for Time Series Variables within the Function system.
Operations support for Minimum Flow Requirement nodes
- The Required Flow (previously Required Water) on Minimum Flow Requirement nodes can be overridden.
- More of the recordable values in Minimum Flow Requirement nodes can be viewed in the Operations Tabular Editor
- Operations Forecast Scenarios can be defined
Also, the 'Recorder Set Filtering Option' may be of use when running Operations in Command Line mode in order to filter out the data recorded for the Tabular Editor.
Enhancements &. Bug Fixes
Some other smaller enhancements and bug fixes are:
- Additional parameters available in Scenario Input Sets to support Storage Operating Constraints settings
- Additional checks when loading .RES.CSV files to identify non-contiguous data
- A new option for setting how Ownership is shared when Unaccounted Difference is used in Storages and Weirs
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.
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Details here: /wiki/spaces/SC/pages/51651480
Full Release Documentation
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|