Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

calibrate tether upside down #732

Merged
merged 1 commit into from
Jan 31, 2025
Merged

Conversation

rpauszek
Copy link
Contributor

Why this PR?
Sometimes you want to calibrate your tether with a known orientation but without flipping the kymo. Followup to #726

@rpauszek rpauszek requested review from a team as code owners January 30, 2025 09:24
@rpauszek rpauszek force-pushed the ray/calibrate-tether-upside-down branch 2 times, most recently from 32a1538 to 5385da7 Compare January 30, 2025 10:05
Copy link
Member

@JoepVanlier JoepVanlier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Small optional suggestion regarding naming.

Other than that, don't forget to squash the fixup.

@@ -1123,7 +1122,7 @@ def label(self):
@dataclass(frozen=True)
class PositionCalibration:
unit: PositionUnit = PositionUnit.pixel
value: float = 1.0
factor: float = 1.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a mild preference for scale given that one often talks about scale and offset in the context of transforms, but I don't feel very strongly about it.

@rpauszek rpauszek force-pushed the ray/calibrate-tether-upside-down branch from 5385da7 to 73effc8 Compare January 31, 2025 13:40
@rpauszek rpauszek merged commit 98f7e2c into main Jan 31, 2025
8 checks passed
@rpauszek rpauszek deleted the ray/calibrate-tether-upside-down branch January 31, 2025 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants