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.
...
- 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 Scenario Scenario Types for the different types available); and
- Click OK.
...
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
...
| Anchor | ||||
|---|---|---|---|---|
|
Four scenarios have been described in this guide:
...
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.
...
When copying a partial scenario, the effect on each network element is different, see Nodes and Links - Copying and pasting.
Audit Log
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.
...