Skip to content

Main content

Retinal Scan Bscan Spacing Budget Tool

Explicit endpoint-inclusive versus equal-cell B-scan placement convention, without an acquisition-density recommendation.

Loading tool…

Description

Explicit endpoint-inclusive versus equal-cell B-scan placement convention, without an acquisition-density recommendation.

Vision research uses stimulus angles, chart notations, image scales, viewing distances, coordinate origins, and observation windows. These quantities have different denominators and measurement conventions. A conversion or support share does not independently establish a visual measurement or its clinical interpretation.

Explicit endpoint-inclusive versus equal-cell B-scan placement convention, without an acquisition-density recommendation.

When to use this tool

Use Retinal Scan Bscan Spacing Budget when you need this image, stimulus, notation, coordinate, or observation component for supplied research data.

How to use the tool and how it works

  1. Enter span, bscans, endpointInclusive. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read intervals, spacing, representedSpan. Use the output convention below.

For nonnegative span and positive integer bscans choose intervals=bscans-1 if endpointInclusive, otherwise bscans. Require at least two scans on the inclusive branch. Return spacing=span/intervals and representedSpan=span for inclusive endpoints, otherwise span*(bscans-1)/bscans.1

Input fieldMeaning and unitsAccepted input
spanSpanRequired. Finite number; minimum 0.
bscansBscansRequired. Safe integer; minimum 1.
endpointInclusiveEndpoint InclusiveRequired. Boolean.
Output fieldInterpretationReturned shape
intervalsIntervalsRequired. Safe integer.
spacingSpacingRequired. Finite number.
representedSpanFirst-to-last scan-start span under the selected endpoint convention.Required. Finite number.
json
{
  "input": {
    "span": 6,
    "bscans": 13,
    "endpointInclusive": true
  },
  "output": {
    "intervals": 12,
    "spacing": 0.5,
    "representedSpan": 6
  }
}

Limitations and assumptions

  • Span and spacing use one length unit. The other branch places scan starts before the final boundary and permits one scan with representedSpan zero; no scan acquisition, image quality, anatomy, or clinical adequacy is verified.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use calibrated acquisition and a documented visual or imaging protocol for complete interpretation. Confirm the reporting notation, viewing geometry, image scale, and support of the underlying observations.

References

  1. Calculation and input contract: ophthalmology/retinal-scan-bscan-spacing-budget — tool.io

Similar or alternative tools

  • Visual Stimulus Frame Slack

    For nonnegative integer availableFrames and requiredFrames and positive frameRate return slackFrames=available-required and slackSeconds=slackFrames/frameRate.

  • Retinal Pixel Angle Factor

    Apply a supplied retinal research image angular calibration, without inferring retinal anatomy or disease.