Skip to content

feat: allow .tree cluster-data for higher-order networks#425

Draft
antoneri wants to merge 1 commit intomasterfrom
feat/issue-247-tree-clusterdata
Draft

feat: allow .tree cluster-data for higher-order networks#425
antoneri wants to merge 1 commit intomasterfrom
feat/issue-247-tree-clusterdata

Conversation

@antoneri
Copy link
Copy Markdown
Member

@antoneri antoneri commented Apr 9, 2026

Summary

  • allow .tree and .ftree cluster-data input to be normalized to state-level leaf ids before the existing tree init path runs
  • support both physical and state-level tree input on higher-order networks without adding any new flags or arguments
  • extend native and Python regressions for first-order, higher-order, lifecycle, parser recovery, and sanitizer coverage

Why

Issue #247 asks for tree-based cluster-data input to work through the normal optimization flow. The previous implementation only matched tree leaves directly by state id, which meant physical tree input on higher-order networks was not handled safely through the public --cluster-data / cluster_data interfaces.

Validation

  • make test-native CTEST_ARGS='-R partition'
  • make build-native test-native
  • make build-python test-python test-js-metadata test-docs using the local venv toolchain
  • make test-sanitizers CTEST_ARGS='-R partition'

Closes: #247

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Algorithm for improving partitions based on tree input

1 participant