The main issues faced here are based on the System Requirements, shown in Error Warning, which often are forgotten to try to check them again.

There were improvements in the importation and exportation of coordinates after version 2.0, which were required due to the implementation of the viewer. Therefore, if you have run anything on previous versions, it is required to import your block model and run it again in the current version, available here.

Another common issue is related to the Licensing System. MiningMath relies on online activation based on the internet connection, or through an identification code from your hardware as a contingency. Therefore, you can solve your issue by understanding the main information disclosed on the "licensing screen", from Licensing Error, in the following order:

1. Identify your error number/message.

2. Get your hardware identification code (Host ID), by the two following options:

   • Copy the text disclosed at the "Informations for support", if it is available for you.

   • Execute this procedure bellow, explained in this video.

     1. Download the file, available here, and place it on your desktop

     2. Press Windows Key + R.

     3. Type cmd, then press enter.

     4. Type the code cd c:\Users\<YOUR USERNAME>\Desktop, then press enter.

     5. Type the code rlmutil rlmhostid -q -32, then press enter.

     6. Copy the text disclosed.

3. Send us the error number/message generated and the identification (Host ID) by filling this form.

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 one scenario, choose where the files should be and save them. It is important to mention that Marvin block model is disclosed at the link bellow, thus if lost it or want to import it again feel free to do so.

DOWNLOAD MARVIN DEPOSIT

While Running the pre-defined scenarios, you can already face some errors which happens when MiningMath tries to communicate with Excel and fails. The reason why it happens is that there are additional windows (like a login screen, an activation failure, etc.) being opened before the worksheet, which is interfering in MiningMath reports generation.

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 so that it would fix this interference.

If you have more than one Excel version in place or it's impossible to use due to a lack of license, it is recommended to uninstall and use another platform, to open the .csv reports generated and do your own reports.

The main focus here is on the requirements. Try to pay attention to the header names, which should be short(less than 13 characters) with no special symbols*. This nomenclature recommendation is also applied to the name of folders and files. Beyond that avoid a high number of subfolders to place your files, which can interfer in the viewer while loading it.

The data format is also a common issue, always remember to remove the air blocks, which could also be checked on the viewer. Note that a CSV file (Comma Separated Value), usually contains just one column* with all the information, when it is opened on excel. Therefore, if you are facing issues to import it, check if it has a similar format as the Marvin_Strategy_Optimization.csv disclosed in the installation process.

*Some Mining Packages export data with letters and values between quotation marks(""), check if this kind of format is interfering in the importation process.
**If you need to join columns a useful tip used in Excel is the formula: =A1&","&B1&","&C1 ....

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, as mentioned here, and the visual validation before running it, as explained in the last item of this page.

Formatted example

The Figure aside provides an example of a block model prepared and ready to be imported into MiningMath using the Marvin block model - based on data available in the MineLib¹ repository.

Optional fields inside the block model are listed below:

• • Density (t/m³).

  • Slope angle (degrees).

  • Process recoveries (values from 0 to 1).

There are a lot of reports coming from this page, the first trick here is to check the tooltips when any question appears. A common issue occurs when we assign the variables to the wrong field type. The second trending mistake happens when we forgot to place the origin accordingly with the Mining Packages previously used, which generates surfaces totally disconnected from your original data. To solve these problems just import your block model again. The last one is related to the "Next" button which can be explained here.

If you are working with Marvin Deposit along with MiningMath, be aware that the inclusion of new fields is allowed, as long as there is no inclusion or exclusion of blocks in the file, and the SLOPE, DENSITY, and INDEX or COORDINATES fields are not modified. The error message displayed at the aside occurs when modifications are detected in the basic structure of the standard Marvin deposit. Therefore, use the original CSV file disclosed at item 2 of this page.

This is the moment of validating every parameter that should be inserted on the evaluation. Thus, it is pretty useful to understand the main warnings on the surfaces importation. Usually, when you import an invalid surface the box would be in red, and by holding the mouse within its limits 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, which should be related to the origins or the surface size. 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.

It is always worthwhile to identify the warnings and validate your surfaces using this page if you have any warning about them.