Skip to content

Commit 1f6458b

Browse files
michaelayeclaude
andcommitted
Release 0.7.1 — doc-only patch for --clip-to-footprint framing
Documentation-only patch release. No code behavior changes — all csm2map pipeline outputs are bit-identical to 0.7.0. The preceding commit (918ca79) rewrote --clip-to-footprint documentation across CLI help, module docstrings, and both doc chapters to drop the now-disproved "matches ISIS cam2map" framing. This commit bumps the version and logs the change in the CHANGELOG. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent 918ca79 commit 1f6458b

2 files changed

Lines changed: 41 additions & 2 deletions

File tree

CHANGELOG.md

Lines changed: 40 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,44 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
77

88
## [Unreleased]
99

10+
## [0.7.1] - 2026-04-12
11+
12+
Documentation-only patch release. No code behavior changes — all
13+
csm2map pipeline outputs are bit-identical to 0.7.0.
14+
15+
### Documentation
16+
17+
- **Corrected `--clip-to-footprint` documentation.** The flag was
18+
originally documented as an "ISIS cam2map compatibility mode" that
19+
matched `cam2map` by clipping csm2map output to the `footprintinit`
20+
polygon. That framing was based on a working hypothesis later
21+
disproved empirically: ISIS `cam2map` ignores the polygon entirely
22+
(stripping the polygon from the cube and re-running `cam2map`
23+
produces bit-identical output — see `docs/csm2map.qmd § "The
24+
footprintinit polygon precision story"` for the full narrative).
25+
All affected documentation has been rewritten to drop the
26+
cam2map-matching claim and reframe the flag as an escape hatch for
27+
downstream tooling that explicitly wants a polygon-shaped output
28+
mask. Affected surfaces:
29+
- `isistools csm2map --help` — Typer option help text and
30+
command docstring no longer claim ISIS-compatibility.
31+
- `docs/csm2map.qmd` — Purpose paragraph, Usage example comment,
32+
options table row, and the former "Pixel-perfect match"
33+
paragraph rewritten. Cross-references the empirical-disproof
34+
section.
35+
- `docs/csm2map-design.md` §6 Known limitations gains a new
36+
entry 7 documenting the flag as a historical
37+
hypothesis-test-reject artifact, flagged as paper-worthy.
38+
- `src/isistools/processing/project.py``clip_to_footprint`
39+
parameter docstring, the in-function console message, and
40+
the `_rasterize_footprint` helper docstring all corrected.
41+
42+
### Known limitations (unchanged from 0.7.0)
43+
44+
The `--clip-to-footprint` flag itself is retained in 0.7.1 for
45+
backward compatibility. Deprecation or removal is being considered
46+
for a future release.
47+
1048
## [0.7.0] - 2026-04-12
1149

1250
### Added
@@ -335,7 +373,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
335373
- Typer CLI with commands: `mosaic`, `tiepoints`, `footprints`,
336374
`cnet-info`.
337375

338-
[Unreleased]: https://github.com/michaelaye/isistools/compare/v0.7.0...HEAD
376+
[Unreleased]: https://github.com/michaelaye/isistools/compare/v0.7.1...HEAD
377+
[0.7.1]: https://github.com/michaelaye/isistools/compare/v0.7.0...v0.7.1
339378
[0.7.0]: https://github.com/michaelaye/isistools/compare/v0.6.0...v0.7.0
340379
[0.6.0]: https://github.com/michaelaye/isistools/compare/v0.5.3...v0.6.0
341380
[0.5.3]: https://github.com/michaelaye/isistools/compare/v0.5.2...v0.5.3

src/isistools/__init__.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
"""isistools — Python review tools for ISIS3 coregistration workflows."""
22

3-
__version__ = "0.7.0"
3+
__version__ = "0.7.1"

0 commit comments

Comments
 (0)