A Source model consists of two parts - a project and one or more scenarios. A project is a collection of one or more scenarios. It identifies the project name (also the file name), description, and any scenarios associated with the project. You can only have one project file open at a time and you should not open the same project file using more than one copy of Source.
A scenario is the representation of a node-link network in Source. The An example of the relationship between a project and a scenario is shown in Figure 51.
Figure
51. Projects and scenarios
A scenario describes the major processes in a river system or catchment that are modelled. This includes catchment and sub-catchment definition, rainfall runoff and constituent generation models, data sets and parameters. You can create multiple scenarios to:
...
In the resulting window (Figure 12), enter the following:
- The scenario name. Once again, provide a meaningful name or accept the default. All the scenarios in a project must have unique names;
- Choose the desired kind of scenario (refer to About scenario types for the different types available); and
- Click OK.
Figure
...
2. New Project dialog
Saving a project
...
To close an open project, choose . This closes the current project and prompts to save your work (Figure 23). Click the appropriate button.
Figure
...
3. Close project
Opening an existing project
...
This opens the standard Windows™ open dialog (Figure 34). Note that opening a new project prompts you to save any open project.
Figure
...
4. Open project
Copying projects
You can duplicate existing projects by copying them. In your local machine's File Explorer, select the desired project, right-click and choose Copy. In the target location, right-click and choose Paste.
...
| Anchor | ||||
|---|---|---|---|---|
|
Three Four scenarios have been described in this guide:
- A schematic scenario is primarily concerned with modelling longer time-scales;
- An operations scenario is primarily concerned with shorter time-scales. It utilises facilities for forecasting and working with unaccounted differences, and typically makes heavy use of the Tabular Editor; and
- A catchments scenario which deals with the management of upland catchment processes. It is usually constructed using the Geographic Wizard for catchments which is a structured sequence of steps that guides you through the construction process.
- A single catchment scenario builder allows to build a simple catchment scenario to be used for testing purposes.
It is important to choose the correct type of scenario before you start building your model. Although a project can contain several scenarios, a scenario type is fixed once it is created and cannot be changed later. Note that scenarios are independent of each other; a change in one scenario does not impact another scenario.
...
| Info | ||
|---|---|---|
| ||
| Note: You can only create a schematic or catchments scenario using the method outlined below. To create a forecasting scenario, refer to Creating a scenarioForecast scenarios. |
A project must contain at least one scenario. Whenever you create a new project, you are also prompted to create a scenario. You can create additional scenarios using any of the following methods:
...
| Info | ||
|---|---|---|
| ||
Note: You must upgrade a project if it was created in Source v3.1.0 or earlier. If you open these projects in later versions of Source, an error message (shown in Figure 45) will appear prompting you to save in v3.1.0. Follow the steps outlined in the dialog to automatically upgrade the project to the current version of Source. Figure45. Opening a project, error |
Copying a scenario
You can duplicate existing scenarios, provided they are part of the same project. You may want to do this if you wish to experiment with variations without affecting your original scenario.
| Info | ||
|---|---|---|
| ||
| Note: To copy only certain network elements, refer to Copying network elements. |
To duplicate a scenario, click Copy Scenario on the Project Explorer toolbar. Source makes a copy of the current scenario and asks you to name the copy (as shown in Figure 56). You can either accept the proposed name or supply one of your own. Keep in mind that scenario names must be unique within a project.
The new (copied) scenario will be a duplicate of the original at the time of the copy.
Figure
56. Copy Scenario
Renaming a scenario
Source automatically gives new scenarios the default name of "Scenario #n" , where n is a number. To rename a scenario:
- Select the scenario in the Project Hierarchy; and
- Once the scenario name is selected, pause then click again. When the entry is highlighted, you can enter a new name. Remember that scenario names must be unique within a project.
Linking scenarios
You can link two scenarios using a Connecting Models. Note that some components of the first scenario may not pass on to the second, linked scenario.
Anchor compscen compscen
Comparing Scenarios
| compscen | |
| compscen |
The full version fo of Source has functionality for determining the difference between scenarionsscenarios. For more information please see Troubleshooting and Debugging.
Anchor Copying network elements Copying network elements
Copying network elements
| Copying network elements | |
| Copying network elements |
When copying a partial scenario, the effect on each network element is different, see Nodes and Links - Copying and pasting.
Audit Log
Figure 1. Audit Log Commit Message
The audit log keeps track of the changes made to a project over time. This is particularly important for projects that are worked on by multiple people. It contains a combination of software generated information on model changes and provides an opportunity for users to annotate the purpose of those changes with a commit message when the project is saved.
Figure 7. Audit Log Commit Message
Commit messages are used to group software generated logs in a way that makes sense to users working on the project. If the same issue is being worked on in multiple concurrent sessions, you can select Merge with current task to group the logs under the previous commit message.
Figure
28. Audit Log Viewer
A large audit log attached to a project can become a processing burden, especially in the case of large projects. Audit logging is on by default, but can be disabled in Edit »Project Options» Audit Log Settings by toggling off Enable Logging.
Figure
39. Project Options, Audit Log Settings
...