...
The priority of an action is defined as:
Priority = (1- Condition ) x / Importance
where Condition unless specified by the user is equal to
Condition = EXP(- time since last successful spellseason/average return interval)
...
CommitEstimatedCostToPortfolios will distribute the estimated cost of a group across portfolios so that the Portfolio.AvailableWater is reduced. This distribution works in a similar way to distribution of water user orders to supply points. That is, the cost will be split across the highest priority portfolios first in the share percentages specified in the portfolio configuration. Lower priority portfolios will only be used once higher priority portfolios have no available water.
Once the prioritise are priorities are calculated, the main loop begins:
...
It is important to note a few things in the above psuedo pseudo code. First, groups that were enabled the last time the EFM was run will be prioritised before other groups that were not, regardless of priority. Secondly, if a group has no actions that are in season today, they will always be disabled. The ReducePortfoliosByCost function is the same as described above.
...
The environmental flow manager sorts groups of actions into ascending priority order by examining the priority values generated for each action by the importance and condition functions. The condition is calculated by default by dividing the average desired return interval by the number of days since last success (with values limited to maximum of 1). This can be replaced by a user specified condition function. The importance weighting is calculated using a user defined function, which allows flexibility in the way the events are prioritised and coordinated.
Priority = (1- Condition ) / Importance
If groups have the same priority value, then they are ranked by the importance values, then by the condition. The priority of a group is considered to be equal to that of the highest priority action within that group.
...
The environmental flow manager will not enable an action if it returns an importance value of zerothat is zero or nagative. Groups with any actions with importance > 0 will still be enabled along with any actions in them. To disable a group with multiple actions all actions would need to have importance = 0.
...
The default condition calculation if not specified by the user is EXP(- time since last successful spellseason/average return interval)
...
An action will effectively be disabled if the flow manager does not allocate water to its group, however, the action will still monitor the flow based on action definition. The manager
will not enable When an action if the season has already be passed in this water year.
...
is disabled at the EFN, the action has effectively been turned off for the whole run, as opposed to the enabling/disabling by the manager which is dynamic.
Portfolios
Each account within a portfolio can have a balance adjustment specified.
...