The changes in this beta will be available in the 4.13 Source version 5 production release, due out at the end of June 2020.
Waiting on:
| Jira Legacy |
|---|
| server | JIRA |
|---|
| serverId | c4ca6e0f-9f42-3d1a-879c-870abe699ab1 |
|---|
| key | MH-264 |
|---|
|
| Jira Legacy |
|---|
| server | JIRA |
|---|
| serverId | c4ca6e0f-9f42-3d1a-879c-870abe699ab1 |
|---|
| key | MH-263 |
|---|
|
Changes in this release include ....
A new
So to minimise the effect in splitting this phase in two, we've written some migration code.
| Jira Legacy |
|---|
| server | JIRA |
|---|
| serverId | c4ca6e0f-9f42-3d1a-879c-870abe699ab1 |
|---|
| key | RM-16975 |
|---|
|
- The organisation of custom charts has come has began| Jira Legacy |
|---|
| server | JIRA |
|---|
| serverId | c4ca6e0f-9f42-3d1a-879c-870abe699ab1 |
|---|
| key | RM-18770 |
|---|
|
- Ability to adjust order from supplements to meet the downstream demand including irrigator demand| Jira Legacy |
|---|
| server | JIRA |
|---|
| serverId | c4ca6e0f-9f42-3d1a-879c-870abe699ab1 |
|---|
| key | RM-17711 |
|---|
|
- Add Lock/Unlock usage function for the selected recorder associated with a modelled variable in Function Editor| Jira Legacy |
|---|
| server | JIRA |
|---|
| serverId | c4ca6e0f-9f42-3d1a-879c-870abe699ab1 |
|---|
| key | RM-18940 |
|---|
|
- Command line server to support save of results to specific location| Jira Legacy |
|---|
| server | JIRA |
|---|
| serverId | c4ca6e0f-9f42-3d1a-879c-870abe699ab1 |
|---|
| key | RM-18396 |
|---|
|
- ...Operations Tabular editor changes
| Jira Legacy |
|---|
| server | JIRA |
|---|
| serverId | c4ca6e0f-9f42-3d1a-879c-870abe699ab1 |
|---|
| key | RM-15794 |
|---|
|
- Look into viewing data in results manager from Tabular Editor| Jira Legacy |
|---|
| server | JIRA |
|---|
| serverId | c4ca6e0f-9f42-3d1a-879c-870abe699ab1 |
|---|
| key | RM-19021 |
|---|
|
- Allow pasting into multiple rows after selecting a single cell into the tabular editorFeatures of this release include:
- Changes to the way custom charts are managed.
- Command line improvements.
- Updates to River Operation mode within Source.
We have also introduced the concept of Locking to the Function Modelled Variables, selected variables can now be locked, making it less likely for mistakes to occur.
Ordering for the Irrigator demand model now includes an option to make the Flow phase and Order phase identical.
Custom charts
Custom charts are no longer saved by default!
All automatically generated charts are created under Temporary and only saved when moved into Saved. Users can also create folders and subfolders for organising custom charts:
Image Added
We will also want to include a toolbar with a filter/search for custom charts:
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | a22b5711-2728-3bcc-860f-2832d905a432 |
|---|
| key | RM-19119 |
|---|
|
will be available in a beta soon.Operations Tabular Editor changes
The Operations Tabular Editor now allows you to copy-paste into multiple cells and view charts directly in the Results Manager.
Performance improvements for the command line
We have done some work to improve the performance of the command line, less memory (RAM) is now used during a run and to speed up run time in the command line.
The command line now has additional options for results saving:
| Code Block |
|---|
--resultsOutputMode |
There are three modes available:
- noOutput - This improves performance when using automatic exporting tools such as Scenario Options: Simulation results or Simulation Log which automatically exports results after each run to a specific location.
- serverNamedFormat - This mode saves from the server, rather than transferring data back to the client when in client-server mode. This is also now the default for a single computer run, meaning performance is improved by not transferring the data.
- clientNamedFormat - (default for client-server mode). The data is transferred back to the client and saved (current behaviour).
Plugin Developers
We are planning on moving to C# 7, Visual Studio 2019 and .NET 4.8.0 soon, so you will need to make sure you have updated Visual Studio to continue developing plugins in the beta versions.
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: 4.12.1 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
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | type,key,status,summary,assignee,reporter |
|---|
| maximumIssues | 150 |
|---|
| jqlQuery | project in (RM, Insight) AND fixVersion = 4.12.1beta AND statusCategory not in ("To Do") |
|---|
| serverId | c4ca6e0fa22b5711-9f422728-3d1a3bcc-879c860f-870abe699ab12832d905a432 |
|---|
|