The changes in this beta will be available in the next Source production release, due out at the end of December 2020.
Improvements in this release include:
- A significant increase in the amount of data that can be presented in Order Crawler (new functionality released in Source 5.0 for analysing complex interactions between ordering and delivering, especially over long travel times).
- Application setting for Source data directories, such as temp data directories.
- Extension of constituent marker routing with Weirs and Storage Routing to allow it to handle non-conservative constituents.
- Range of minor improvements.
Improvements have also been made to the new Urban Developer plugin, including:
- Custom end-uses can now be defined with a Function or Data Source.
- The parameteriser can now work on all existing end-use models.
- Graphs are now shown for end-use models.
Order Crawler Recorder
The order crawler recorder is a new recorder to show all the nodes and links in a network. Available under: Miscellaneous \ Ordering \ Order Crawler. The Order Crawler is a fully interactive, zoomable schematic that shows the entire network with node locations in the same location as the network. There is a slider-bar to choose the day you are interested in. The data available in Order Crawler includes:
- Min Constraints (All, Min Travel time, Max Travel Time, Min & Max)
- Max Constraints (All, Min Travel time, Max Travel Time, Min & Max)
- Orders \ Requirements (All, Min Travel time, Max Travel Time, Min & Max)
- Downstream Flow
- Travel Time (Min and Max)
Note: for large networks, it does record a lot of data and is primarily for problem-solving and not intended to always be turned on.
Application setting for Source data directories
You can now specify the path that Source will use for storing temporary data and applications settings. Available under Edit \ Application Settings...
Constituent marker routing with Weirs and Storage Routing
Marker routing can now use constituent processing models at Weirs and in Storage Routing links.
- Feature table (and other tables) now includes units when exported,
- Environmental Flow Nodes have a new recorder for consecutive successful time steps.
- Functions or modelled variables that are used and don't have a Time of Evaluation (ToE) set will trigger a new assurance rule with an error by default.
- The maximum node limit of 1,000 nodes has been removed.
- Other minor bug fixes.
Urban Developer Changes
Custom end-uses can now be defined under Edit \ Urban Developer Options. Right click Custom End Uses to add your own.
When linking a Source scenario to Urban Developer Scenarios, you can now use the Urban Water User Parameteriser for all existing end use types.
Appliance configurations now have graphs to provide more insight into water use
We have moved to .NET 4.8 and are looking at moving to the new .csproj format on our journey to .net core. Once we complete this, we will require plugin developers to upgrade to Visual Studio 2019.
We have removed the tolerance in our regression tests to help find issues earlier if we get different results on different machines or versions of operating systems.
Regression test repository changes since the first Source 5.0: 01 Project results updated with changes to plugins 02 Projects edited to be a warning
01 Project results updated with changes to plugins
02 Projects edited to be a warning
Details here: 5.1 Regression Test Changes
To run Insight, you also need to install the 32bit version of Microsoft Visual C++ 2010 Redistributable Package.
This installer is for both 32bit machines and 64bit machines since the library we use is 32bit: Microsoft Visual C++ 2010 Redistributable Package (x86).
Full Release Documentation