The only mandatory requirement for using MiningMath is a 64-bits system, due to its use of Direct Block Scheduling technology. Other minimum requirements are listed further:
64-bits system (mandatory)
110 MB of space (installation) + additional space for your projects' files.
Processor: processors above 2.4 GHz are recommended to improve your experience.
Memory: at least 4 GB of RAM is required. 8 GB of RAM or higher is recommended to improve your experience.
OpenGL 3.2 or above. Discover yours by downloading and running the procedure available at here
Memory should be a higher priority when choosing the machine in which MiningMath will be run on. In addition, a list of priority upgrades to improve performance with large scale datasets is given below.
Higer Ram frequency
Higher processing clock
Notice that MiningMath does not use multiple processing threads for a single scenario. To take full advantage of a multi-thread processor, consider running different instances of MiningMath with different scenarios.
Put it to run!
Installing, activating and running!
Video 1: MiningMath installation process.
Activating your License
To activate your license, you will need to:
Open MiningMath (It will open automatically after the installation, but you can open it manually afterward).
On the left menu, click License.
Select the field "I have an activation code", paste the License Code provided by MiningMath.
Click "Activate license".
MiningMath’s licensing method demands an internet connection.
Play with the predefined scenarios
MiningMath allows you to learn with each scenario by providing standard parameters which simulate some common constraints a mining company may face. Standard scenarios are listed and described below so you can identify the main changes made within the “Overview” tab.
The ultimate goal of this practice is to prepare you to build Decision Trees, which allow you to organize scenarios in order to understand how variables influence one another and, consequently, how these variables determine the final NPV.
The Base Case consists of the initial scenario, with a uniform production capacity and without sum, average or surface mining limits.
While the base case considers a uniform production capacity, the BaseCase-RampUp scenario offers the possibility to vary the levels of production within the different timespans. We have an initial production capacity of 10Mton on the first 2 periods; 20 Mton on periods 3 and 4; and 30 Mton from period 5 until the end of the mine’s lifetime, with a total movement constraint of 30, 60, and 80 Mton, considering the increase of production within the time-frames mentioned.
PriceUp and PriceDown
Scenarios “PriceUp” and “PriceDown” differ in relation to the basic scenario in the economic value used for the calculation of the P1 process, where there is an increase and a decrease of 10% at the copper selling price, respectively. In the destination tab, “P1 Cu +10” and “P1 Cu -10” were the values used for the process.
PriceUp-RampUp and PriceDown-RampUp
These scenarios consider a 10% copper selling price increase and decrease, and a ramp-up of the production capacity at the same time, as mentioned before.
PriceUp-RampUp-Protection300 and PriceUp-RampUp-Protection400
This scenario considers a 10% copper selling price increase and a ramp-up of the products at the same time, as mentioned in the previous scenario. In addition, a restrict mining surface (this constraint is used to prohibit access to this area in a specific timeframe) was included up to the fourth period, since it may represent some legal constraints on a project.
Below you can see a description of some scenarios of other Decision Trees.
The MW150 scenario considers different geometries from the base case at the geometric constraints. In this scenario, 150 meters was used as mining width (the horizontal distance between the walls of two surfaces that belonged to consecutive periods), and a vertical rate advance of 180 meters.
In the AvgCu scenario, blending constraints were added in the average tab to consider allowed at the process plant 0.5% as a minimum and 0.7% as a maximum average copper grade. The optimization will have to fulfill the P1 process capacity and, as an additional challenge, it has to meet this new set of parameters related to the Cu average content within the ore.
Here, the same blending constraints of the previous scenario (AvgCu) were added, in addition to a stockpile limit of 5Mton for process 1, on the destination tab. This feature allows you to control the stock limit of your whole process, which increases the optimization flexibility to feed the plant, while respecting the blending constraints that were already implemented.
Proc13000h and Proc13000h-33Mt
Scenario Proc13000h considers 13.000 hours of processing equipment used as the maximum limit. This constraint was inserted at the sum tab and it controls variables such as rock type feeding, energy consumption, and any parameter controlled by its sum. Scenario Proc13000h-33Mt considers an increase of 10% in the production, inserted at the production tab beyond the parameters mentioned previously.