Lab reports
The why behind each part of RadBeeper, written up properly — the arithmetic, the failures that shaped it, and the prior art.
| The cascade strip | Chained dyadic time compression: one row of a terminal that holds ten minutes of a Geiger counter and still shows this second. |
| The native build | This is where new work goes now. The one-file Python is the original, and it is now the archive: it is kept as the differential oracle, as the owner of the part |
| Prior art: what GeigerLog and gq-gmc-control already know | Read on 4 September 2026, against radbeeper 0.1.0. |
| The big number and the five averages | ← The counters and the dials · ↑ Reading the window · The status line → |
| The counters and the dials | ↑ Reading the window · The big number and the five averages → |
| The counts | ← The drum spectrogram, read as a landscape · ↑ Reading the window · The random line → |
| The drum spectrogram, read as a landscape | ← The status line · ↑ Reading the window · The counts → |
| Reading the drum spectrogram | The striped panel in the middle of the RadBeeper window, and how to read it. It answers one question: is anything reaching the counter on a schedule? |
| The random line | ← The counts · ↑ Reading the window · The table → |
| The status line | ← The big number and the five averages · ↑ Reading the window · The drum spectrogram, read as a landscape → |
| The table | ← The random line · ↑ Reading the window |
| Reading the window | What every number on the RadBeeper window means, feature by feature. |
| Reference | The parts of RadBeeper worth looking up rather than reading: the tube factor, the counter's protocol, what it costs to run, how it is tested, and how the screen |
| Running it | A lab report on keeping a counter logging unattended: the boot service, one log directory two programs can both write, hotplug, and publishing the result withou |
| Technical description | How RadBeeper works, for somebody who wants to know: what it reads, what it computes, what every part of the screen is made of, and what it writes to disk. |
| A Signed Chain of Custody for a Single-Maintainer Rust Crate | Paul Richeson · RadBeeper · Copal Linux |
| The drum spectrogram | A short-time Fourier transform of a Geiger counter, kept a row at a time and laid up the paper like a seismograph's, by a pen that is hotter and wider for what |
| Reading the Raw Record: A Frame Browser for a Continuously Sampled Decay Log | Paul Richeson · RadBeeper · Copal Linux |
| The log | A lab report on the files RadBeeper writes: what is in a row, why an empty field is not a zero, where the bytes live, and the second file that records the room |
| The Monthly Record: Publishing a Continuous Measurement Without Publishing a Street Address | Paul Richeson · RadBeeper · Copal Linux |
| Random numbers out of decay | A lab report on RadBeeper's entropy source: where the bits come from, three ways this is normally done wrong, why the model that used to be assumed was measurab |
| The spectrum, where flat is the good answer | Radioactive decay is a Poisson process, and the power spectrum of a Poisson process is flat — white noise, every frequency carrying the same expected power. A h |
| The stream | One reader, many watchers: sharing an exclusively-locked serial port among a logger, a terminal monitor and a window, and the instrument panel built on top of i |
| Troubleshooting | 1. No serial node. /dev/ttyUSB does not exist. Four causes, in the order they are worth checking — the first three are the counter's end and cost nothing to rul |