simplify_hierarchy and CondensedTree._select_clusters optimisations #677
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR simplifies and optimises the
CondensedTree._select_clusters
andsimplify_hierarchy
functions. It turns out that thesimplify_hierarchy
operation reduces to iterating over thecluster_tree
in reverse order (so children are processed before their parents).The PR introduces one behavioural change to
simplify_hierarchy
. Density values are no longer updated when two leaves combine into one. This change ensures that the resulting leaf-combination retains its full density range. Consequently, the resulting simplified tree more accurately reflects the persistence threshold. Only when a leaf merges into a non-leaf are the leaf's density values updated to avoid breaking the condensed tree plot. Those points can have densities higher than the non-leaf's birth density, resulting in child clusters breaking off from a parent cluster before its icicle ends.