Skip to content

Main content

Leapfrog Half Step Velocity Offset Tool

Calculate leapfrog half step velocity offset from explicit caller-supplied inputs.

Loading tool…

Description

Return leapfrog velocities at neighboring half steps.

A simulation update combines supplied states, fluxes, forces and time conventions. Local integration and interface terms can be evaluated independently, while a full solver must also supply consistent fields, boundary conditions, conservation and convergence behavior.

Return leapfrog velocities at neighboring half steps.

When to use this tool

Use Leapfrog Half Step Velocity Offset when checking one explicitly supplied integration, flux or lattice-population contribution.

How to use the tool and how it works

  1. Enter centerVelocity, acceleration, step. 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 previousHalfVelocity, nextHalfVelocity. Use the output convention below.

Return leapfrog velocities at neighboring half steps. Require step > 0; previousHalfVelocity = centerVelocity-acceleration*step/2, nextHalfVelocity adds that increment.1

Input fieldMeaning and unitsAccepted input
centerVelocityCenter VelocityRequired. Finite number.
accelerationAccelerationRequired. Finite number.
stepStep duration or increment under the stated convention.Required. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
previousHalfVelocityPrevious Half VelocityRequired. Finite number.
nextHalfVelocityNext Half VelocityRequired. Finite number.
json
{
  "input": {
    "centerVelocity": 3,
    "acceleration": 2,
    "step": 0.5
  },
  "output": {
    "previousHalfVelocity": 2.5,
    "nextHalfVelocity": 3.5
  }
}

Limitations and assumptions

  • This assumes the supplied centered acceleration and time convention; no full leapfrog integration or error estimate is performed.
  • 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 and validate the complete numerical method with its state initialization, boundary conditions and physical model for a reliable simulation.

References

  1. Calculation and input contract: computational-physics/leapfrog-half-step-velocity-offset — tool.io

Similar or alternative tools