Skip to content

Main content

Nerve Trace Proximal Distal Latency Difference Tool

Signed supplied two-site latency-difference velocity, without measurement acquisition or a clinical conduction interpretation.

Loading tool…

Description

Signed supplied two-site latency-difference velocity, without measurement acquisition or a clinical conduction interpretation.

Neurophysiological research records use sample coordinates, event clocks, epoch boundaries, references, signal amplitudes, and spectral bins. Timing conversions and support shares depend on rate, origin, exclusion, and boundary policies. Arithmetic on supplied values is separate from signal detection, validated acquisition, or neurological interpretation.

Signed supplied two-site latency-difference velocity, without measurement acquisition or a clinical conduction interpretation.

When to use this tool

Use Nerve Trace Proximal Distal Latency Difference when you need this research signal, sample, event, epoch, reference, or spectral component from supplied data.

How to use the tool and how it works

  1. Enter proximalLatency, distalLatency, intersiteDistance. 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 latencyDifference, segmentVelocity. Use the output convention below.

Require proximalLatency!=distalLatency and nonnegative intersiteDistance. Return latencyDifference=proximal-distal and segmentVelocity=distance/difference.1

Input fieldMeaning and unitsAccepted input
proximalLatencyProximal LatencyRequired. Finite number.
distalLatencyDistal LatencyRequired. Finite number.
intersiteDistanceIntersite DistanceRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
latencyDifferenceLatency DifferenceRequired. Finite number.
segmentVelocitySigned distance/latency-difference ratio under compatible units.Required. Finite number.
json
{
  "input": {
    "proximalLatency": 0.008,
    "distalLatency": 0.004,
    "intersiteDistance": 0.2
  },
  "output": {
    "latencyDifference": 0.004,
    "segmentVelocity": 50
  }
}

Limitations and assumptions

  • Distance and latency units determine velocity, such as m/s for meters and seconds. Negative differences and velocities are allowed; stimulation-site validity, physiological assumptions, temperature, measurement quality, and clinical nerve-conduction interpretation are not assessed.
  • 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 the intended signal-analysis protocol for a complete assessment. Verify sample rate, coordinate origin, clock offsets, reference configuration, filtering assumptions, and observation support.

References

  1. Calculation and input contract: neurology/nerve-trace-proximal-distal-latency-difference — tool.io

Similar or alternative tools

  • Nerve Trace Stimulus Response Gap

    Signed interval from supplied event sample indices after an explicit trigger-delay correction, without event detection or a diagnostic latency limit.

  • Evoked Window Anchor Gap

    Return relativeStart=windowStart-stimulusAt, relativeEnd=windowEnd-stimulusAt, and anchorGap=suppliedAnchor-stimulusAt.