Running scenarios
Once you have configured the input datasheets for a scenario, you are then ready to run the scenario through the calculations of the package's transformer (i.e. model). The result of running a scenario through a transformer will be to generate one or more output datasheets for the scenario.
Whenever you run a scenario, the first thing SyncroSim does is to automatically spawn a new scenario - called a results scenario - that is an exact copy of the parent scenario (i.e it contains the original scenario's values for all input datasheets). It is this results scenario - rather than the parent scenario - that is then passed to the package's transformer in order to generate model output, with the results of the transformer's calculations then being added to the results scenario as output datasheets (and thus the name "results" scenario). In this way the results scenario contains both the output of the run and a snapshot record of all the model inputs.
Parent scenarios
To run a scenario:
- Select the scenario(s) you want to run in the Explorer.
- Choose Run from the Scenario menu.
Tip
You can also run scenario(s) by right-clicking on the scenario(s) and selecting Run, or by clicking on the Run icon
in the SyncroSim Studio toolbar.

After starting a Run, the Run Monitor will appear and show you the status of the currently running scenarios. Note that you can run multiple scenarios at the same time as long as they belong to the same project.
Results scenarios
Once a model run is complete, a new results scenario will be added to Results subfolder of the original scenario in the Explorer.

In the image above, scenario 2 has been run, as indicated by the green arrow overlay
for its icon. There is also now a Results subfolder containing a single results scenario with an ID of 11. By default the date and time of the model run is appended to the results scenario name.
Note
Results scenarios behave much like parent scenarios. Key differences however include: (1) Results scenarios contain both input and output datasheets (while regular scenarios contain only input datasheets); (2) Results scenarios are always read-only (with the exception of the scenario name, which can be changed after the run); (3) Results scenarios have an additional Run Log Summary Property.