As outlined in Fundamental Concepts, projects act as 'wrappers' for a collection of one or more scenarios. This page outlines how to work with them.
...
| 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 4) 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. Figure 4. Opening a project, error |
Copying a scenario
You can duplicate existing scenarios as a whole, 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.
...
The new (copied) scenario will be a duplicate of the original at the time of the copy.
Figure 5. 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.
Importing scenarios
Source allows you to import scenarios from the same or a different project. This is useful when there are two project files that have related scenarios or scenarios that you wish to bundle together into a single project.
If you have an open project, you can import a scenario by choosing File » Import Scenario. This allows you to select a project, then opens the Import Scenario dialog (shown in Figure 6). Follow the instructions shown in this figure to import a scenario. Note this when loading a project (Step 1).
You can import as many scenarios at a time as are in the loaded project. Click once to select; click again to deselect.
Figure 6. Import scenario
Anchor compscen compscen
Comparing scenarios
| compscen | |
| compscen |
Source also has the capability of comparing two scenarios (both residing in either the same, or different projects) using the Source Difference tool. The goal of this tool is to compare similar scenarios, and is useful when several users are collaborating and making changes to a model. It allows them to view the exact changes made in a scenario.
| Info | ||
|---|---|---|
| ||
| Note: The Scenario Difference Tool can also be accessed in the absence of the Source user interface. |
In Source, the Scenario Difference Tool is used as follows:
- Choose Tools » Diff... to open the Scenario Diff dialog (Figure 8);
- Click Load project for both Project 1 and Project 2. Note this when loading projects;
- Click Find Differences;
- This opens the Choose Scenario... dialog (Figure 7) where you choose how to display the results and click Find Differences; and
- Once the comparison is complete, results are displayed in the bottom half of the Scenario Diff dialog.
Based on the results, the panel on the left self-populates. Select an item in this list to view specific details on the right.
Figure 7. Choosing results display
Figure 8. Scenario Difference tool
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. The section outlines what you must be aware of when copying some parts of a scenario.
- Both functions and modelled variables are copied across, but the copy must also contain any nodes that the modelled variable points to;
- For input sets in data sources, both the source and target scenarios can have different input sets. But, only data related to the matching input set will be copied; and
- Suppose an execution order rule involves two nodes. Copying these nodes from one scenario to another will result in the rule also being copied across.