...
- 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.
Note: The contextual menus shown in Figures 6 and 7 can be applied at any point within their respective hierarchical displays. If you select an individual model element, the effect will be limited to just that element. Applying a recording choice to a group propagates the effect to all elements grouped below it in the hierarchy. For example, to record only Downstream Flow for all straight-through routing links, you would select Link » Straight-Through Routing and choose Record None (Figure 6), and then select Downstream Flow in the Parameter pane and select Record All (Figure 7).
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 indicated in Figure 7.
Figure 7. Running scenario (error)
shown below:
You can investigate the causes of errors or warnings using the Log reporter (Figure 8). If as shown below:
If the Log Reporter window is not visible, do either or both of the following:
...
Once the Log Reporter is active, you can view all the logs run by SourceMUSIC, 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 8). Table 1 provides a description of each of the columns in the Log Reporter.
Figure 8. Log Reporter
Table 1. Log Reporter, Columns
...
Column
...
Description
...
There are three types available:
- Admin - These are general administration messages and are generally logged from non-runtime sources such as an inability to parse a function;
- Note - These are user-generated notes added throughout the system; and
- Run time - These are generated throughout the simulation run. Some of these are user-configurable Assurance Rules.
Execution order rules
During a scenario run, components of the scenario are run in a particular order to ensure that they comply with inbuilt Simulation phases and execution order rules.
Note: The execution order is based on leaf node names alphabetically. Thus, renaming a node can change the order.
Execution order rules are now available in Scenario Options: Execution Order Rules
above).
Scenario results
Note: Results of a scenario run can be viewed in the Results Manager or using the Recording 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.
...