...
Changes in this release include:
- New
Order Crawler
recorder:Jira Legacy server JIRA serverId c4ca6e0f-9f42-3d1a-879c-870abe699ab1 key RM-19366 - Add an ownership adjustment at the end of timestep in storages and weirs:
Jira Legacy server JIRA serverId c4ca6e0f-9f42-3d1a-879c-870abe699ab1 key RM-19197 Recorder
- Ownership adjustment for Storages and Weirs
- Utility for interacting with the new Results streaming format
- New version number system
Order Crawler Recorder
..
Add an ownership adjustment at the end of timestep in storages and weirs
..The order crawler recorder is a new recorder to show all the nodes and links in a network and what their orders and requirements are on a particular date. Available under: Miscellaneous \ Ordering \ Order Crawler. The Order Crawler is a fully interactive zoomable schematic that shows:
- order data for all nodes and links (water users show their requirements)
- the entire network with node locations in the same location as the network
- the minimum order time values (same value as order recorder) e.g. if order travel time is 3 (minimum) to 5 (maximum) days the orders for 3 days out will be shown.
Ownership adjustment for Storages and Weirs
We previously have no way of adjusting the ownership mass balance on storage nodes post timestep. Often there are decisions that move ownership about as a result of management/policy decisions based on what happened that day. We now have an option to adjust the End of day volumes in Storages and Weirs.
Results Streaming
Results can now be streamed to files on disk rather than stored in memory. This is to prevent memory issues with large runs. Results streaming is off by default, however, it can be turned on in Project Options:
...
We have changed the version number system to help users understand when users need a new version to open projects. The previous database version was a letter that wasn't in the version number.
Previous The previous system was:
| Order | Name | |
|---|---|---|
| 1 | Major Version number | |
| 2 | Prod/Beta identifier | All Prod numbers are even. All Beta identifiers are +1 the most recent Prod identifier |
| 3 | Regular Functionality Release | Incremented when a new Beta is released every 1 to 2 months. Rarely updated for Prod releases. |
| Not included in version number | Database Upgrade letter | Needed when changes are made that require DB upgrades between official releases. This is used to identify what the current database structure of the project will be. Resets to 'a' when the 'Regular Functionality Release' changes. |
| 4 | Build number | Essentially a unique identifier for Source builds |
This is why this release is 4.13.0beta rather than 4.12.4beta.
New system:
| Order | Name | |
|---|---|---|
| 1 | Major Version number | |
| 2 | Prod/Beta identifier/Regular Functionality Release | Reset when the Major Version number increments. Increments with every official Prod and Beta release. We may increase by more than +1 |
| for production releases. | ||
| 3 | Database Upgrade Number | Needed when changes are made that require DB upgrades between official releases. This is used to identify what the current structure of the database's project will be. |
| 4 | Build number | Essentially a unique identifier for Source builds |
This is why this release is 4.13.0beta rather than 4.12.4beta, as it would have been in the previous system.
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.
...