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 are now available in the Order Crawler, and
- Improved validation of Node / Link names.
Unregulated system improvements
...
When using Source through a remote desktop session, it could hard crash the application when viewing charts. Improvements we made in this release should now resolve 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 understand all the changesrecognise 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:
...
Constraint Factors in the model are Current Time Step → Minimum Travel Time. We have now included them in the Order Crawler. They are available 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 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.
...
Full Release Documentation
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|