Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Version 5.0 includes three significant features:

  • Urban Developer... 

Urban Developer

eWater’s Urban Developer Tool gives water managers the ability to undertake a detailed analysis of household demand, taking into account the range of dwelling types, how water is used and the water efficiency of different appliances and fittings. Urban Developer is now available as a plugin for eWater Source, allowing for a more sophisticated assessment of urban water demands to be integrated within the Source modelling framework.

With Urban Developer you can assess the full range of indoor and outdoor water uses for four types of dwellings, detached house, detached house with a rainwater tank, semi-attached house and apartments. It generates a database of average water demand for every combination of household type, occupancy and end-use, for the given climate. Urban Developer takes into account the full range of water efficiency End-uses include showers, hand taps, toilets, washing machines, dishwashers, pools and outdoor use.

image2019-2-1_9-19-58.pngImage Added

Urban Developer helps water managers understand things like:

  • the potential demand savings from different water-efficiency measures
  • the impact on demand when dwelling types change, for example, detached housing is replaced by apartments
  • the volume of non-potable household demand that could be replaced by alternative water supplies
  • the effect of potable water substitution on water storages and distribution networks

MUSICX

MUSIC - Model for Urban Stormwater Improvement Conceptualisation) is Australia’s leading tool for water sensitive urban design. MUSIC is used by urban developers, planners, engineers, local government and development approval agencies to manage the impact of urban development and other land-use changes on waterways. MUSIC can:

  • simulate urban stormwater systems from the individual lot to suburb scale
  • estimate the potential for stormwater harvesting and reuse and understand the effects on downstream flows and water quality
  • model pollutants, including suspended solids, total phosphorus and total nitrogen
  • compare the water-quantity, quality and cost/benefit objectives of different treatment options, such as swales, bio-retention system, rainwater tanks, wetlands etc
  • design urban development proposals that meet WSUD standards.

eWater has recently released MUSICX, the most significant upgrade to MUSIC in a decade. MUSICX will soon be available as a plugin to Source. 

Tools for integrated water management

The release of Urban Developer and MUSICX as plugins to Source gives water managers a powerful tool for developing integrated water management solutions, allowing them to consider water quality and quantity, at the catchment and local scale.   

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 linked to eWater Source catchment and river system models. Allowing you to explore possible interactions between different components of the water cycle and evaluate demand and water supply options together, to understand the best balance of traditional water supply, demand management and alternative water supplies, such as the use and recycling of stormwater, wastewater and groundwater.

Improvements to Source

Source 5.0 also includes a range of upgrades and enhancements, as described below.

Date Range changes

Could this be under minor?

...

In a later Beta release, we will implement a utility to convert across while keeping results consistent as much as possible along with user interface improvements to help users understand Date Ranges better.

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:

...

Source.DataUtility.exe - eWater Source Time Series Data Utility                                                                                                                                                                                              
Usage:                                                                                                                                                                                                                                                       
        -?, --help[optional]... Show usage help                                                                                                                                                                                                              
                                                                                                                                                                                                                                                               
        -i, --input[optional]... Input file to read timeseries from. All standard TIME timeseries formats are supported.                                                                                                                                     
Example: -i "Run1.sdb" or -i "Run1.res.csv"                                                                                                                                                                                                                  
                                                                                                                                                                                                                                                               
        -o, --output[optional]... Output file to save timeseries to. The extension selects the output format based on the standard TIME I/O formats. A directory of the name specified will be created if the format only supports a single timeseries.      
Example: -o "output.res.csv" for Source Results CSV or -o "output.sdb" for SourceDB etc.                                                                                                                                                                     
                                                                                                                                                                                                                                                               
        -k, --key[optional]... Key of a timeseries to output. This can appear multiple times. If no keys are specified then all timeseries will be exported. Use the '--list' option to list timeseries in the input file. The DisplayName is used as the key.
Example: -k "someResult" -k "someOtherResult"                                                                                                                                                                                                                
                                                                                                                                                                                                                                                               
        -q, --query[optional]... SourceDB filter query. Use the '--list' option to list timeseries in the input file together with possible MetadataKeys to filter on.                                                                                       
Example: -q "WaterFeatureType=Storage" -q "ElementName=Storage Volume"                                                                                                                                                                                       
                                                                                                                                                                                                                                                               
        --startTime, --st[optional]... Start time for extracting partial results. If not specified the start of the input timeseries is used.                                                                                                                
Example: --st 1/1/2011                                                                                                                                                                                                                                       
                                                                                                                                                                                                                                                               
        --endTime, --et[optional]... End time for extracting partial results. If not specified the end of the input timeseries is used.                                                                                                                      
Example: --et 31/12/2011                                                                                                                                                                                                                                     
                                                                                                                                                                                                                                                               
        -l, --list[optional]... List the timeseries and metadata contained in the input timeseries file. Standard output may be redirected to a '.json' file.                                                                                                
                                                                                                                                                                                                                                                               
        -a, --addOrReplace[optional]... Add input timeseries to an existing output SourceDb (.sdb) file. Existing timeseries with matching metadata will be replaced. Only supported for SourceDb output files.                                              
Example: --addOrReplace                                                                                                                                                                                                                                      
                                                                                                                                                                                                                                                               
        -f, --force[optional]... Don't prompt for confirmation when overwriting an existing file.

Performance improvements for the command line and Service interface

We have done some work to improve the performance of the command line, less memory (RAM) is now used during a run.  Run times have been reduced in the command line.

...

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

...


Summary of minor changes

  • We have introduced the concept of Locking to the Function Modelled Variables, selected variables can now be locked, making it less likely for mistakes to occur. 

  • Ordering for the Irrigator demand model now includes an option to make the Flow phase and Order phase identical.

  • Data Sources can now find data based on the column name rather than the index. Being able to match by name is important when using Reload on RunMatch data items by Name is now the default option.
    It will validate and fail to run if you are matching based on name and reload a file with duplicate names.

  • The Operations Tabular Editor now allows you to copy-paste into multiple cells and view charts directly in the Results Manager. 

  • We have made changes to significantly improve performance for editing and saving in some large models, for one project this reduced the time to save from 12 minutes to 45 seconds.
  • Constituent Trend and % removal model. Links and Storages decay models have been extended to include a decay to a background concentration rather than to 0 and a % removal that can occur after the decay.

  • Annual Accounting recorder changes. Some annual accounting recorders at RAS system level were giving incorrect values. The recorded values of "Total account spill reduction", "Total usage water year" and "Total Account Adjustments" at RAS system level values will change. See RM-18149 for details.
  • The order crawler recorder is a new recorder to show all the nodes and links in a network and what their orders and requirements are on a particular date.  Available under: Miscellaneous \ Ordering \ Order Crawler. The Order Crawler is a fully interactive zoomable schematic. Note that for large networks, it does record a lot of data and is primarily for problem-solving and not intended to always be turned on.
  • Ownership adjustment for storages and weirs - End of day volumes in Storages and Weirs can now be adjusted.
  • Custom charts now include a search bar and more menu items under right-click. Customs charts are also no longer saved by default. All automatically generated charts are created under Temporary and only saved when moved into Saved. Users can also create folders and subfolders for organising custom charts.

...