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:
Calibration using Parallel runs within Source
When using the Shuffled Complex Evolution optimisation, you can now run multiple instances of Source to improve the speed of the calibration:
Environmental Flow Node and Environmental Flow Manager
There has been a number of improvements in Environmental Flows. We have extended the Environmental Flows node's Spell action. Functions are now available for:
- Number of spells in a season,
- Number of spells for success in a season, and
- Spell duration.
The values of these functions can't change every day during a simulation. The values of the functions are taken from before the start of the season. To allow for the forcing of spells during a season, the values need to be taken allowing for travel time before the start of the season.
There is also a new option to allow the fall phase of spells to occur after the end of the season.
Scenario Input Sets and the Export summary now include more information about Environmental Flow Actions. The path for the existing Scenario Inputs Sets will need to change from Rules → Actions. API details are in RM-16591. Terminology in the User Interface for one of the Initial Values at the start of run has been corrected during the process of developing the full API. Time since last successful season has been changed to Time since last successful spell in a successful season.
The Environmental Flow Node and the Environmental Flow Manager now both support the addition of Notes.
Scenario Input Sets in Node / Link feature editors
When working with large models with significant scenario modelling with Scenario Input Sets, it can be hard to recognise that Input Sets may change the run-time configuration. When there are multiple Scenario Input Sets, we have included Scenario Input Sets in each feature editor to show the number of changes to the current node/link across the Scenario Input Sets:
Splitters can now be considered regulated in Rules-based Ordering
The Option Treat Splitter as a Regulated Supply Node in Rules Based Ordering is now available in the controlled splitter node:
This can be used when connecting an unregulated section of a network to a regulated section. Previously, the confluence node would only allow you to consider branches to be regulated if there was a Storage node above it, this has been changed to allow splitters to operate as a regulated structure and receive orders.
Confluences now also handle constraints for Unregulated sections of networks. For orders to be passed up to the splitter, constraints needed to be propagated down confluences. This improvement makes Confluences sum together the forecasts from each of its two branches when they are both unregulated.
River Operations Improvements
The Operations Tabular Editor has new options including Uncheck All for working with the active recorders:
From within View Overrides you can now Clear Historical Overrides:
Operations models now have a summary of Forecast models across the model
Hot start rainfall-runoff models
When running Rainfall-runoff models GR4J or Sacramento, you can take a Snapshot of their internal state variables, they can then be saved to a file and applied at the start of a model run. This removes the need to do a warmup period for running these rainfall-runoff models. The snapshot files now include catchment name and functional unit names as well as an additional metadata file, e.g:
- rsnap
- rsnap.metadata
Safe Release Capacity
The Save Release Capacity setting on Storage Outlet Paths was previously a static value. This has been changed to allow a function to be set. We changed the internal model processing so that the release algorithm checks the input parameter for every calculation:
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:
Summary of minor changes
...
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
- We 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
We have moved to .net 4.8.0 which requires Visual Studio 2019. We are planning on moving to .NET 56. The transition to .NET 56.0 won't be a quick process as some components we currently use will no longer be supported, however it does provide a potential pathway to running natively on Linux. Source can currently be run on Linux under Wine, but only natively on Windows.
...
Some results have changed between Source 5.0 10 and Source 5.4. 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/51643296.12. The 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