Source 3.8.11beta is ready for download and testing. Changes include lots of small issues, some are highlighted here:
- Run without needing to configure first!
- Scenario Transfer Node - for connecting two scenarios in the one project
Jira Legacy server System JIRA serverId c4ca6e0fa22b5711-9f422728-3d1a3bcc-879c860f-870abe699ab12832d905a432 key RM-13657 - Orders can go up stream from the downstream scenario to storages in an upstream scenario
- Flow and constituents flow downstream
- Node acts like a minimum flow node when not linked
- Use with Scenario Import to link basin models!
Projects will be modified during backwards compatibility to ensure results don't change as a result of: Jira Legacy server System JIRA serverId c4ca6e0fa22b5711-9f422728-3d1a3bcc-879c860f-870abe699ab12832d905a432 key RM-12829 - Projects will have execution order rules added to the project
- Ownership in Catchments - still needs testing
- Results viewer:
- When trying to filter results you should hold Ctrl to get Dora to filter to the node
Jira Legacy server System JIRA serverId c4ca6e0fa22b5711-9f422728-3d1a3bcc-879c860f-870abe699ab12832d905a432 key RM-13845 - Melbourne Water plugins are now ready to go in new structure
- Annual descriptive stats
- New Mass balance tool
- Dora Transform: Aggregate Time Series to Monthly or Annual (still needs water year)
- When trying to filter results you should hold Ctrl to get Dora to filter to the node
- Charting changes - Lots of them including:
- import background image on charts
- drag drop into other tools and
- be able to place chart title and legend outside chart frame
- Copy Paste within and between scenarios - now also includes:
Execution order rules
Still doesn't include:- Constituents
- Catchments (including Rainfall runoff models / constituent generation)
- Ownership
- Resource Assessment - we now have a plan for Resource Assessment
...
Full Release Documentation
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|