Loading...

Get the NPV upper bound better than the Best Case scenario!

Our Plans
Updated on November 18, 2024

Warnings

Estimated reading: 6 minutes 534 views

  Warning 1101

The Force Mining surface (S1) was initially above the topography. Correction applied: S1 has been projected onto the level of the topography.

  Warning 1102

The Force Mining (FM) surface used was initially below the economically viable last period surface. Correction applied: FM depth has been reduced by increasing its Z-level.

  Warning 1103

The Force Mining surface (S1) used for period X+1 was initially above the one (S2) used for period X. Correction applied: the elevation of S1 has been reduced to match S2.

Note: ‘X’ can represent any period value (1, 2, 3, etc.)

  Warning 1104

The Force Mining surface (S1) employed was initially below the Restrict Mining surface (S2) during period X. Correction applied: S1 has been adjusted upward to align with the elevation of S2.

Note: ‘X’ can represent any period value (1, 2, 3, etc.)

  Warning 1105

The restrict mining surface used violated slope constraints of the last period surface. Correction applied: the surface has been adjusted accordingly.

  Warning 1106

The force mining surface used violated slope constraints of the last period surface. Correction applied: the surface has been adjusted accordingly.

  Warning 1107

The force mining surface (S1) imported for the last period surface was initially below the restrict mining surface (S2) imported for the same purpose. Correction applied: the elevation of S1 has been increased to align with that of S2.

  Warning 1108

The restrict mining surface (S1) imported for the last period surface was initially above the force mining surface (S2) imported for the same purpose. Correction applied: the elevation of S1 has been decreased to align with that of S2.

  Warning 1109

The force mining surface (S1) did not initially provide sufficient space to meet minimum operational constraints. Correction applied: adjustments have been made to S1 in critical areas.

  Warning 1110

The restrict mining surface (S1) was initially below the origin Z level. Correction applied: S1 has been projected to align with the origin Z level.

  Warning 1111

The force mining surface (S1) was initially below the origin Z level. Correction applied: S1 has been projected to align with the origin Z level.

  Warning 1112

The edges of the restrict mining surface (S1) were initially below the topography level. Correction applied: the edges of S1 have been projected to align with the topography level.

  Warning 1113

The edges of the force mining surface (S1) used were initially below the topography level. Correction applied: the edges of S1 have been projected to align with the topography level.

  Warning 1114

The restrict mining surface (S1) used was initially above the topography. Correction applied: S1 has been projected to align with the topography level.

  Warning 1115

The restrict mining (RM) surface utilized was initially above the economically viable last period surface. Correction applied: the depth of RM has been increased by reducing its Z-level.

  Warning 1116

The restrict mining surface (S1) used for period X-1 was initially below surface S2 used for period X. Correction applied: the elevation of S1 has been increased to match that of S2.

Note: ‘X’ can represent any period value (1, 2, 3, etc.)

  Warning 1201

Slope angles for the restrict mining surface have been adjusted for period X.

Note: ‘X’ can represent any period value (1, 2, 3, etc.)

  Warning 1202

Slope angles for the force mining surface have been adjusted for period X.

Note: ‘X’ can represent any period value (1, 2, 3, etc.)

  Warning 2301

The vertical rate has been adjusted by N meters to adhere to production and/or surface constraints in period X. Note: ‘X’ can represent any period value (1, 2, 3, etc.). ‘N’ can represent any value in meters.

  Warning 2401

The production capacities informed may force a mining schedule with more than 100 periods. Do you want to continue anyway?

This warning message is designed to prevent users from spending time on incorrect scenario setups by flagging potential inconsistencies with the block model data.

It often occurs due to typos, such as inputting values with lower magnitudes than intended. For instance, if production is meant to be 10 million tons per year but is mistakenly entered as 10 thousand tons per year.

MiningMath conducts basic validation checks before each scenario optimization, comparing parameters like production limits with the available material. If values are significantly lower than expected, it triggers a warning, as it may result in an unrealistically long mine life, typically over 100 years.

  Warning 2402

The block model must have at least two Economic Value fields, one for process and another one for dump.


MiningMath requires at least one process and one dump destination with their respective economic values. You should analyze your model and be sure to have this fields.

The economic value calculation is one of most important procedures of MiningMath. Any error on the formula could cause incompatible results and even increase the complexity and runtime based on wrong assumptions that could be done based on these values. The main validations on this step could be done by evaluating the minimum and maximum values. Once the data has been imported you can also perform a data validation procedure.

  Warning 2403

The pre-defined scenarios with Marvin deposit can usually appear with Red Warnings.




This means that within the installation process MiningMath could not find a folder to place it. Therefore, to run it you just have to click in the scenario, choose where the files should be and save them.


It is important to mention that Marvin block model is available here, thus if lost it or want to import it again feel free to do so.

  Warning 2404

Error parsing surface.

Usually, when you import an invalid surface the relative field will be in red. By hovering the mouse over the field you could see the message about it.

The first common issue here is about importing a surface which does not meet the block model limits. To check this issue verify your origins and check your coordinates by following the steps mentioned on this page.

An additional error is based on the name of the headers of the surface file, which might be always “X, Y, Z”. Thus, if it has any other name or type, correct it accordingly with this statement.

  Warning 3501

MiningMath tries to communicate with Excel and fails.

The reason why it happens is that there are additional windows (like a login screen or an activation failure) being opened before the worksheet, which is interfering with MiningMath generation of reports.

To find out, close the Excel instances completely and reopen it. If an additional window appears, before the worksheet, try to solve what this message asks.

Common Issues - Previous Reported user issues Next - Common Issues Floating-point numbers
Share this Doc

Warnings

Or copy link

CONTENTS
Chat Icon

Hi, it's Mima here 😇 Ask me any questions!