Page Comparison

...

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...

Image Removed

Constituent marker routing with Weirs and Storage Routing

Marker routing can now use constituent processing models at Weirs and in Storage Routing links.

Minor improvements

• 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

Custom end-uses can now be defined under Edit \ Urban Developer Options.  Right click Custom End Uses to add your own.

Image Removed

Urban parameteriser

When linking a Source scenario to Urban Developer Scenarios, you can now use the Urban Water User Parameteriser for all existing end use types.

Image Removed

Appliance configuration 

Appliance configurations now have graphs to provide more insight into water use

Showers:

Image Removed

Washing Machines:

...

• how weirs process constituents,
• the Sub Source plugin,
• expanded Order recorders, 
• performance improvements for constituent marker routing, and 
• the Source Data Base (.sdb) can now be used when auto exporting run results.

Weirs and Constituents

The previous logic for running Constituent Instream Processing for Weirs was based on the logic for Storages.

• The Instream Processing model was given the entire body of water associated with the feature.
• The processing model would run once per time step for each constituent.

This was different from how these models behave for Storage Routing Links. Which is:

• given access only to a single division, and
• run once for each division and constituent in a Link.

The previous logic wouldn't work when the model included hard limits e.g. in this model, the average concentration is not meant to exceed 9mg/L. When the Model runs for the entire Weir, we can see this is true on average:
Image Added

But when we look per division, we can see that some divisions drop to 0 while others can reach double the cap 18.
Image Added

Changing the logic for weirs to be consistent with storage routing resolves this issue since the cap is applied in each division rather than across the entire link.

Constituent Instream Processing for Weirs is restricted to Marker routing, i.e. it is not implemented for Lumped routing.  (If Lumped routing is being used storages would make a more sensible model for the infrastructure than weirs.)

Sub Source plugin improvements

Previously mappings between main and sub-models were tied to a single run configuration. If you make a new run configuration then the mapping has to be redone.  Sub Source mappings have now been moved into a manager so that the same mapping can be used by multiple run configurations. Available under  Tools » Sub-model Manning Manager. 

We have also improved how Sub Source works with single projects. For single projects, the plugin will now:

• get meta data from the loaded project rather than starting the service when doing configuration, and 
• Run the current project without needing to manually save before the run

Documentation is available here: /wiki/spaces/SD50/pages/50136239

Order recorders

Additional recorders were requested to better understand the water that has been ordered when using functions.

We have added recorders with the following names under rules-based-ordering:

Orders > Arriving Current Timestep (expected)

Orders > Minimum Travel Time

Orders > Maximum Travel Time

Note Arriving Current Timestep (expected) is equivalent to the original Orders recorder.

Plugin Developers

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.

Regression Testing

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. 

...

Details here: 5.2 Regression Test Changes

Insight

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