Scenarios are run to produce results by clicking on button. Each scenario run produces a collection of result sets.

During a run, each nodes in the scenario can produce one or more result sets in the form of Mean Annual Loads (MAL), Node Water Balance (NWB), Treatment Train Efficiency (TTE), water flows, volumes, contaminants loads, concentration and other outputs specific to that node.

Recording parameters

When you run a scenario, Source nodes produce results in the form of MAL and NWB, Treatment Nodes in the form of TTE, MAL and NWB and receiving node in the form of MAL and TTE. These nodes can also produce times series data on flow, contaminants and other data outputs specific to that node. To view or save these model outputs after the run, you need to select them to record before you run. When you save a project or make a copy of a scenario, MUSICX automatically saves the list of model outputs selected for recording. There are two ways to select which parameters and model elements to record, using the Project Hierarchy to select model parameters at the component level (eg. source node, wetland), or more fine-grained parameter-level control in the Parameter pane.

Before running the scenario, give consideration to the required output and only record the parameters of interest. These node types can produce more than 20 separate data outputs. In general, the more outputs you record, the longer the simulation will take.

Component-level controls

For a given scenario run, you can select which outputs will be recorded using the component's contextual menu or the Record icon in the Project Explorer toolbar:

Using the Project Explorer, right-click a group or individual model element in the Project Hierarchy as shown below. From the contextual menu, select:

Record All – every parameter at this level and below will be recorded;
Record None – no parameters at this level and below will be recorded;
If the indicator appears as , some (not all) parameters at this level and below will be recorded.

Parameter-level controls

For fine-grained control of individual recordable parameters as shown below:

Select the group or model element within the Project Hierarchy. Selection causes all of the group's or element’s parameters to be displayed in the Parameters area; and
Use the contextual menu to enable or disable individual parameters or parameter groups.

Using the Log Reporter

If a scenario run results in errors or warnings, the first indication of those is displayed in the Run completion dialogue by a red or yellow icon next to the Close button as shown below:

You can investigate the causes of errors or warnings using the Log reporter as shown below:

If the Log Reporter window is not visible, do either or both of the following:

Choose View » Log Reporter to make it visible; and/or
Make the Log Reporter active by clicking the Log Reporter tab.

Once the Log Reporter is active, you can view all the logs run by MUSIC, from configuring a scenario to running it. You can clear the log or export its contents to a .csv file using the contextual menu (as shown in Figure above).

Scenario results

Note: Results of a scenario run can be viewed in the Results Manager.

Once run, every scenario generates a result set – a distinct collection of results recorded for that run. Scenario results can be examined and analysed using the Results Manager, which opens when a run completes. Within Results Manager, results can be evaluated graphically in charts, numerically in tables or as statistics, and they can also be filtered and manipulated using transforms. With custom charts, you can also view and statistically analyse multiple results within and between runs, compare results to external data sources and automatically update with the latest results each time a model is run. See Results Manager for more information.

In Results Manager, result sets are listed in the tree menu on the left side. The name of scenario's result set is formed by concatenating the run number from the current session with the name of the scenario. Figure below shows the results for a scenario run:

Browser not supported