...
Networks with multiple outlet nodes can be configured to run separate networks (multiple outlets) simultaneously. This should not be selected as an option if there are calculation dependencies across the separate networks, e.g. Subnetwork 2 calls a function which involves a value from Subnetwork 1.
...
Now, all subcatchments, including rainfall runoff and constituent generation models, are calculated in parallel.
...
Water User Orders
Orders generated by water users were previously calculated sequentially from the bottom to the top of the system. Orders are now generated simultaneously within a timestep and passed to the supply points. In 3.8.18beta, this is now the default option for ordering. In a small number of cases that use continuous accounting, the sequence of water user orders may change the results. Future versions will allow for the parallel water user option to be turned off if necessary, but most users should be able to utilise the improved performance option without issue.
Audit Log
The audit log keeps track of the changes made to a project over time. This is particularly useful for projects that are worked on by multiple people over a period of time, but can become a processing burden, especially in the case of large projects. It is now possible to disable and clear the audit log (Edit » Project Options).
...
Full Release Documentation
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|