Creating a Block Model in Maptek Vulcan | Mining University

Creating a Block Model in Maptek Vulcan

Contrary to popular belief, creating a block model in the Maptek Vulcan software package is not overly difficult. Estimating grades for the block model can be as tedious and convoluted as you want it to be but creating the shell for that model to go in is an elementary exercise.

block model slice
Block Model slice showing air (blue), country rock (brown) and ore (red).
To start, create a new block definition file (*.bdf) by selecting Block > Construction > New Definition. By selecting this menu option you will enable the Block Model utility in Vulcan Workbench and open the Block Definition panel.

block model orientation
Block Model Orientation - defines origin and rotation.
The first decision we need to make in creating our block model is the origin and orientation of the model. The origin is the minimum x, y and z coordinate of the block model. Fill in the fields ‘X Coordinate:’, ‘Y Coordinate:’ and ‘Z Coordinate:’ with the appropriate values. These should usually be something farther east and south than the deposit we are modeling and at a lower elevation. Don’t get too carried away, we don’t want to model the entire country, just enough to contain a mine design.

The rotation is defined as the rotation of the block model around the origin point. By default, Vulcan has designated the ‘Bearing’ as being 90. This sets the x axis pointing east instead of north. If your deposit is disseminated or has an unknown orientation I would advise you to leave the rotation with the default settings. If your orebody has a specific trend, set the rotation to follow this trend. This will often help when estimating the ore grades. The panel is very self-explanatory when defining the fields:
  • Bearing: the absolute bearing of the X axis around the Z axis
  • Plunge: the relative rotation of the X axis around the Y axis
  • Dip: the relative rotation of the Y axis around the X axis
  • Rotation: follows the left hand rule (i.e. clockwise is positive)

block model schemes
Block Model Schemes - defines the parent and child block sizes.
Parent and child block sizes are set in the ‘Schemes’ section of the panel. In Maptek Vulcan we can use sub-blocks to better define the boundary between geologic regions. This means that, rather than use big blocks everywhere, we can use big blocks most places but when we intersect a boundary we can use smaller blocks. This gives a balance between lots of data and small file size. Fill out the panel, keeping the following definitions in mind:
  • Scheme: The name of the block sizes to be defined. These are often called Parent and Child schemes.
  • Start Offset: This is the offset from the origin where we want to start creating blocks. This is usually zero, although you could set the origin to zero and the offset to the origin coordinates if you really wanted to.
  • End Offset:  The maximum extent of the block model as measured from the origin point.
  • Block Size: The size of the block model block in the X, Y and Z directions. Parent blocks are usually quite large with child blocks being significantly smaller. Parent blocks must be a multiple of child blocks.
  • Blocking Maximum: Once a parent block has been broken down into the child blocks Vulcan will try to combine them back together again to create the largest block that honors the geologic boundary up to the blocking maximum. The blocking maximum may be as large as the parent block. Parent blocks do not need a blocking maximum definition.

block model variables
Block Model Variables - defines the variable name and type.
Variables define the space in which to store data for each block model block. If you forget to add a variable during creation of the block model, don’t worry. You can add variables later. I would advise everyone to add the variables to the block definition file at the same time they are adding them to the existing block model. Later, when you are re-creating your block model with updated drilling, you will thank me. 

Enter the variable name and variable type. The variable type may be one of the following:
  • Name: This is for string type data (i.e. geologic domains). Your data is stored in the block model as integer data and then converted back to the name values using a translation table.
  • Byte: This is an integer value between 0 and 255. The byte variable type takes up one byte of memory.
  • Short: Integer value between -32,768 and +32,767 requiring two bytes of memory.
  • Integer: Records integer values between positive and negative two billion. Uses four bytes of memory.
  • Float: Real number using four bytes of memory. Can store up to seven significant figures.
  • Double: real number using eight bytes of memory. Can store up to fourteen significant figures.

Keep in mind that minimizing the amount of memory for each variable can significantly shrink the file size of a block model with millions of blocks. Unless you are storing incredibly accurate grade data or plan to store UTM coordinates to your variables, the Float type variable is probably good for any real numbers you need to store. Remember that you can break down by the Name, Byte, Short and Integer variable types when generating reserves later.

Default value is the result given to each block as it is created. Description is the definition of the variable saved with the block model. The first rule of Vulcan applies here, as it does everywhere else: 'Always, always, always use a description.'

block model boundaries
Block Model Boundaries - triangulations defining geologic regions.
Boundaries are the triangulations that define the geologic domains. Select your triangulations (surfaces or solids) and the variable they will which they will write information. Value is the variable result that will be written. Priority is the order that the variables will be written. If two triangulations overlap, priority 2 will overwrite priority 1. Inversion reverses the direction in which the triangulation is projected (i.e. solids will be flagged outside the shape, surfaces will be flagged from Z up instead of Z down) if ‘complete’ is selected. ‘None’ is the default option. If your surfaces completely cross the block model area you don’t need to worry about ‘partial.’ Projection is the direction in which the surfaces will be flagged, default is along the Z axis.

block model limits
Block Model Limits - defines the coalescing of child blocks.
Limits sets a maximum size for child coalescing based on a variable value. This is interesting but I almost never use it. It might be useful inside an ore zone just so the grades can be defined on a tighter interval. I don’t know many people who use this option.
block model exceptions
Block Model Exceptions - defines which blocks not to include in the block model file.
Exceptions are blocks that should not be created in the block model. Back in the days when memory was limited, it was common to define regions of the block model (above topo, outside mineralization, etc…) that should not be saved to the block model file. As memory has become more cheaper and different formats have become available, the necessity of making exceptions has gone away. I would suggest that you not exclude any blocks.

block model format
Block Model Format - classic or extended. Always extended, always.
The original Vulcan block model format (Classic) stored all data for all blocks. This meant that if you had a million blocks with the default value, your block model file had written the default value one million times. This resulted in a very large model file. 

The ‘Extended’ format writes all default information to the header and then references the header for any blocks with default values. This means than in the extended format, if you have a million blocks with the default value the block model file will write this value to the header once (not a million times). This method saves a significant amount of file space. Always use the ‘Extended’ format.

At this point your block definition file (BDF) is complete. Go ahead and save it by selecting the ‘save’ icon or the File > Save menu option.
create block model
Create Block Model panel.
Next, create your block model by selecting Model > Create Model. In the Create Block Model panel select your BDF file for the ‘Definition file name’ field. The Block model name will auto populate with a block model file (BMF) with the same name. I like to keep the name the same for the BDF and BMF so that I know which files were used in the block model creation. Leave the ‘Index model’ box checked. Indexing makes the model faster to search and display. I’m not sure why there is an option to not index the model. Leave the ‘Ensure project prefix’ box un-checked. This is an antiquated check of your project prefix. Click ‘OK.’
block model t-shell
Block Model t-shell.
A t-shell window will pop up while the block model is being created. When it is done follow the instructions and ‘Press any key to continue …’

Return to Envisage by clicking File > Quit Block Model Utility.

In the Vulcan Explorer expand the Block Models folder. Your new block model will appear below. Expand the block model to see the variables in the model. That’s it. You just created a Vulcan block model.

What’s next?
Create a Block Model Color Legend
Display a Block Model in 3D

No comments:

Post a Comment