-
Notifications
You must be signed in to change notification settings - Fork 23
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
Testing for PSDP #173
Testing for PSDP #173
Conversation
Is this PR complete? You can tag me wherever you think it's ready for code review. Thank you. @banrovegrie |
Yea, I will tag you as soon as this is complete. |
@FanwangM initially my tests were failing now I have fixed the basic tests. I will open a new PR for uploading the new algorithm's implementation |
This PR relates to the tests required for #98. |
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 PR is very nice. Thank you for the contribution. I have put some minor comments, which should be easy to fix. You can put comments if there is anything unclear.
One more tip. For merging the upstream repo code to your local branch, a better way is to use git checkout master
# suppose you have setup [email protected]:theochem/procrustes.git as your upper steam, named theochem
git pull theochem master
# if you want to update your master branch remotely
# git push origin master
git checkout test-psdp
git rebase master
git push test-psdp A good point of doing this is that we will avoid the commit history of merging upstream codes. If you want to practice, you can close this PR and create a new one following this trick. But it doesn't matter too much whichever way you go. @banrovegrie More details can be found at https://www.atlassian.com/git/tutorials/merging-vs-rebasing and https://git-scm.com/docs/git-rebase. |
Oh yeah, I should rebase instead of the way I merged. I will keep that in mind from now on. Thanks! |
@FanwangM after we merge this, I will open the PR for algorithm 2 (Peng et al). Some issues with the Peng Algorithm:
|
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 PR is complete now. I am going to merge it. This PR fixes #172.
Thank you for the nice improvement! @banrovegrie
I have moved your question to the Discussion board.
Thanks a lot! |
The first commit deals with #172. Scaling, translation etc. have been fixed for the input arrays. There are some changes to docstring too. Namely: