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
Just reporting that on Apple Silicon macs, I need to set os.environ["PARLAY_NUM_THREADS"] = "1" to avoid a kernel crash. Any higher values cause instability when using dbscan in quick succession. This is not necessary on x86 linux.
P.S. This package is incredible, it speeds up Omnipose by nearly 2x. Will be sure to cite you.
I add this comment just to say that I encountered the same error. I run dbscan in a jupyter notebook, and executing the same cell in quick succession causes high cpu usage and long execution time.
When everything works, dbscan returns labels in few ms.
The cause of the problem may be the same. We are testing on platforms that are not x86.
The DBSCAN from sklearn does not have this issue.
Can simply reproduce the issue.
Activity
NorwegianGoat commentedon Feb 8, 2025
I add this comment just to say that I encountered the same error. I run dbscan in a jupyter notebook, and executing the same cell in quick succession causes high cpu usage and long execution time.
When everything works, dbscan returns labels in few ms.
wjxianjian commentedon Apr 24, 2025
I try to run the DBSCAN on ARM64 platform. After a few loop calls program will hung. (need to use kill -9 to force terminate the process)
The cause of the problem may be the same. We are testing on platforms that are not x86.
The DBSCAN from sklearn does not have this issue.
Can simply reproduce the issue.