The last production release was Source 3.7.

Performance Enhancement Options

We're currently developing a range of performance enhancements which include options that will allow you to change the way Source runs the model. Many of these options will be suitable for the majority of models, but they can cause changes in results for some users, so caution should be used when selecting them. These include:

Parallel Networks

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.

Simultaneous Subcatchments

Source was originally designed to perform subcatchment calculations in sequence from the top of the catchment to the bottom. It is now possible to select a performance option which will allow Source to perform subcatchment calculations in parallel within a timestep. Once again, this is only suitable for subcatchments where values are not called from other subcatchments within the same timestep. This can currently only be done in Source with either using a function or in catchment model plugins.

---

Subcatchments can now be calculated in parallel.

Previously, each subcatchment was calculated as it was encountered on the node-link network.

Now, all subcatchments, including rainfall runoff and constituent generation models, are calculated in parallel.

And then the node-link network is calculated in the normal sequence.

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).

Some models will show significant improvement in load and run times by selecting these options, particularly with larger models.

Namoi Model Run Time

Results

The Results Manager now allows you to set the start/end dates for annual results. This means that you will be able to specify and report on water years.

River Operations

It is sometimes necessary for a river operator to override the modelled storage release. When an operating target is set for the storage, the releases influence the amount of water ordered to try and meet target levels. Overridden releases values are now used to calculate the order the storage sends up stream.

Regression Testing

Regression Test Report including coverage (index.html): 3.8.18beta Regression test report.zip

Regression test repository changes since the first Source 3.8.17beta:
7 Project results changed
14 Projects edited
Continuous accounting projects can give inconsistent results in 3.8.18beta.

Details here: 3.8.18 Regression Test Changes

Insight

To run Insight you also need to install the 32bit version of Microsoft Visual C++ 2010 Redistributable Package.
This is for both 32bit machines and 64bit machines since the library we use is 32bit: Microsoft Visual C++ 2010 Redistributable Package (x86).

Full Release Documentation

type	key	status	summary	assignee	reporter

Loading...

Refresh

Browser not supported