Planetary pre-processing, modernized and open

OPIPP is an independent, fully managed continuation of PIPP (Planetary Imaging PreProcessor). It reads the same captures, accepts the same command-line switches and produces the same output layout — but the code is new, readable C# that can keep evolving.

Download for Windows Source on GitHub 0.3.0-alpha GPLv3 Windows x64 · self-contained

01Where it stands

Runner results, parity comparisons and planning estimates are labelled separately. Only the parity cases are compared with the original binaries; the rest are managed tests, golden files and independent decodes.

1446
tests, 0 failing
27/27
compared parity cases
131
switches addressed
76
verified byte-for-byte
≈95%
weighted estimate
EvidenceWhat it establishes
1446 managed teststhe managed engine follows the contracts in status.md; 2 skip in CI without the evaluation capture
Golden filesoutput matches committed native fixtures for the registered synthetic cases
Independent decodesfiles are readable and numerically correct outside OPIPP's own readers
27/27 parityevery registered comparison against the original engine matches; 2 differences are deliberate
CIbuild, suite, documentation consistency and a packaged smoke convert pass on a clean runner

0.3.0-alpha — field-rotation correction is now part of final-image integration. PIPP aligns by translation only, so a rotating capture — a handheld lunar video, or an alt-az mount without a derotator — blurs as the radius grows. OPIPP estimates a per-frame angle against frame 0, rotates bicubically about the image centre, crops to the rectangle every rotation fills, and finishes with a correlation offset. Edge sharpness gains 2.42x at 1.45 deg of rotation and 21.5x at 116 deg; a still sequence is byte-identical. See derotation. Release notes.

Integration has also been run on real captures: Jupiter (2011 AVI, 2023 TIFF) and Saturn (2022, 8,984 frames), plus Moon and Mars stills. Peak process memory is measured for every integration route, staging is owned by a run directory, and a raw Bayer capture now tells you to debayer first (-db) instead of guessing. See validation and memory. Release notes.

02Completeness by area

Weighted by how much of the product each area represents. The weights are a judgement call, published in the roadmap so they can be argued with. These are planning estimates, not measured reliability or an accuracy score.

Output formats99%
Core image operations98%
Frame selection97%
Calibration & masters96%
Input formats95%
Animation / GIF95%
Layout, logs, -gui99%
GUI application92%
Alignment & tracking85%
Stacking70%

Surface-feature tracking is exact on 23 of 30 frames of one real Saturn capture, and one pixel off on the rest. That result does not measure general tracking accuracy. Final-image stacking controls, disk-backed median and the other known gaps remain open.

03Roadmap

Phases are closed only when a parity case or a test proves them.

PhaseStateWhat it means
1 · Drop-in paritydoneOutput layout, numbering, logs, exit codes, -gui token stream
2 · Remaining formatsdoneBMP, Y8, GIF, colour SER, AVI including MJPEG
3 · CalibrationdoneDark/flat/flat-dark masters in the engine's .tmp format
4 · Selection, alignment, stackingin progressSelection and Core stacking tested; tracking, final-image controls and large median stacks remain open
5 · Animation & long taildone-anim_*, WinJUPOS naming, legacy AVI, RAW switches
6 · GUI paritydoneFully managed — no native DLL required
7 · Alpha builddoneSelf-contained Windows build with GUI and CLI

Next unit of work

Port the engine's coarse search stage (FUN_1400a7ec0) and re-enable the seed. Success criterion: the synthetic probe still refuses content the original refuses, and the Saturn fixture reaches at least 28 of 30 frames.

04What it does

Reads your captures

SER, AVI (including MJPEG), FITS, TIFF, PNG, BMP and baseline DNG — decoded in managed code.

Pre-processes

Debayer, calibrate with dark/flat masters, stretch, bin, resize, rotate, flip, mono or colour.

Selects & aligns

Quality ranking (three algorithms), planet detection with rejection reasons, centring, surface tracking, stacking.

Writes what you need

TIFF, FITS, PNG, BMP, SER, AVI and animated GIF, in the original's numbered layout with matching logs.

Drops in

The CLI speaks the same switches and the same stdin protocol as pipp_core.exe, so existing scripts and front-ends keep working.

Stays open

GPLv3, no native dependencies, no vendored binaries — build it yourself from source.

05Known gaps & deliberate divergences

Listed rather than hidden. If something here matters to your workflow, that is exactly the feedback worth sending.

06Feedback is the point

This is early. The most useful thing you can send is a capture that fails, stalls or comes out worse than the original.

Report a capture

Attach the SER/AVI, the command line you used, and the log from <output>/logs/.

Describe a workflow

What do you do in PIPP that OPIPP makes awkward or impossible?

Compare output

Run a job through both engines and diff the frames — the parity harness makes this mechanical.