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
As of version 1.2.7 the Leiden algorithm is also implemented directly in igraph, see igraph/rigraph#346. That implementation should be faster, and more straightforward to use and doesn't require reticulate or Python. The downside is that it doesn't offer the same degree of flexibility (e.g. no multilayer support, only supports CPM/Modularity), but if you don't depend on these additional options, it may be easier to switch to using cluster_leiden as implemented in igraph.
The text was updated successfully, but these errors were encountered:
…mentation from igraph rather than that of the Leiden package that requires reticulate and a python install. This reduces dependencies and avoid the recent errors and warnings elevated to errors from the Leiden package. Should also be faster as originally suggested in #378 by @vtraag .
Replace reshape with reshape2 for melt() import as the first raises warnings in newer R versions.
In igraph/python-igraph#458 we realised that
inferCNV
is using theleiden
R package that usesreticulate
to use myleidenalg
Python package.As of version 1.2.7 the Leiden algorithm is also implemented directly in
igraph
, see igraph/rigraph#346. That implementation should be faster, and more straightforward to use and doesn't requirereticulate
or Python. The downside is that it doesn't offer the same degree of flexibility (e.g. no multilayer support, only supports CPM/Modularity), but if you don't depend on these additional options, it may be easier to switch to usingcluster_leiden
as implemented inigraph
.The text was updated successfully, but these errors were encountered: