Skip to content

Main content

Acoustic Gravity Wave Wavenumber Component

Resolve a supplied wave-number magnitude along horizontal and vertical axes at an explicit radian angle measured from horizontal.

Loading tool…

Description

Resolve a supplied wavenumber magnitude into planar components.

Atmospheric scalar terms require explicit averaging, spectral, geometric and propagation conventions. One fluctuation product is not a time-averaged flux, a squared deviation is not a full scintillation index, and a Nyquist interval does not de-alias radar velocity. Layer terms require compatible units and model assumptions.

Resolve a supplied wavenumber magnitude into planar components.

When to use this tool

Use Acoustic Gravity Wave Wavenumber Component when you already have wavenumberMagnitude, propagationAngleRadians and need to resolve a supplied wavenumber magnitude into planar components.

How to use the tool and how it works

  1. Enter wavenumberMagnitude, propagationAngleRadians. 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 horizontalComponent, verticalComponent. Use the output convention below.

Require magnitude>=0; horizontal=k*cos(angle), vertical=k*sin(angle).1

Input fieldMeaning and unitsAccepted input
wavenumberMagnitudeNonnegative angular wavenumber in the chosen inverse-length unit.Required. Finite number; minimum 0.
propagationAngleRadiansSigned angle from horizontal in the chosen plane; not degrees.Required. Finite number.
Output fieldInterpretationReturned shape
horizontalComponentHorizontal ComponentRequired. Finite number.
verticalComponentVertical ComponentRequired. Finite number.
json
{
  "input": {
    "wavenumberMagnitude": 2,
    "propagationAngleRadians": 0
  },
  "output": {
    "horizontalComponent": 2,
    "verticalComponent": 0
  }
}

Limitations and assumptions

  • Angle is radians from the horizontal in the chosen plane, and k must use a consistent angular-wavenumber convention. No dispersion relation, wave propagation or atmospheric mode is solved.
  • 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 the complete measurement and physical retrieval model. Include calibration, averaging, source geometry, spectral response and relevant transfer or flow effects when local weights and signal factors cannot establish the desired atmospheric quantity.

References

  1. Calculation and input contract: atmospheric-physics/acoustic-gravity-wave-wavenumber-component — tool.io

Similar or alternative tools