Skip to content

Releases

v0.3.0-alpha

v0.3.0-alpha Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 28 Oct 06:21

OPIPP 0.3.0-alpha (Open PIPP) - Windows x64

Self-contained alpha build of the managed PIPP continuation. It was built and
tested, packaged, and smoke-tested from the extracted zip by the tag-triggered
release workflow before this release was created.

Artifact OPIPP-0.3.0-alpha-win-x64.zip
Size 53557567 bytes
SHA-256 68f6392555b9221ebb012237b6db3be024cf8d8ce50ff2a1d40022dd9f8c0f10
Tag v0.3.0-alpha
Commit b6c858d
Workflow run https://github.com/openpipp/opipp/actions/runs/40643034911

Package contents

  • Opipp.App.exe - the GUI, fully managed, no pipp_dll.dll
  • Opipp.Cli.exe - the command-line engine, drop-in for pipp_core.exe
  • README-ALPHA.txt - quick start, status and licence notes

Status and licence

ALPHA: a working preview, not an official PIPP release, and not affiliated
with Chris Garry or the PIPP project. AI was used to build this. GPLv3 or
later for this repository's code and artwork; not a licence to PIPP. See
NOTICE in the repository.

What changed in 0.3.0

Field-rotation correction

PIPP has no field-rotation correction. Its only rotation is the fixed 90/180/270 family, and every
alignment path (-ctr, surface-feature tracking, -ctrf, stabilisation) produces translation. A
rotating capture therefore smears with radius: on a 30-frame lunar sequence at 0.05°/frame,
translation-only stacking kept 26% of the single-frame edge sharpness; at 4°/frame it kept 2.6%.
That is the blurry limb reported after a minute of handheld lunar video.

Final-image integration now accepts an OPIPP extension:

-derotate=on                 correct field rotation (default off)
-derotate_search=<deg>       search range either side of frame 0 (default 5, 0.1..45)

Both require -stack=. With the switch off, or absent, output is byte-identical to before.

The stage estimates each frame's angle against frame 0 by normalised cross-correlation on luma —
both images rotated by ±θ/2 so resampling does not favour either side, the full surviving rectangle
scored, 256 px working side, sub-pixel translation, and a predicted search window that widens once
at the edge. It then rotates with a bicubic Keys kernel (a = -1.0), crops every frame to one
centred rectangle all rotations can fill, and finishes with a correlation offset (below 0.05 px is
treated as zero). Mean, sum and median all work because the frames stay rectangular.

Measured on real lunar texture, outer-annulus Laplacian variance:

Sequence Translation-only Derotated Gain
1.45° total rotation 411.7 994.4 2.42×
116° total rotation 40.3 866.0 21.5×
40 frames, 2.34° rotation plus 5 px handheld drift 34.2 (-ctr: 268.4) 813.3 mean, 828.0 median 23.8× plain, 3.0× centred
identical stills 1567.4 1567.4 unchanged (diff 0.0000)

Angle error averages 0.039°, max 0.13°. The mild 1.45° case is the weakest and misses an internal
2.5× target by 3%; realistic handheld rotation is larger, where the gain is an order of magnitude.

GUI: Processing → Final image integration… → Correct field rotation (derotate), persisted as
FINAL_IMAGE_DEROTATE and FINAL_IMAGE_DEROTATE_SEARCH.

Limits: in-plane rotation only; the rotation must be observable (a featureless or perfectly
symmetric disc estimates 0°); -derotate_search bounds the search; cropping shrinks the canvas
(512² → 499² at 1.45°, 640×480 → 575×431 at 5°); raw Bayer frames are refused with -db guidance;
derotated median re-rotates per band and costs more than mean.

Tests and docs

1,446 tests, 0 failing. New coverage: rotation estimation accuracy against analytic truth, crop
containment, bicubic-versus-bilinear margin, correlation offsets against a known shift, fast
rotation (4°/frame), still-sequence equivalence, CLI parsing and error taxonomy, GUI settings,
persistence and a form-to-engine run. docs/derotation.md records the verification, algorithm,
measurements and limits.

OPIPP 0.3.0-alpha (Open PIPP) - Windows x64

An independent, fully managed continuation of PIPP (Planetary Imaging
PreProcessor). ALPHA: a working preview, not an official PIPP release.

NOT AFFILIATED WITH PIPP. Not affiliated with, endorsed by or supported by Chris
Garry or the PIPP project. New C# code, no original binaries redistributed.
Published in the belief that this is fair use.

AI was used to build this and will keep being used. Behaviour claims are backed
by tests or parity cases; unverified items are listed as known gaps.

What is in this folder
Opipp.App.exe the GUI (managed; no native pipp_dll.dll needed)
Opipp.Cli.exe the command-line engine, drop-in for pipp_core.exe

Quick start
GUI: double-click Opipp.App.exe
CLI: Opipp.Cli.exe -help
Opipp.Cli.exe -tif -od=C:\out capture.ser

Status
Built automatically from tag v0.3.0-alpha by the release workflow after the
full test suite passed. This exact zip was extracted and smoke-tested
(a generated SER file converted to TIFF) before the release was published.
Parity against the original PIPP engine is not run in CI because it needs
the original binaries, which are not redistributable; see docs/parity.md
and docs/status.md at the tagged commit for the accounting and known gaps.
Workflow run: https://github.com/openpipp/opipp/actions/runs/40643034911

Licence
GPLv3 or later for this repository's code and artwork. Not a licence to PIPP.

Requires Windows 10/11 x64. Self-contained: no .NET installation needed.

Checksum

68f6392555b9221ebb012237b6db3be024cf8d8ce50ff2a1d40022dd9f8c0f10  OPIPP-0.3.0-alpha-win-x64.zip

v0.2.2-alpha

v0.2.2-alpha Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 24 Oct 03:55

OPIPP 0.2.2-alpha (Open PIPP) - Windows x64

Self-contained alpha build of the managed PIPP continuation. It was built and
tested, packaged, and smoke-tested from the extracted zip by the tag-triggered
release workflow before this release was created.

Artifact OPIPP-0.2.2-alpha-win-x64.zip
Size 53541398 bytes
SHA-256 f0e459f2371488eeb2d271c4c8b3da9d0e772361bf09f2d45989706dd57af5fe
Tag v0.2.2-alpha
Commit c06fe53
Workflow run https://github.com/openpipp/opipp/actions/runs/40060092637

Package contents

  • Opipp.App.exe - the GUI, fully managed, no pipp_dll.dll
  • Opipp.Cli.exe - the command-line engine, drop-in for pipp_core.exe
  • README-ALPHA.txt - quick start, status and licence notes

Status and licence

ALPHA: a working preview, not an official PIPP release, and not affiliated
with Chris Garry or the PIPP project. AI was used to build this. GPLv3 or
later for this repository's code and artwork; not a licence to PIPP. See
NOTICE in the repository.

What changed in 0.2.2

This release is about evidence: real captures, measured memory, and the working path for raw Bayer
data. No integration arithmetic changed.

Real-capture validation

Integration was run on captures that are not Saturn-2016 or synthetic:

Capture Object / date Result
Slooh AVI, 49 extracted frames Jupiter + Ganymede, 2011-09-08 joined mean → one 640×480 colour image; visually clean disc and moon
Strata SER, 200-frame subset of 8,984 Saturn, 2022-10-25 raw CFA + centring rejected as designed; -db + mean → one 619×598 colour image in ~3 s, clean rings and globe
Strata TIFF Jupiter, 2023-11-02 conversion correct (IR685 green cast expected)
Wikimedia stills Moon (2010) and Mars (2003) PNG→FITS→PNG and PNG→TIFF round-trips correct

Two real input gaps were found and are documented rather than hidden: the Slooh AVI is I420
(planar YUV), and an ffmpeg rawvideo bgr24 AVI reports its first frame as truncated. Both are
rejected with clear messages; extracting PNG frames is the current workaround. See
docs/validation.md for sources, licences and commands.

Debayer guidance

A raw mosaic can only move by whole pixels without changing its CFA phase, and centring commonly
produces odd shifts. The help section and every Bayer-phase error now say so and name -db /
-db=<pattern> and the GUI's "Debayer Monochrome Frames" option, instead of only saying "debayer".
A fixture-gated regression runs the real Saturn capture both ways: rejection without -db, one
correct colour image with it, and a plain 30-frame conversion as control.

Measured memory

tools/Opipp.IntegrationProbe runs each configuration in its own process and samples peak working
set every 20 ms. Measured on this machine (i5-13600K, 128 GB, .NET 10.0.13):

Case Route Peak working set
300 × 512×256 mono8 mean, spilled streaming 46 MB
300 × 512×256 mono8 median, spilled streamed 89 MB
100 × 1920×1080 RGB16 median in memory 2,476 MB
200 × 1920×1080 RGB16 median, 4 GB scratch tiled 11,679 MB

Two honest findings: the in-memory median holds two copies of the selection (2.5 GB for 1.2 GB
of frames), and the tiled route's process peak is dominated by allocation churn (6,800 temporary
full-frame buffers), even though live data is ~2.5 GB. The default 512 MiB scratch budget refuses
the 200-frame case before writing anything. docs/memory.md records all numbers and commands.

Run-owned staging

Integration stages inside <output>/.opipp-staging/<run-guid>/ and deletes that directory on
success, failure or cancellation. A later run removes stale GUID directories older than an hour;
nothing outside .opipp-staging is enumerated, so an operator's files are never at risk. The GUI's
stale comments about a flat .integrating file were corrected; it still deletes only registered
paths.

Cancellation and restart

The GUI reused a single Process object for every run. After a cancel, that object's stdin pipe was
already disposed, so the next run could fail at launch with "The pipe is being closed" — a supported
workflow (cancel, then try again) broken by resource reuse. Each run now creates a fresh process,
restores the SynchronizingObject the designer had set (without it, engine callbacks arrive on pool
threads and the transcript verdict races the form), and a shutdown exception while a run is being
cancelled keeps the verdict CANCELLED instead of being re-labelled a start failure. The cancellation
test now uses a long-enough selection for Cancel to end the run, and its assertion reports the
engine's exit code, output and captured errors if it ever diverges.

Verification

  • 1,324 tests, 0 failures, nine projects.
  • Parity unchanged: 27 compared, 27 matched, 2 deliberate differences, 0 gaps.
  • Real-capture outcomes reproduced from the built CLI; images inspected, not just exit codes.

Known limits

  • No sigma-clipped or robust rejection yet; that is the 0.3.0 milestone.
  • In-memory median holds two copies of the selection; tiled median's process peak grows with
    allocation churn even though live memory stays bounded.
  • AVI input: I420/planar YUV and ffmpeg rawvideo layouts are not supported.
  • Integration output is still quantised to the input depth; no float FITS delivery.
  • No lunar or solar sequence validation yet; Moon/Mars coverage is stills only.

OPIPP 0.2.2-alpha (Open PIPP) - Windows x64

An independent, fully managed continuation of PIPP (Planetary Imaging
PreProcessor). ALPHA: a working preview, not an official PIPP release.

NOT AFFILIATED WITH PIPP. Not affiliated with, endorsed by or supported by Chris
Garry or the PIPP project. New C# code, no original binaries redistributed.
Published in the belief that this is fair use.

AI was used to build this and will keep being used. Behaviour claims are backed
by tests or parity cases; unverified items are listed as known gaps.

What is in this folder
Opipp.App.exe the GUI (managed; no native pipp_dll.dll needed)
Opipp.Cli.exe the command-line engine, drop-in for pipp_core.exe

Quick start
GUI: double-click Opipp.App.exe
CLI: Opipp.Cli.exe -help
Opipp.Cli.exe -tif -od=C:\out capture.ser

Status
Built automatically from tag v0.2.2-alpha by the release workflow after the
full test suite passed. This exact zip was extracted and smoke-tested
(a generated SER file converted to TIFF) before the release was published.
Parity against the original PIPP engine is not run in CI because it needs
the original binaries, which are not redistributable; see docs/parity.md
and docs/status.md at the tagged commit for the accounting and known gaps.
Workflow run: https://github.com/openpipp/opipp/actions/runs/40060092637

Licence
GPLv3 or later for this repository's code and artwork. Not a licence to PIPP.

Requires Windows 10/11 x64. Self-contained: no .NET installation needed.

Checksum

f0e459f2371488eeb2d271c4c8b3da9d0e772361bf09f2d45989706dd57af5fe  OPIPP-0.2.2-alpha-win-x64.zip

v0.2.1-alpha

v0.2.1-alpha Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Oct 06:05

OPIPP 0.2.1-alpha (Open PIPP) - Windows x64

Self-contained alpha build of the managed PIPP continuation. It was built and
tested, packaged, and smoke-tested from the extracted zip by the tag-triggered
release workflow before this release was created.

Artifact OPIPP-0.2.1-alpha-win-x64.zip
Size 53539535 bytes
SHA-256 d28d4be9f328d2d3ca469b2e485501e61905cb87b473199ecfec7aa76df621a9
Tag v0.2.1-alpha
Commit 15d713d
Workflow run https://github.com/openpipp/opipp/actions/runs/39378137361

Package contents

  • Opipp.App.exe - the GUI, fully managed, no pipp_dll.dll
  • Opipp.Cli.exe - the command-line engine, drop-in for pipp_core.exe
  • README-ALPHA.txt - quick start, status and licence notes

Status and licence

ALPHA: a working preview, not an official PIPP release, and not affiliated
with Chris Garry or the PIPP project. AI was used to build this. GPLv3 or
later for this repository's code and artwork; not a licence to PIPP. See
NOTICE in the repository.

What changed in 0.2.1

A correctness patch for final-image integration. Every fix closes a way to get a wrong image, destroy
someone else's file, or silently ignore a configured resource limit.

Raw CFA frames are no longer averaged across colour sites. Integration compared Bayer tags before
registration, but an odd-pixel shift moves the 2×2 mosaic to another phase, and bilinear sampling on a
raw mosaic blends four differently coloured sites. Each contributor's effective phase is now computed
after placement and after the output crop: the output is tagged at its actual origin, contributors that
disagree are rejected before any sample changes, and a fractional offset on a raw mosaic is refused
outright with a message pointing at debayering. (A single frame shifted by −1 is now correctly tagged
GRBG; two RGGB frames placed one pixel apart are rejected instead of averaged.)

Integration no longer reloads the retained capture. The pipeline used to materialise every selected
frame into a list before integrating, defeating the retention budget; median then spilled them again
while the full set stayed reachable. Frames are now read from the retention store one at a time (and
re-read per median band) with no frame held across calls. A 300-frame spilled selection peaks at about
2 MB of live objects instead of ~19 MB.

Staging files are owned, not guessed. The predictable <name>.integrating<ext> path could truncate
and then move away an unrelated existing file. Staging now uses a unique GUID name created with
CreateNew, and cleanup deletes only that exact path. A preseeded .integrating sentinel survives
success, failure and cancellation.

The area of interest is applied after registration. Cropping before registration threw away source
pixels needed inside the requested aligned crop (a 10×10 AOI came out 7×9 with 63 valid samples). The
AOI is now a request on the delivered canvas and is applied to the integrated result, giving the
requested 10×10 and 100 valid samples; a request that misses the overlap fails with both rectangles named.

Median honours its in-memory threshold. Every median selection was forced through the disk path,
ignoring MaxRetainedMedianFrames; with the default budget a 44-frame Full-HD RGB stack failed although
it is below the cap. Median now routes in memory when the count and a declared byte estimate fit, and to
the disk-backed path otherwise. Both routes produce identical pixels; the chosen route and estimate are
reported on the result.

GUI integration settings are part of the option lifecycle. Enabled, method, coverage and subpixel
are written to .pof files, restored on load (old files get explicit defaults), cleared by Reset
Options and restored by Undo Reset. Previously a reset run still emitted -stack=sum.

Corrections to earlier claims

  • "One file per run" was wrong: integration produces one file per batch input, or one per joined unit.
  • "Median stays in memory up to 64 frames" was not true in production before this patch; it now is,
    subject to the byte estimate, with the disk path above it.
  • A run where an input fails still publishes the accepted frames' integration as a labelled partial
    result with exit 1; final integration does not require every selected file to decode.
  • A hard kill during output staging can still leave one uniquely named .integrating orphan, because
    the engine cannot run cleanup when the GUI kills it. It is never mistaken for a finished image, and
    the GUI deletes only files it owns rather than sweeping the directory.

Verification

  • 1,319 tests, 0 failures, nine projects.
  • Parity unchanged: 27 compared, 27 matched, 2 deliberate differences, 0 gaps.
  • Reproduced against the built CLI: two RGGB frames whose centring places them one pixel apart now exit
    1 with the phase conflict named and write nothing; a static odd-shift case succeeds with the tag
    computed at the output origin; the 40×30 AOI case returns a 10×10, all-200 image; a preseeded
    a.integrating.ser survives an integrating run unchanged.

Known limits

  • No sigma-clipped or robust rejection; every contributing frame counts.
  • Integration output is quantised to the input depth (double intermediate, integer delivery); no float
    FITS output yet.
  • Raw mosaics reject fractional registration and phase-changing shifts; debayer to colour first.
  • Subpixel translation only: no rotation, drizzle or local warping.
  • Median above the in-memory caps is exact but slower, and scratch use still grows with contributor
    count at a fixed band height.

OPIPP 0.2.1-alpha (Open PIPP) - Windows x64

An independent, fully managed continuation of PIPP (Planetary Imaging
PreProcessor). ALPHA: a working preview, not an official PIPP release.

NOT AFFILIATED WITH PIPP. Not affiliated with, endorsed by or supported by Chris
Garry or the PIPP project. New C# code, no original binaries redistributed.
Published in the belief that this is fair use.

AI was used to build this and will keep being used. Behaviour claims are backed
by tests or parity cases; unverified items are listed as known gaps.

What is in this folder
Opipp.App.exe the GUI (managed; no native pipp_dll.dll needed)
Opipp.Cli.exe the command-line engine, drop-in for pipp_core.exe

Quick start
GUI: double-click Opipp.App.exe
CLI: Opipp.Cli.exe -help
Opipp.Cli.exe -tif -od=C:\out capture.ser

Status
Built automatically from tag v0.2.1-alpha by the release workflow after the
full test suite passed. This exact zip was extracted and smoke-tested
(a generated SER file converted to TIFF) before the release was published.
Parity against the original PIPP engine is not run in CI because it needs
the original binaries, which are not redistributable; see docs/parity.md
and docs/status.md at the tagged commit for the accounting and known gaps.
Workflow run: https://github.com/openpipp/opipp/actions/runs/39378137361

Licence
GPLv3 or later for this repository's code and artwork. Not a licence to PIPP.

Requires Windows 10/11 x64. Self-contained: no .NET installation needed.

Checksum

d28d4be9f328d2d3ca469b2e485501e61905cb87b473199ecfec7aa76df621a9  OPIPP-0.2.1-alpha-win-x64.zip

v0.2.0-alpha

v0.2.0-alpha Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Oct 04:16

OPIPP 0.2.0-alpha (Open PIPP) - Windows x64

Self-contained alpha build of the managed PIPP continuation. It was built and
tested, packaged, and smoke-tested from the extracted zip by the tag-triggered
release workflow before this release was created.

Artifact OPIPP-0.2.0-alpha-win-x64.zip
Size 53531333 bytes
SHA-256 dc215f47d1f0a175083e95a4928a902f3c98458034f0aaf7be76d892da3fa65b
Tag v0.2.0-alpha
Commit 21cb533
Workflow run https://github.com/openpipp/opipp/actions/runs/39368574850

Package contents

  • Opipp.App.exe - the GUI, fully managed, no pipp_dll.dll
  • Opipp.Cli.exe - the command-line engine, drop-in for pipp_core.exe
  • README-ALPHA.txt - quick start, status and licence notes

Status and licence

ALPHA: a working preview, not an official PIPP release, and not affiliated
with Chris Garry or the PIPP project. AI was used to build this. GPLv3 or
later for this repository's code and artwork; not a licence to PIPP. See
NOTICE in the repository.

What changed in 0.2.0

Final-image integration is now a first-class operation. Joining captures, building calibration
masters and integrating science frames are three separate things, and the third one is finally
reachable without writing code.

User-facing

  • CLI: -stack=mean|sum|median produces one final image. -stack_coverage=crop|canvas chooses
    whether the output is cropped to the region every frame can fill (default) or keeps the first
    frame's canvas. -stack_subpixel=on|off controls fractional registration (default on). These are
    OPIPP extensions; the original pipp_core.exe exits 127 on them.
  • GUI: Processing → Final image integration… offers the same three choices and shows the
    current setting in the transcript when a run starts. Ordinary runs emit exactly the same switches
    and transcripts as before.
  • Result: exactly one file per run, written under a staging name and moved into place only after
    success, so a cancelled or failed integration leaves nothing that looks finished.

Registration and borders

  • Each frame's alignment offset is applied by the integrator. The whole-pixel part is exact; the
    fractional part is bilinear, and mean, sum and median share one sampler so they register
    identically.
  • Coverage is counted per pixel. crop intersects the valid regions (a bilinear tap loses a border
    column on the side it samples from) and returns that rectangle; canvas keeps the first frame's
    canvas and reports zero-coverage pixels rather than filling them with invented data.

Precision

  • Accumulation is double. IntegrationResult.PrecisionSamples exposes it: a mean of 100 and 101 is
    exactly 100.5 there. The delivered image is quantised to the input depth with half-away-from-zero
    rounding and clamping; sum clamps at the depth maximum. Float FITS output is not implemented yet.

Median at scale

  • Median up to 64 frames stays in memory. Above that, every frame is spilled once and the image is
    produced in horizontal bands, sorting each pixel's contributors per band. Memory is bounded by the
    band, not the selection, and the result is exact: 65 and 1,000-frame cases match an independent
    per-pixel reference. The scratch budget is declared and exceeded budgets fail clearly.

Correctness around integration

  • Mixed Bayer phases, mixed geometry or depth, a colour frame with a CFA tag, and non-uniform weights
    under median are all rejected before any sample, count or provenance changes.
  • Contributors (source, weight, applied shift) and per-pixel coverage are reported with the result;
    the output frame keeps the contributing source's identity.
  • Cancellation is checked per band and per frame read; no partial output or spill file survives.

Verification

  • 1,164 tests, 0 failures across nine projects.
  • Native parity unchanged: 27 compared, 27 matched, 2 deliberate differences, 0 gaps.
  • Reproduced end-to-end from the built CLI: mean of a joined 5 and 6 writes 6; mean of 100 and 101
    writes 101; median of 10/20/30 writes 20; mixed-CFA join exits 1 with no file; unknown method exits 2.

Known limits

  • No sigma-clipped or robust rejection; every selected frame contributes.
  • Alignment is subpixel translation only; no rotation, drizzle or local warping.
  • Integration output is quantised to the input depth (double intermediate, integer delivery).
  • Median above the cap trades speed for bounded memory; it is exact, not approximate.
  • Surface-feature tracking remains 23/30 on one fixture; unequal-frame native master goldens are
    still missing.

OPIPP 0.2.0-alpha (Open PIPP) - Windows x64

An independent, fully managed continuation of PIPP (Planetary Imaging
PreProcessor). ALPHA: a working preview, not an official PIPP release.

NOT AFFILIATED WITH PIPP. Not affiliated with, endorsed by or supported by Chris
Garry or the PIPP project. New C# code, no original binaries redistributed.
Published in the belief that this is fair use.

AI was used to build this and will keep being used. Behaviour claims are backed
by tests or parity cases; unverified items are listed as known gaps.

What is in this folder
Opipp.App.exe the GUI (managed; no native pipp_dll.dll needed)
Opipp.Cli.exe the command-line engine, drop-in for pipp_core.exe

Quick start
GUI: double-click Opipp.App.exe
CLI: Opipp.Cli.exe -help
Opipp.Cli.exe -tif -od=C:\out capture.ser

Status
Built automatically from tag v0.2.0-alpha by the release workflow after the
full test suite passed. This exact zip was extracted and smoke-tested
(a generated SER file converted to TIFF) before the release was published.
Parity against the original PIPP engine is not run in CI because it needs
the original binaries, which are not redistributable; see docs/parity.md
and docs/status.md at the tagged commit for the accounting and known gaps.
Workflow run: https://github.com/openpipp/opipp/actions/runs/39368574850

Licence
GPLv3 or later for this repository's code and artwork. Not a licence to PIPP.

Requires Windows 10/11 x64. Self-contained: no .NET installation needed.

Checksum

dc215f47d1f0a175083e95a4928a902f3c98458034f0aaf7be76d892da3fa65b  OPIPP-0.2.0-alpha-win-x64.zip

v0.1.12-alpha

v0.1.12-alpha Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Oct 21:15

OPIPP 0.1.12-alpha (Open PIPP) - Windows x64

Self-contained alpha build of the managed PIPP continuation. It was built and
tested, packaged, and smoke-tested from the extracted zip by the tag-triggered
release workflow before this release was created.

Artifact OPIPP-0.1.12-alpha-win-x64.zip
Size 53510614 bytes
SHA-256 7a51abafdc06371b8a6aeabcb964a244113b43ec74d9ab6cd821b7d6e3fc5a24
Tag v0.1.12-alpha
Commit c306b88
Workflow run https://github.com/openpipp/opipp/actions/runs/39325802959

Package contents

  • Opipp.App.exe - the GUI, fully managed, no pipp_dll.dll
  • Opipp.Cli.exe - the command-line engine, drop-in for pipp_core.exe
  • README-ALPHA.txt - quick start, status and licence notes

Status and licence

ALPHA: a working preview, not an official PIPP release, and not affiliated
with Chris Garry or the PIPP project. AI was used to build this. GPLv3 or
later for this repository's code and artwork; not a licence to PIPP. See
NOTICE in the repository.

What changed in 0.1.12

Two correctness fixes from an execution-based review of 0.1.11, plus the documentation accounting
that review asked for.

A rejected later FITS IMAGE header no longer truncates the file. FitsReader.Scan caught a
FitsFormatException while walking later HDUs and simply stopped: a three-image file whose second
IMAGE header had BSCALE=0, or a PCOUNT/GCOUNT inconsistent with its payload, wrote only the first
frame, discarded the valid third frame, and exited 0 with SUCCESS. The same faults in the first HDU
were rejected. Image-header constraints now live in one place (FitsImageConstraints) used by both
the reader and -check, and a rejected header fails the file with the HDU named. A truncated second
data block still produces a labelled partial result.

Verified against independently written FITS bytes:

Case -check Processing
BSCALE=0 in HDU 2 exit 2, "HDU 2: BSCALE cannot be zero" exit -1, FAILURE, 0 frames, input and HDU named
PCOUNT/GCOUNT mismatch exit 2, constraint named controlled failure, no SUCCESS
truncated data in HDU 2 exit 2, byte count given exit 1, PARTIAL FAILURE, 1 frame labelled incomplete
valid 3-HDU control exit 0, "3 image HDU(s)" exit 0, SUCCESS, 3 frames

Joined stacks keep the identity of the source that contributed. A joined run named its single
unit after the first file, so a stack that selected only frames from the second capture wrote the
first capture's observer/telescope/instrument. Each frame now carries the file it was actually read
from through joining, retention and spilling, and the stacker's first-accepted rule sees the real
origin. Verified through the CLI with a flat capture and a planet-like capture: both input orders
select the planet frame and the header says Observer-DISC.

Documentation now separates what the numbers mean. The site previously said everything was
"measured against the original binaries" and labelled 926 as "tests passing". It now carries an
evidence table — managed tests, golden files, independent decodes, 27/27 parity, CI — states that only
the parity cases involve the original engine, and labels the approximately 94% figure as a weighted
estimate. The roadmap no longer claims "everything else is at or near exactness" and notes that the
23/30 tracking result is one Saturn fixture, not a general accuracy figure.

Verification

  • 971 tests, 0 failures, nine projects (2 skip in CI without the evaluation capture, so CI counts
    969 passed + 2 skipped = 971).
  • Parity unchanged: 27 compared, 27 matched, 2 deliberate differences, 0 gaps.
  • Both fixes reproduced against the built Release CLI with fixtures written by the reviewer rather
    than by OPIPP's own writers.

Known limits

  • Median stacking retains at most 64 frames; disk-backed tiled median is not implemented.
  • Mean/sum/median final stacking remains a Core API capability, not a CLI or GUI control.
  • A Bayer-marked selection is stacked as ordinary samples (Bayer=None on the result).
  • A valid image extension whose geometry differs from the first is still skipped under the documented
    same-shape rule.
  • Floating-point FITS is converted to the integer model without scaling; 0.1-0.9 collapses to 0/1.

OPIPP 0.1.12-alpha (Open PIPP) - Windows x64

An independent, fully managed continuation of PIPP (Planetary Imaging
PreProcessor). ALPHA: a working preview, not an official PIPP release.

NOT AFFILIATED WITH PIPP. Not affiliated with, endorsed by or supported by Chris
Garry or the PIPP project. New C# code, no original binaries redistributed.
Published in the belief that this is fair use.

AI was used to build this and will keep being used. Behaviour claims are backed
by tests or parity cases; unverified items are listed as known gaps.

What is in this folder
Opipp.App.exe the GUI (managed; no native pipp_dll.dll needed)
Opipp.Cli.exe the command-line engine, drop-in for pipp_core.exe

Quick start
GUI: double-click Opipp.App.exe
CLI: Opipp.Cli.exe -help
Opipp.Cli.exe -tif -od=C:\out capture.ser

Status
Built automatically from tag v0.1.12-alpha by the release workflow after the
full test suite passed. This exact zip was extracted and smoke-tested
(a generated SER file converted to TIFF) before the release was published.
Parity against the original PIPP engine is not run in CI because it needs
the original binaries, which are not redistributable; see docs/parity.md
and docs/status.md at the tagged commit for the accounting and known gaps.
Workflow run: https://github.com/openpipp/opipp/actions/runs/39325802959

Licence
GPLv3 or later for this repository's code and artwork. Not a licence to PIPP.

Requires Windows 10/11 x64. Self-contained: no .NET installation needed.

Checksum

7a51abafdc06371b8a6aeabcb964a244113b43ec74d9ab6cd821b7d6e3fc5a24  OPIPP-0.1.12-alpha-win-x64.zip

v0.1.11-alpha

v0.1.11-alpha Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Oct 20:33

OPIPP 0.1.11-alpha (Open PIPP) - Windows x64

Self-contained alpha build of the managed PIPP continuation. It was built and
tested, packaged, and smoke-tested from the extracted zip by the tag-triggered
release workflow before this release was created.

Artifact OPIPP-0.1.11-alpha-win-x64.zip
Size 53509541 bytes
SHA-256 bcc066e3556a1b5511998116cc189a81c53de1c416522389f4408147a2188313
Tag v0.1.11-alpha
Commit 504de3a
Workflow run https://github.com/openpipp/opipp/actions/runs/39319902761

Package contents

  • Opipp.App.exe - the GUI, fully managed, no pipp_dll.dll
  • Opipp.Cli.exe - the command-line engine, drop-in for pipp_core.exe
  • README-ALPHA.txt - quick start, status and licence notes

Status and licence

ALPHA: a working preview, not an official PIPP release, and not affiliated
with Chris Garry or the PIPP project. AI was used to build this. GPLv3 or
later for this repository's code and artwork; not a licence to PIPP. See
NOTICE in the repository.

What changed in 0.1.11

A correctness patch driven by an execution-based review of 0.1.10. Two of the fixes close paths that
could produce a silently wrong result; the rest make failures controllable and claims honest.

Raw SER output now describes the frame it contains. 0.1.10 corrected the CFA phase inside the
pipeline, but the SER header writer still copied the source file's ColorID. A horizontally flipped
8x6 RGGB capture therefore wrote correct pixels under a header that still said RGGB, where GRBG is
correct; flips, rotations, odd-origin crops and odd translations were all affected, and a binned image
kept a mosaic header after the lattice had been destroyed. The ColorID is now derived from the
delivered frame's pattern: RGGB 8, GRBG 9, GBRG 10, BGGR 11, None 0, colour 101. A sequence whose
frames disagree on phase is refused with a controlled error rather than written under one header.
Verified through the built CLI, not only tests: the flip case writes ColorID 9 with the expected
tile.

Format failures can no longer escape as raw exceptions. FitsFormatException,
FitsTruncationException and BayerPhaseException derive from Exception and were absent from the
decode-failure and CLI catch lists, so a corrupt FITS ended the process with 0xE0434352 instead of a
reported failure, and a mixed-CFA join crashed after correctly refusing the input. They now count as
per-input failures with a name and reason, the CLI maps every escaped format/calibration fault to a
documented exit code (2 configuration, 1 partial/runtime), and the last-resort handler deliberately
does not swallow cancellation.

-check audits every image HDU. It previously decoded only the first frame, so a file whose first
HDU was valid and whose second was truncated reported OK. It now walks the header chain, recomputes
each data offset and payload length from NAXISn/PCOUNT/GCOUNT/BITPIX, verifies the bytes are present,
and reports the image-HDU count without decoding pixels. Help documents this as structural validation
versus a full processing run.

Quality weights no longer depend on storage order. Frames were sorted into source order before
positional quality weights were assigned, so -nr or -no_ram_buff changed which ranks received
extra copies: the review's seven-frame case moved a mean from 95 to 44 from identical selected
inputs. Copy counts now attach to quality rank before any delivery reordering; default, -nr,
-no_ram_buff, both together, and spilled runs produce byte-identical masters (95 in that case).

Final stacks keep identity metadata. FrameStacker.Result dropped SourceName, so observer,
telescope and instrument fields were written empty. The first accepted frame's metadata is carried;
if sources disagree, the first frame's whole set wins (documented, no field mixing).

The picker offers only what the engine can open. JPEG, MOV/MP4/MKV and non-DNG camera RAW were
listed but could never be processed. The filter is now derived from the engine's own format set, a
stale raw_file_extensions setting can no longer re-admit unsupported types, DNG files are probed at
add time so compressed/tiled variants are rejected before a run, and rejections say why.

Help matches behaviour. -avi_codec documents DIB as the only implemented codec (1/2 are
rejected, with a compatibility note), and -avi_quality is 1..10 rather than 1..100. Documentation no
longer claims PGM or DNG as general read/write science formats: PGM is a calibration input, DNG is
read-only.

Test honesty. Four UnitTest1 placeholders that asserted nothing are gone. GUI transcript cases
that need samples/saturn30.ser no longer return early and report a pass; they skip explicitly with
the missing path when the fixture is absent.

Verification

  • 926 tests, 0 failures, nine projects (0 skipped locally; fixture-dependent cases skip loudly in CI).
  • Parity unchanged: 27 compared, 27 matched, 2 deliberate differences, 0 gaps.
  • Reproduced against the built CLI: flipped RGGB SER writes ColorID 9 with tile [107,53;191,107];
    corrupt FITS under -check exits 2 naming the truncated header; mixed-CFA join exits 1 with a
    controlled explanation.

Known limits

  • Median stacking retains at most 64 frames; disk-backed tiled median is not implemented.
  • Mean/sum/median final stacking remains a Core API capability, not a CLI or GUI control.
  • A Bayer-marked selection is stacked as ordinary samples (Bayer=None on the result).
  • Floating-point FITS is converted to the integer model without scaling; 0.1-0.9 collapses to 0/1.
  • Native master goldens come from identical inputs; unequal-frame fixtures are still missing.

OPIPP 0.1.11-alpha (Open PIPP) - Windows x64

An independent, fully managed continuation of PIPP (Planetary Imaging
PreProcessor). ALPHA: a working preview, not an official PIPP release.

NOT AFFILIATED WITH PIPP. Not affiliated with, endorsed by or supported by Chris
Garry or the PIPP project. New C# code, no original binaries redistributed.
Published in the belief that this is fair use.

AI was used to build this and will keep being used. Behaviour claims are backed
by tests or parity cases; unverified items are listed as known gaps.

What is in this folder
Opipp.App.exe the GUI (managed; no native pipp_dll.dll needed)
Opipp.Cli.exe the command-line engine, drop-in for pipp_core.exe

Quick start
GUI: double-click Opipp.App.exe
CLI: Opipp.Cli.exe -help
Opipp.Cli.exe -tif -od=C:\out capture.ser

Status
Built automatically from tag v0.1.11-alpha by the release workflow after the
full test suite passed. This exact zip was extracted and smoke-tested
(a generated SER file converted to TIFF) before the release was published.
Parity against the original PIPP engine is not run in CI because it needs
the original binaries, which are not redistributable; see docs/parity.md
and docs/status.md at the tagged commit for the accounting and known gaps.
Workflow run: https://github.com/openpipp/opipp/actions/runs/39319902761

Licence
GPLv3 or later for this repository's code and artwork. Not a licence to PIPP.

Requires Windows 10/11 x64. Self-contained: no .NET installation needed.

Checksum

bcc066e3556a1b5511998116cc189a81c53de1c416522389f4408147a2188313  OPIPP-0.1.11-alpha-win-x64.zip

v0.1.10-alpha

v0.1.10-alpha Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Oct 19:39

OPIPP 0.1.10-alpha (Open PIPP) - Windows x64

Self-contained alpha build of the managed PIPP continuation. It was built and
tested, packaged, and smoke-tested from the extracted zip by the tag-triggered
release workflow before this release was created.

Artifact OPIPP-0.1.10-alpha-win-x64.zip
Size 53502251 bytes
SHA-256 6dbf5b0106ea7919783088569819eccf32da2330afbbdf6905705322703d2e96
Tag v0.1.10-alpha
Commit 653b24e
Workflow run https://github.com/openpipp/opipp/actions/runs/39312458061

Package contents

  • Opipp.App.exe - the GUI, fully managed, no pipp_dll.dll
  • Opipp.Cli.exe - the command-line engine, drop-in for pipp_core.exe
  • README-ALPHA.txt - quick start, status and licence notes

Status and licence

ALPHA: a working preview, not an official PIPP release, and not affiliated
with Chris Garry or the PIPP project. AI was used to build this. GPLv3 or
later for this repository's code and artwork; not a licence to PIPP. See
NOTICE in the repository.

What changed in 0.1.10

A correctness patch: every fix below removes a way to get a plausible-looking but wrong or incomplete
result.

8-bit FITS files are now padded correctly. The writer emitted one byte per sample for 8-bit data but
padded as if it had written two, so the 2x2 mono8 case produced 5,756 bytes instead of 5,760. A
tolerant reader still opened the single image, but multi-image 8-bit files placed later headers at the
wrong offset (two written images read back as one). Padding is now derived from the bytes actually
written, and tests walk each header at its computed offset without relying on the reader.

Bayer handling is one rule instead of three behaviours. Debayered colour frames used to inherit the
raw mosaic marker, which made colour FITS output fail. They now carry no CFA pattern. An explicit
-db=<pattern> is applied before calibration and overrides container metadata, so an untagged mono
mosaic can be debayered and a wrong header can be corrected. Raw flips, rotations and odd-origin crops
recompute the phase from the mapping; binning and bilinear resize end the mosaic and clear it. A
sequence whose frames end up with different phases is refused with BayerPhaseException rather than
writing a header that lies.

Partial runs no longer look complete. A run that wrote frames and then failed on a later input
reports PARTIAL FAILURE, names the failing file, labels the output incomplete, and exits 1. The GUI
shows PROCESSING INCOMPLETE instead of claiming completion.

-check does what it advertises. It validates the command line, inputs, calibration masters,
geometry and output settings, prints the result, and exits 0 or 2 without creating an output directory
or any file. The help text records that the original engine treated -check as an alias of -chk.

Cancellation deletes only its own files. The cleanup used to delete every *.tmp in the chosen
output folder; with an existing folder that destroyed unrelated files. Cleanup now removes only paths
the run registered.

Every AVI preset produces a file. Two presets selected codecs the engine does not implement
(FMP4/MPEG-4 and ULRG/Ut Video) and failed at run time. Both now select uncompressed DIB, the codec
the engine writes, with the size implication visible.

GUI calibration counts every image in a FITS file. The file list counted each FITS path as one
frame and passed that as a build limit, so a two-image dark contributed one image and the master mean
was wrong. The list now probes the real frame count, and a full master build is not capped by a
display estimate.

Saved flat and flat-dark no longer collide. A mono flat was saved under the flat-dark name, so
requesting both left only one file (and the wrong one). Each master now has its own name.

Verification

  • 824 tests, 0 failures, nine projects.
  • Parity unchanged: 27 compared, 27 matched, 2 deliberate differences, 0 gaps.
  • Checked from the packaged CLI, not only in tests: an 8-bit FITS output is 5,760 bytes (2880-aligned);
    -check on valid input exits 0 with no output directory; a valid PNG followed by a corrupt PNG exits
    1 with PARTIAL FAILURE and one clearly labelled incomplete frame.

Known limits

  • Median stacking retains at most 64 frames; disk-backed tiled median is not implemented.
  • Mean/sum/median final stacking remains a Core API capability, not a CLI or GUI control.
  • A Bayer-marked selection is stacked as ordinary samples (Bayer=None on the result).
  • Native master goldens come from identical inputs; unequal-frame fixtures are still missing.
  • Floating-point FITS is converted to the integer model without scaling; 0.1-0.9 collapses to 0/1.

OPIPP 0.1.10-alpha (Open PIPP) - Windows x64

An independent, fully managed continuation of PIPP (Planetary Imaging
PreProcessor). ALPHA: a working preview, not an official PIPP release.

NOT AFFILIATED WITH PIPP. Not affiliated with, endorsed by or supported by Chris
Garry or the PIPP project. New C# code, no original binaries redistributed.
Published in the belief that this is fair use.

AI was used to build this and will keep being used. Behaviour claims are backed
by tests or parity cases; unverified items are listed as known gaps.

What is in this folder
Opipp.App.exe the GUI (managed; no native pipp_dll.dll needed)
Opipp.Cli.exe the command-line engine, drop-in for pipp_core.exe

Quick start
GUI: double-click Opipp.App.exe
CLI: Opipp.Cli.exe -help
Opipp.Cli.exe -tif -od=C:\out capture.ser

Status
Built automatically from tag v0.1.10-alpha by the release workflow after the
full test suite passed. This exact zip was extracted and smoke-tested
(a generated SER file converted to TIFF) before the release was published.
Parity against the original PIPP engine is not run in CI because it needs
the original binaries, which are not redistributable; see docs/parity.md
and docs/status.md at the tagged commit for the accounting and known gaps.
Workflow run: https://github.com/openpipp/opipp/actions/runs/39312458061

Licence
GPLv3 or later for this repository's code and artwork. Not a licence to PIPP.

Requires Windows 10/11 x64. Self-contained: no .NET installation needed.

Checksum

6dbf5b0106ea7919783088569819eccf32da2330afbbdf6905705322703d2e96  OPIPP-0.1.10-alpha-win-x64.zip

v0.1.9-alpha

v0.1.9-alpha Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Oct 18:51

OPIPP 0.1.9-alpha (Open PIPP) - Windows x64

Self-contained alpha build of the managed PIPP continuation. It was built and
tested, packaged, and smoke-tested from the extracted zip by the tag-triggered
release workflow before this release was created.

Artifact OPIPP-0.1.9-alpha-win-x64.zip
Size 53489927 bytes
SHA-256 4740db0cb4c418261050f109423df943f8a4c4ea00b067843b755ce0b0ec0558
Tag v0.1.9-alpha
Commit 27c354f
Workflow run https://github.com/openpipp/opipp/actions/runs/39305860069

Package contents

  • Opipp.App.exe - the GUI, fully managed, no pipp_dll.dll
  • Opipp.Cli.exe - the command-line engine, drop-in for pipp_core.exe
  • README-ALPHA.txt - quick start, status and licence notes

Status and licence

ALPHA: a working preview, not an official PIPP release, and not affiliated
with Chris Garry or the PIPP project. AI was used to build this. GPLv3 or
later for this repository's code and artwork; not a licence to PIPP. See
NOTICE in the repository.

What changed in 0.1.9

This is a corrective release for defects found in 0.1.8 and in paths it exposed.

Joining no longer loses images from multi-image FITS files. 0.1.8 treated FITS as a guaranteed
single-frame format when counting a joined sequence. One FITS file can hold several image HDUs, so a
join of two two-image files reported two frames instead of four and the processor stopped once its
window was reached. FITS is now opened and counted; the single-frame shortcut is limited to readers
that provably return one frame (BMP, TIFF, PNG). Tests cover two multi-HDU files, ordering, a FITS/SER
mixture, and one-reader-at-a-time.

A cached flat can no longer be corrected twice. The "already corrected" state was a bare boolean,
reset whenever the flat-correction branch was skipped while the cached master survived. Running with
calibration, turning flat correction off, then on again could subtract the flat-dark a second time.
The state now lives with the cached master's identity (paths, frame counts, input signature and
flat-dark correction signature), and reuse requires the file to still exist. The three-run sequence is
tested: 104/156, uncorrected, then 104/156 again with no rebuild and no -flat_dark_tmp.

Cancel during master building restores the form. The in-process cancellation path now uses the
same transition as the engine-exit path, so Start Processing and the tabs come back in a finally
even if temporary-file cleanup throws.

Declining Quit no longer deletes cached masters. The close handler returned into the deletion of
the session directory after cancelling the close; it now returns immediately, and cached artifacts are
checked for existence before reuse.

A non-zero engine exit is reported as failure. The GUI treated only negative exit codes as errors,
so the CLI's exit 1 (runtime/calibration) and 2 (configuration) were displayed as COMPLETE. Only exit
0 is success; cancellation keeps its own end state.

Saving the flat-dark master still works. Suppressing -flat_dark_tmp for a corrected flat had
also removed the master the save operation needed. The GUI now writes the requested master itself
(logs/pipp_master_flat_dark.tif) from the .tmp it built, without restoring double subtraction.

An explicitly named missing master stops the run. Previously the loader returned no master and
processing continued uncalibrated. A named file that does not exist now raises a diagnostic naming the
path and switch, exits 2, and writes no science output. A bare -dark/-flat/-flat_dark with no
filename, and the GUI's corrected-flat handoff, remain valid.

Master publication is transactional. Existing masters are renamed aside before the new pair is
published (PGM first, authoritative .tmp last). If either rename fails, the new files are removed
and the backups restored, so the destination is either the complete previous pair or the complete new
pair, never a mixture. If restoring itself fails, the error names the kept backups.

Verification

  • 744 tests, 0 failures, nine projects.
  • Parity unchanged: 27 compared, 27 matched, 2 deliberate differences, 0 gaps, 0 failed.
  • The packaged zip is extracted and smoke-converted by the release workflow before publication.

Known limits

  • Median stacking retains at most 64 frames (759 MiB at 1920x1080 RGB); disk-backed tiled median is
    not implemented.
  • Mean/sum/median final stacking remains a Core API capability, not a CLI or GUI control.
  • A Bayer-marked selection is stacked as ordinary samples (Bayer=None on the result).
  • Native master goldens come from identical inputs; unequal-frame fixtures are still missing.

OPIPP 0.1.9-alpha (Open PIPP) - Windows x64

An independent, fully managed continuation of PIPP (Planetary Imaging
PreProcessor). ALPHA: a working preview, not an official PIPP release.

NOT AFFILIATED WITH PIPP. Not affiliated with, endorsed by or supported by Chris
Garry or the PIPP project. New C# code, no original binaries redistributed.
Published in the belief that this is fair use.

AI was used to build this and will keep being used. Behaviour claims are backed
by tests or parity cases; unverified items are listed as known gaps.

What is in this folder
Opipp.App.exe the GUI (managed; no native pipp_dll.dll needed)
Opipp.Cli.exe the command-line engine, drop-in for pipp_core.exe

Quick start
GUI: double-click Opipp.App.exe
CLI: Opipp.Cli.exe -help
Opipp.Cli.exe -tif -od=C:\out capture.ser

Status
Built automatically from tag v0.1.9-alpha by the release workflow after the
full test suite passed. This exact zip was extracted and smoke-tested
(a generated SER file converted to TIFF) before the release was published.
Parity against the original PIPP engine is not run in CI because it needs
the original binaries, which are not redistributable; see docs/parity.md
and docs/status.md at the tagged commit for the accounting and known gaps.
Workflow run: https://github.com/openpipp/opipp/actions/runs/39305860069

Licence
GPLv3 or later for this repository's code and artwork. Not a licence to PIPP.

Requires Windows 10/11 x64. Self-contained: no .NET installation needed.

Checksum

4740db0cb4c418261050f109423df943f8a4c4ea00b067843b755ce0b0ec0558  OPIPP-0.1.9-alpha-win-x64.zip

v0.1.8-alpha

v0.1.8-alpha Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Oct 16:15

OPIPP 0.1.8-alpha (Open PIPP) - Windows x64

Self-contained alpha build of the managed PIPP continuation. It was built and
tested, packaged, and smoke-tested from the extracted zip by the tag-triggered
release workflow before this release was created.

Artifact OPIPP-0.1.8-alpha-win-x64.zip
Size 53483167 bytes
SHA-256 4768ca1a7e5f5a486ee9b19c7ca6def95e86d7125faa846d680f7f2dadcef2a5
Tag v0.1.8-alpha
Commit ed632d3
Workflow run https://github.com/openpipp/opipp/actions/runs/39283695875

Package contents

  • Opipp.App.exe - the GUI, fully managed, no pipp_dll.dll
  • Opipp.Cli.exe - the command-line engine, drop-in for pipp_core.exe
  • README-ALPHA.txt - quick start, status and licence notes

Status and licence

ALPHA: a working preview, not an official PIPP release, and not affiliated
with Chris Garry or the PIPP project. AI was used to build this. GPLv3 or
later for this repository's code and artwork; not a licence to PIPP. See
NOTICE in the repository.

What changed in 0.1.8

Calibration masters now work end to end. Five defects in the master workflow were fixed:

  • A flat-dark master is built from the engine's own .tmp container instead of failing with
    NotSupportedException; the builder reads .tmp through the same reader that wrote it.
  • A failed build is a result, not a -1 sentinel. The GUI shows the reason, marks the run failed and
    does not launch the engine or pass a master that was never written.
  • A flat-dark is subtracted exactly once. When the GUI builds the corrected flat it no longer also
    hands the flat-dark to the engine; a user-supplied flat plus flat-dark still subtracts at processing
    time, and both paths are tested.
  • RGB master darks keep their three channels: the full-fidelity .tmp is authoritative and the luma
    PGM is a fallback only when no .tmp exists.
  • Cancel stops master building, not just the engine that had not started yet. A cancelled or failed
    build leaves no staging file and no publishable master.

The regression fixture runs flat [200,100], flat-dark [50,0], science [125,125] through master
creation, the files on disk and the exact switches the GUI passes, and asserts [104,156]. Double
subtraction produces a different result, so the test proves the handoff.

Stacking arithmetic is now pinned. Mean, sum and median are covered for mono/RGB at 8 and 16 bits:
exact values, saturation at 255/65535, fractional truncation, even-median half-up (documented as
distinct from mean truncation), independent RGB channels, reference subtraction before averaging, and a
32-bit overflow guard at 65,538 frames. Median no longer retains the caller's sample arrays by
reference, so a reused buffer can no longer rewrite frames already submitted. An unknown stack method
is rejected instead of producing a zero image.

Joined inputs are bounded. -join opens one reader at a time and disposes each input as it is
exhausted; a long joined PNG sequence no longer holds every compressed payload at once.

GIF test correction. The late-colour reservoir fixture started blue at sample 245,760, before the
262,144 cap, so it did not actually prove replacement sampling. It now starts after 270,336 samples.

Verification

  • 713 tests, 0 failures, nine projects.
  • Parity unchanged: 27 compared, 27 matched, 2 deliberate differences, 0 gaps, 0 failed.
  • Packaged and smoke-converted by the release workflow before publication.

Known limits

  • Median stacking retains at most 64 frames (759 MiB for 64 RGB frames at 1920x1080). Disk-backed
    tiled median is not implemented.
  • Mean/sum/median final stacking is a Core API capability; the CLI and GUI do not expose a method
    selector yet.
  • A Bayer-marked selection is stacked as ordinary samples and the result carries Bayer=None;
    debayer first if the mosaic must be preserved.
  • Master-file compatibility is pinned by native goldens built from identical inputs; unequal-frame
    native goldens that would distinguish averaging and subtraction rules are still missing.

OPIPP 0.1.8-alpha (Open PIPP) - Windows x64

An independent, fully managed continuation of PIPP (Planetary Imaging
PreProcessor). ALPHA: a working preview, not an official PIPP release.

NOT AFFILIATED WITH PIPP. Not affiliated with, endorsed by or supported by Chris
Garry or the PIPP project. New C# code, no original binaries redistributed.
Published in the belief that this is fair use.

AI was used to build this and will keep being used. Behaviour claims are backed
by tests or parity cases; unverified items are listed as known gaps.

What is in this folder
Opipp.App.exe the GUI (managed; no native pipp_dll.dll needed)
Opipp.Cli.exe the command-line engine, drop-in for pipp_core.exe

Quick start
GUI: double-click Opipp.App.exe
CLI: Opipp.Cli.exe -help
Opipp.Cli.exe -tif -od=C:\out capture.ser

Status
Built automatically from tag v0.1.8-alpha by the release workflow after the
full test suite passed. This exact zip was extracted and smoke-tested
(a generated SER file converted to TIFF) before the release was published.
Parity against the original PIPP engine is not run in CI because it needs
the original binaries, which are not redistributable; see docs/parity.md
and docs/status.md at the tagged commit for the accounting and known gaps.
Workflow run: https://github.com/openpipp/opipp/actions/runs/39283695875

Licence
GPLv3 or later for this repository's code and artwork. Not a licence to PIPP.

Requires Windows 10/11 x64. Self-contained: no .NET installation needed.

Checksum

4768ca1a7e5f5a486ee9b19c7ca6def95e86d7125faa846d680f7f2dadcef2a5  OPIPP-0.1.8-alpha-win-x64.zip

v0.1.7-alpha

v0.1.7-alpha Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Oct 08:05

OPIPP 0.1.7-alpha (Open PIPP) - Windows x64

Self-contained alpha build of the managed PIPP continuation. It was built and
tested, packaged, and smoke-tested from the extracted zip by the tag-triggered
release workflow before this release was created.

Artifact OPIPP-0.1.7-alpha-win-x64.zip
Size 53479555 bytes
SHA-256 2208c282fabc6079a5939c779a62e59fbf8a32617b13c52e593b6b436a4b0205
Tag v0.1.7-alpha
Commit 20f27b8
Workflow run https://github.com/openpipp/opipp/actions/runs/39220114781

Package contents

  • Opipp.App.exe - the GUI, fully managed, no pipp_dll.dll
  • Opipp.Cli.exe - the command-line engine, drop-in for pipp_core.exe
  • README-ALPHA.txt - quick start, status and licence notes

Status and licence

ALPHA: a working preview, not an official PIPP release, and not affiliated
with Chris Garry or the PIPP project. AI was used to build this. GPLv3 or
later for this repository's code and artwork; not a licence to PIPP. See
NOTICE in the repository.

What changed in 0.1.7

0.1.6 did not start. This release fixes that. The About box rewrite left a corrupted
$this.Icon entry in the main form's resources: the .resx still declared a BinaryFormatter
serialized Icon, but its payload had been replaced with raw .ico bytes. The project compiled and
all tests passed, then InitializeComponent threw SerializationException: Invalid value: 536870912 before the window appeared. The icon now comes from the executable's own embedded icon
(the project's ApplicationIcon), and the resource entry is gone.

A new test constructs the real Form1 and the real About dialog on an STA thread, so a window that
cannot be built fails the build instead of the download.

Version numbers now have one source. The window title and About box read the assembly's
informational version, which comes from Directory.Build.props. Three fields (Version,
AssemblyVersion, FileVersion) and every document are checked against each other in CI; a partial
bump - which shipped a 0.1.6 build whose FileVersion still said 0.1.5.0 - now fails.

Carried over from 0.1.6: the original project's About box, application icon, assembly metadata
and update check are gone, replaced with OPIPP's own; the GIF colour cache is bounded; cancellation
stops SER/AVI preparation promptly; spill storage is always closed; empty containers can no longer
count as parity matches.

Verification

  • 634 tests, 0 failures, including two that construct the application windows.
  • Parity: 27 compared, 27 matched, 2 deliberate differences, 0 gaps, 0 failed.
  • The packaged zip is extracted and smoke-converted by the release workflow before publication, and
    the GUI was launched from the packaged build as part of this release.

Note on earlier releases

0.1.6 was withdrawn because it could not start. 0.1.2 to 0.1.5 were withdrawn because their
About box and icon were the original project's. This release supersedes all of them.

OPIPP 0.1.7-alpha (Open PIPP) - Windows x64

An independent, fully managed continuation of PIPP (Planetary Imaging
PreProcessor). ALPHA: a working preview, not an official PIPP release.

NOT AFFILIATED WITH PIPP. Not affiliated with, endorsed by or supported by Chris
Garry or the PIPP project. New C# code, no original binaries redistributed.
Published in the belief that this is fair use.

AI was used to build this and will keep being used. Behaviour claims are backed
by tests or parity cases; unverified items are listed as known gaps.

What is in this folder
Opipp.App.exe the GUI (managed; no native pipp_dll.dll needed)
Opipp.Cli.exe the command-line engine, drop-in for pipp_core.exe

Quick start
GUI: double-click Opipp.App.exe
CLI: Opipp.Cli.exe -help
Opipp.Cli.exe -tif -od=C:\out capture.ser

Status
Built automatically from tag v0.1.7-alpha by the release workflow after the
full test suite passed. This exact zip was extracted and smoke-tested
(a generated SER file converted to TIFF) before the release was published.
Parity against the original PIPP engine is not run in CI because it needs
the original binaries, which are not redistributable; see docs/parity.md
and docs/status.md at the tagged commit for the accounting and known gaps.
Workflow run: https://github.com/openpipp/opipp/actions/runs/39220114781

Licence
GPLv3 or later for this repository's code and artwork. Not a licence to PIPP.

Requires Windows 10/11 x64. Self-contained: no .NET installation needed.

Checksum

2208c282fabc6079a5939c779a62e59fbf8a32617b13c52e593b6b436a4b0205  OPIPP-0.1.7-alpha-win-x64.zip