Fix generalized procrustes algorithm#217
Merged
FanwangM merged 1 commit intotheochem:mainfrom Feb 24, 2025
Merged
Conversation
The generalized procrustes implementation was never updating the reference shape -- in effect, this means it would always run just one iteration of the algorithm and then return because the change in ref would be zero. This PR adds the missing line to update the reference shape. (Might also be a good idea to add a test which catches this in the future since the existing ones didn't -- though that could always be added later.)
Contributor
Author
|
Actually, I think there are a few other bugs I didn't address here:
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #217 +/- ##
=======================================
Coverage ? 94.13%
=======================================
Files ? 11
Lines ? 802
Branches ? 0
=======================================
Hits ? 755
Misses ? 47
Partials ? 0
|
Collaborator
|
Hi @msegado . Thank you for noticing the issue. I will take a closer look at the PR during the weekend. |
Collaborator
|
Thanks for noticing the issue in the codes. I am going to merge this PR and add tests later. As for two questions you mentioned, I will open issues and address them. @msegado |
Contributor
Author
|
No problem -- thanks for your work in maintaining this project!
…On Mon, Feb 24, 2025, 6:17 PM Fanwang Meng ***@***.***> wrote:
Thanks for noticing the issue in the codes. I am going to merge this PR
and add tests later. As for two questions you mentioned, I will open issues
and address them. @msegado <https://github.com/msegado>
—
Reply to this email directly, view it on GitHub
<#217 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOM43SSKIOX3ILPWQPWWTT2ROR6NAVCNFSM6AAAAABXUCQWTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZZHEYDGOJZGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: FanwangM]*FanwangM* left a comment (theochem/procrustes#217)
<#217 (comment)>
Thanks for noticing the issue in the codes. I am going to merge this PR
and add tests later. As for two questions you mentioned, I will open issues
and address them. @msegado <https://github.com/msegado>
—
Reply to this email directly, view it on GitHub
<#217 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOM43SSKIOX3ILPWQPWWTT2ROR6NAVCNFSM6AAAAABXUCQWTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZZHEYDGOJZGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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.
The generalized procrustes implementation was never updating the reference shape -- in effect, this means it would always run just one iteration of the algorithm and then return because the change in ref would be zero. This PR adds the missing line to update the reference shape.
(Might also be a good idea to add a test which catches this in the future since the existing ones didn't -- though that could always be added later.)