-
Notifications
You must be signed in to change notification settings - Fork 267
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
Kendall tau method added to mantel computation #1675
Conversation
In Khaligh-Razavi, S. M., & Kriegeskorte, N. (2014) it is suggested to prefer the Kendall's tau over Spearman's rho as correlation coefficient when comparing models in which the order of variables is important. This is for example the case in y work where I am comparing deep neural networks embeddings with brain neural patterns. Reference: |
Thanks for the contribution @AnnaTruzzi, looks like there are conflicts with your branch. Also, would you mind adding a new test to exercise this choice? |
Hi, I resolved the conflict, sorry about that. |
Thanks @AnnaTruzzi, really appreciate this. I was referring to adding a unit test in |
Hi, |
@AnnaTruzzi No need to worry about messing anything. Yes, you are correct we would need to add the method in that line as well as checking that the methods using that attribute also work. For example in line 99 and in line 183. If you would like some pointers, here's a document where we give some suggestions on how to test your code. |
I need to make sure that the the script test_mantel.py is up to date in order not to work on obsolete functions
Added and ran in the debugger: the 39 tests ran were ok.
|
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.
Thanks for adding tests, I've left a few comments in the PR.
@AnnaTruzzi, one more note: you'll need to resolve conflicts in the CHANGELOG.md file. Let me know if I can help. |
Edit as per PEP8 requirements Co-Authored-By: Yoshiki Vázquez Baeza <yoshiki89@gmail.com>
Edit to follow changelog format Co-Authored-By: Yoshiki Vázquez Baeza <yoshiki89@gmail.com>
Hi, thank you for correcting the mistakes! |
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.
@AnnaTruzzi thanks for updating the PR. I just noticed the entries in the CHANGELOG.md file are in a section for an older release. Also, going through the test_mantel.py
, I've noticed that there's a few other test cases that would be good to test. For example adding a check for 'kendalltau'
in the method in line 88 test_statistic_same_across_alternatives_and_permutations
, and the method in line 112 test_zero_permutations
.
Apologies for not catching this before, thanks so much for your contribution.
Co-Authored-By: Yoshiki Vázquez Baeza <yoshiki89@gmail.com>
Co-Authored-By: Yoshiki Vázquez Baeza <yoshiki89@gmail.com>
Co-Authored-By: Yoshiki Vázquez Baeza <yoshiki89@gmail.com>
Co-Authored-By: Yoshiki Vázquez Baeza <yoshiki89@gmail.com>
Co-Authored-By: Yoshiki Vázquez Baeza <yoshiki89@gmail.com>
Hi, sorry for the later reply, I've been caught in some deadlines. |
Hi @ElDeveloper, do I need to make other changes for this pull request? |
Hi @AnnaTruzzi, thanks for following up. The code changes look good, however I think the conflict resolution in the ChangeLog is still not correct. The diff still shows a few more bullet points that shouldn't be included in your PR. Can you fix that? The diff should only show |
Hi! yes at this point I could use some help, I guess I'm missing some fundamental step. What I do to to solve the conflict is to open the changelog with the conflicting lines, and remove the two versions leaving only the right line and then I commit it. What am I doing wrong? Thank you! |
Thank you! Lines deleted |
Thanks so much! |
Please complete the following checklist:
I have read the guidelines in CONTRIBUTING.md.
I have documented all public-facing changes in CHANGELOG.md.
This pull request includes code, documentation, or other content derived from external source(s). If this is the case, ensure the external source's license is compatible with scikit-bio's license. Include the license in the
licenses
directory and add a comment in the code giving proper attribution. Ensure any other requirements set forth by the license and/or author are satisfied. It is your responsibility to disclose code, documentation, or other content derived from external source(s). If you have questions about whether something can be included in the project or how to give proper attribution, include those questions in your pull request and a reviewer will assist you.This pull request does not include code, documentation, or other content derived from external source(s).
Note: REVIEWING.md may also be helpful to see some of the things code reviewers will be verifying when reviewing your pull request.