The document outlines the development timeline and key features for different versions of an EFlows software model. Version 0.9 focused on initial infrastructure and spreadsheet conversion. Version 1 removed infinite benefits and sped up species calculations. Version 2 revisited rewatering loops and scenario permutations. Version 3 restricted wetlands to one watering per year. Version 5 extends runs over multiple years and revisits water distribution and species benefit calculations by adding fields like benefit duration and migratory status. It presents four approaches to recalculating species benefits based on these new fields.

1. EFlows Development Overview
Lindsay Bradford – 03/12/2012
1

2. EFlows Release Timeline:
Now: 0.9b:
Version 0.9a:
0.9d/e:
0.9c:
• Base Infrastructure (left)
EflowsModelV1-4
EflowsModelV1:
• EflowsModelV1:
• Initial Spreadsheet cutover
Infrastructure changed for CSV (left)
• Initial Spreadsheet cutover
EFLowsModelV5
EFlowsModelV2: (6?):
• Removal of infinitebenefit
Revisit rewatering loops
‘Scenario Permutations’
• Speedup: for species
calculations which scenario to
Randomise
• WorkSpreadsheet:
• in season.
apply to aprogress. 56 seconds
• .NET:
EFlowsModelV3: 6 seconds.
• Revisit water swaps, allowing
full range of possible swaps.
EFlowsModelV4:
• Regulated wetlands restricted
to 1 watering per year/run.
2

3. EFlowsModelV5 – Water Budget
• Extend runs to multiple years
– Revisit water distribution balance per year:
• Strict Yearly Budget:
– Yearly total is distributed in a single year across the seasons
of only that year.
– Closest to current behaviour
• Flexible Yearly Budget:
– Yearly water totals aggregated into a total pool, and
allocated across all the years (possible differing distributions
of water across each year).
– Budgeting types incompatible. Either chose one
type, or build one model each per budget type.
3

4. EFlowsModelV5 – Species Benefits
• Revisit species benefit calculations based on rewatering needs of species.
– Approach #1: Adding ‘BenefitDuration’ field to species
• Once a wetland is watered, no new benefit for a species in that wetland is possible until
‘BenefitDuration’ months has elapsed.
• Benefit calculated from start of period of watering.
• Once elapsed, the next time a wetland is watered, the default multiplier benefit for the
species/season is re-applied.
• Multiple non-overlapping species benefits possible over run.
– Approach #2: Adding ‘BenefitDuration’ field to species
• If a wetland is watered, and a species benefits from it, the species can benefit again if
rewatered within ‘BenefitDuration’ period, extending the benefit period for that species.
• Multiple overlapping species benefits possible over run (double/triple/etc -dipping).
– Approach #3 (based on #1): Adding a ‘migratory’ flag to a species.
• If a species is migratory, it operates as outlined in approach #1
• If not migratory, failure to rewater a species will see no further rewatering benefit for a species
through to the end of the given run (modelling the species going extinct in an area).
• Limit of one benefit possible over run for non-migratory species.
– Approach #4 (based on #1): Adding a ‘migratory’ flag to species.
• If a species is migratory, it operates as outlined in approach #1
• If not migratory, check at end of run for non-migratory species fully rewatered over entire run.
• No benefit given at all for non-migratory species that are not fully rewatered over the run.
4

5. EFlowsModelV5 – Species Benefits(2)
– Approach #1: Adding ‘BenefitDuration’ field to
species records
– Approach #2: Adding ‘BenefitDuration’ field to
species records
5

6. EFlowsModelV5 – Species Benefits(3)
– Approach #3 (based on #1): Adding a ‘migratory’
flag to species records.
– Approach #4 (based on #1): Adding a ‘migratory’
flag to species records.
6