Contents
| Table of Contents | ||||
|---|---|---|---|---|
|
About Nodes
| Info | ||
|---|---|---|
| ||
| The following nodes are not available in Source (public version): Off-allocation and Transfer Ownership. |
Nodes represent places where actions or measurements occur in a river system, where water can be added, extracted, stored, recorded, or change ownership in a model. A node can be used to represent things that actually happen over a large physical area but that, for modelling purposes, occur at a single point. In sub-catchments, they provide a position in the catchment network where water management information can be placed. In Source, nodes are depicted using the icons shown in Figure 1.
| Info | ||
|---|---|---|
| ||
| Note: This section describes how nodes can be configured in Source. For the scientific background behind their operation, refer to the Source Scientific Reference Guide. |
Figure 1. Source node icons
Using nodes in Source
This section outlines how to work with nodes in Source. Some actions can be duplicated for links.
...
Figure 2. Renaming a node or link
| Info | ||
|---|---|---|
| ||
Note: Source does not support duplicate names for nodes or links and will warn you if there is one. You must ensure that the names you choose are unique to the scenario. |
| Anchor | ||||
|---|---|---|---|---|
|
...
You can copy and paste a selection of nodes and/or links within or between scenarios in the same project. For multiple component selection, you can click and drag to draw a rectangle over the region with your mouse. Right click and choose Copy. To paste the selection, right click on the Schematic Editor and choose Paste.
The section outlines what you must be Be aware of the following when copying some parts of a scenario.
- For copying within a single scenario:
- Components copied and pasted that have functions that reference components inside the copied selection will maintain their relative references in the new functions, with new component names; and
- Functions that reference a component outside of the copied selection will maintain the same reference.
- For copying between scenarios:
- Both functions and modelled variables are copied across, but the copy must also contain any nodes that the modelled variable points to
- .
- Copied functions will be pasted
- into a new folder
- named From<OrginatingScenarioName>. This is to prevent duplicate function names by giving them a unique absolute path.
- Components copied and pasted within a single scenario that have functions that reference components inside the copied selection will maintain their relative references in the new functions, with new component names. Functions that reference a component outside of the copied selection will maintain the same reference
- Functions that are not used by a component are not copied across, even if Force Evaluate is on.
- Resource assessment systems are not copied across.
- Constituents and their uses are not copied across unless you have created a constituent of the same name in the destination scenario.
- Scenario options are at the scenario level, so are not copied. To maintain settings of nodes and links that are affected by scenario options (eg. the Storage Processing Method), ensure both originating and destination scenarios have the same scenario option configuration before copying and pasting.
- For scenario input sets with data sources, both the originating and destination scenarios can have different input sets. But, only data related to
- matching scenario input
- sets will be copied
- .
- Suppose an execution order rule involves two nodes. Copying these nodes from one scenario to another will result in the rule also being copied across.
...
Deleting nodes can be achieved simply by selecting the node and pressing the delete key, or by right-clicking it and choosing Delete from the contextual menu. Deleting a link removes only the link. Deleting a node removes both the node and any links that were attached to the node.
...