eWater is pleased to announce the latest Production Release of Source version 5.1012. Key enhancements in version 5.10 12 include improvements to the Operations Tabular Editor, the ability to Hot Start GR4J and Sacramento rainfall-runoff models, significant enhancements to the Calibration Tool, updates to the Environmental Flow Node and Manager and additions to Scenario Input Sets to make it easier to work with large models with significant scenario modellingComplex Supply Point Distribution Loss, improvements to the Urban Developer Plugin and a number of minor issues.
You can now model 9 different
| Table of Contents | ||
|---|---|---|
|
Improvements to Source
Calibration Improvements
The calibration tool has been significantly extended, you can now:
- calibrate Schematic Scenarios,
- calibrate any parameters in the model that are available through Scenario Input Sets, and
- specify relationships between meta-parameters.
This is a significant step forward for the calibration tool, it's currently called Flow Calibration Tool, however, this should be updated soon.
The Calibration tool and Bivariate stats now support multiple parameters for Objective Functions. The Square-root Daily, Exceedance, and Bias function now has three parameters, Alpha (α), Lamda (λ) and Mu (μ). Details of the implementation are here: Bivariate Statistics SRG
These can now be set in both the Calibration tool and when looking at the Bivariate stats in the Results Manager:
Ability to model individual components of distribution loss
|
Supply Point Distribution Loss in Source
The editor has been simplified and the logic as well. There are now also more recorders for each individual loss. It now makes it clear that the proportion is of Supplied demand, rather than Ordered demand.
You can now model 10 individual components of Distribution Loss at a Supply Point. This is on a new, an optional, separate tab Complex Distribution Loss:
Urban Developer
We have improved the User interface performance when editing models in Urban Developer and we have enabled Urban Developer to run as a sub-model by Source through the command line.
We will provide more information and a webinar on using Source with Urban Developer next year.
Summary of minor changes
- Other minor bug fixesWe have extended Scenario Input Sets - now available from the Node or Link feature editor. Associated Scenario Input Sets are visible in the feature editor when there is at least a single Scenario Input Set, that isn't empty.
- Fixed an issue with Scenario Data Sources that failed to reload
- Fixed an issue with running Insight that occurred in a minor release of Source 5.10
- Improved the naming within Data Sources Overview to be consistent
- Extended the DoDoc plugin so it can be accessed through Scenario Input Sets and in the Export Summary.
- Fixed an issue with some tables, such as the Rainfall Runoff editor, where the export would no longer import.
Community Plugin Changes
...
Some results have changed between Source 5.10 and Source 5.12. Changes include how marker constituent processing works in Weirs and how the confluences process unregulates sections of a network. Details are available here: /wiki/spaces/SC/pages/51643296The eWater development team maintains a detailed system to track when results vary between different versions of Source.
The main result changes in the regression test suite were due to:
- modifying the order of storage outlet paths, and
- preventing negative storage volume in storage routing link subdivisions.
Ordering Storage Outlet Paths
We found in a particular configuration of a complex model, the order in which Outlet paths were processed in a Storage could change the results. We now enforce consistent Outlet path processing to remove this inconsistency.
This has resulted in minor result differences in a number of models in our regression test suite.
Preventing negative storage volume in sub divisions
We found in a rare case that when a weir runs dry, it can cause negative volumes to occur in subdivisions of storage routing links.
The algorithm has been fixed to prevent this from occurring.
To test your project:
- Create a regression test in Source 5.10, see 5.10 Regression testing
- Run it in Source 5.12 to test for any result changes, see 5.12 Regression testing
If you would like help with your projects or would like to have your projects included for testing, please contact support: support.ewater.org.au