-
Notifications
You must be signed in to change notification settings - Fork 63
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
kBET metrics does not work with scipy==1.14.0 #412
Comments
Just encountered this issue in OpenProblems as well! Thanks for posting a workaround, @kollo97 ! |
rcannood
added a commit
to openproblems-bio/openproblems-v2
that referenced
this issue
Sep 4, 2024
rcannood
added a commit
to openproblems-bio/openproblems-v2
that referenced
this issue
Sep 4, 2024
* update images * fix numpy issues * fix scib kbet by pinning scipy to <= 1.13 (see theislab/scib#412) * remove unnecessary workaround * add workaround to other mse component * update viash test to only run on the main branch or in PRs
rcannood
added a commit
to openproblems-bio/openproblems
that referenced
this issue
Sep 4, 2024
* update images * fix numpy issues * fix scib kbet by pinning scipy to <= 1.13 (see theislab/scib#412) * remove unnecessary workaround * add workaround to other mse component * update viash test to only run on the main branch or in PRs Former-commit-id: 9493835
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
first of all I want to say that this is a great tool!
I ran into an error related to the recently released scipy version 1.14.0.
When trying to calculate the kBET score of an integration, I currently get the following error:
After a quick search, I found that this was most likely related to my currently installed scipy version 1.14.0. As described in the following issue and release notes of scipy v1.14.0, the
.A
attribute of a csr_matrix has been deprecated in this release.scipy/scipy#21049
https://github.com/scipy/scipy/releases/tag/v1.14.0
Downgrading the scipy version to v1.13.0 solved the issue for me.
Best regards!
The text was updated successfully, but these errors were encountered: