Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Import Link Fixer

...

This release includes a number of small improvements in usability and validation. There have been significant improvements to:

  • Environmental Flows,
  • The Date Ranges interfaceCalibration Improvements,
  • Date Time format changes, 
  • Hot Start Rainfall runoff models and ,
  • Ownership proportions at Splitters.

...

There has been a number of improvements in Environmental Flows. We have extended the

...

Environmental Flows node's Spell action. Functions are now available for:

  • Number of spells in a season
  • Number of spells for success in a season, and
  • Spell duration.

The values of these functions can't change every day during a simulation. The values of the functions are taken from before the start of the season. To allow for the forcing of spells during a season, the values need to be taken allowing for travel time before the start of the season.

There is also a new option to allow the fall phase of spells to occur after the end of the season.

Scenario Input Sets and the Export summary will now include more information about Environmental Flow Actions.

...

 The path for the existing Scenario Inputs Sets will need to change from Rules → 

...

Actions.  API details are in RM-16591.

...

Date Ranges interface

Jira LegacyserverJIRAserverIdc4ca6e0f-9f42-3d1a-879c-870abe699ab1keyRM-18488Terminology in the User Interface for one of the Initial Values at the start of run has been corrected during the process of developing the full API. Time since last successful season has been changed to Time since last successful spell in a successful season. For spell-based actions, we have removed the use of the term planned and now only use forcing.

Calibration Improvements

You can now calibrate parameters using Scenario Input Sets.  We are continuing to develop this and there will be more details and changes in 5.9beta.

Date Time format changes

We have had a couple of issues with date formats changing on different computers. We are resolving this by moving to export based on yyyy-MM-dd HH:mm:ss. We will continue to import data from a variety of formats, however, tools such as Scenario Input Sets, and the Export Summary will now be using this format regardless of the user's computer settings.

...

The user interface has been consolidated to :

XXXXXXX

and we have improved the validation.a single tab, and it's been made clear that it has currently only been implemented for GR4J and Sacramento.

Image Added

Ownership proportions at Splitters

...

It previously assumed the allocated flow was always less than the actual flow. This has now been resolved. 

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.are now upgrading to Visual Studio 2019. Plugin developers will need to use Visual Studio 2019 for 5.8beta onwards.

Regression Testing

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. 

...

Full Release Documentation

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