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
Currently {clustree} assumes the user knows the order of resolutions but this might not always be the case (if a clustering parameter doesn't have a natural order or has a non-linear effect) or it might just be interesting to see a "data-driven" order of resolutions.
One way to come up with an ordering would be to calculate the Adjusted Rand Index between pairs of clustering. Potentially starting with the clustering with most clusters and greedily adding those with highest ARI to build up the tree.
Idea originally from Aaron Lun.
The text was updated successfully, but these errors were encountered:
Currently {clustree} assumes the user knows the order of resolutions but this might not always be the case (if a clustering parameter doesn't have a natural order or has a non-linear effect) or it might just be interesting to see a "data-driven" order of resolutions.
One way to come up with an ordering would be to calculate the Adjusted Rand Index between pairs of clustering. Potentially starting with the clustering with most clusters and greedily adding those with highest ARI to build up the tree.
Idea originally from Aaron Lun.
The text was updated successfully, but these errors were encountered: