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
Enhance SLR with applying series of transformations and fix optimize bug for parameter missing in old scipy versions #470
Closed
Closed
Changes from 8 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
8a0453c
ENH: allowing cascades of linear transforms e.g. first rigid then aff…
Garyfallidis 67ff60f
TEST: checking different testing ideas for the cascade
Garyfallidis f114b16
Removed some empty lines
Garyfallidis ccb86ea
TEST: Completed test for applying a series of transformations
Garyfallidis 0a05eab
BF: added default options for optimizer for older scipy versions
Garyfallidis d991c23
TEST: covering more versions of options
Garyfallidis a741106
Adding exception catch for 0.11 to 0.12 parameter missing in L-BFGS-B
Garyfallidis c8e36f1
Null commit to wake Travis
Garyfallidis 6486b77
Using maxfun when maxiter is not available
Garyfallidis 54a431b
BF: allowing for None check for iterations
Garyfallidis 4b9be1b
Changing verbosity to identify where Travis stops
Garyfallidis 507990b
Reduced to standard verbosity to identify where Travis stops
Garyfallidis fa68569
Test was too strict. Removing iterations asserts.
Garyfallidis File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
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
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
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
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
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.
typo: shifting
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.
This seems like a strange default. Isn't it better to have the default be
np.eye(4)
? That is, the default is not to pre-apply any transformation?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.
No eye(4) would be a very bad strategy. The default idea in registration is that you first find the center of mass of the two objects that you want to register and then you move them to the origin. In that way you make sure that your rotations during the registration will make sense. Is that clear?