Planetary SER stacking, and the three things it insists you choose

Planetary takes exactly one local, uncompressed SER capture, validates its fixed 178-byte header before reading a single timestamp or frame sample, and then requires three explicit choices — a region, a reference frame and how many of the best frames to keep — because each of them changes what the picture is, and none of them can be inferred from the file.

Why keeping the worst frames makes the picture worse

A planet is bright enough to expose in milliseconds, so a capture is thousands of frames rather than dozens. The atmosphere is not steady across them: a few per cent are taken through a moment of calm air and are genuinely sharp, most are not, and averaging all of them averages the calm ones into the turbulent ones.

So the frames are ranked and only the best fraction is stacked. That is the whole idea, and everything below is about making the ranking mean something.

A SER file opens with a fixed 178-byte header describing the dimensions, the pixel depth and the colour layout. This mode validates all of it before reading a single timestamp or frame sample — because a capture whose header disagrees with its contents will otherwise be read as a plausible picture of the wrong thing, at the wrong size, in the wrong colour order.

Uncompressed MONO, RGB, or BGR where the file declares BGR. A layout it cannot name is a refusal rather than a guess about which two channels to swap.

The three choices, and why none of them has a default

What it refuses, by name

Try it on your own night

Open the stacker Nothing is uploaded and nothing is installed; the frames are read in your browser.