NTP
The de facto standard internet protocol for time synchronization, in widespread use since 1985. It estimates network latency by exchanging messages with upstream atomic clock servers and corrects the local clock accordingly, using a slewing mechanism to adjust the clock gradually and avoid time jumps.
Timeline (last 90 days)
Google proposed and adopted the Leap Smear transition technique in 2011, spreading the extra 1 second evenly across each NTP time signal within a window around the leap second.
The Linux kernel maintains the system clock, and the NTP implementation in the kernel is responsible for adjusting the local clock rate and offset based on upstream time sources.
The current NTP+RL paradigm has three mechanistic gaps: the absence of goal generation, the absence of embodiment and interaction, and the absence of continual learning.
NTP is the training objective and autoregressive generation is the inference method, both based on the same mechanism of predicting the next token from the preceding context.
NTP provides the compression foundation for general representations, and RL provides the ability to perform goal-directed search over those representations; in principle, the combination of the two can approach general intelligence.
The strongest argument supporting that NTP can produce general capabilities comes from the equivalence of compression and prediction.
Computers track time through a battery-powered RTC (real-time clock) and an OS software clock driven by the CPU crystal oscillator; thermal expansion and contraction, aging, and defects in the crystal oscillator can cause drift of several milliseconds to several seconds per day.
NTP uses a slewing mechanism that gradually speeds up or slows down the system clock over an extended period to catch up to true time, avoiding sudden time jumps.
NTP has been the de facto standard for Internet time synchronization since 1985, and its slewing mechanism adjusts the clock at a rate of up to 500 ppm per day.
NTP uses January 1, 1900 as its epoch starting point.
2 more timeline events
All Facts (12)
Common sensor synchronization approaches include hardware trigger synchronization, NTP/PTP network time protocols, and interpolation alignment in post-processing
85%UnverifiedThe Linux kernel maintains the system clock, and the NTP implementation in the kernel is responsible for adjusting the local clock rate and offset based on upstream time sources.
50%UnverifiedGoogle proposed and adopted the Leap Smear transition technique in 2011, spreading the extra 1 second evenly across each NTP time signal within a window around the leap second.
50%UnverifiedNTP is the training objective and autoregressive generation is the inference method, both based on the same mechanism of predicting the next token from the preceding context.
50%UnverifiedNTP provides the compression foundation for general representations, and RL provides the ability to perform goal-directed search over those representations; in principle, the combination of the two can approach general intelligence.
50%UnverifiedThe strongest argument supporting that NTP can produce general capabilities comes from the equivalence of compression and prediction.
50%UnverifiedThe current NTP+RL paradigm has three mechanistic gaps: the absence of goal generation, the absence of embodiment and interaction, and the absence of continual learning.
50%UnverifiedComputers track time through a battery-powered RTC (real-time clock) and an OS software clock driven by the CPU crystal oscillator; thermal expansion and contraction, aging, and defects in the crystal oscillator can cause drift of several milliseconds to several seconds per day.
50%UnverifiedNTP uses a slewing mechanism that gradually speeds up or slows down the system clock over an extended period to catch up to true time, avoiding sudden time jumps.
50%UnverifiedNTP has been the de facto standard for Internet time synchronization since 1985, and its slewing mechanism adjusts the clock at a rate of up to 500 ppm per day.
50%UnverifiedNTP uses January 1, 1900 as its epoch starting point.
50%UnverifiedFor scenarios such as email sending, even physical clocks calibrated with NTP cannot completely eliminate judgment errors caused by clock drift, which represents the theoretical upper limit of lease mechanisms.
50%