Skip to main content
Dryad

Data from: A Search for Technosignatures Around 31 Sun-like Stars with the Green Bank Telescope at 1.15–1.73 GHz

Cite this dataset

Margot, Jean-Luc; Pinchuk, Pavlo; Geil, Robert; Lynch, Ryan (2021). Data from: A Search for Technosignatures Around 31 Sun-like Stars with the Green Bank Telescope at 1.15–1.73 GHz [Dataset]. Dryad. https://doi.org/10.5068/D1937J

Abstract

This dataset describes candidate signal detections obtained at the Green Bank Telescope in 2018 and 2019 and reprocessed with the 2020 UCLA SETI Group data processing pipeline.

We conducted a search for technosignatures in April of 2018 and 2019 with the L-band receiver (1.15–1.73 GHz) of the 100 m diameter Green Bank Telescope.  These observations focused on regions surrounding 31 Sun-like stars near the plane of the Galaxy.  We present the results of our search for narrowband signals in this data set as well as improvements to our data processing pipeline.  Specifically, we applied an improved candidate signal detection procedure that relies on the topographic prominence of the signal power, which nearly doubles the signal detection count of some previously analyzed data sets.  We also improved the direction-of-origin filters that remove most radio frequency interference (RFI) to ensure that they uniquely link signals observed in separate scans.  We performed a preliminary signal injection and recovery analysis to test the performance of our pipeline.  We found that our pipeline recovers 93% of the injected signals over the usable frequency range of the receiver and 98% if we exclude regions with dense RFI.  In this analysis, 99.73% of the recovered signals were correctly classified as technosignature candidates.  Our improved data processing pipeline classified over 99.84% of the ~26 million signals detected in our data as RFI.  Of the remaining candidates, 4539 were detected outside of known RFI frequency regions.  The remaining candidates were visually inspected and verified to be of anthropogenic nature.  Our search compares favorably to other recent searches in terms of end-to-end sensitivity, frequency drift rate coverage, and signal detection count per unit bandwidth per unit integration time.

Methods

Please see journal article for methods.  

Usage notes

The field descriptions are as follows:

  • ID: a unique integer identifier for the signal
  • NAME: the name of the source
  • SCAN: the scan index number (1, 2) for the source
  • MJD: the Modified Julian Date at the start of the scan
  • FREQ: the frequency (Hz) at the start of the scan
  • DFDT: the rate of change in frequency (Hz/s)
  • Z: the signal power integrated over the scan duration aka Z score (standard deviations of the noise)
  • BW: an estimate of the bandwidth (FWHM) of the signal (Hz)
  • FSNR: a flag set to Y if signal power exceeds detection threshold
  • FDOP: a flag set to Y if DFDT is not zero
  • FBTH: a flag set to Y if signal is detected in both scans of this source
  • FOTH: a flag set to Y if signal is not detected in scans of other sources
  • FAND: a flag set to Y if FSNR=FDOP=FBTH=FOTH=Y
  • PARTNER: the ID of the signal in a subsequent scan of this source, if known
  • RFICODE: an identifier for the probable source of RFI
  • NOTES: additional notes
The field names and types are as follows:

+---------+--------------+
| Field   | Type         |
+---------+--------------+
| ID      | int(11)      |
| NAME    | varchar(50)  |
| SCAN    | int(4)       |
| MJD     | double(16,8) |
| FREQ    | double(20,6) |
| DFDT    | double(14,8) |
| Z       | double(15,3) |
| BW      | double(8,1)  |
| FSNR    | char(1)      |
| FDOP    | char(1)      |
| FBTH    | char(1)      |
| FOTH    | char(1)      |
| FAND    | char(1)      |
| PARTNER | int(11)      |
| RFICODE | char(5)      |
| NOTES   | text         |
+---------+--------------+