Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Repair Jira Macros

The changes in this beta will be available in the next Source production release, due out at the end of June 2021.

This release includes:

  • Improvements

...

  • a number of minor improvements.

Calibration using Parallel runs within Source

Minor changes

  • Auto export results now use the dimension Display Units,
  • The Simulation log file has more content for Data Sources,
  • New recorder on confluences:  Constrained Historical Order For Long Branch
  • New Scenario creator Single Catchment Scenario Builder:

Image Removed

  • to Unregulated system ordering,
  • Crashes with Remote Desktop and SciChart resolved for Results Manager,
  • Scenario Input Sets affecting Nodes and Links are now visible within Node / Link feature editors,
  • Constraint Factors are now available in the Order Crawler, and
  • Improved validation of Node / Link names.

Unregulated system improvements

Confluences now handle constraints for Unregulated sections of networks. We introduced changes to allow splitters to be considered regulated in 5.6 - Beta Release (February 2021). 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.

Crashes with Remote Desktop and SciChart Resolved

When using Source through a remote desktop session, it could hard crash the application when viewing charts.  Improvements we made in this release have resolved this

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

Image Added

Constraint Factors in the Order Crawler

Constraint Factors in the model are Current Time Step → Minimum Travel Time. We have now included them in the Order Crawler. They are specified per owner when there are multiple owners in the system, so we have included the average across owners. We also resolved a bug when there were multiple owners. The total wasn't always being shown. It was reporting the results for the first owner it found.

Operations Forecast Models Summary

Operations models now have a summary of Forecast models across the model:

Image Added

Improving validation of Node / Link names

We no longer support node or link names with trailing white space. For example, nodes and links with names such as "Storage " won't be allowed to open in this version of Source. You will need to fix these names in a previous version of Source.

These trailing white spaces were causing errors to occur in the results manager. 

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.

...

We have removed the tolerance in our regression tests , to allow for earlier identification of different machines or versions of operating systems giving different results. 

...

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

Jira Legacy
serverSystem JIRA
columnstype,key,status,summary,assignee,reporter
maximumIssues150
jqlQueryfixVersion in (5.7beta) order by issuetype
serverIdc4ca6e0fa22b5711-9f422728-3d1a3bcc-879c860f-870abe699ab12832d905a432