| Anchor | ||||
|---|---|---|---|---|
|
Once open, you can see that Source follows the user interface conventions of a standard Microsoft Windows™ application (as shown in Figure 6)1. For example:
- The main window can be maximised or minimised using controls at the right hand end of the title bar;
- A menu bar with familiar File, View and Help menus. Additional menus direct you to more specific functions of Source; and
- Toolbars providing point-and-click access to many commands.
Figure 1. User interface for Source
The following toolbars (available from the main Source screen) allow you direct access to various sections of Source:
- 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 - allows you to create a new project, opening an existing project, and saving a project (and all the scenarios within that project);
- Function manager toolbar - allows you to add and manage all functions and expressions in Source;
- Ordering toolbar - provides quick access to ordering-related functions. The button on this toolbar reveals a pop-up menu;
- Project toolbar - allows you to toggle view of the Project Explorer, Recording Manager, Log Reporter and Chart Recording Manager;
- Recording Manager toolbar - allows you to manage results in the Recording Manager;
- Scenario toolbar - allows you to hide or display the Geographic Editor, Schematic Editor and Tabular Editor, the Function Manager, Data Sources, the Node Palette, the Layer Manager and Location Control panels; and
- Simulation toolbar - allows you to set the analysis type (single, stochastic or flow calibration), specify start and end dates for the simulation, and to run the catchment model.
...
The Model Parameters area (refer to Figure 9Figure 2) shows which parameters will be recorded for the scenario element (node, link, catchment etc) that is currently highlighted in the Project Hierarchy. The indicators have the following meanings:
...
Layer Manager
The Layer Manager (Figure 114) is mainly associated with the Geographic Editor. It is visible by default when you create a new catchments scenario. Choose if the Layer Manager is not visible. You can add new layers, and move layers up and down in order of visibility. The checkbox next to a layer’s name indicates that the layer is visible in the Geographic Editor. Note that any layers that are added or removed are not persisted in the scenario.
...
Each node or link type supports different parameters, so the exact structure of feature editors varies according to the type of node or link being manipulated. However, the controls shown in Figure 12 are Figure 5 are common to many feature editors.
The left panel lists all parameters associated with the node or link. You can also add a note to a node or link to indicate a specific feature for example, which may affect its behaviour during a scenario run. This note is indicated as an exclamation mark on the component's icon in the Schematic Editor. It also appears in the Recording Manager after a scenario run. To include a note, right click on the component's icon in the feature editor and choose Add Note. This is shown in Figure 157.
Contextual menus can be accessed by right-clicking on various elements in the user interface. In some cases, choices in contextual menus duplicate those in toolbars and the main menu structure. In others, the contextual menus are the only way to access a particular function. All contextual menus available in Source are shown with the relevant feature editor or graphic;
...
- Parameters applicable to a node or link may be grouped according to related purposes;
- Some user interface elements are only enabled if their prerequisites have been met;
- The ability to search for elements in the hierarchical list, with the result displaying all instances of the query (both parent and child if applicable). Notice that when you enter the search criteria (as shown in Figure 14 Figure 6), the results are displayed in blue. In this case, the term ‘flow’ appears in both the parent and child; and
- When multiple values can be entered for a single parameter, only one value can be adjusted at a time. A highlight (normally blue) indicates the field being manipulated. To edit a different field in this table, click the mouse pointer in the target field.
...
Each of the different message types has a different icon. Figure 15 7 shows an example of an information note added to an Inflow node.
Figure 7. Notes, Overview
If a note can be added to an item, when you right-click on the item the option Add Note will be available from the context menu, refer to Adding notes to nodes and links. The exception is adding notes to a function, which is done using the Add/Edit Note icon in the Function Editor toolbar, see Adding a note to a function.
A summary of all the notes configured in a scenario can be viewed using View » Notes. For the example shown in Figure 16Figure 8, the First inflow andDam nodes, the $AllocGS function and the Default Link #1 link have notes associated with them.
...
Once a scenario containing notes has been run, the notes are listed in the log reporter with a message type of Note. Also listed is the notification level, the name of the associated item (eg. Inflow 1) and the text message. Furthermore, the Schematic Editor shows all the nodes and links that have notes configured on them. Figure 17 9 shows two nodes with informational notes, one with a warning note, and one error note.
...
Date-pickers are used in a number of places within Source. They are a combination of an editable text field and a pop-up calendar. Figure 18 10 shows the relationship between the various components.
...