...
Figure 3. Expanded Environmental Flow Manager Conceptual Model: Detailed flowchart for the 'Prioritise and activate/flag actions' box in Figure 2.
Environmental Flow Manager Prioritisation Phase:
...
where Condition unless specified by the user is equal to
Condition = EXP(- time Time since last successful spell in a successful season/average return interval)
...
It is important to note a few things in the above pseudo code. First, groups are prioritised in the following order: Groups that were actively ordering last timestep, 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 disabledthen by priority. 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 as the natural exponent of the number of days since last success (with values limited to maximum of 1)divided by the average desired return interval. 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.
...
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. Priority can be 0, or even negative, and these are considered a higher priority than any positive value.
If all actions in a groups have an importance of <= 0, the group is disabled.
The environmental flow manager will not enable an action if it returns an importance value that is zero or nagativenegative. 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 Time since last successful spell in a successful season/average return interval)
...