pile-up and the bunch crossing
Picture a strobe light flashing in a crowded room. Each flash freezes a moment, but in that one moment you might catch several people doing several different things at once, all overlaid on top of each other. A bunch crossing is the collider's version of one strobe flash: the protons are not a continuous stream but are gathered into tight clumps called bunches, and a bunch crossing is the instant two such clumps pass through each other. Pile-up is what makes that snapshot messy — the fact that during a single crossing, many separate proton pairs collide at almost the same place and time.
Here is why it happens. To get enough rare, interesting collisions, you have to pack each bunch with billions of protons. When two such bunches cross, you do not get one collision — you get many, perhaps thirty or fifty or more, all squeezed into the same few centimetres and the same fraction of a nanosecond. Only one of them might contain the rare process you care about; the rest are ordinary 'minimum bias' collisions that dump extra tracks and energy into your detector. Pile-up from collisions in the same crossing is called in-time pile-up; leftover signals from neighbouring crossings are out-of-time pile-up.
Pile-up is the price of high luminosity, and managing it is one of the central practical challenges of a modern collider. Experiments fight back with finely segmented detectors and precise vertex reconstruction: by measuring exactly where along the beam each track originated, they can assign tracks to separate collision vertices and keep only those from the interesting one. A common misconception is that more collisions always means better data; beyond a point, pile-up degrades resolution and can fake or wash out a signal, so detectors must be specifically designed to cope with it.
In a busy LHC run, a single bunch crossing might produce a tangle of fifty overlapping collisions along the beam line. The detector sees fifty separate vertices, like fifty tiny explosions in a row, and the analysis software must pick out the one that matters and ignore the other forty-nine.
One crossing, many collisions: pile-up is the overlap of dozens of vertices in a single snapshot.
Pile-up is not noise from the electronics — every overlapping collision is a real, physical event. The challenge is sorting the wanted collision from a crowd of equally real but uninteresting ones.