The changes in this beta will be available in the next Source production release, due out at the end of June 2021.
Improvements in this This release includeincludes:
- Improvements to Unregulated system ordering,
- Crashes with Remote Desktop and SciChart Resolvedresolved for Results Manager,
- Scenario Input Sets affecting Nodes and Links are now visible within Node / Link feature editors, and
- Constraint Factors have been added to are now available in the Order Crawler, and
- Improved validation of Node / Link names.
Unregulated system improvements
We have made it so Confluences now handle constraints for Unregulated sections of networks. After changes were introduced We introduced changes to allow splitters to be considered regulated in 5.6 - Beta Release (February 2021), for . For orders to be passed up to the splitter, constraints needed to be propagated down to it. This change confluences. This improvement makes Confluences sum together the forecasts from each of its two branches when they are both unregulated.
...
When using Source through a remote desktop session, you it could sometimes hard crash the application when viewing charts. This should now be resolved.
Constraint Factors in the Order Crawler
Constraint Factors are used in the model from the current Time Step → Minimum travel time. They are available per owner when there are multiple owners in the system.
...
Improvements we made in this release have resolved this.
Scenario Input Sets in Node / Link feature editors
When working with large models that have with significant scenario modelling with Scenario Input Sets, it can be hard to understand all the changes when looking at individual nodes/linksrecognise 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 that are made to the current node/link across the Scenario Input Sets:
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:
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 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|