...
- Build and run a catchments scenario that models water quality constituents;
- Develop river operator scenarios to support day-to-day operations;
- Input data in several ways, including with the Function manager or the Climate data Import tool;
- Use additional analysis tools and plugins; and
Run and analyse the results using either the command line or the user interface.
Restrictions on functionality are detailed below:
- Limited Node palette (i.e. not all nodes are available)
- Limited to 20 Nodes & Catchments in total (excluding confluence nodes)
- Simple Function editor
- Simple Calibration tool (limited to 1 objective function and 1 calibration engine)
- Plug-in capabilities but specific Plugins will be available separately via the Plugin Store
- Basic IT/Installation support included
- Some scenario management tools are not available (such as Import/Copy Scenario Functionality, Scenario Diff tool and Scenario Input Sets)
- Some edit tools such as Feature Table and Tabular Editor
- User Logs (Note: it is not Log Reporter) are no available
- NetLP optimisation is not available
- GN1D groundwater flux model are not available
- Constituents and Water Quality models (i.e., Constituents generation, Constituents filters, Routing and Storages) are not available
Details of what Source Modules are available here: https://ewater.org.au/products/ewater-source/ewater-source-access-and-pricing-policy/
| Info | ||
|---|---|---|
| ||
In the user guide, content that is not available in Source (public version) is identified on the relevant pages. |
These components of Source are not available in Source (public version).
Context variables
...
Full Function Editor (limited functionality)
Only /wiki/spaces/SD516/pages/54986558 is available in Source (public version). Most types of variables including /wiki/spaces/SD516/pages/54986558, /wiki/spaces/SD516/pages/54986558, /wiki/spaces/SD516/pages/54986558 , /wiki/spaces/SD516/pages/54986558 and /wiki/spaces/SD516/pages/54986558 are not available in Source (public version).
- /wiki/spaces/SD516/pages/54986558 - creates a dataset of repeating time-dependent values (eg. daily or monthly pattern). Value used is based on the current simulation date and time;
- /wiki/spaces/SD516/pages/54986558 - uses a time series data source as input. Value used is based on the current simulation date and time;
- /wiki/spaces/SD516/pages/54986558 - creates a lookup table that interpolates a Y value based on an X value.
- /wiki/spaces/SD516/pages/54986558 - similar to a piecewise linear variable, but allows you to look up and interpolate between values in two dimensions;
- /wiki/spaces/SD516/pages/54986558 - for applying the same function in a number of locations that use modelled variables.
Off allocation node
The off-allocation flow sharing node is used to determine how much off-allocation flow is available in the river (at the node), as well as how to share this between the downstream water users that have licence shares. Off-allocation flows are those that are in excess of regulated requirements. They can be generated from unallocated tributary inflows downstream of storages, and from storage spills.
Bulk Licensing node
The Bulk Licensing Node is used to represent an administrative arrangement where a group of water users share a common portfolio of accounts.
Ownership and the Transfer of Ownership node
...
To manage the transfer of flow between owners at a given point in an ownership system; or
To act as a boundary between adjacent ownership systems by managing the transfer of orders and flow at the boundary.
Scenario Transfer node
The Scenario transfer node (STN) handles the joining of two scenarios and conceptually comprises of two components, the Upstream STN and Downstream STN (as shown in Figure 1). The node links two scenarios and runs them together. Constituents, orders and ownership are passed between the two scenarios. However, off allocation does not operate over scenarios, instead, the STN operates like an off allocation boundary - similar to the Transfer Ownership node.
NetLP Parallel Arcs node
The NetLP Parallel Arcs node allows you to define multiple parallel arcs with different capacities and costs at a particular location, to influence the flow in a network. Each arc can be used to represent different flow requirements at a location, such as an environmental or hydrological demand, or flood flow. Note: This node can only be used in NetLP-based ordering.
Resource assessment
Many regulated river systems support several resource assessment schemes to share the available resource (water) among users. In Source, a resource assessment system:
...