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 running UMAP with batched nn descent, fit is supported today but not transform, which falls back to using brute force knn (#6215). If I run fit with data_on_host set to True, this causes the transform call to throw an illegal memory access error.
Independent of having transform support batched nn descent (which I would imagine is a larger effort), we should handle this fallback appropriately in cases where data_on_host was True during the fit.
The text was updated successfully, but these errors were encountered:
When running UMAP with batched nn descent, fit is supported today but not transform, which falls back to using brute force knn (#6215). If I run fit with
data_on_host
set to True, this causes the transform call to throw an illegal memory access error.Independent of having transform support batched nn descent (which I would imagine is a larger effort), we should handle this fallback appropriately in cases where data_on_host was True during the fit.
The text was updated successfully, but these errors were encountered: