Scheduling Setup: Options

To access this screen:

In the Scheduling Setup screen, select the Options tab.

This screen is used to set general settings for your scheduling scenario and specifically, the Maroma solver. In effect, these define base 'rules' for the scheduler aside from those required by preceding screens.

These options are:

Stockpiles type	Stockpile type allows selecting between Warehouse Stockpiles and Mixed Stockpiles. Warehouse Stockpiles compute faster and are suitable for projects with large number of periods. With this option a stockpiled block is considered available to be reclaimed with its own grades without mixing with other stockpiled blocks. Maximum periods to reclaim – Set the maximum number of periods a block can be stockpiled before being reclaimed. With Mixed Stockpiles, the grade of a stockpile is weighted average of the blocks sent to the stockpile. Using mixed stockpiles may increase the computation time. When this is a problem need to consider using warehouse type. See Mixed & Warehouse Modes.
Optimizer switches to Multipass...	A Multipass heuristic will be used when the periods to optimize are greater than the user defined value (between 30 and 60). The default optimizer setting is to solve submitted problems globally to within a guaranteed optimality tolerance. The optimizer can be configured to run a “multipass” heuristic to obtain a solution, rather than to attempt to solve the problem globally. Note: The principle of a multipass heuristic is to break up the problem into smaller problems, and to use these to obtain a feasible solution to the global problem, though at the cost of an optimality guarantee.
Schedule all blocks...	Check Mine All to schedule all blocks even if they have negative contribution to the Net Present Value. If Mine All is unchecked, Maroma will not schedule these blocks potentially leaving some benches or a whole pushback unmined.
Solver timeout	Solver timeout is useful when optimization runs take long time to complete. The default value 1440 minutes (24 hours) may need to be reduced if runs are expected to last long. When the timeout limit has been reached and there is sub-optimal solution found the results will be displayed. Otherwise the message "Problem has no solution" displays.
Number of cores	Maroma can utilize multiple cores when obtaining an optimal solution. The Number of cores is set to four by default. Utilizing more cores may help finding a solution faster, but will use more system resources.
Optimality Gap	Defines how hard (long) Maroma works to obtain the best solution. The default gap is 5% but you can set values between 0.1 and 10. Small values will increase computation time particularly for more complex schedules with multiple constraints and many periods. Tip: 1-2 % optimality gap is reasonable for most projects.