Open busFred opened 2 months ago
I actually did a little troubleshoot on my end and i think the problem is that cuml-cpu would not load certain modules correctly once it detects cuda packages are installed. so we have some remote computing resources with very old gpu, even below cuml minimum cuda computability. However, those gpu can still run pytorch in gpu mode if cuda drivers are installed. so what i was trying to do was install cuml-cpu version while having pytorch-gpu at the same time. I guess this is a corner case that cuml-cpu didn't take into consideration during development
Thanks for the report @busFred, that corner case indeed is something we did not think about. Have been working significantly on improvements to the are around cuml-cpu, and will be submitting significant improvements in the next few versions, will keep the issue open so we track this usecase as well.
Here is how I set up conda environment
After I import cuml, here is the list of all available module, which is a subset of its gpu counterpart.
From the documentation, it seems NearestNeighbor is officially supported on cpu.
Could someone help me look into this?