You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you select the UMAP algoithm in the dropwdown, al the features in the features list and click on run, nothing happends, whereas tSNE and PCA work. When using the debugger to step through the code, I found that this line throws an error:
The error comes from numba: "SystemError: initialization of _internal failed without raising an exception". The error has been described here, with a possible fix being to downgrade numpy to 1.23.5.
Doing mamba install numpy==1.23.5 in my environment fixed the issue for me.
Possible fix
Pinning numpy to `numpy<1.24.0´ could do the trick, although I don't like pinning numpy. he problem has been observed in quite a few packages, though.
The text was updated successfully, but these errors were encountered:
lazigu
changed the title
Remove pinned numpy version (UMAP not working with Numpy>1.23.5)
Remove pinned numpy version when the problem is fixed (UMAP not working with Numpy>1.23.5)
Mar 21, 2023
hey @ziw-liu,
thanks for catching this, I'm pretty sure that it should not cause a problem but let me test it first! It will definitely be removed in the overhaul that we are working on atm but I thinks it's a good idea to update it in the current version as well.
Hi,
I was just testing some things and noticed that the UMAP was not functional in a fresh devbio-napari installation.
To reproduce
I create some sample data with this code:
When you select the UMAP algoithm in the dropwdown, al the features in the features list and click on
run
, nothing happends, whereas tSNE and PCA work. When using the debugger to step through the code, I found that this line throws an error:The error comes from numba:
"SystemError: initialization of _internal failed without raising an exception"
. The error has been described here, with a possible fix being to downgrade numpy to 1.23.5.Doing
mamba install numpy==1.23.5
in my environment fixed the issue for me.Possible fix
Pinning numpy to `numpy<1.24.0´ could do the trick, although I don't like pinning numpy. he problem has been observed in quite a few packages, though.
The text was updated successfully, but these errors were encountered: