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 options available); and
- Click OK.
| Anchor | ||||
|---|---|---|---|---|
|
- MUSICX: This option is to create a standard MUSICX scenario
- MUSIC-link: This option is to create a MUSIC model with embedded guidelines approved by local authorities. Please see here.
- MUSIC-MSF Importer: This option is to import existing MUSIC model (MSF files) into MUSICX. Further details are here.
Saving a project
To save an open project, choose . This saves a project file with the extension *.mxproj. If it is the first time you are saving your project, the Save As dialog opens and gives you the opportunity to choose the location and name of your project file. By default, the name of the file is the name of your project. If you wish to save a different version of your file, choose
...
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
...
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.
...
Working with scenarios
Scenario management
...
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.
...