Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Import Link Fixer

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 in the Feature Table,
  • Internal spilling can be specified by the Owner,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.  

Image Added

Environmental Flow Actions are now in the Feature Table

Spell Based Actions and Transluency Translucency Actions from the Environmental Flow Node are now available to be edited in the Feature Table.  

Image RemovedImage Added 

Internal spilling to be specified by

...

Owner

Jira Legacy
serverJIRA
serverIdc4ca6e0f-9f42-3d1a-879c-870abe699ab1
keyRM-19913

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.

Image Added

Replicate runner - First implementation

We have started to implement a replicate runner within Source for applications such as a risk of spill assessment.

Jira Legacy
serverJIRA
serverIdc4ca6e0f-9f42-3d1a-879c-870abe699ab1
keyRM-20198

...

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.

Image Added

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 (RM-20178) , which is an important performance improvement (RM-20178), 
  • Limited validation in UI User Interface (RM-20180)

Jira Legacy
serverJIRA
serverIdc4ca6e0f-9f42-3d1a-879c-870abe699ab1
keyRM-19601

  • .

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
serverSystem JIRA
columnstype,key,status,summary,assignee,reporter
maximumIssues150
jqlQueryfixVersion in (5.14beta) order by issuetype
serverIdc4ca6e0fa22b5711-9f422728-3d1a3bcc-879c860f-870abe699ab12832d905a432