Block Model Custom Variables

1 Overview
2 Inline formula vs Custom Variable
- 2.1 Creating Custom Variable
3 Custom Variables Examples
- - 3.1.1 Dry Tonnes
  - 3.1.2 Grade bins
  - 3.1.3 Multiple Grade Bins
- 3.2 Ore Ratio
  - 3.2.1 Ore Ratio code
4 Multiple Custom Variables
5 Variable validation and Error list resolution

Overview

Sometimes you need to map a Block Model field that isn't coded in the original Block Model. For example, Ore and Waste definitions can be more complex and multiple grades and types inputs are required. In this case, to define different properties use Custom Variable functionality implemented through the Script Editor.

Scripting language is C#.

Inline formula vs Custom Variable

To define different properties you can write an inline formula using “IF” statement, such as If N(“Fe”) is greater than 60 return “hg” otherwise if N(“Fe”) is greater than 58 return “mg” otherwise if N(“Fe”) is greater than 57,5 return “lg1” otherwise if N(“Fe”) is greater than 56 return “lg2” otherwise if N(“Fe”) is greater than 50 return “minw” otherwise call it “waste”.

Block Model with Inline Formula

But such linear formulas can be too long and confusing. Therefore, if there are multiple properties and parcel types that need to be separated, it is recommended to use Custom Variables.

Custom variables allow us to write complex logic in a readable and reusable way, which can then be mixed with other inline formulas in the block model mappings.

Custom Variable editor

Creating Custom Variable

Go to Setup > Block Model > Edit > Reservable Model Generator.
Click Custom Variables to open the Script Editor.
Clear all text from the Script Editor.
Replace it with one of the sample codes listed below.
In the list of available variables on the right you will see a new variable CustomT("Parcel") in bold, map it to the Parcel field.

Custom Variables Examples

Dry Tonnes

using System; 
using System.Collections.Generic; 
using System.Text; 
using System.Linq; 
using Alastri.Scripting; 
using Alastri.BlockModel.Engine.CustomVariables;

public class DryTonnes : IDoubleCustomVariable
{
    public double GetNumber(CustomVariablesContext context)
    {
        double density = context.N("DENSITY");

        double volume = context.N("XINC")*context.N("YINC")*context.N("ZINC");
        
        return (density > 0 ? density * volume : 0);
        
    }
}

Grade bins

using System;
using System.Collections.Generic;
using System.Text;
using System.Linq;
using Alastri.Scripting;
using Alastri.BlockModel.Engine.CustomVariables;

public class Parcel : ITextCustomVariable
{
    public string GetText(CustomVariablesContext context)
    {
        double fe = context.N("fe");
        
        if(fe > 60)        return "hg";
        else if(fe > 58)   return "mg";
        else if(fe > 57.5) return "lg1";
        else if(fe > 56)   return "lg2"; 
        else if(fe > 50)   return "minw";
        else               return "w";

    }
}

Multiple Grade Bins

using System;
using System.Collections.Generic;
using System.Text;
using System.Linq;
using Alastri.Scripting;
using Alastri.BlockModel.Engine.CustomVariables;

public class Parcel : ITextCustomVariable
{
    public string GetText(CustomVariablesContext context)
    {
        double fe = context.N("fe");
        double al = context.N("al");
        string geology = context.T("geology");
        
        string fe_bin;
        
        if(fe > 60) 
        {
             fe_bin = "60";
        }
        else if(fe > 55) 
        {
            fe = Math.Floor(fe); 
            fe_bin = fe.ToString("#,##0");
        }
        else
        {
           fe_bin = "50";
        }

        string al_bin;

        if(al < 3)
        {
           al_bin = "3";
        }
        else if(al < 6)
        {
           al = Math.Ceiling(al);
           al_bin = al.ToString("#,##0");
        }
        else
        {
          al_bin = "9";
        }

        string geoClass = "1";
        if(geology.Equals("detrital", StringComparison.OrdinalIgnoreCase))
        {
           geoClass = "2";
        }

        return fe_bin + "_" + al_bin + "_" + geoClass;
    }
}

Ore Ratio

Rapid Reserver block model fields cannot report Stripping Ratio, because Stripping Ratio is not a sum or weight average type field. Instead, we can report ore ratio, which is the weight average of ore tonnes over total tonnes.

To do this we can set up a weight-averaged field called OreRatio as a child of "dryTonnes" or "wetTonnes" (whichever you want to report). This field will report a "1" for ore and a "0" for waste. The weight average of the 1s and 0s across a blast becomes the ore ratio.

Ore Ratio code

Multiple Custom Variables

To create multiple custom variables, a class implementing the IDoubleCustomVariable or ITextCustomVariable interface needs to be created for each variable. These classes need to be listed under one another in the Custom Variables Script Editor, as shown in the examples below.

Multiple Custom Variables

Multiple variables with shared logic

Access Custom Variable from another Custom Variable

Access Custom Variable values from another Custom Variable

Variable validation and Error list resolution

Check if the statement is correct by pressing the Compile button at the top left corner of the Script Editor.

If you did a mistake, the Compile Error window will pop up, showing row and column of an error with a short description of its type.

Read the error message description and correct the lines specified.

If there are no errors during compilation, the custom variables should be listed in the Variables panel.

When the Errors panel is blank, and all relevant fields are mapped, press Generate to build the Reserve Model.