viewof clock_error_value = Inputs.range([0, 1000], {
value: 1,
step: 0.1,
label: "Clock Error Value"
})
viewof clock_error_unit = Inputs.select(
["nanoseconds", "microseconds", "milliseconds"],
{
value: "microseconds",
label: "Time Unit"
}
)
clock_error_seconds = clock_error_unit === "nanoseconds" ? clock_error_value * 1e-9 :
clock_error_unit === "microseconds" ? clock_error_value * 1e-6 :
clock_error_value * 1e-3
position_error_meters = clock_error_seconds * 299792458
html`<div style="padding: 12px; background: #fff3cd; border-left: 4px solid #E67E22; margin: 12px 0;">
<strong style="color: #2C3E50;">Position Error:</strong>
<span style="color: #E74C3C; font-size: 1.2em; font-weight: bold;">${position_error_meters.toFixed(2)} meters</span>
${position_error_meters > 1000 ? `<span style="color: #7F8C8D; margin-left: 8px;">(${(position_error_meters / 1000).toFixed(2)} km)</span>` : ''}
<div style="margin-top: 8px; color: #7F8C8D; font-size: 0.9em;">
This is why GPS satellites need atomic clocks with ~1 nanosecond/day accuracy!
</div>
</div>`Clock Error Impact
Clock Error Impact
animation
gps
location
Try Set clock error Value to 1 and change Time Unit from microseconds to nanoseconds.
Observe Watch Position Error for 1 microsecond and 1 nanosecond.
Explain Explain why 1 microsecond creates a larger Position Error than 1 nanosecond.
Technical boundaries. Position Error is clock error in seconds multiplied by light speed. The calculation models clock error alone.
Critical Challenge: Both transmitter and receiver must have synchronized clocks to know the true transmission time.
NoteClock Error Impact
Key insight: Even tiny clock errors create huge position errors because signals travel at light speed (300 million meters/second).