chore(release): v1.3.1#92
Merged
Merged
Conversation
Patch release with one bug fix (#69 -> #91): - ringwise_flatness is now cleared every ring (not only on rings with revert candidates), so stale flatnesses no longer leak into the next ring's TGR mean/stdev. Numerical impact on KITTI 00-10: +0.003 F1 (within run-to-run noise). Bumps: - python/pyproject.toml 1.3.0 -> 1.3.1 - cpp/CMakeLists.txt 1.3.0 -> 1.3.1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Patch release on top of v1.3.0. One bug fix only:
ringwise_flatnessis cleared every ring instead of only when revert candidates exist, so stale flatnesses no longer leak into the next ring'stemporal_ground_revertmean/stdev. Numerical impact on KITTI 00–10 is +0.003 F1 (within run-to-run noise); fix is correctness.Bumps:
python/pyproject.toml: 1.3.0 → 1.3.1cpp/CMakeLists.txt: 1.3.0 → 1.3.1CHANGELOG.md updated with the v1.3.1 entry.
After merge: cut a
v1.3.1GitHub Release to trigger the PyPI publish workflow.