To assure ourselves that the receiver is running properly,
SETI@home checks its system temperature on a daily basis. We interpret
high system temperatures as a warning; higher temperatures interfere with
the receiver's ability to detect signals and can be due to either a
hardware failure of some kind or interference from an external source
(such as RFI).
Every day we monitor system temperature by downloading and plotting
chunks of sample data from Arecibo. (This data is sampled from our hydrogen survey. ) Below are system temperature graphs for February
2-3, 2003. The first graph (February 3) is an example of a normal day when
everything is running smoothly:

| System temperature graph for February
3, 2003. |
Similar to other graphs from our hydrogen survey (from Newsletter
18, for example), the x-axis represents velocity relative to our solar
system; negative velocities represent hydrogen moving away from us while
positive velocities represent hydrogen moving toward us. The y-axis
represents system temperature, which increases as noise and/or signal
detections increase. We expect a hump close to a velocity of zero, because
most detected hydrogen moves at slow rates relative to the solar system.
The red data is from SETI@home's data recorder, while the green line
represents data from the LDS hydrogen survey. (The Leiden-Dingeloo Survey
(LDS), published in 1997, is the most complete hydrogen survey to date.)
We compare our data with the LDS data to affirm that nothing unusual is
happening.
The next graph is from a day earlier (February 2, 2003). The volatile
fluctuation of the red line indicates that there was a problem on this
day—in this case, a radar transmission was broadcast from Arecibo,
generating noise loud enough to drown out our ability to detect data:

| System temperature graph for February
2, 2003. |
|