Change log

You are here: / / Change log

Change log

A number of improvements based on feedback from use of Version 2.

Computation

  1. Adjusted how the assessment period (season) is determined, to now assess only a portion of the reporting year based on the partial curve provided. Previously, the full year (from the start month provided) was assessed, with scores adjusted by the season partial curve. This lead to unexpected results on rule temporal components (such as lowflow duration), as the whole year was being assessed. The assessment period is now determined by analysing the curve to find the longest continuous block of months with a score >0, starting from the provided start month. For example, a spring/summer lowflow rule with a duration of 100% would previously need to be met on every day of the year to get a duration score of 100%, which is not possible if only 6 months (spring/summer) of the year had a season score >0. In this case, it was expected that the rule duration would be set by the user at 50%. Now only the 6 in-season months will be assessed, and so a rule duration of 100% can be achieved. This aligns with how V1 treated seasons, and we believe it is a much more intuitive approach.
  2. Adjusted how sub-season climate results get aggregated, so a climate with a disabled (and thus not assessable) rule is not included when calculating the proportion of other climates in the season. This is an unlikely situation, as typically a disabled climate will not be present in the climate data being used.

Models

  1. Added a new Off-stream model, which is a replication of the ‘custom rule’ found in V1. It is used to capture rules that cannot be assessed with available data. The model will generate output files with placeholder yearly results to be manually entered. These results have no visualisation and are available only as a download in the form of legacy_results.csv

Functionality

  1. Added a reporting tier column in explorer, so you can see rule reporting tiers without opening the rule
  2. Added a reporting tier filter in compliance report add rules screen
  3. Added additional rule reporting tiers (Traditional Owners, Boating, Birdwatching, Angling and Camping), these flow through to legacy output download as additional columns
  4. Added routing to the url when navigating through folders in the explorer. This means you can refresh the page and will remain in the same folder. This also means when you navigate back to the explorer from a rule, you will be placed in the rules folder. This should greatly improve the explorer user-experience.

Version 2 of eFlow Projector released. The new version allows data to be managed independently through a data library and for flow rules to be managed independently and be reused across multiple performance reports. The new features are described here and a demonstration example for the Murray Darling Basin is presented here.

When the event number exceeds the target number of events, lowest magnitude events are removed. The previous event sorting approach has been replaced by retaining the event list and removing low magnitude events from the event list to ensure the event ordering is maintained.

The following changes apply to within year and multiyear freshes flow rule types

Event Selection

The selection of a freshes event from within an event opportunity, has been updated to be the first occurrence of the maximum score event. Previously, the selected event was updated if the event score was equal to the previously selected event, resulting in the selection of events toward he end of the event opportunity. The result of the change is that where events of equal score occur within an event opportunity, the selected event will be the first, rather than the last occurrence of the maximum score event.

Event Selection for failed independence

Where events are too close (gap is less than the minimum independence criteria), one of the events is discarded. Previously, the first event was discarded. This has been revised so that the event of the lowest score is discarded (which may be the second event).

Event independence scoring

Where the prescribed event number is one or when only one event is detected, the event independence score is set to the maximum score.

In the system setup, you can now link the flow data to API services fro Queensland, New South Wales and Victoria. In addition there is a global update button. Pressing the global update will check all API enabled flow data and retrieve the most up to date flow data. This functionality will allow for rapid testing of within season environmental watering performance.

The multiyear flow rule allows the consideration of a flow requirement across multiple years with the additional inclusion of of a ‘maximum period’. An example flow requirement suitable for the multiyear flow rule would be: I require 3 flow events over a 10 year period and the maximum time between events is 4 years.

The partial success tables now have a chart to illustrate the shape of the response curve between target% and performance %.

The results can now be visualised in the ‘explore results’ tab. The explore results allows you to see results for a single year or across all year, aggregated to region, catch, sub-catchment, site or at an individual flow rule level.

The results visualisation can be filtered by reporting level

Initial release of eFlow Projector

Support & feedback

If you need some support, find any bugs or odd behaviour, or would like to give us some feedback about eFlow Projector please feel free to contact us.

Contact us
Truii-logo-reverse-no clear space

eFlow Projector is a Truii product.

If you are interested in learning more about Truii and viewing their full range of data-driven web applications, follow the link below.

Find out more about Truii >>