| 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 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.
...
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 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 9 shows two nodes with informational notes, one with a warning note, and one error note.
...
- You should always include an explicit origin of (0,0). This avoids the need for the model to extrapolate in the negative direction along the X-axis. It also avoids any potential problems which might arise if the model silently assumes an origin of (0,0);
- X-values should always be in monotonically increasing order. In the current implementation, an X-value that is entered out of order is highlighted in red until a Y-value is entered, after which Source re-orders the table. You can use this feature to add interstitial coordinates to a table by adding new (X,Y) coordinates to the last row and waiting for the table to re-order;
- Y-values should also increase monotonically. Be cautious if you need to violate this guideline, and especially cautious if the right-most line segment has a negative slope;
- The right-most coordinate pair should lie beyond your most extreme known value. This avoids the need for the model to extrapolate in the positive direction along the X-axis, and also means that you do not need to remember which piecewise linear editors use linear extrapolation of the right-most line segment vs those which project the right-most Y-value to infinity;
- All values should be sensible. For example, there is no point in entering coordinate-pairs that violate mass balance (eg. a loss exceeding inflows); and
- If your model employs optimised ordering, keep your piecewise linear editors to as few data-points as possible. Complex curves usually increase run-time and can sometimes lead to infeasible solutions. Refer to the chapter on Ordering.
| Anchor | ||||
|---|---|---|---|---|
|
...