5.51 Beta Release (January 2025)

The changes in this beta will also be available in the next Source production release.

This release includes:

• Added a new recorder “Farm Dam Surface Area” to “Onstream Farm Dam” node.

• A bug in the Irrigator Demand Model relating to fluctuating requirements or orders where there were different Max and Min Travel Times has been addressed. 

• Replacement of the old Environmental Flow Node logic with the new Spell Observer logic. Users are requested to configure the spell observer for the EF Actions as the old EFN logic will soon be retired.

• At the Environmental Flow Node, users can now specify the amount of water that needs to be debited to EFN using a function either at the node level or the action level if those actions within the node have same portfolio configuration.

• Added consistency across charts, tables, data and statistics in Results Manager. The table data and statistics will now only be displayed for the zoomed part of the chart.

• NetCDF export files will now have a unique ID, as we have modified the “Station IDs” to ensure each node/link in the network is uniquely mapped.

• Added the ability to load and merge custom charts using a newly added icon in the Results Manager window. Also, users can now manually select and merge one custom chart with another by selecting one of the saved custom charts.

• Added a new Option in the Chart Drop-Down Menu in Results Manager: “Sum All” will sum all time series plots with commensurate units.

• Added the ability to compare multiple time-series in the bivariate statistics comparison by selecting “Total Table” from the top left drop-down.

• Other enhancements and bug Fixes.

SWP :

• Added a new recorder “Farm Dam Surface Area” to “Onstream Farm Dam” node to record the farm dam surface area. The default recorder unit is same as default input unit which is Ha .

Open

• Removed the "Use Minimum Constraint Flow to Satisfy Orders" checkbox from the “Supply Point” node configuration. If the Supply Point node does not extract water, the minimum constraint will be raised to the water ordered at this node i.e., the Minimum Constraint at a non-extractive supply point will now be set to the maximum of the upstream minimum constraint or the requirement at the node.

   

Open Old version screenshot	Open Option is removed now with 5.51 version

Open Old version screenshot	Open Option is removed now with 5.51 version

• Users can now uncheck the value of “Add Orders to Downstream Orders“ at a Supply Point using Scenario Input Sets:

  

• Previously, if the Upstream minimum constraint was equal to or greater than the requirement at the EFN, the EFN requirement would be considered met by the minimum constraint, and no demand would be generated. This behavior has now been updated. EFN no longer considers the Upstream minimum constraint and will order on top of the Downstream order. This change ensures that the EFN behavior is consistent with the Minimum Flow Node in terms of ordering.

• Addressed a bug in the Irrigator Demand Model relating to fluctuating requirements or orders where there were different Max and Min Travel Times. Previously, if there was in increase in demand, the system would only generate new orders to be fulfilled from Max Travel Time.  With the fix additional orders can now be fulfilled from Min Travel Time.  This fix also involved some improvements to the code base.

   

IRMU :

The old Environmental Flow Node logic is now replaced by a new Spell Observer logic. Users are requested to configure the spell observer for the EF Actions as the old EFN logic will soon be retired. With the intent of allowing some time for users to fully transition their models to the new spell observer logic, the old logic can still be accessed from the “Experimental/Redundant features” of “Application settings”. Please refer to “Environmental Flow Node “ page for detailed information about the UI & logic changes and how it affects your models.

At the Environmental Flow Node, users can now specify a function-based account deduction.

Now, when creating a new project or when opening an old project this setting will be disabled by default unless the checkbox is checked. Once checked users can choose between the following two options:

1. Account deduction at the node level

2. Account deduction at the action level

Open

1. Account Deduction at the Node Level

1. When this option is selected, users can specify a function at the node level to deduct water from the Environmental Flow Manager Portfolios of the node’s actions.

    

   Open

   

2. All actions within the node must have the same portfolio configuration to enable this mode. This does not require actions to be attached to the same group, but if different groups are used, they must have identical portfolio configurations. An "identical portfolio configuration" means that the actions have the same set of portfolios with identical priorities and shares. If the node’s actions have different portfolio configurations, an error message is displayed, and the setting cannot be saved. Adding new actions, deleting actions, or disabling actions triggers a reevaluation of the feasibility of enabling account deduction at the node level.

   Open

   

3. When node-level account deduction is enabled:

   • Spell-based actions continue to order water according to their spell configurations.

   • Account deduction is based on the function specified at the node level.

   • The deduction volume is distributed across water accounts based on the priority and share of the portfolios and their associated accounts.

4. Recording System:

   • Action-level recorders (Environmental Flow Manager > Group x > Action y > Portfolio z > Account a > Debited Volume) will display NaN when this setting is enabled, as account deductions do not occur at the action level.

   • The node-level recorder (e.g., Environmental Flow Node x > Total Volume Debited) will capture the total volume deducted by the function.

5. An assurance rule validates the portfolio configurations of all actions at runtime to ensure compatibility with this setting. This prevents users from running the model if the portfolio configurations become inconsistent after enabling node-level account deduction.

   Open

   

    

   Open

   

    

6. Users can configure node-level account deductions through Scenario Input Sets. See the below screenshot for an example configuration.

Open

2. Account Deduction at the Action Level

1. When this option is selected, users can view a list of spell-based actions in the node and:

   • Select which actions participate in action-level account deduction.

   • Specify functions for the account deduction of participating actions.

   Open

   

    

2. To enable account deduction at action level, actions in the node do not need identical portfolio configurations.

   • For actions participating in action-level account deduction, account deduction occurs according to the specified function, regardless of whether the action orders water in a given timestep.

   • For non-participating actions (e.g., actions not selected for this option like Spell Based Action 3 in the above screenshot), account deduction occurs normally based on actual ordered volumes and received water at the node

3. Recording System:

   • Action-level recorders (Environmental Flow Manager > Group x > Action y > Portfolio z > Account a > Debited Volume) reflect the deductions caused by the specified function for each action, portfolio, and account.

   • The node-level recorder (Environmental Flow Node x > Total Volume Debited) captures the total volume deducted for all actions in the node.

4. Users can configure action-level account deductions through Scenario Input Sets. See the below screenshot for an example configuration.

Open

Open

There are 3 minor enhancements delivered as part of IRMU. They are as follows:

1. Displaying NaN value in the “Debited Volume” recorder in EFM when the Volume ordered exceeds the deduction cap set in “Specify Maximum Account Deduction”.

2. Previously the EFM and EFN “Debited Volume” Recorders did not show correct values when accounts that are being debited ran out of water. This has been fixed now & the recorders now show the correct values.

3. Auto populating the settings of spell observer with their respective spell ordering values in case the user checks the checkbox that says “use same value as ordering”.

Open

EEWD :

• NetCDF export files will now have a unique ID, as we have modified the “Station IDs” to ensure each node/link in the network is uniquely mapped.

• Added the ability to load and merge custom charts specifically using the icon highlighted below. Also can be accessed with a hot key [Ctrl + M].

Open

• Also, users can now manually select and merge one custom chart with another by selecting one of the saved custom charts.

Open

• When a user zooms on a part of the chart (including lasso zoom, zoom via mouse, drag chart , zoom reset, zoom in, zoom out etc.), the data in the Table tab and statistics in the Statistics tab are updated based on the zoomed part of the chart. The table data and statistics will only be displayed for the zoomed part. For example, the first value of the table is the left most value of the chart and the last value of the table is the right most value of the chart.

Open	Open

Open	Open

• Added new Option in Chart Drop-Down Menu, “Sum All” to add all time series plots with commensurate units.

Open

• Added the ability to compare multiple time-series in the bivariate statistics comparison by selecting “Total Table” from the top left drop-down.

Open

Other Enhancements &. Bug Fixes:

Minor enhancements and Bug fixes include:

• Trade Manager logic was modified to make it vulnerable to negative account balances in the meantime we decide the approach to deal with negative account balances. Fixed now

• Often the ‘SimpleProgressWindow’ throws an exception of " System.NotSupportedException - ImageSourceConverter cannot convert from (null)" while loading a project. Fixed now

• 'Activation Date' and ‘Activation Date Enabled’ are added to the feature table for Farm Dam node configuration. Added successfully

• We have added <gcServer enabled="true"/> as a standard for all releases which makes it convenient to activate Garbage Collection Setting in Source. This has improved the performance and efficiency. We observed approximately 2 mins faster run time than the 5.50 version for the GBCCL model, this could be more effective with larger models. Improved Performance

•  

Regression Testing

There is no tolerance in our regression test suite to allow for earlier identification of results being different on different machines or versions of operating systems. 

See: 5.51 Regression Test Changes