Crossover Passage Width Checker

Audit measured crossover bottlenecks against explicit caller width policy; unsampled obstructions, occupant flow, accessibility and legal egress remain unverified.

Description

A crossover passage’s measured bottleneck is its narrowest sampled station.

A crossover passage’s measured bottleneck is its narrowest sampled station. Sampling does not establish complete obstruction coverage.1

Enter nonempty positive widths and positive required width. Return narrowest width, strict-below indices and signed margin.

When to use Crossover Passage Width Checker

Use Crossover Passage Width Checker when you need to evaluate the supplied records under the calculation and evidence rules below. No occupant flow, accessibility, unsampled obstruction or legal egress is verified.

Prepare the actual venue, production, inventory or financial records requested. Confirm units and supply applicable local limits or verified catalog values.

How to use Crossover Passage Width Checker and understand its results

  1. Prepare the actual venue, production, inventory or financial records requested. Confirm units and supply applicable local limits or verified catalog values.
  2. Enter observedCrossoverStationWidthsM, callerPassageMinimumM using the field table and calculation rules, then run the tool.
  3. Read narrowestObservedCrossoverWidthM, belowPolicyStationIndices, signedNarrowestWidthMarginM. The explanation below defines the units, signs, ordering and any flags or placeholder values.
  4. If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
Input fieldMeaningValue type; see rules belowRequirement
observedCrossoverStationWidthsMObserved crossover station widths mlist of numberRequired
callerPassageMinimumMCaller passage minimum mnumberRequired

Enter nonempty positive widths and positive required width. Return narrowest width, strict-below indices and signed margin.

minimum=min(widths); margin=minimum−policy

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output fieldMeaningValue type
narrowestObservedCrossoverWidthMNarrowest observed crossover width mnumber
belowPolicyStationIndicesBelow policy station indiceslist of number
signedNarrowestWidthMarginMSigned narrowest width margin mnumber
json
{
  "input": {
    "observedCrossoverStationWidthsM": [
      1.2,
      1,
      0.8
    ],
    "callerPassageMinimumM": 1
  },
  "output": {
    "narrowestObservedCrossoverWidthM": 0.8,
    "belowPolicyStationIndices": [
      2
    ],
    "signedNarrowestWidthMarginM": -0.19999999999999996
  }
}

Limitations and assumptions

No occupant flow, accessibility, unsampled obstruction or legal egress is verified.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Wing Space Clearance Minimum Lookup: Wing clearance is the space left after stored scenery occupies a measured width. Signed deficits help review the local lane plan. For a complementary task, use Trap Room Headroom Checker: Trap-room headroom is reduced by overhead obstructions. The measured stations define the coverage of the check.

References

  1. Crossover Passage Width Checker — tool.io

Similar or alternative tools

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