6.1 Beta Release (December 2025)

6.1 Beta Release (December 2025)

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

This release includes:

SWP (Source Work Program)

  • Resolved an issue where off-allocation water take did not function correctly for water users with two supply points due to the 'SetRemainingSourceOrder' method, which is now fixed; regression tests confirmed the expected changes.

  • Improved travel time calculation for Off Allocation by selecting the shortest path to a node when multiple link paths exist, delaying rounding of decimal values for travel time until the end, and incorporating travel time through the weir node, along with other enhancements.

  • Changes made in coordination with MDBA to correct Marker age calculations.

  • Added few Marker Routing referential integrity checks that can be optionally turned on with an assurance rule.

  • Corrected a bug in Marker Routing where certain inflow conditions at a hydraulic connector would cause an error, halting the run.

  • Set the Initial Mass of the constituents in a storage at the very first timestep, even if constituent processing activates later in the run.

  • Streamlined carryover scalar reporting by removing duplicate recorders, eliminating confusion in the Annual Accounting System caused by carryover scalar values being reported at both the Account Host and Account Type levels. So, removed the recorder at the Account Host level and updated the Account Type recorder to return null values (-9999) until the first reassessment, after which it reports the same value as the first account in that type.

  • Corrected end-of-year carryover logic to ensure unallocated carryover water rolls into the next water year when the carryover scalar does not reach 100%.

  • Resolved a bug where the MassBalance check always used the default value of 1000 instead of the user-specified value entered in Scenario Options. This fix applies to mass balance checks for catchments, links, networks, and nodes.

  • Addressed issues caused by a mismatch between the data source/time-series variable timesteps in the custom function GetDataTimeSteps() and the model's run configuration timestep; the fix now allows using different timesteps in the custom function's data while running the model at a different timestep, with a warning provided.

  • Fixed an issue in Source which incorrectly handled disaggregation of annual or monthly time series data to daily or sub-daily data due to leap years (annual only) and variable month lengths (monthly only). 

  • Removed the duplicate Mass Balance recorder, observed in four rainfall runoff models (Observed catchment runoff depth, Function Based, Nil Runoff, Observed catchment surface runoff depth) within RiverSystem caused by property override naming conflicts.

  • Fixed an issue in which dates were not aligning properly when a non-fixed span (e.g. monthly) time series was listed with a fixed span (daily) time series in a custom chart. 

  • Improvements to the crop factor charts under Crop parameters for Irrigator, IQQM, and Pride, ensuring they are displayed correctly. Differences in default start dates between IQQM and Pride are now clarified, with users responsible for selecting the actual start date. Additionally, the X-axis labels for Irrigator (showing days since the start of the crop season) and IQQM/Pride (showing calendar months) are now correctly aligned with the underlying algorithms and specifications.

 

Roadmap Initiatives

  • Recording Manager has been fully decommissioned and removed from Source in version 6.1. Recorders that previously worked only in Recording Manager have been removed or updated so that all supported recorder outputs now function exclusively through Results Manager.

    • The Multiple Supply Path Solver recorder has been removed from the Project Hierarchy, as its data was only supported by the now-deprecated Recording Manager and was never available in Results Manager. NetLP Debug information is still available through the NetLP Scenario Options screen.

    • The Forecast Volume recorder, previously available only through Recording Manager and not producing results in Results Manager, has now been fixed. It is fully supported in Results Manager and available for Inflow and Gauge nodes.

  • 3 old recorders WaterUserReturnFlowElementRecorder, WaterUserStorageElementRecorder, RainfallRunoffRecorder are now upgraded to the new GUID-based system. This improves internal tracking of functionality (e.g. Modelled Variables) based on these recorders.

River Operations

  • Introduced new functionality to launch the Source User Interface with a specific scenario from the command line or batch file, enabling users to quickly start a selected scenario in the Source project file.

  • Multiple fixes/changes to tabular editor :

    • A new search bar has been added to the top of the column editor panel, allowing users to filter columns by recorder name. The list dynamically shows only the columns that match the entered search text.

    • The Tabular Editor now supports text-based header comments, with the first row reserved for comments that can be shown or hidden. These comments persist in the same way as column formatting, and data begins from the second row.

    • The comment box in the Tabular Editor has been enlarged and now supports vertical scrolling for easier editing of longer comments.

    • Fixed a bug where comments added to a cell were removed when that cell was overridden.

    • Fixed an issue with incorrect travel times displayed by the cutout lines in the Tabular Editor, caused by outlet travel times being zero, which led to inflated travel times in the editor.

  • Fixed an issue in Results Manager charts where the manually entered minimum Y-axis value was ignored when the axis range was set to Manual. This fix does not affect the Auto mode.

     

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: 6.1 Regression Test Changes

 

Full Release Documentation