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
ANCOM unit test failures with scipy 0.17.0 #1259
Comments
Thanks for investigating this. What do you recommend to fix this? Can we just update the tests and require the development version of scikit-bio to depend on scipy 0.17.0? |
I'm not sure what the fix is -- we'd want to know why the expected values are different between scipy versions before updating the unit tests to use new expected values (the observed vs. expected values are very different). |
Of course, let me add some more context Looking at the If you look at the original p-value matrix generated by the mann-whitney U-test with scipy==0.16, you get the following.
Now, if you look at the same p-value matrix with scipy==0.17, you'll get different results
And this is still different when alternative='less'
So, looks like the mann-whitney U-test has completely changed since they incorporated the alternative keyword. Not sure what the best way to proceed with this. |
Thanks for the details! Can these two tests be updated to use a different scipy stat function that is better behaved across scipy versions? |
Fixed in #1260. |
Hi, The following two explain what happened with scipy 1.7.0 |
Thanks @josef-pkt! |
The following ANCOM unit tests fail with scipy 0.17.0 on Python 2 and 3:
The tests pass using the previous scipy release (0.16.1, available via
conda
andpip
). Note that scipy 0.17.0 is currently only available viapip
.The tests are failing because something in
scipy.stats.mannwhitneyu
changed between scipy 0.16.1 and 0.17.0. Changingtest_ancom_alternative_test
to passalternative='less'
fixes the test. However, making the same change totest_ancom_normal_data
doesn't fix the failure.See #1258 for original discussion.
The text was updated successfully, but these errors were encountered: