lavaanExtra
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A side-by-side editorial comparison of simlandr and tbrf — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Time-based rolling statistics for water-quality data, finally getting plotting and padding built in.
tbrf computes rolling statistics over time windows rather than fixed row counts — geometric means, confidence intervals and related summaries indexed by date. That distinction matters for irregularly sampled environmental monitoring data, where a fixed-width window spans different amounts of real time. Version 0.1.7 folds in stat_stepribbon() from ggalt, ships an Entero example dataset for lognormal workflows, and adds na.pad across the tbr_ family.
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.
tbrf computes rolling statistics over time windows rather than fixed row counts — geometric means, confidence intervals and related summaries indexed by date. That distinction matters for irregularly sampled environmental monitoring data, where a fixed-width window spans different amounts of real time. Version 0.1.7 folds in stat_stepribbon() from ggalt, ships an Entero example dataset for lognormal workflows, and adds na.pad across the tbr_ family.
The package spent its middle releases absorbing upstream breakage — a lubridate duration redefinition, a tibble 3.0.0 subassignment change, tidyselect internals. The 0.1.7 release breaks that pattern: it is the first in five years to add capability rather than repair it, and it does so by internalising a stat from an abandoned dependency instead of relying on it. Cadence remains very low, with a five-year gap between 0.1.5 and 0.1.6.
Absorbing stat_stepribbon() directly suggests further vendoring of the plotting layer rather than new statistical functions. The entries do not indicate which rolling statistics, if any, are queued next.
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 simlandr or tbrf.
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 simlandr alternatives → · See all tbrf alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. simlandr and tbrf 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. simlandr and tbrf 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 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.
Top tbrf alternatives in Analytics are ranked by recent ship velocity. Browse the "tbrf alternatives" section above for the current picks, or visit /alternatives/tbrf for the full list with editorial commentary on each.