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. |
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 |
|---|
| Configuring node and link parameters |
|---|
| Configuring node and link parameters |
|---|
|
Configuring node and link parameters
...
- For copying within a single scenario:
- Copied components are given unique names.
- Functions and variables are not duplicated. The function will list both original and copied components as usages.
- 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.
- Functions that are not used by a component are not copied across, even if Force Evaluate is on.
- Restriction curves are fucked.
- If a water user node with configured crop type(s) is copied, the corresponding crop parameter(s) will also be copied across.
- 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.
- To copy constituents and their uses across, first create constituents of the same names in the destination scenario.
- For scenario input sets with data sources assigned to copied network components, both the originating and destination scenarios can have different input sets. But, only data sources related to matching scenario input sets will be copied when you copy across.
- Suppose an execution order rule involves two nodes. Copying and pasting both these nodes within or between scenarios will copy the execution order rule.
- Resource assessment systems are not copied within or between scenarios.
...
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.
...