Skip to content

Main content

Doppler Angle Correction Input

Apply an explicit Doppler cosine correction under a supplied angle in the open interval from -90 to 90 degrees without estimating flow or recommending an angle.

Loading tool…

Description

Apply a supplied cosine-angle correction to a velocity component.

Cardiology records distinguish event times, signal intervals, recording duration, paper calibration and Doppler angle conventions. A waveform distance requires a stated recording speed, and a signed projected velocity is not a diagnosis. Timing fractions and source labels do not establish cardiac function or appropriate care.

Apply a supplied cosine-angle correction to a velocity component.

When to use this tool

Use Doppler Angle Correction Input when you already have measuredVelocity, angleDegrees and need to apply a supplied cosine-angle correction to a velocity component.

How to use the tool and how it works

  1. Enter measuredVelocity, angleDegrees. 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 angleCorrectedVelocity. Use the output convention below.

Require angle strictly between -90 and +90 degrees; return measuredVelocity/cos(angle*π/180).1

Input fieldMeaning and unitsAccepted input
measuredVelocityMeasured VelocityRequired. Finite number.
angleDegreesAngle strictly between -90 and 90 degrees; corrections become sensitive near either endpoint.Required. Finite number; strictly above -90; strictly below 90.
Output fieldInterpretationReturned shape
angleCorrectedVelocityAngle Corrected VelocityRequired. Finite number.
json
{
  "input": {
    "measuredVelocity": 1,
    "angleDegrees": 60
  },
  "output": {
    "angleCorrectedVelocity": 1.9999999999999996
  }
}

Limitations and assumptions

  • Velocity may be signed. The angle must match the beam/flow convention; near 90 degrees amplifies errors. No angle, flow, sampling, clinical finding or appropriate correction is established.
  • 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

Review the original trace, acquisition settings, measurements and complete clinical context. Use the appropriate professional assessment for interpretation; local conversions and flags do not identify rhythms, assess disease or guide treatment.

References

  1. Calculation and input contract: cardiology/doppler-angle-correction-input — tool.io

Similar or alternative tools