Figure 1. User interface for Source
...
The Data Sources toolbar allows you to add and manage sources of data (time series or by linking to another scenario). You can edit or view this data once it has been loaded in the Data Sources Explorer.
File toolbar
The File toolbar contains commands for creating a new project, opening an existing project, and saving a project (and all the scenarios within that project).
...
To create an Operations scenario, first create a River Manager scenario. Then, choose to open the River Operations dialog.
Opening a scenario
When a project only contains one scenario, that scenario is opened automatically when you open the project. However, when a project contains more than one scenario, you must open each scenario individually.
...
| Info | ||
|---|---|---|
| ||
Note: You cannot use an earlier version of Source to open a project that was saved by a later version. |
Copying a scenario
You can duplicate existing scenarios. You may want to do this if you wish to experiment with variations without affecting your original scenario.
...
| Info | ||
|---|---|---|
| ||
Note: Catchment runoff is fed into links, so deleting a link that is associated with a catchment effectively stops that catchment runoff from entering the system. When this happens, the catchment boundary is highlighted to indicate that the catchment is disconnected from the network. Follow the steps listed to reconnect the catchment to the network. |
You can also set geolocation coordinates and elevations for nodes and reaches using the Location Control window (using View » Location Control, as shown in figure 12). While it is not essential, it is convenient to set elevations with respect to Australian Height Datum (AHD). You can enter negative numbers for components that are below sea level, such as the lower lakes of the Murray. The elevation of a component is the zero point for that component. For example, the zero point for a storage is the lowest point in the storage.
Figure 12. Location control
| Anchor | ||||
|---|---|---|---|---|
|
...
You can customise the Tabular Editor to your needs. For each type of node or link, you can select:
- A background colour for the cell;
- A foreground colour and stylistic variation (eg. bold-face) for values displayed in the cell; and
- The number of decimal places to be displayed.
...
- By adjusting a set of user preferences. See Tabular Editor Formatting. Changes made via this method apply to all projects; or
- By right-clicking a column heading and choosing Column Formatting (refer to Column formatting). Changes made via this method only apply to the current project.
Column formatting
In this window, the Multiple Expressions tab (as shown in Figure 19) allows you to apply conditional formatting to cells in the tabular editor to highlight when thresholds or rules are breached eg. Flow < 500 ML/day. More than one expression can be applied to a cell. Click Add to specify the details of an expression, and Edit to define the expression using the Function editor. When more than one condition is satisfied, the cell is formatted as per the left side of the panel. Hover the mouse over the cell with the conditional format, and the expression name is displayed. Click Remove to delete an expression from the list.
...
The Column Settings tab allows you to override project-related Tabular Editor Format Settings for the parameters displayed in the Tabular Editor.
Figure 20. Tabular editor, Formatting, column settings
...
Figure 33. Notes, Overview
A summary of all nodes configured in a scenario can be viewed using View » Notes. This opens the Notes dialog (shown in Figure 34) displaying all the notes that have been configured. In this example, the Inflow1 node, the $allocGS function and the Default Link #1 link have notes associated with them.
Figure 34. Notes, Summary
Once all the notes have been added and the scenario has been run, the Schematic Editor shows all the nodes that have notes configured on them. Figure 35 shows nodes with two informational notes, one warning, and one error note.
| Info | ||
|---|---|---|
| ||
| Note: A scenario must be run before the notes become visible in the Schematic Editor. |
Figure 35. Schematic Editor, Notes on nodes
| Anchor | ||||
|---|---|---|---|---|
|
...