[time-nuts] Thunderbolt temperature spikes

[Mark Sims]

Looking back through some old logs with my New and Improved Spike Finder (tm),  it appears that spikes seem to occur, on average, around every 2-3 hours and their effect shows up in the data for around 20 seconds...  so figure on 1 part in 500 of the temperature data is corrupted by their effect.  It is almost certain that the spikes are not caused by real temperature changes,  but are the effect of some noise or firmware glitch.  In a system where performance is measured in parts per trillion,  something that effects .2% of a critical parameter's measurement is bound to have an adverse effect.
----------------------------------------

_________________________________________________________________
It’s a talkathon – but it’s not just talk.
http://www.imtalkathon.com/?source=EML_WLH_Talkathon_JustTalk