Description
Compare a recorded position with a Verlet step.
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.
Compare a recorded position with a Verlet step.
When to use this tool
Use Verlet Position Residual when checking one explicitly supplied integration, flux or lattice-population contribution.
How to use the tool and how it works
- Enter previousPosition, currentPosition, acceleration, timeStep, recordedNext. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read predictedNext, residual. Use the output convention below.
Compare a recorded position with a Verlet step. Require timeStep >= 0; predictedNext = 2*currentPosition-previousPosition+acceleration*timeStep², residual = recordedNext-predicted.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| previousPosition | Previous Position | Required. Finite number. |
| currentPosition | Current Position | Required. Finite number. |
| acceleration | Acceleration | Required. Finite number. |
| timeStep | Step duration in the same time unit used by rates and accelerations. | Required. Finite number; minimum 0. |
| recordedNext | Recorded Next | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| predictedNext | Predicted Next | Required. Finite number. |
| residual | Signed difference in the direction stated above, with matching units. | Required. Finite number. |
{
"input": {
"previousPosition": 0,
"currentPosition": 2,
"acceleration": 1,
"timeStep": 1,
"recordedNext": 6
},
"output": {
"predictedNext": 5,
"residual": 1
}
}Limitations and assumptions
- Use consistent length/time units; forces, constraints and the validity of the previous integration state are not 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
Use and validate the complete numerical method with its state initialization, boundary conditions and physical model for a reliable simulation.
References
Similar or alternative tools
- Verlet One Position Step
Return one position-Verlet update.
- Molecular Dynamics Half Kick One Axis
Return one molecular-dynamics half kick.