A MUSICX 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 MUSICX.
...
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.
Scenarios
Working with scenarios
Scenario management
Various menu items allow you to manage scenarios at a high-level.
...
Creating a scenario
Note: You can only create a schematic or catchments scenario using the method outlined below. To create a forecasting scenario, refer to Forecast 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:
- Choose
- Click New Scenario on the File toolbar; or
- Click New Scenario (by menu) on the Project Explorer toolbar.
To create an Operations scenario, first create a Schematic scenario. Then, choose Tools » Rivers Operations
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. To view a scenario that is contained within a project, double click the scenario name from the list in the Project Hierarchy. This opens the appropriate editor for the selected scenario, and changes the scenario name to a bold appearance so that you know it is the current, or active scenario.
You can also select a scenario from the list of loaded scenarios on the View menu. Selecting a scenario from the list makes it active.
Source supports backward compatibility for projects created in Source after v3.1.0.
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 5) 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 5. 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.
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 MUSICX makes a copy of the current scenario and asks you to name the copy (as shown in Figure 6). 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 6. Copy Scenario
Renaming a scenario
Source automatically MUSICX 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.
Comparing Scenarios
The full version of Source has functionality for determining the difference between scenarios. For more information please see Troubleshooting and Debugging.
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
...
- a
...
- project
...
- .
...
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 8. 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 9. Project Options, Audit Log Settings
...