Skip to content

v0.1.12-alpha

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Oct 21:15
· 7 commits to main since this release

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