Description
Map supplied simulation time to a physical-seconds reference.
Numerical physics calculations depend on discretization, index conventions, boundary conditions and model units. A local force kick is only part of an integration method, a stencil residual is not a solved field, and a one-sided power weight is not a spectral-density normalization. Floating-point resolution also limits grid and coordinate representations.
Map supplied simulation time to a physical-seconds reference.
When to use this tool
Use Simulation Time Unit Crosswalk when you already have simulationTime, physicalSecondsPerTimeUnit, originPhysicalSeconds and need to map supplied simulation time to a physical-seconds reference.
How to use the tool and how it works
- Enter simulationTime, physicalSecondsPerTimeUnit, originPhysicalSeconds. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read physicalTimeSeconds. Use the output convention below.
Require physicalSecondsPerTimeUnit>0; return originPhysicalSeconds+simulationTime*factor.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| simulationTime | Simulation Time | Required. Finite number. |
| physicalSecondsPerTimeUnit | Physical Seconds Per Time Unit | Required. Finite number; strictly above 0. |
| originPhysicalSeconds | Origin Physical Seconds | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| physicalTimeSeconds | Physical Time Seconds | Required. Finite number. |
{
"input": {
"simulationTime": 12,
"physicalSecondsPerTimeUnit": 0.5,
"originPhysicalSeconds": 100
},
"output": {
"physicalTimeSeconds": 106
}
}Limitations and assumptions
- Signed simulation time is accepted. No calibration, simulation epoch, clock, physical validity or actual time evolution is inferred.
- 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 discretized model, integration algorithm and boundary treatment. Assess convergence, conservation and stability with the full calculation; individual residuals, CFL components, relaxation terms and index mappings do not establish numerical accuracy or physical validity.
References
Similar or alternative tools
- Time Step Last Short Step Length
Choose a supplied simulation's final shortened time step.
- Leapfrog Staggered Time Label
Preserve explicit position and velocity staggered-time labels.