The changes in this beta will be available in the next Source production release due out at the end of June 2022.
This release includes:
- Spatial Data Exporter plugin included as core,
- Environmental Flow Actions are now in the Feature Table,
- Internal spilling can be specified according to Owner, and
- the first implementation of a Replicate Runner.
Spatial data Exporter
The Spatial Data Exporter from Queensland's Derm Tools plugin has been updated and incorporated into the core application. The Spatial Data Exporter allows you to easily export a number of spatial layers from a Geographic/Catchment scenario in the Source project file. Especially useful is that it allows you to export Links.
For Geographic Scenarios, it's now available under the right-click menu.
Environmental Flow Actions are now in the Feature Table
<Screen shot>
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
RM-19443- Move TimeseriesCycleCreator tool into Source- RM-20177 - Add replicate running configuration to Source
- RM-20189 - Replicate runs in results manager
- RM-20193 - Add sub-run name to res.csv format
- RM-20197 - Support for sub-runs in custom charts
...
Spell Based Actions and Translucency Actions from the Environmental Flow Node are now available to be edited in the Feature Table.
Internal spilling to be specified by Owner
We have added an additional option when using Internal Spilling for Ownership in Storages.
You can enable a single owner to Share Airspace which allows the selected owner to store additional water in its account if there is enough airspace and it does not affect other owners storage.
Replicate runner - First implementation
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.
There are a number of limitations we are continuing to work on. These will be available in future beta releases:
- All data sources are currently cycled, this will be specified in the future (RM-20190),
- Annual Descriptive Statistics doesn't work with sub-runs, this will be the main summary statistics available (RM-20199),
- Runs in series and not in parallel, which is an important performance improvement (RM-20178),
- Limited validation in
...
- User Interface (RM-20180)
...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
- .
Documentation is available here, note it will be updates as Beta releases go so may not match 5.14Beta and contain some documentation from the next releases: Replicate analysis simulations in Source
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.
...
Full Release Documentation
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|