The current partitioning interface does not expose all HORTON partitioning options through XDMSession.setup_partition_schemes().
In particular, options such as lmax and scheme-specific parameters (k, maxiter, threshold) cannot currently be configured by users and are fixed to internal defaults. This limits control over the underlying HORTON partitioning methods.
The implementation should allow passing partitioning-specific keyword arguments from setup_partition_schemes() to the corresponding HORTON partitioning classes while maintaining backward compatibility with the current API.
The current partitioning interface does not expose all HORTON partitioning options through
XDMSession.setup_partition_schemes().In particular, options such as
lmaxand scheme-specific parameters (k,maxiter,threshold) cannot currently be configured by users and are fixed to internal defaults. This limits control over the underlying HORTON partitioning methods.The implementation should allow passing partitioning-specific keyword arguments from
setup_partition_schemes()to the corresponding HORTON partitioning classes while maintaining backward compatibility with the current API.