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 »

This release delivers new and enhanced functionality for describing and managing environmental flow requirements, using time series for initial values, river operations, a new SubSource community plugins, and changes to the Farm Dams community plugin.

Environmental Flow Node

Environmental flows describe the quantity, timing, and quality of water flows required to sustain freshwater and estuarine ecosystems and the human livelihoods and well-being that depend on these ecosystems.  The Environmental Flow Node in Source provides a way of describing these sometimes complex watering requirements and operating rules for delivering water to environmental assets like wetlands. Two types of actions have been implemented to allow users to construct a collective environmental water requirement by using combinations of actions, these are:

 Flood/Fresh/Minimum Flow

      • Baseflow: specifies a minimum flow; usually applied to maintain minimum habitat requirements,
      • High Flow/Flood: specifies a flood/fresh condition, usually associated with an ecological recruitment event such as a trigger for fish movement, water floodplain vegetation or moving sediment deposits
      • Pattern: specifies a pattern of flow; used to define multi-peak events.


 

Translucency is a way of specifying a patterns of flows usually to mimic the natural outflow pattern from a reservoir.

Time Series for initial values

You can now specify initial values for Storages and Resource Assessment using a time series or function rather than having to edit all initial values when you change a run period.

Functions and Modelled variables can now be evaluated at the start of run instead of specifying initial values. Previously, at the start of a run, all the modelled variables were set to the initial value specified (0 by default). If the function using the modelled variable has a time of evaluation before that of the modelled variable, the modelled variable will not have obtained it's first value in the first time step, and the set initial value will be used.

River Operations Changes

This version of Source allows forecasting on Storage/Weir Operating Levels for river operations.

Community Plugins

SubSource

The SubSource plugin runs a second Source model at different points during the main model run which is typically used to forecast water allocations. For example see the below figure: 

The main model (blue): steps through the simulation period, using some information from Sub model (yellow) to calculate water allocations

At each call from the main model, the sub model (yellow) simulates the Dry (worst case) scenario until the end of the water year to estimate harvestable inflows and losses for the main model.

Farm Dams

The Farm Dams plugin has improvements to include API components for all of its nodes. This means they will now work with:

  • the Scenario Diff tool,
  • Scenario Input Sets, and
  • the Export Summary.

 

Regression Testing

Regression Test Report including coverage (index.html): 4.2.5beta Hydrology Test Matrix.zip

Regression test repository changes since the first Source 4.2.4beta:

(warning) 1 Projects results changed
(warning) 1 Projects edited
(plus) 4 Projects added
(plus)(error) 1 Projects added - not yet passing

Details here: 4.2.5 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

type key status summary assignee reporter

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



  • No labels