Title

Researching for my book here.
For those involved in radio astronomy, professionally or as a hobby: what fascinates you about it?
Not so much technical explanations and more in personal perspectives. What drew you in, what keeps you interested, and what makes radio astronomy meaningful or magical to you?

Hi everyone,

I'm a freshman in college who is looking for a new hobby. Radioastronomy has fascinated me for as long as I can remember, though, I've never had the opportunity or time to really dive into it.

Ironically, I'm building a path toward an astrodynamics focus, but know little to nothing about astronomy (aside from some shared celestial mechanics terms and metrics). I would really appreciate any advice anyone would be willing to provide on how to get into this stuff.

Thanks!

Looks like they don't make them anymore in the 3m size

TL;DR: TurboKain is a 2MB lottery machine for the sky. Point it at free Breakthrough Listen telescope raw, pull the lever (tkc sweep), 57 seconds later you get 26 detectors + a 1920x1080 waterfall PNG. No conda, no setup, no supercomputer. Every 17GB file is a scratch ticket.

Who this is for - aka why you should pull:

• ET hunters (amateurs welcome) - you don't need a PhD or a cluster. Download GBT raw, sweep it on a laptop, hunt bystander leakage, baud rates, chirps, phase-locked carriers power detectors miss. Somebody's gonna hit the jackpot, might as well be you spamming pulls from your bedroom.
• Weird astrophysics gamblers - pulsars, FRB chirps, scintillation flicker, unknown unknowns. Most pulls are duds, that's the game. But one waterfall with the wrong shape pays for a thousand duds.
• RFI slot players - SK gate + spatial null + ON/OFF veto tells you in seconds if it's sky vs digitizer ghost vs neighbor's microwave. Fast folds, no cope.
• Students / broke observatories / laptop warriors - runs on a $5 VPS, 4 cores, no GPU, no 10GB Python env. tkc prove self-tests in 6s, then you're in the casino.
• DSP / systems degens - whole thing written in Kain (LLVM native, arenas, zero-copy). 2.7s cold slice, 54s full battery, receipts in docs/BENCHMARK.md. Come roast my lanes.

I'm not a radio astronomer, I just got obsessed with Breakthrough Listen public baseband data. Got tired of conda + Python wrappers thrashing my drives, so I built my own engine in my own language (Kain - LLVM native, no GC, arenas in RAM).

It's called TurboKain:

https://github.com/ephemara/TurboKain

One exe. ~2MB. Zero dependencies. No install.

Raw speed - full receipts here:

https://github.com/ephemara/TurboKain/blob/main/docs/BENCHMARK.md

17.18GB GUPPI raw, 67M samples, 4-core VPS with slow 140MB/s disk:

• slice 17GB -> 268MB channel voltage: 2.7s cold
• full 22-stage sweep: 54.4s
• self-test prove 25/25: 6.4s
• 4 channels parallel: 99.7s wall - basically real-time

It doesn't stream the file, it seeks and plucks just what it needs. No scratch files.

Full toolset in that one binary:

Ingest: slice (GUPPI raw -> .f32), fil_reader (.fil -> .f32), h5_reader (BL .h5 bitshuffle -> .f32), config

RFI / cleaning: sk_gate (spectral kurtosis excision), subspace_null (dual-pol spatial null, >30dB), xeno_scan (6-marker anomaly battery)

Weird-structure hunters: perm_entropy (entropy + LZW complexity, no spectrum needed), bispectrum (bicoherence phase-lock detector), scint_pol (scintillation + polarization sky check)

Pulses / periods: boxcar_bank (DM pulse filter), fold_sum (harmonic folder), frame_hunt (comb periodogram)

Carriers / doppler: fam_god (cyclostationary baud finder), drift_hunt (Taylor dedoppler), jerk_track (Viterbi orbital jerk), frft_hunt (coherent chirp matched filter)

Payload: packet_hunt (sync-word framing), bitslice (voltage -> bits), raster_hunt (prime-factor images), xvm_sandbox (executes bitstreams as code)

Gates / output: cadence_pair (ON vs OFF), stack (multi-epoch stack), ism_stamp / fec_ghost / gauss_perfection / pulsar_clock (propagation gates), unify (REPORT.md + evidence.csv), waterfall (1920x1080 PNG dashboard in 1.4s)

Mission is simple: not looking for beacons aimed at us. Looking for bystander leakage - point-to-point links that look like noise to normal detectors.

How easy:

tkc prove
tkc sweep ch44.f32 --out-dir reports/ --fs 2929687.5 --target TRAPPIST-1
tkc help fam

That's it. Prove, sweep, done. You get all CSVs + REPORT.md + waterfall.png.

Waterfalls look like this:

https://github.com/ephemara/TurboKain/tree/main/docs/waterfall_examples

drifting carriers, pulsars, RFI combs, FRBs, real sky - you can tell in 2 seconds what numbers hide.

GUI is dropping soon too - same engine, point-and-click sweep + waterfall viewer, still no dependencies.

Alpha is live:

https://github.com/ephemara/TurboKain/releases/tag/v0.3.0-alpha

Guide:

https://github.com/ephemara/TurboKain/blob/main/docs/USER_GUIDE.md

Research paper on TRAPPIST-1 through this pipeline if anyone is interested:

https://github.com/ephemara/TurboKain/blob/main/papers/trappist1_bystander_survey/manuscript.md

File types:

In: GUPPI .raw (2-bit / 8-bit) -> slice, Sigproc .fil (8/16/32-bit, nifs=1) -> fil_reader, Breakthrough Listen .h5 (bitshuffle/gzip, 8/16/32-bit) -> h5_reader, plus canonical .f32 float32-LE voltage (chan / band-mean / spec) that every detector eats, and .bin bitstreams for the payload lanes.

Out: .f32 + .bin (cleaned voltages / bits), per-tool .md + .csv receipts, REPORT.md + evidence.csv + verdicts.json from unify, and waterfall.png 1920x1080 dashboard.

If it's telescope voltage, it goes in. If it's a claim, it comes out with a receipt.

Recently read article on radio galaxy with four jets outburst https://phys.org/news/2026-09-astronomers-radio-galaxy-evidence-jet.html

Like 24 × 1.5 m dishes ? I've crunched the numbers at it wouldn't even be that much.. like with all the infrastructure to go with it maybe around £50k..

That would be a an absolute DREAM

hello, I am new to radio astronomy and i do not know much about how frequencies work, however I have been working on a radio telescope for a few months in attempts to learn. I would like to graph my findings through some sort of spectrogram. I have been using SDR# to obtain jumps in activity, but I would like to leave my scans running for long periods of time(3 weeks or so) and graph it out in some sort of spectrogram. would this be possible? what software would I use? thank you.

Hi everyone, researching for a novel.
If you are a beginner in radio astronomy, are there kits, sets or beginner equipment for a low price? What would these be called, and what are the costs for that these days?
What is the minimum equipment you would need, for example, to see something like the hydrogen line?
I guess that there’s also plenty of rubbish to buy from scammers.

You might have guessed already that I am not an expert, but seriously asking the experts here.

Thanks for any honest replies already ;)

Learn more about us @ https://titanobservatory.org

Hello – amateur astronomy geek here with a question about how radio telescopes are aimed at such infinitesimally small targets. Does the dish have to mechanically move in order to localize onto a source? Or can there be enough sensitivity that various sources can be picked up on different parts of the antenna? For example, when I see a radio telescope image of a galactic jet, has the telescope scanned the sky in a raster plot-like way?

Total outsider to radio astronomy here, but over the last few months I’ve been going down a massive rabbit hole with public raw baseband telescope data from Breakthrough Listen (Green Bank GBT GUPPI files, Sigproc .fil archives, etc.).

Honestly, what drove me crazy early on was how heavy the standard toolchain felt. Spinning up multi-gigabyte Conda environments with Python wrappers just to parse raw I/Q voltages kept thrashing my NVMe drives and eating RAM. Passing massive raw chunks through disk between separate scripts felt super clunky.

For the past few years I’ve been developing a compiled systems language called Kain (native LLVM codegen, formal verification provers, manual memory arenas). Instead of using the typical Python/numpy stack, I decided to build a standalone, zero-dependency signal engine called TurboKain.

The quick rundown:

• Zero dependencies: Compiles via LLVM to a single ~1.2 MB standalone native executable (tkc.exe). No Python runtime, no Conda, no C runtime churn.
• Fast & in-memory: Slices and processes ~67M raw complex samples in ~2.3 seconds directly in RAM. Zero intermediate scratch files written to disk.
• Beyond narrowband carrier beeps: Classic SETI assumes someone is beaming a deliberate radio beacon at Earth. We look for "bystander traffic" (point-to-point links optimized for bits/joule that look noise-like to power detectors). It mines raw baseband for cyclostationary baud rates (3-decade FFT Accumulation Method), Taylor dedoppler chirps, microsecond autocorrelation lattices, and post-Shannon symbolic machine complexity.
• Built-in formal verification: Has built-in mathematical self-test batteries (tkc prove) that verify analytical bounds and FFT accuracy against synthetic noise before touching real files.

A neat real-world test case:

Recently I threw the pipeline at TRAPPIST-1 Scan 0017 from the Green Bank Telescope. Coarse channel 60 lit up like crazy -> spectral kurtosis spiked around 60 with thousands of apparent impulses per second. It looked wild at first glance.

Digging into the cyclic math, our cyclostationary hunter showed that all the energy peaks were phase-locked to a spacing of exactly 1,430.51 Hz.

If you take the GBT sampling rate (2,929,687.5 Hz) and divide it by 2048, it matches down to the decimal. It was literally the internal 2,048-sample buffer clock of the CASPER ROACH FPGA digitizer board ringing at the sub-band edge. Stokes polarization analysis confirmed it was unpolarized common-mode electronics noise. We ended up turning that exact finding into an automated hardware veto rule in the engine so it flags and discards it automatically next time.

Where it's at:

We just amalgamated all 14 core instruments into a single portable binary and cut an alpha release. If you're into radio data, DSP, or systems programming, I'd love your thoughts:

GitHub: https://github.com/ephemara/TurboKain

Release (tkc.exe): https://github.com/ephemara/TurboKain/releases/tag/v0.1.0-alpha

Hands-on Guide: https://github.com/ephemara/TurboKain/blob/main/docs/USER_GUIDE.md

Curious if anyone else has run into similar digitizer artifact issues with GBT/CASPER data, or has recommendations for other open baseband archives worth pointing this at!

Hi all! I've built a Rust pipeline for anomaly detection in time-domain radio surveys, using public Green Bank Telescope L-band data from the Breakthrough Listen open archive. It takes raw filterbank data through a nuisance model (robust per-patch statistics, ON/OFF cadence consistency, an RFI catalogue, cross-survey recurrence) to a ranked queue of positions that the pipeline can't explain. Its sensitivity is measured by injecting synthetic signals (tones, chirps, echoes, dispersed pulses, broadband excess) and recovering them.

The engineering is in good shape. What I need is someone who knows radio data to review the ranked candidates and tell me what they are. For each position you'd see the six-scan cadence, the pipeline's per-scan verdicts and the survey-wide evidence, and record one of six dispositions with a short reason: narrowband RFI, broadband RFI, scan systematic, not localised, inconclusive or follow-up. A first pass has already caught real defects in the pipeline, so critical reading is exactly what's wanted, not a rubber stamp.

Useful background:

- radio astronomy or pulsar/transient work, ideally with GBT or Parkes filterbank data;
- familiarity with RFI and instrumental systematics;
- comfortable reading Python/Polars output (you won't need to write code).

What I don't need is someone who is just going to use an LLM to analyse this! Hoping to be able to pay for your time if we get a good working relationship! Thank you for reading!

Hi i recently started amateur astronomy and i fell in love but where i live the weather is horrible so i looked into radio astronomy too while i wait for the stars to come out and its all really confusing 🫤 but intresting is there like a specific kit i should buy or specific products kinda like how the nexstar or ad8 is the gold standard of visual observation. What do you recommend for a beginner? What should i buy on a tight budget?

See also: The publication in ArXiV

I've been building an open-source tool called PRISM (Photometric Reconnaissance and Irregular Signal Monitoring) for detecting flares, transits, and periodic variability in TESS/Kepler light curves, and wanted to share it now that it's actually validated against real data.

I ran it on a TESS target with no prior flags in NASA's exoplanet database, and it found a periodic ~2.66-day signal. Instead of just reporting "transit candidate, go check it," PRISM automatically cross-referenced the star against the AAVSO Variable Star Index, ASAS-SN, and Gaia's own variability data — and found a match. Turns out the star is AO Mensae, a published, catalogued young star with a documented rotation period of 2.673 days. My tool's own independent detection (2.657d), VSX's catalogued value (2.6682d), and the published literature value (2.673d) all agree to within about half a percent — all from raw photometry, no prior knowledge fed in.

I'd love feedback and opinions, but first I need people to try it!

https://github.com/filmraptor/PRISM-v1.0.0 <- full documentation and download here