trigger and data-acquisition system

Imagine a security camera that captures forty million frames every second — far more than any disk could ever store, and almost all of them showing nothing of interest. You would need a smart system that watches the live feed, throws away the boring frames in real time, and saves only the few that matter. That is exactly the problem at a modern collider, and the trigger and data-acquisition system is the solution: it decides, in a flash, which collisions are worth keeping, and then ferries that surviving data off to storage.

The numbers are stark. At the Large Hadron Collider, proton bunches cross about forty million times a second, and recording every crossing would mean petabytes of data per second — utterly impossible to store. The trigger is the fast filter that prevents this. It usually works in stages: a first level, built from custom electronics, looks at coarse information within microseconds and rejects the vast majority of crossings; a later level, running software on large computer farms, examines the survivors more carefully and keeps perhaps a few hundred to a few thousand events per second. The data-acquisition system, or DAQ, is the plumbing that reads out every detector channel for an accepted event, assembles the millions of fragments into one coherent record, and writes it to storage for later analysis.

This stage is invisible in textbooks but absolutely decisive in practice: a discovery you fail to trigger on is a discovery you simply never recorded. Designing triggers is therefore a high-stakes act of foresight — you must decide in advance what a new phenomenon would look like, because anything thrown away is gone forever. The sobering caveat: the trigger introduces an unavoidable bias. Experiments can only study what they chose to keep, so a poorly designed trigger could blind an experiment to genuinely new physics that did not match its expectations.