| 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
61. 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 Project Explorer (Figure 9) allows you to manage model components using a combination of the menu bar, the Project Hierarchy, the Model Parameters area, and pop-up menus. For an active scenario, clicking an item in the Schematic or Geographic Editor highlights it in the Project Hierarchy.
Figure
92. Project Explorer
Project Hierarchy
The Project Hierarchy displays a structural breakdown of the project. The type of display will depend on the view selected within the View Type pop-up menu on the Project Explorer toolbar. All view options will display at least the project and scenarios within the project. The Default View, which is shown on the left side in Figure 10, displays individual elements that make up a model. The Parameter View displays all the recordable parameters for the model. The Geographic View displays elements of the geographic scenario.
Using the contextual menu (as shown in Figure 9), for a selected node/link, you can set parameter recording, edit and rename it.
Figure
...
3. View type menu options
Model parameters
The Model Parameters area (refer to Figure 9) 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:
...
The Layer Manager (Figure 11) 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.
Figure
...
4. Layer manager
Recording Manager
The Recording Manager displays a list of all the recorded results from the model run or runs. Each model run has its own tab. You can sort the results by clicking the column headings. The associated with this window gives quick access to common functions.
...
Just as with standard Microsoft applications, you can adjust panels within the Source window. This provides great flexibility when working with very large models. Refer to Working with the application window Main Application Window for details.
| Anchor | ||||
|---|---|---|---|---|
|
...
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;
Figure
...
5. Feature editor (common controls)
...
- 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), 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.
Figure
...
6. Inflow node (Search functionality)
Many feature editors support loading parameter information from a file. Where present, the Import... button can be used to load parameters into a feature editor whereas the corresponding Export... button will save the table’s current values to an external file. Additionally, as an alternative to entering or importing discrete parameter settings, the feature editors for many nodes allow for the node’s behaviour to be defined via an arithmetic expression or function (refer to /wiki/spaces/SD520/pages/55214908).
...
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 Adding notes to nodes and links and 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, the $AllocGS function and the Default Link #1 link have notes associated with them.
Figure
...
8. Notes, Summary
Once the scenario has been run, 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. |
Figure
...
9. Schematic Editor, Notes
| Anchor | ||||
|---|---|---|---|---|
|
...
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 shows the relationship between the various components.
Figure
1810. Date-picker
You can edit a date directly by selecting either the Day, Month or Year element within the text field (you cannot select the day of the week). Once an element has been selected, you can also change the selection by using the left and right arrow keys. You can adjust an element’s value by using the up and down arrow keys or by entering a new numeric value. Note that you also use numeric values for the Month element. For example, typing "7" changes the Month element to "July".
...