r/SETI

I ran a full independent SETI pipeline over Breakthrough Listen's Proxima
Centauri data - 6 epochs, 700 MHz, 4.9M raw hits, and what survived
▲ 0 r/SETI

I ran a full independent SETI pipeline over Breakthrough Listen's Proxima Centauri data - 6 epochs, 700 MHz, 4.9M raw hits, and what survived

SETI relevance up front (rule 7). This is a narrowband technosignature

search, an independent reanalysis of Breakthrough Listen's public Parkes

archive data for Proxima Centauri.

Not a detection. A clean null result, but the funnel that produced it and

the tooling might interest this sub.

I'm a hobbyist. Over the last few weeks I built an open-source pipeline +

dashboard that works end to end on Breakthrough Listen's public archive:

download (Parkes ON/OFF cadences and GBT ABACAD sessions), turboSETI scans

with configurable drift/SNR, ON/OFF RFI rejection, an automatic per-epoch

RFI zone mapper, barycentric correction, cross-epoch frequency matching,

and incoherent stacking.

The target was Proxima Centauri, six observation epochs from BL's 2017

Parkes campaign, fine-resolution data covering 2.7-3.4 GHz with 3x ON/OFF

cadences per epoch. Closest star, everyone's favorite candidate...

The funnel (all numbers from the final runs)

- Raw turboSETI hits: 4,909,152 (SNR 5+, drift to +/-5 Hz/s)

- ON/OFF rejection kills terrestrial signals present in both pointing

positions: 3,030,707 rejected (61.7%)

- Remaining unique ON frequencies at SNR 8+: 27,533

- Cross-epoch matching at 10 Hz barycentric tolerance, min 3 epochs:

0 frequencies repeat in 3+ epochs

- Final candidates: 0

- Robustness check: relaxing to 2-epoch coincidence at SNR 10 surfaces 7

frequency matches. All 7 fail the OFF veto or report drift rates equal

to the search grid's minimum step, the signature of stationary RFI

rather than a drifting transmitter.

Each epoch was also RFI-zone audited (sliding-window ON-OFF residual vs

the epoch's own noise floor; zones auto-excluded downstream), and the six

epochs were incoherently stacked for sensitivity below single-epoch

threshold. Zero candidates survived the full chain.

Why does a null result matter? It's a constraint, nothing narrowband above

SNR ~8-10 is leaking from Proxima's direction in this band during these six

epochs, verified by an independent implementation with different parameter

choices than BL's published searches. Replication with different tools is

how parameter-choice blind spots get caught. The barycentric matching

is the fun part. Without correction, Earth's orbital motion smears a real

transmitter across tens of kHz between epochs; RFI can't hold a barycentric

frequency across months, so it's the strongest automated filter there is.

The whole thing is open source (MIT, Python, Windows-tested):

https://github.com/w4gon79/backyard-seti

The README walks the full process. Clone to running dashboard to stacked

epochs, both telescopes' data conventions decoded. Work in progress,

but fully usable.

Happy to answer anything about the pipeline, the data handling, or the

funnel numbers.

u/Puzzleheaded_Dish624 — 2 days ago
▲ 0 r/SETI+1 crossposts

A New Hypothesis for the Wow! Signal: A Transient, Moving Source

**A New Way to Look at the 1977 Wow! Signal:

What If the Source Was Moving?**

The 1977 Wow! signal is still one of the most famous radio detections ever made — a strong, narrowband spike near the hydrogen line, lasting 72 seconds, never repeating, and never explained.

Most attempts to understand it assume the source was stationary — something fixed in the sky that Big Ear happened to catch once. But there’s another possibility that fits the data just as well, maybe better:

What if the source was moving?

Not a civilization, not a starship — just anything traveling through the galaxy:
a natural object, a transient emitter, a rotating source, or something sweeping past Earth.

This idea doesn’t require anything exotic. It simply uses the geometry of how Big Ear observed the sky.

1. Why the 72‑second duration doesn’t tell us the signal length

Big Ear didn’t track objects.
It used drift‑scan mode, meaning:

  • the telescope stayed still
  • Earth’s rotation moved the sky across its beam
  • each point in the sky was observed for ~72 seconds

So the Wow! signal lasted 72 seconds because that’s how long Big Ear looked, not because the transmitter emitted for 72 seconds.

The real signal could have been:

  • shorter
  • longer
  • continuous
  • intermittent

We only saw the moment the beam passed over it.

2. The Wow! coordinates aren’t actually “empty”

The Wow! signal came from a patch of sky in Sagittarius, near Chi Sagittarii, along the Milky Way’s plane.

That direction contains:

  • dense star fields
  • interstellar gas
  • dust clouds
  • transient astrophysical sources

Even though the exact optical patch looks blank, the line of sight passes through a busy region of the galaxy.

This matters because objects naturally move through busy regions — stars, debris, gas clouds, and interstellar visitors all follow paths shaped by galactic rotation and gravitational structure.

No civilizations implied.
Just astrophysics.

3. A moving source explains the Wow! signal’s behavior

If the source was in transit — natural or artificial — then:

  • Earth intercepted the signal once
  • Big Ear moved on after 72 seconds
  • the source moved on afterward
  • follow‑up observations saw nothing because the source wasn’t there anymore

This neatly explains:

  • the one‑off nature
  • the narrowband spike
  • the lack of repeat
  • the absence of any visible object
  • the failure of every re‑observation attempt

Nothing about this requires assuming intent or intelligence.

4. Why a second signal would be a breakthrough

If the source was moving, then a second signal — even decades later — would give us:

Direction of motion

A different sky position = a vector.

Speed (via Doppler drift)

A slightly shifted frequency = radial velocity.

Trajectory

Two spacetime points = a path.

Even a faint, ambiguous signal could reveal:

  • whether the source was inbound or outbound
  • whether it was accelerating
  • whether it was rotating
  • whether it was natural or artificial

One more detection turns the Wow! signal from a mystery into a solvable physics problem.

5. Why SETI hasn’t done this yet

SETI traditionally assumes:

  • transmitters are fixed
  • signals repeat
  • sources sit on planets
  • beacons target Earth

So most follow‑ups re‑observe the same coordinates.
But if the source was moving, that strategy will never work.

What’s missing is a search for motion‑linked siblings of the Wow! signal:

  • wide‑field transient monitoring
  • Doppler‑drift pattern matching
  • multi‑decade signal correlation
  • AI‑assisted anomaly detection

This is a gap in current SETI methodology.

6. What a modern Wow! search should look like

A realistic, non‑speculative strategy would include:

Wide‑field radio monitoring

Using arrays like MeerKAT, VLA, FAST, ATA, or CHIME‑style transient detectors.

AI‑driven signal analysis

To identify:

  • narrowband spikes
  • Doppler drift
  • transient events
  • modulation patterns
  • signals similar to Wow! across decades of data

Cross‑observatory verification

Multiple telescopes confirming sky position, frequency, and drift.

Optical/IR mapping

Cataloging stars and objects along any candidate trajectory.

7. Conclusion

If the Wow! signal came from a moving source, then the key to solving it isn’t re‑observing the original coordinates — it’s finding a second signal with similar characteristics.

Even one more detection could reveal:

  • direction
  • speed
  • trajectory
  • origin
  • destination
  • classification

This transforms the Wow! signal from an isolated anomaly into a tractable astrophysical event.

A modern, AI‑assisted, wide‑field search could finally answer the question that has lingered since 1977.#SETI #WowSignal #RadioAstronomy #Astrophysics #SignalAnalysis #Technosignatures

reddit.com
u/Steviestarsteven — 6 days ago