lavaanExtra
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A side-by-side editorial comparison of maths.genealogy and simlandr — release velocity, themes, recent moves, and the top alternatives to consider.
A young Mathematics Genealogy client spending its first four releases satisfying CRAN.
maths.genealogy queries the Mathematics Genealogy Project over a WebSocket connection and renders academic advisor-student trees, with plot_grviz() as the visualisation entry point. The package reached CRAN in early 2025 and its functional surface has barely moved since — max_zoom() for deep trees at 0.1.1 is the only user-facing addition in the visible history.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
simlandr builds potential landscape plots from simulations of dynamic systems, with barrier-height calculations and batch simulation grids. Its three substantive releases are all consolidation: parameters renamed, functions renamed, defaults removed. By 0.3.0 the bespoke accessors had been replaced by ggplot2's autolayer() and base summary(), and the package carried print, summary, and plot methods for its own classes.
maths.genealogy queries the Mathematics Genealogy Project over a WebSocket connection and renders academic advisor-student trees, with plot_grviz() as the visualisation entry point. The package reached CRAN in early 2025 and its functional surface has barely moved since — max_zoom() for deep trees at 0.1.1 is the only user-facing addition in the visible history.
Every release after the first is CRAN policy management. Three consecutive entries deal with the same underlying problem: examples that hit a live network resource and therefore fail unpredictably on check machines. The progression from wrapping them in \donttest{} to catching a stray case to rewriting all examples against published API-package guidance shows the maintainer converging on a pattern rather than adding features. That is the normal cost of shipping a network client to CRAN, and it appears to be settling.
With the examples problem resolved, the next release is the first plausible opportunity for feature work — likely on the plotting side, given max_zoom() was the sole non-compliance change so far. The entries do not name anything specific in progress.
simlandr builds potential landscape plots from simulations of dynamic systems, with barrier-height calculations and batch simulation grids. Its three substantive releases are all consolidation: parameters renamed, functions renamed, defaults removed. By 0.3.0 the bespoke accessors had been replaced by ggplot2's autolayer() and base summary(), and the package carried print, summary, and plot methods for its own classes.
Every release trades a package-specific name for a conventional one - var and par became arg and ele, get_geom() became an autolayer() method, get_barrier_height() became a summary() method, hash_big.matrix became hash_big_matrix. The one methodological change, an adjusted minimal energy path algorithm, arrived inside a release otherwise full of renames. Removing default values for barrier calculation because they were often unsuitable reads as the maintainer deciding the defaults were doing harm.
The feed stops at 0.3.0 in late 2022, mid-consolidation; these entries give no indication of what followed, if anything did.
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 maths.genealogy or simlandr.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
From a bundled hospital dataset to a live CMS API client.
See all maths.genealogy alternatives → · See all simlandr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. maths.genealogy and simlandr 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. maths.genealogy and simlandr 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 maths.genealogy alternatives in Analytics are ranked by recent ship velocity. Browse the "maths.genealogy alternatives" section above for the current picks, or visit /alternatives/maths-genealogy for the full list with editorial commentary on each.
Top simlandr alternatives in Analytics are ranked by recent ship velocity. Browse the "simlandr alternatives" section above for the current picks, or visit /alternatives/simlandr for the full list with editorial commentary on each.