Unlimited scenarios and decision trees for your strategic evaluations


Importing Data

Estimated reading: 2 minutes 388 views

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.


Protected: Imperial system

There is no excerpt because this is a protected post.

In-depth MiningMath

This tutorial provides a detailed guidance to the pages in the knowledge base fo...

Theory Validation

MiningMath’s results are only possible due to its proprietary Math Program...

Guaranteed Solutions

Multiple, complex constraints increase the likelihood of not finding or not exis...

MiningMath Uniqueness

MiningMath allows mining managers to improve their strategic analysis through ri...

Time Limit

It is possible to indicate a time limit in hours before running a scenario in th...

Must read articles

In order to take the maximum of MiningMath’s Optimization we recommend this fl...





Formatting the Block Model

The main focus here is on the requirements. Try to pay attention to the header...

Chat Icon Close Icon