Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A Source model consists of two parts - a project and one or more scenarios. A project is a wrapper for a collection of one or more scenarios. It identifies the project 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.

...

Info
iconfalse

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. 

Anchor
compscen
compscen
 Comparing Scenarios

The full version fo Source has functionality for determining the difference between scenarions. For more information please see Troubleshooting and Debugging

Anchor
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

    , see Nodes and Links - Copying and pasting.