This page shows results from Nebula, the SETI@home back end. For an explanation of the information here and how it's computed, see Nebula: Completing the SETI@home pipeline. For announcements and discussion, see the Nebula Blog.
This is a work in progress; we're still working out the scoring and RFI algorithms. These pages show the current state. Probably nothing here is an ET signal.
Every so often, after a batch of changes to the algorithms, I run the Nebula pipeline, producing a new set of results here. See a log of the pipeline runs.
The following generally shows the results of analyzing 100K pixels (out of 16M).
Top scores, normalized across signal types
You can 'bookmark' pixels, multiplets, and signals that are of interest (e.g. they look like an ET signal, or RFI removal didn't work properly).
View graphs showing the distributions of signals removed by various RFI algorithms.
RFI zones (pre-Nebula)
RFI zones (Nebula)
This is based on our database of 'WU groups', each of which describes a 107-second period and contains a list of pointings (RA, dec, time) during that period. Early WU groups had one pointing record per 5 seconds. Later this was changed to 1 second, and later still to about 3 seconds.
The telescope sky direction changes at different rates:
This rate is called the 'angular velocity'. We're especially interested in the range from .0021 to .0105, because in that range we can look for Gaussian signals. We'll call that the 'Gaussian range'.
A 'pixel observation' is a string of consecutive pointings within one pixel. An observation is called 'Gaussian' if the angular velocity is within the Gaussian range at least once during the observation.
Here's some data about sky coverage:
©2018 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.