Open guensen0 opened 2 years ago
@guensen0 Did you ever solve this issue?
Just run into the same problem and found solution. I'll post it here in case anyone will need it.
Briefly: adata.uns['neighbors']['params']['metric'] = 'cosine'
will do the trick (or choose any other valid metric)
Not completely sure, but seems it happens when neighbour graph consists of more than one components. In this case umap
needs to estimate the distance between them. It takes metric name from adata.uns['neighbors']['params']['metric']
but angular
is not supported in umap
that cause the problem. The strange thing that the example given by @guensen0 uses defaults that at least now is euclidean
. Maybe it was different in the past. But at least in my case the above-mentioned trick solved the problem.
Other options are 1) make sure that neighbour graph if fully linked (increase number of neighbors) b) use metrics that are supported by both bbknn
and umap
(almost all except angular)
Hi, I got an error when running tl.umap after bbknn normalisation... new in version 1.7.2
Minimal code sample (that we can copy&paste without having any data)
Versions