Coregistration GUI modernisation (phase 3) - #14218
Merged
Merged
Conversation
Member
|
Because we squash-merged #14203 the commits still show up here and in the diff. Can you rebase the one new commit |
payamsash
force-pushed
the
coreg_gui_dev_phase_1_3
branch
from
August 25, 2026 09:46
45f45b8 to
473e5f3
Compare
larsoner
approved these changes
Aug 25, 2026
larsoner
enabled auto-merge (squash)
August 25, 2026 14:07
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.
Reference issue (if any)
following #14203 and phase 3 of #14141
What does this implement/fix?
add test for coregistration fitting math now so later any algorithmic changes can be (hopefully) caught. I guess from next PRs we could start working on the UI/interactions/algorithms ...