eWater is pleased to announce the latest Production Release of Source version 5.12. Key enhancements in version 5.12 include improvements to Complex Supply Point Distribution Loss, improvements to the Urban Developer PLugin Plugin and a number of minor issues.
| Table of Contents | ||
|---|---|---|
|
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 9 different 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. The eWater development team maintains a detailed system to track when results vary between different versions of Source.
The main project result changes in the regression test suite were due to:
- modifying the order of storage outlet paths, and
- preventing negative storage volume in sub divisionsstorage 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.
...
We found in a rare case that when a weir runs dry, it can cause negative volumes to occur in subdivisions of Storage storage routing links.
The algorithm has been fixed to prevent this from occurring.
...
- 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
...