Anchor
| Anchor | ||||
|---|---|---|---|---|
|
...
- 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.
Quitting Source
You can quit Source by doing either of the following:
...
If you have not saved your project previously, choose and you will be prompted to name your project. Source uses the Windows file extension ".rsproj" to identify its project files.
Editors
Source uses editors which are tailored to the needs of the main scenario types. There are three main editors, known as the Geographic, Schematic and Tabular editors, which support the catchments, management and operations scenario types respectively. These editor-scenario type associations are not absolute and you will often use multiple editors within a given project. For example, you can use the Schematic Editor to define the model of a river system for both operations and management scenario types. Details for each of these editors are available at Geographic Editor, Schematic Editor and Tabular Editor. You can also view scenarios on a background map image using the Map tab.
...
Figure 5. Feature editor (common controls)
...
You can include a text based message associated with a node, link or function, function, or item in a Resource Assessment System, which can be have a notification level of either:
- Information;
- Warning; or
- An error.
Each of the different message types has a different icon. Figure 15 shows an example of an information note added to an Inflow node.
Figure 7. Notes, Overview
Refer 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 and . 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 for more information.
A summary of all the notes configured in a scenario can be viewed using View » Notes. For the example shown in Figure 16, the Inflow1 node First inflow andDam nodes, the $AllocGS function and the Default Link #1 link have notes associated with them.
Figure 8. Notes, Summary
Once the 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 shows two nodes with informational notes, one with a warning note, and one error note.
| Info | ||
|---|---|---|
| ||
| Note: A scenario must be run before the notes become visible in the Schematic Editor. |
...