Data Validation

Estimated reading: 2 minutes 1183 views

Running an optimization for complex projects with several constraints may demand hours only to validate if the formatting has been done properly. Therefore, we present here an efficient workflow to structure your project. It is important to mention that you can run each topic of this content individually at any time you find suitable, but, we strongly recommend you to take it step by step to understand the main idea of the process

The next pages use the example below within Marvin Deposit and aim to exemplify the following set of constraints:

Constraint	Value
Processing capacity	10 Mt per year
Total movement	40 Mt per year
Sum of processing hours	4,000 per year (detailed estimate of the plant throughput)
Vertical rate of advance:	150m per year
Copper grade	Limited until 0.7%
Minimum Mining Width	50m
Minimum Bottom Width	100m
Restrict Mining Surface	`Surface-RM-offset-400m.csv` Due to a processing plant in the area
Fixed Mining (Stockpiling)	0.9$/t
Rehandling cost (Stockpiling)	0.2$/t

Table 1: Set of constraints example.

Validate it First

In order to validate your data and cut its runtime, we strongly recommend running MiningMath Full with the following set up:

Process and dumps set with respective recovery values.
A bigger production capacity than the expected reserves. In this example, the expected life of mine vs production rate is 35-year producing 10 Mt per year. Hence, a value of 1,000 Mt would be big enough to cover the whole reserve.
No discount rate.
No stockpiling.
Density and slope values.
Timeframe: Years (1), since it would all be processed in 1 period.

Figure 1 depicts this set up at MiningMath, with the highlighted fields. This execution will also generate the topography surface so that you can create a force or restrict mining areas.