Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Changing recorders

3.4.3 no longer supports the water user recorder for Ordered Water Supplied.  This is because its purpose was not clear.  Where model variables use this recorder the user will need to select another recorder.  In most cases the Supply Point recorder Extracted Volume will be suitable.

Constituent Routing Change

The changes made to lumped constituent routing were made to facilitate realistic approximate link decay models within approximate lumped routing.  Prior to this change decay models did not work.  Constituent models without decay will show small changes in constituent concentrations and timings of changes in concentrations.   

The total constituent load over time, will not change.  The change to constituent routing involved changing the order in which outflows, inflows and mixing were processed at link storages. Inflows to link storages are no longer fully mixed before processing the outflow from the link storage.

Existing projects should either not upgrade, or repeat baseline runs.

Minimum Flow Node Units

The minimum requirement at a minimum flow node is now input as a rate instead of a volume. This has been done for consistency. All projects should be automatically upgraded without user interaction to use the new units.

New functionality

  • Resource Assessment customisations for Victoria and MDBA 
    • Modify off allocation system to support a linked account 
    • Ability to transfer water from one water account to another water account which are under different Resource Assessment Systems
    • Too easy to accidentally change which function is selected
  • Meaningful errors
    • Errors now report where they occurred
    • New log reporter with filtering on each column
    • Improved mass balance reporting
  • Changes to insight - (there is a known issue with Insight results viewing that we will resolve in a new build shortly)
    • Allow objective functions to be a range of statistics of results from multiple scenario runs
    • Report the values of non-optimised objective functions (secondary objective functions) 
    • Save optimisation results back into Source (Pass user-selected decision variables from Insight to Source project)
    • Insight user guide content has been added: Insight: Objective optimisation
  • Reporting Tool for analysing results of many runs (Dora) is now available in beta form: Run it from <Install Path>\RiverSystem.RecorderExplorer.exe
  • A number of Command line bugs
  • Minimum flow requirements can now be input as rule curves.
  • Recorded functions are now accessible on the Tabular Editor
  • Reload on Run for Data Source:Scenarios

New Community Plugins!  

Existing Issues

  • Copy & paste functionality does not copy expressions
  • Can now add constituents to a catchments model.  Save and re-load project  - it will not be able to run straight away.

Insight

To run Insight you also need to install the 32bit version of Microsoft Visual C++ 2010 Redistributable Package.
This is for both 32bit machines and 64bit machines since the library we use is 32bit:
http://www.microsoft.com/download/en/details.aspx?id=5555

Plugins

If you are downloading community plugins then you will need to manually 'unblock' the dll's in Windows after downloading. To do this, right click on the dll file in windows explorer and select properties. At the bottom of this window will be comment along the lines of 'this file has been downloaded from the internet and has been blocked to protect this computer'. There should be an 'unblock' button next to the warning. Click unblock and then click ok. The plugin should then load

Release Documentation

type key status summary assignee reporter

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels