Eye Tracked Foveation Latency Calculator
Actual gaze-to-new foveated-region photon latency for independently aligned sample/eventms, not generic tracking stage sumor headset prediction delay.
Description
Gaze-to-photon latency spans a gaze sample and the photons displaying its matched foveated region.
Gaze-to-photon latency spans a gaze sample and the photons displaying its matched foveated region.1
Both timestamps need a common clock and an independently matched event. The calculation and input requirements are explained below.
When to use Eye Tracked Foveation Latency Calculator
Enter matched gaze-sample and new-region photon timestamps in milliseconds on the same clock.
How to use Eye Tracked Foveation Latency Calculator and how it works
- Prepare the measurements or independently established model inputs described below, with matching units and observation scope.
- Enter the required fields and run Eye Tracked Foveation Latency Calculator.
- Read the result fields using the formula, output units, signs and ordering explained below.
- Correct any rejected inputs and rerun; interpret the result within the stated model and its assumptions.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| actualNewFoveationPhotonTimestampMs | Actual New Foveation Photon Timestamp Ms. Use the units and matching context stated in the calculation below. | number | Required; finite; other constraints below |
| actualMatchedGazeSampleTimestampMs | Actual Matched Gaze Sample Timestamp Ms. Use the units and matching context stated in the calculation below. | number | Required; finite; other constraints below |
Enter matched gaze-sample and new-region photon timestamps in milliseconds on the same clock. The photon timestamp must be at least the sample timestamp. Return their difference, with equal timestamps giving zero.
latencyMs=photonTimestampMs-gazeSampleTimestampMs Apply the input ordering, units and branch conditions stated above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Object containing the calculated or selected fields below. | object |
| result.value | Numeric result under the formula and output units explained above. | number |
{
"input": {
"actualNewFoveationPhotonTimestampMs": 10,
"actualMatchedGazeSampleTimestampMs": 5
},
"output": {
"result": {
"value": 5
}
}
}Limitations and assumptions
The calculation uses the supplied observations and model inputs. It does not collect measurements, select a reference population or coefficient, or establish that the model applies to the actual case. The stated branch conditions and output units remain part of the result.
All fields require explicit values. Unexpected fields, wrong types, nonfinite numbers and sparse arrays are rejected. Alignment, bounds and supported-token rules are explained above; extremely large inputs or nonfinite results can also fail. Input errors differ from successful false comparisons, unavailable-domain flags and empty match lists.
Alternative or Complementary methods
Use Tracking Precision mm Calculator for a complementary operation: Tracking precision concerns how closely repeated measurements cluster.
Use Tracking Accuracy mm Calculator for a complementary operation: Tracking accuracy compares a measured position with an independent reference position.
References
-
Eye Tracked Foveation Latency Calculator — tool.io
Similar or alternative tools
- Tracking Precision mm Calculator
Tracking precision concerns how closely repeated measurements cluster.
- Tracking Accuracy mm Calculator
Tracking accuracy compares a measured position with an independent reference position.