About Nodes

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.

Figure 1. Node icons for Source

Using nodes in Source

This section outlines how to work with nodes in Source. Some actions can be duplicated for links.

Adding nodes in a model

To add a node to a model, either drag the appropriate type of node from the Node Palette and drop it onto the Schematic Editor, or right-click on the Schematic Editor and choose the appropriate node from the Add menu.

Node and link default names

Whenever a node or link is created, it is given a default name in the pattern:

type #

where "type" is the type of node or link and "#" is a number which increases monotonically during the life of the schematic.

Node connections

Nodes can be joined to each other according to the matrix in Figure 2. Links between nodes will vary depending on the nodes being connected. For example, a wetland conveyance link will occur when a storage node is linked to a wetland connector.

Figure 2. Node connection matrix

Renaming nodes and links

Changing the name of a node or link only alters it in the scenario that you changed it in. A change in one scenario does not propagate to others; they are not linked in any way. You can change the name of a node or link using one of the following methods:

If the Project Explorer is not visible, make it visible either by choosing View » Project Explorer or by clicking its equivalent on the toolbar. In the Project Hierarchy, click the node or link to select it, pause, and click a second time. The name will be prepared for editing (Figure 3 ). Type the new name and press return; or

Right-click the node or link in the schematic and choose Rename. The name will be prepared for editing. Type the new name in the field, then press return.

Figure 3. Renaming a node or link

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 (schematic).

Editing nodes

Use the feature editor of a node to change the parameters associated with them. To open a feature editor you can either double click on the node icon, or right click on the icon and select Edit.

Searching for nodes and links

The Find panel in Source allows you to search for specific nodes and links within open scenarios. Press Ctrl+F to open the Links panel (Figure 4) and enter the search term. The result set indicates the scenario containing the node/link along with its type. This is useful when you are working with very large scenarios.

Figure 4. Find panel

Copying and pasting

You can copy and paste a desired selection of nodes and/or links within the same scenario. Select the desired nodes and/or links, right click and choose Copy. To paste the selection, right click on the Schematic Editor and choose Paste. Any time-series files or settings get copied in this way.

Note: Any expressions associated with the nodes and/or links do NOT get copied.

Deleting nodes and links

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.

Note: Deleting a node will cause loss of any data associated with that node, as well as any links connecting to or from it. A delete operation cannot be undone. You must recreate the link or node.

This chapter describes how the various nodes available in Source can be configured. For details on how they operate, refer to the Source Scientific Reference Guide.

Note: In a catchments scenario, all nodes are, by default, confluence nodes, so every node ever created will be, at least, a confluence.

Browser not supported