Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Import Link Fixer

Installing Source

Outlined below are the minimum and recommended system requirements for installing Source. Note that software installation may require the assistance of a system administrator.

Minimum requirementsRecommended requirements
  • Windows XP (with service pack 3 and .Net framework);
  • 2Ghz premium processor or equivalent;
  • 2GB RAM (4GB recommended minimum); and
  • 1024X768, high colour, 32-bit;
  • Windows 7 (64-bit);
  • 16GB RAM;
  • A 10,000 RPM hard drive with write caching or a solid state disk; and
  • Upto 500MB 5GB of available space may be required, and maintaining a free hard disk space of at least 8GB 16GB is recommended.

If using Insight, you will also need the Microsoft Visual C++ 2010 Redistributable Package, 32-bit version (for both 32 and 64-bit machines): available here. 

Info
iconfalse
Note: Standard laptop drives are not recommended for optimum performance.

 

 

 

Figure 1. User interface for Source 

...

The individual menus and toolbars, along with the commands they contain, are explained in more detail in the User interface reference chapter.

On start-up, the Welcome screen (Figure 2) appears, which can be used to start a new project or open an existing one. You can also choose from a list of the most recent projects that were open in Source. Additionally, you can report a bug and provide feedback by clicking on Report Bug/Feedback. Note that you must have a working Internet connection for this to work.

...

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 Tools » River Operations 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
iconfalse

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
iconfalse

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

Image Modified

Anchor
Customising views in Schematic Editor
Customising views in Schematic Editor
Customising views in Schematic Editor

...

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

...

The Data Sources tab allows you to view and manage time series at one location in Source. When time series are added using the Data Sources Explorer, they are available for use throughout Source. For more details on using this, refer to Importing data.

Function Manager

The Function manager panel allows you to create, manage and maintain all functions and expressions defined in Source. Just as all data in the Data Sources Explorer is available throughout Source, all functions and expressions added in the Function manager can be used in the same way.

...

Chart Recording allows you to compare the results of different scenario runs. You can change certain parameters in a scenario to see how the output is affected. Refer to Chart Recording Manager for more information on this.

...

Figure 33. Notes, Overview

Image Modified

 

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.

...

  • 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.

Working with date-pickers

...