Bench Height Calculator

Audit actual bench top/toe level inventory against independently established height bounds, not overall pit slope or a bench design standard. Caller independently verifies units, applicability and matching conditions; no operational recipe, safety certification, causal efficacy or legal/resource classification is inferred.

Description

Bench height uses top and toe elevations sharing a survey datum.

Bench height uses top and toe elevations sharing a survey datum.1

A matched upper bound provides a strict review threshold for each observation.

When to use Bench Height Calculator

Use this tool to calculate or review the supplied observations under the stated rules. Match completed survey or ledger observations by block, segment or stage and confirm their units and boundaries.

How to use Bench Height Calculator and understand its results

  1. Match completed survey or ledger observations by block, segment or stage and confirm their units and boundaries.
  2. Enter observedBenchTopElevationsM, observedBenchToeElevationsM, callerMatchedMaximumBenchHeightsM, using the field meanings and rules below, then run the tool.
  3. Read observedBenchHeightsM, benchHeightReviewIndices. Inspect nested result fields where present, and review unknown records separately from known matches.
  4. Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
Input fieldMeaningValue typeRequirement
observedBenchTopElevationsMObserved bench top elevations mlist of numberRequired
observedBenchToeElevationsMObserved bench toe elevations mlist of numberRequired
callerMatchedMaximumBenchHeightsMCaller matched maximum bench heights mlist of numberRequired

Use aligned finite top/toe levels and positive maximum heights. Require top−toe≥0. Return heights and indices strictly above their matched maximum; equality is not flagged.

height_i=top_i−toe_i; review={i:height_i>maximum_i}

Use the matching field units and the exact boundary, ordering and reference rules above.

Output fieldMeaningValue type
observedBenchHeightsMObserved bench heights mlist of number
benchHeightReviewIndicesBench height review indices; zero-based positions in the relevant supplied record or adjacent-pair listlist of number
json
{
  "input": {
    "observedBenchTopElevationsM": [
      100,
      200
    ],
    "observedBenchToeElevationsM": [
      90,
      185
    ],
    "callerMatchedMaximumBenchHeightsM": [
      12,
      12
    ]
  },
  "output": {
    "observedBenchHeightsM": [
      10,
      15
    ],
    "benchHeightReviewIndices": [
      1
    ]
  }
}

Limitations and assumptions

Units, ledger boundaries, survey interpretation and model applicability must be independently established. These summaries do not assign reserve/resource classifications or establish support adequacy, ventilation safety or an operating setting.

Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above.

Alternative or Complementary methods

For a related step, use Pit Depth Calculator: A rim-to-floor depth needs paired elevations sharing the same datum. For a complementary comparison, use Mining Width Calculator: An extraction width survey can be compared with independently marked target dimensions.

References

  1. Bench Height Calculator — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies