seriation
Infrastructure for Ordering Objects Using Seriation
seriation stopped shipping algorithms and started shipping a way to pick between them.
◆Recent moves
- 0y ago
seriation 1.5.8 realigns linear criterion with Hubert and Schultz
The linear seriation criterion now follows the original 1976 definition and is treated as a merit measure rather than a loss. Users comparing methods on this criterion will see the optimization direction flip, so it is more consequential than the one-line note suggests. The accompanying partial argument match fix is the same CRAN sweep that hit arulesViz the next day.
View source ↗ - 1y ago
seriation 1.5.7 adds BK_unconstrained, handles tiny inputs
A contributed seriation method joins the registry, and all methods now degrade gracefully when given too few objects instead of failing. Routine registry growth on top of the 1.5.0 infrastructure.
View source ↗ - 1y ago
seriation 1.5.6 replaces FORTRAN BEA with C, modernizes allocation
Internal modernization: BEA's FORTRAN implementation is swapped for code from TSP, ME moves to C, and the optimal and stress routines adopt R's memory allocation. Users see the same results from a smaller legacy surface.
View source ↗ - 2y ago
seriation 1.5.5 digest: AOE method, rep parameter, MDS_angle fix
A rolled-up entry covering 1.5.3 through 1.5.5. The substance sits in 1.5.3 — an AOE method for correlation matrices, dendrogram permutation accepting seriation methods, and a rep parameter on every method — plus a fix for MDS_angle ordering varying across BLAS implementations.
View source ↗ - 3y ago
seriation 1.5.1 refines pimage, permute and hmap
Convenience and correctness work a day after 1.5.0: order = TRUE triggers default seriation in pimage and permute, hmap gains distance-matrix palettes, and zlim is applied correctly. The cleanup pass that follows a large release.
View source ↗ - 3y ago
seriation 1.5.0 adds seriate_best and parallel repeated search
⚡ SPARKThe release that changed what the package does for you. Rather than running one algorithm and accepting its ordering, seriate_best(), seriate_rep() and seriate_improve() exploit the fact that many methods are randomized, running them repeatedly in parallel and keeping the best result by the registered criterion.
View source ↗