TS. Refinements

Owned by iarmstrong
Last updated: Feb 14, 2023
3 min read

RU

Overview

The Refinements step is only visible if in Configuration Options step option Use Extension has been enabled.

Refinements step overview for a sample project

Refinements are customized and work differently for all projects.

Refinements require custom scripts.

These custom scripts are loaded in the Extensions Source step.

Refinements are usually configured as part of the implementation process.

Refinements examples

The Refinements step displays custom inputs for Site Specific Extensions (“.sln” file imported in the Extension Source step).

Example of site extensions for configuring Drilling and Blasting in the project

 

Scripts may be used to apply:

  • Mining recovery,

  • Product recovery,

  • Product call factors,

  • Moisture balancing,

  • Topsoil calculations,

  • Loader rate factors by pit and bench,

  • Material type recategorisation,

  • Above/Below water table designation,

  • Effective Flat Haul calculations,

  • Custom Calendar Availability, etc.

Contact your Alastri support representative for assistance with Site Specific Extensions.

Example of custom refinements for Drill and Blasting setup by pattern type, with different parameters specified.

Errors

Unless all errors are addressed, either in the setup steps or in your custom script, the message shown below will be shown in the main viewport, and you will not be able to proceed with the project setup:

“There is no extension loaded, or the extension does not gather inputs from this benches form“.

Examples of some error messages, with recommendations on how to fix them, are given below. In the case of other errors that you can not solve yourself, you can contact Alastri support.

Missing fields

“Failed to find fields: <drilling_explosives, misc_blastType, misc_surfaceArea>”.

Reason

Solution

Reason

Solution

Mismatching between the fields in the script and the fields added in the project.

Return to the specified Data Field steps and add the missing fields.

Pay attention to spaces and spelling.

Note for advanced users

If you do not need the specified fields, double click on the error message - a window will appear with a detailed description of the issue, indicating the line in your custom script containing this field. If you are an experienced user with scripting skills in Microsoft Visual Studio, you can open the relevant script yourself and make changes in it. Otherwise, contact Alastri support representative.

Fields Not Mapped

“System.Exception: misc_surfaceArea must be mapped in Map Fields”.

Reason

Solution

Reason

Solution

The custom field is not mapped to data from the inventory database.

Navigate to the Map Fields step and do the matching for the field specified in the error message for all relevant stages.

Data not selected

“System.Exception: Hole diameter needs updating in blast <Reserves/Mine/Pit1/Stage1/800>, Pattern Type: [Trim]”.

Reason

Solution

Reason

Solution

No data selected in the custom field (example, Hole Diameter), but it is required by the script.

Read the error message and select relevant option from the dropdown for the specified field.