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
I have here a little demo that appears to show that pymde.preserve_neighbors uses cuda only if the user specifies device="cuda" and not if the user specifies device=torch.device("cuda"). While I see that the type hint is str for that input, I still think this behavior is unexpected. Example:
leads to ArpackError: ARPACK error -9: Starting vector is zero. (see #82 ... this error appears when arpack is used on cpu), so this seems not to be running on CUDA.
I think the potential fix would be to change this line
I have here a little demo that appears to show that
pymde.preserve_neighbors
uses cuda only if the user specifiesdevice="cuda"
and not if the user specifiesdevice=torch.device("cuda")
. While I see that the type hint isstr
for that input, I still think this behavior is unexpected. Example:This works fine and seems to run on CUDA.
But this
leads to
ArpackError: ARPACK error -9: Starting vector is zero.
(see #82 ... this error appears when arpack is used on cpu), so this seems not to be running on CUDA.I think the potential fix would be to change this line
pymde/pymde/recipes.py
Line 366 in 40472bc
to allow for
torch.device("cuda")
as well.If you think I'm on the right track, I'd be happy to write a PR.
The text was updated successfully, but these errors were encountered: