tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of geodist and seriation — release velocity, themes, recent moves, and the top alternatives to consider.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
seriation stopped shipping algorithms and started shipping a way to pick between them.
seriation finds meaningful orderings for matrices, distance objects and dendrograms, and carries a large registry of methods from classic combinatorial criteria to t-SNE and UMAP embeddings. The 1.5.0 release added a layer above that registry — seriate_best(), seriate_rep() and seriate_improve() — which run randomized methods repeatedly, in parallel, and keep the best result. Recent work is definitional and numeric rather than additive: 1.5.8 corrects the linear seriation criterion to match Hubert and Schultz's original 1976 definition.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
Development has been about making the speed-accuracy trade visible rather than hiding it. The 0.0.6 release added messages telling users to pick a different measure once the default cheap approximation is applied beyond 100km, where its error stops being negligible. Around that, the work is input handling — tibble support, better lon/lat column matching, vector inputs — and hardening the C code. It is a package that treats being small and correct as the feature.
Expect continued low-frequency maintenance: compiler warnings and geodesic source updates account for three of the last six releases, and the function surface has grown by only two entries in five years.
seriation finds meaningful orderings for matrices, distance objects and dendrograms, and carries a large registry of methods from classic combinatorial criteria to t-SNE and UMAP embeddings. The 1.5.0 release added a layer above that registry — seriate_best(), seriate_rep() and seriate_improve() — which run randomized methods repeatedly, in parallel, and keep the best result. Recent work is definitional and numeric rather than additive: 1.5.8 corrects the linear seriation criterion to match Hubert and Schultz's original 1976 definition.
The package has shifted from breadth to judgment. Through 1.3.x the additions were new methods; from 1.5.0 the registry started carrying metadata about the methods — whether they are randomized, what criterion they optimize — so the package could choose and evaluate on the user's behalf. The 1.5.6 replacement of FORTRAN with C for BEA and ME points the same way, reducing the legacy surface underneath that machinery.
Further criterion audits are the likeliest next move, since 1.5.8 shows a published definition being reconciled against the implementation and the registry now records what each method optimizes. Expect corrections rather than new seriation algorithms.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either geodist or seriation.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
A single-purpose ggplot2 inset tool, refining the same three arguments.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools stopped guarding its own object model and started accepting everyone else's.
The glue package that makes R carry units and uncertainty through the same calculation.
See all geodist alternatives → · See all seriation alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. geodist and seriation are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. geodist and seriation are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top geodist alternatives in Analytics are ranked by recent ship velocity. Browse the "geodist alternatives" section above for the current picks, or visit /alternatives/geodist-r for the full list with editorial commentary on each.
Top seriation alternatives in Analytics are ranked by recent ship velocity. Browse the "seriation alternatives" section above for the current picks, or visit /alternatives/seriation-r for the full list with editorial commentary on each.