Set up Worker Configurations

Each MSO scenario represents the data and settings required to generate optimal mineable stope shapes for downstream planning and evaluation. Each runnable scenario is represented by a "worker" and each worker requires a configuration.

The Run screen is used to set up worker configurations, one for each scenario, before queuing the worker(s) for processing.

Note: You don't have to queue or process all scenarios. The queue of workers in a batch is fully customizable.

Activity steps

Create an MSO scenario and define a block model.
Configure other settings as required.
Display the Run screen.

The Worker Configurations table shows an entry for every scenario that exists for your project.
Review or Define Processing Settings.
For each scenario you intend to process, edit the following table properties:
- Queue – Check to flag the scenario as ready for queuing.
- Scenario – Static text describing a scenario.
  
  Tip: Change the name of a scenario on the Manager screen. Access this using the Run screen's Edit Scenarios button.
- Concurrent Threads – MSO can utilize multiple cores. Assign one (the default) or more threads to allow MSO to process multiple runs in parallel, saving time.
  
  Note: Threads are used by all running processes on your PC, including your operating system. MSO will only access threads that are available. The setting above is the maximum threads that can be targeted. Fewer will be assigned if the full amount are not free.
- MIP Solver – The 'engine' used to provide an optimal solution considering the objectives described by your input MSO parameters.
  - LP Solve – The default solver, requiring no license.
  - CPLEX – An alternative solver, requiring an additional license. Contact your local Datamine office for support.
Once one or more scenarios is 'queued', click + to transfer them to the Worker Queue table below.
Continue the processing run. See Set up a Worker Queue.