The changes in this beta will be available in the next Source production release due out at the end of June December 2022.
This release includes:
- Geographic Scenario Reporting Tool improvements,
- changes to Supply Point ordering user interface,
- Merge Catchment Scenarios,
- Functional Unit rename and
- Replicate runner - second phase.
Geographic Scenario Reporting Tool
We have introduced the concept of Reporting Regions. Available under Edit \ Reporting Regions
These regions are used in the new Reporting Regions Data Collector. Available under Tools \ Analysis Windows \ Reporting Regions Data Collector….
And the results will be displayed in Tools \ Analysis Windows \ Map:
Detailed documentation is available here: Catchment Map Reporting Region
Supply Point User interface changes
We have made some changes in the Supply Point user interface to be clearer about what different options were doing.
In Rules-Based Ordering:
- Add Orders To Downstream Orders remains unchanged
- Use Unregulated Flow To Satisfy Orders is now Use Min Constraint Flow To Satisfy Orders
In Net LP Ordering
- Add Orders To Downstream Orders is now NetLP 2 phase solution: Add orders in 2nd phase
- Use Unregulated Flow To Satisfy Orders is no longer selectable. It already had no effect on processing.
Merge Catchment Scenarios and Functional Unit rename
Now available under Tools \ Merge Catchments. You can now merge two catchment Scenarios into a single Scenario.
To help with using this tool, we also implemented Functional Unit renaming allowing you to rename Functional Units before or after a merge.
Replicate runner - Next phase
We have started to implement a replicate runner within Source for applications such as a risk of spill assessment.
There is a new Run configuration available in Scenario Options called Replicate Analysis Configuration. This can be added to the scenario.
The following example cycles the Data Sources used in the model to create 20 Replicates. Replicates are generated using the same method that's been implemented in the Run Manager: Time Series Cycle Creator.
Results can be used in custom charts and viewed in the Results Manager. .res.csv now includes meta data to identify the SubRunName that will be in the export.
- Data sources can now be selected (RM-20190),
- Annual Descriptive Statistics will now with across sub runs (RM-20199).
There are limitations we are continuing to work on. This will be available in future releases:
- Runs in series and not in parallel, which is an important performance improvement (RM-20178),
Documentation is available here: Replicate analysis simulations in Source and will be incorporated into the documentation after the production release.
Plugin Developers
As we are moving to .net 6, we have now updated the .csproj format that is used by Source. Please see: Csproj Format to go through the conversion process.
To compile Source you now require:
- .Net Framework 4.8 Developer pack - https://dotnet.microsoft.com/en-us/download/dotnet-framework/thank-you/net48-developer-pack-offline-installer
- .NET 5.0 SDK - https://dotnet.microsoft.com/en-us/download/dotnet/5.0
- Visual Studio 2022 - https://visualstudio.microsoft.com/vs/older-downloads/
- Updates to the Storage Ownership logic.
- Modifications to the Operations Tabular Editor.
- Bug fixes for the Environmental Flow node.
Updates to Storage Ownership logic
In Source 5.14 Beta and Source 5.16 changes were made to allow "Internal spilling to be specified by Owner". This added a new option to 'Ownership' in storage and weir nodes allowing an owner to 'Use Airspace'. Following testing and feedback from those releases, further changes have been made in this release to address a number of identified issues. These changes include:
- A new proportional loss calculation method has been introduced.
- The 'Use airspace' option can be used when internal spilling is disabled.
- The 'Use Airspace' owner can receive water internally spilled from other owners, if it is below its specified capacity share (not allowing this could cause incorrect spill calculations).
- Fixes for negative and close to zero ownership values in storage ownership.
- Improved test coverage of storage ownership.
The new proportional loss calculation method has been separated out into an independent implementation from the original storage ownership methodology to allow for comparison of results between the old and new versions. It is expected that the new method will be adopted as part of the next production release, in December 2022, at which point the dual implementation will be removed.
Details of the changes are outlined in Owner Working Volume Proportion Method.
Fixes for negative and close to zero ownership values were made in common code shared by both the old and new methods, as such some very small result changes have been identified through regression tests.
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.
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Details here: /wiki/spaces/SC/pages/51651480
Insight
To run Insight, you also need to install the 32bit version of Microsoft Visual C++ 2010 Redistributable Package.
This installer is for 32bit machines and 64bit machines since the library we use is 32bit: Microsoft Visual C++ 2010 Redistributable Package (x86).
Full Release Documentation
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|