Run MSO Scenario

The Run screen is where scenarios are queued and executed by MSO.

This screen differs from those earlier in the workflow in that the full MSO ribbon is replaced by a streamlined version containing the following items:

• Edit Scenarios – This is where scenarios are managed and run.

  Note: Click Edit Scenarios to reinstate the 'full' MSO ribbon view and display most recently displayed screen.

• Settings – Display the Processing Settings screen to configure solver and processing behaviour before adding jobs to the queue.

• Review – Visualize scenarios outputs once completed, using the Review screen.

An MSO "run" is tied to a particular scenario or batch of scenarios. Each runnable scenario is called a "worker" and each worker can be queued, assigned 1 or more cores to undertake processing (up to the maximum available on your PC) and allocated a "solver". By default, LP Solve is used to process the run, but you can also use the commercial solver CPLEX instead (although this requires an additional license).

Tip: Define default worker configurations using the Processing Settings screen.

About Threads

Simply put, a thread is the smallest unit of processing that can be performed by your computer's CPU. MSO allows multithreading to accelerate computations by executing tasks in parallel. However, performance gains don’t scale linearly with the number of threads—too many threads may cause memory bottlenecks and reduced efficiency.

Tip: It is recommended to test optimal thread counts per machine. These are often less than the total number of available logical threads.

Summary

This part of the MSO workflow is used to:

• Add scenarios to the worker queue and monitor them in real-time.

• Control concurrency using thread configurations.

• Cancel or reprioritize runs on the fly.