Uploading block models to BlockSync

You can add block models to BlockSync by:

  • Publishing a block model from an integrated app
  • Uploading a block model file via BlockSync in *.csv, *.parquet or *.dm (Datamine) formats

This topic contains important information about uploading block model files directly to BlockSync. It is divided into:

See the Importing a new block model topic for information on adding a new block model to BlockSync via the BlockSync portal.

File formats and block model types

You can upload block models to BlockSync in the following formats:

  • *.csv
  • *.parquet
  • *.dm (Datamine)

Block model types supported are:

  • Regular block models. A regular block model has blocks that are all the same size and are never divided.
  • Octree sub-blocked models. An octree sub-blocked model has blocks that are repeatedly halved where selected triggering surfaces intersect the blocks. Instead of dividing a block entirely into small sub-blocks when sub-blocking is triggered, the block is first divided in half in a particular direction, and then only the partitioned blocks that still trigger a further division are divided into smaller units. This creates a series of sub-blocks of different sizes, and because many are larger than the smallest sub-block and the smallest sub-blocks only exist where a contact requires it, processing can be more efficient.
  • Fully sub-blocked models. With fully sub-blocked models, blocks are fully sub-divided when they contain a triggering boundary. This can create many sub-blocks and so processing a fully sub-blocked model can be slower than processing an octree sub-blocked model. In contrast to octree sub-blocked models, however, fully sub-blocked models support block subdivisions using numbers other than power-of-two numbers. Fully sub-blocked models do not support variable height sub-blocks.
  • Flexible sub-blocked models. With flexible sub-blocked models, sub-blocks can be any size that is an increment of the minimum block size. This is the method of sub-blocking used by Vulcan.

An important warning on grid definition

Once a block model has been uploaded to BlockSync, its grid definition cannot be changed. If you later need to upload a version of the model that has a different grid definition, you will need to upload it as a new model.

Block model version numbering

When a block model is first uploaded to BlockSync, two versions of the model are created:

  • Version 1 is the empty model based on the grid definition. Once a block model has been created in BlockSync, its definition cannot be changed.
  • Version 2 populates the model definition with data, i.e. its data columns.

A model’s version history is linear, with no branching. Each update to the model creates a new version of the entire model.

The version history cannot be edited and versions cannot be deleted. To ‘rollback’ a model, download the version you wish to use as the latest version and upload it again to make it the latest version.

New versions of a block model can be published via integrated applications. They can also be uploaded via the BlockSync portal, which is described in the Uploading a new version topic.

Sub-blocked models

When importing a sub-blocked model, all sub-blocks contained within a parent block must be present, along with all columns. This is necessary for maintaining a consistent sub-blocking structure in the model when merging changes from future versions.