Skip to content

Main content

Redshift Velocity Composition Gap Tool

Collinear special-relativistic beta composition only, not a cosmological redshift-to-recession-velocity conversion.

Loading tool…

Description

Compose two collinear special-relativistic velocity fractions.

Cosmology uses several distance measures and often expresses the expansion rate in mixed astronomical units. Scale-factor relations, inverse-Hubble scales and relativistic velocity composition answer different questions; units and the distinction between local algebra and an integrated expansion history are essential.

Compose two collinear special-relativistic velocity fractions.

When to use this tool

Use Redshift Velocity Composition Gap when checking one explicit cosmological distance, redshift-factor or unit convention.

How to use the tool and how it works

  1. Enter firstBeta, secondBeta. 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 composedBeta, additiveGap. Use the output convention below.

Compose two collinear special-relativistic velocity fractions. Require abs(firstBeta),abs(secondBeta) < 1; composedBeta = (b1+b2)/(1+b1*b2), additiveGap subtracts the simple sum.1

Input fieldMeaning and unitsAccepted input
firstBetaFirst signed collinear velocity divided by light speed, strictly between -1 and 1.Required. Finite number.
secondBetaSecond signed collinear velocity divided by light speed, strictly between -1 and 1.Required. Finite number.
Output fieldInterpretationReturned shape
composedBetaComposed BetaRequired. Finite number.
additiveGapAdditive GapRequired. Finite number.
json
{
  "input": {
    "firstBeta": 0.5,
    "secondBeta": 0.5
  },
  "output": {
    "composedBeta": 0.8,
    "additiveGap": -0.19999999999999996
  }
}

Limitations and assumptions

  • Beta is velocity divided by light speed; this is not cosmological recession velocity from redshift.
  • 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 a complete cosmological distance/time calculation and the appropriate observation model when an actual source distance, age or velocity is required.

References

  1. Calculation and input contract: cosmology/redshift-velocity-composition-gap — tool.io

Similar or alternative tools