-
Notifications
You must be signed in to change notification settings - Fork 4
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
BUG: Fix off-by-one bug in end frame for 3D registration #127
Merged
jcfr
merged 1 commit into
BrownBiomechanics:main
from
sbelsk:fix-off-by-one-registration-end-frame
Nov 21, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Considering
endFrame
is set to the value ofCTSelectorNode.GetNumberOfDataNodes()
, usingrange(startFrame, endFrame)
seems to be correct.Indeed, considering the items in a sequence are retrieved starting with 0, calling
self.autoscoperLogic.getItemInSequence(ctSequence, idx)
with idx set to the number of item would not be correct.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also extending the list
nodeList
while it is being iterated over does not seem to be correct.This pattern seems to be used in a few location
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To follow-up offline discussion with @sbelsk, since this code was known to work, this will likely be reviewed/addressed in follow-up pull requests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, thanks for pointing out the inconsistency. The UI frame selector slider was set to go from minimum=
0
to up to maximum=CTSelectorNode.GetNumberOfDataNodes()
which would add one more frame than there really is.I pushed a fix to make sure the maximum value the user is able to select is actually the last frame in the sequence. I believe all other places in the code use
CTSelectorNode.GetNumberOfDataNodes()
consistently such that the first frame is treated as index0
and the last is treated asGetNumberOfDataNodes()-1
. (E.g., error checks inTreeNode.py
of the formif idx >= self.transformSequence.GetNumberOfDataNodes():
and the loop that goesfor idx in range(self.transformSequence.GetNumberOfDataNodes()):
).