Page Comparison

...

Version 5.0 includes the release of Urban Developer and MUSICX functionality as plugins to Source. This is a significant step forward for Urban water analysis. By using these three tools together, water managers have the ability to assess and plan for truly  truly integrated water management solutions, that consider water consider water quality and quantity, at a range of scales.      

MUSIC and Urban Developer were originally designed to complement each other, to draw together information on urban water quantity (Urban Developer) and water quality (MUSIC) to develop integrated water management solutions in urban areas. These models can now be integrated with eWater Source catchment and river system models. This allows users to analyse interactions between different components of the water cycle and jointly evaluate demand and water supply options.  This   This provides water managers with the tools to understand the best balance of traditional centralised bulk water supply, demand management and alternative water supplies, including the use and recycling of stormwater, wastewater and groundwater.

Question - should we acknowledge the investment by Melbourne Water and us?
GD:I think it would be good to acknowledge them.  Yep.  But need to run it past them first.  Also need to acknowledge the broader urban beta testers etc?We would like to acknowledge the leadership and financial support of Melbourne Water to enhance Urban Developer and the contribution of our urban beta tester group, who have played a key role in making sure that Urban Developer and MUSICX are fit for purpose.

Source 5.0 also contains a broad range of other upgrades and enhancements to the platform, including changes to support river operations management, a new ordering system analysis tool, a range of performance improvements, and greater control over the interaction between planned constraints on supply, planned orders, and water deliveries.

...

We have been working with the MDBA to operationalise Source in operations mode. A focus has been enhancements to the Operations Tabular Editor. The editor is now more stable, easier to use, allows you to seamlessly add and remove nodes and is independent of the recorder selection.

NB: Geoff D to add a new pictureRecorders are now selected using the new column editor:

Image Added

The tree on the left has also had significant improvements:

Image Added

A new recorder for analysing orders

...

The function system has been augmented to provide more information around when constraints happen, to make information available earlier and finer control over function execution during the ordering process.     Just put a link for the below to a confluence page ...

Phase logic has changed from:

...

1. Evaluate functions and modelled variables - where Time of Evaluation equals Order Phase and where the function is not used at a network element.
   
2. Process Water Users: 
   1. Water User order calculations can be run in Parallel at this point in the ordering phase with the option enabled: "Process Water User Orders in Parallel": Scenario Options \ Performance
   2. For each Water User:
      1. Evaluate functions and modelled variables - where Time of Evaluation equals Order Phase, and where the function is used at this Water User.
         
      2. Calculate and distribute the demands of each Water user.
3. Constraint Phase:
   1. For each Network Element:
      1. Calculate minimum and maximum constraints at each element and pass the constraints downstream.
4. Ordering Phase:
   1. For each Network Element:
      1. Evaluate functions and modelled variables - where Time of Evaluation equals Order Phase, and where the function is used at this network element.
      2. Calculate regulated orders and pass upstream.
      3. Calculate off allocation orders and pass upstream.

To:

...

10. Water User and Constraint Phase

1. Evaluate functions and modelled variables - where Time of Evaluation equals Water User & Constraint Phase and where the function is not used at a network element.
2. Process Water Users: 
   1. Water User order calculations can be run in Parallel at this point in the ordering phase with the option enabled: "Process Water User Orders in Parallel": Scenario Options \ Performance
   2. For each Water User:
      1. Evaluate functions and modelled variables - where Time of Evaluation equals Water User and Constraints Phase, and where the function is used at this Water User.
      2. Calculate and distribute the demands of each Water user.
3. Constraint Phase:
   1. For each Network Element:
      1. Evaluate functions and modelled variables - where Time of Evaluation equals Order Phase, and where the function is used at this network element.
      2. Calculate minimum and maximum constraints at each element and pass the constraints downstream.

11. Ordering phase:

1. Evaluate functions and modelled variables - where Time of Evaluation equals Order Phase and where the function is not used at a network element or is used at a Water User.
2. Ordering Phase:
   1. For each Network Element:
      1. Evaluate functions and modelled variables - where Time of Evaluation equals Order Phase, and where the function is used at this network element.
      2. Calculate regulated orders and pass upstream.
      3. Calculate off allocation orders and pass upstream.

The important thing to note is that the timing has changed.

Example: A function assigned to a Water User, that says it evaluates in the Ordering Phase, will now happen later than it previously did. To evaluate it at the same time as it did in v4.11, the time of evaluation needs to be moved to the Water User & Constraint Phase. To minimise the effect in splitting this phase in two, we've written some migration code.

The logic is:

• IF a function or modelled variable has a time of evaluation of 'Ordering Phase' (in v4.10.1)
• AND it is used on a model that is either:
• a Non-Network Element (e.g. Resource Assessment, Env Flow Manager)
• a Water User
• THEN move its time of evaluation to 'Water User & Constraint Phase'

also

• IF a function or modelled variable has a time of evaluation of 'Ordering Phase' (in v4.10.1)
• AND it is not used anywhere
• AND it has Force Evaluate set to On
• THEN move its time of evaluation to 'Water User & Constraint Phase'

otherwise, we leave it as 'Ordering Phase'

Limitations

We know our migration codes is not perfect:

• We don't cater for Functions activated via input sets. 
• Functions not used on a model, but only used by other Functions will not be moved

Recommended steps

We recommend you review any functions that are evaluated in the ordering phase and ensure they are configured correctly using: Edit \ Feature Table.. \ Functions.

Backward compatibility steps are detailed here: A new Water User and Constraint Phase

Results Streaming

Results can now be streamed to files on disk rather than stored in memory. This is to prevent memory issues with large runs.  Results streaming is off by default, however, it can be turned on in Project Options:

Image Modified

The format used (called Source Time Series Database .sdb) is now also available as a general time series format.  There is also a new command line utility for interacting with the format: Source.DataUtility.exe run with --help to see the instructions for interacting with the utility.

...

1. NoOutput - Does not save results anywhere, hence does not fetch results either. Can be used where the result data files are ignored. E.g. in tests, or where a plugin gives a different pathway to results. This improves performance when using automatic exporting tools such as Scenario Options: Simulation results or Simulation Log which automatically exports results after each run to a specific location. 
2. ClientNamedFormat - Results fetched to client, saved to output file from there, in a format based on output file extension. The data is transferred back to the client and saved (current behaviour).
3. ServerNamedFormat - Results saved to output file directly from server, in a format based on output file extension. Does not fetch results to client. This "server side" save is more efficient. Default for InProcess mode, since "server side" is local here. Can be used in Client mode, assuming the end user has access to the path provided to the server e.g. a network drive.

...

Some results have changed between Source 4.11 and Source 5.0. Result changes are mostly around the Pipe Junction node, Weir infiltration, and Constituents in wetlands. Details are available here: 5.0 Result Results and Configuration Changes from 4.11