simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of semmcci and svines — release velocity, themes, recent moves, and the top alternatives to consider.
Monte Carlo confidence intervals for SEM, now mostly reacting to upstream deprecations
semmcci generates Monte Carlo confidence intervals for structural equation model parameters, working alongside lavaan. Its four-year release history is a run of patch versions from the jeksterslab account, each adding a function or adjusting method detail. The recent ones are quieter still: the latest addresses a lavaan::getCov() deprecation in tests, and the one before it is described only as minor method edits.
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
svines fits stationary vine copula models to multivariate time series, extending the rvinecopulib engine with the serial dependence structure that makes vines usable for temporal data. The visible history is three releases carrying one real addition — pseudo-residual computation and logLik support at 0.2.2 — with the rest tracking its C++ dependency.
semmcci generates Monte Carlo confidence intervals for structural equation model parameters, working alongside lavaan. Its four-year release history is a run of patch versions from the jeksterslab account, each adding a function or adjusting method detail. The recent ones are quieter still: the latest addresses a lavaan::getCov() deprecation in tests, and the one before it is described only as minor method edits.
The functional build-out finished some time ago. MCGeneric() in 1.1.3 and Func()/MCFunc() in 1.1.4 opened the package to user-defined functions of parameters, which is the natural end point for a Monte Carlo interval tool — once arbitrary functions are supported, there is little left to add. Since then releases have tracked lavaan's changes rather than semmcci's own direction, and the gap between them has stretched from months to over a year.
Expect the next release to be triggered by another lavaan deprecation rather than by new capability.
svines fits stationary vine copula models to multivariate time series, extending the rvinecopulib engine with the serial dependence structure that makes vines usable for temporal data. The visible history is three releases carrying one real addition — pseudo-residual computation and logLik support at 0.2.2 — with the rest tracking its C++ dependency.
This package moves when rvinecopulib moves. The 0.2.4 release exists solely to adapt to a new rvinecopulib version, and 0.2.7 carries auto-generated GitHub release notes with no description at all. It shipped on the same day as kde1d 1.1.1, another package from the same maintainer, which is the pattern to watch: changes in the shared C++ layer surface as near-simultaneous releases across the vine family rather than as independent work.
The next release most plausibly follows another rvinecopulib update rather than adding modelling capability. Two of the three visible entries carry no substantive notes, so this feed will keep underreporting what changed.
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 semmcci or svines.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
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.
See all semmcci alternatives → · See all svines alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. semmcci and svines 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. semmcci and svines 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 semmcci alternatives in Analytics are ranked by recent ship velocity. Browse the "semmcci alternatives" section above for the current picks, or visit /alternatives/semmcci for the full list with editorial commentary on each.
Top svines alternatives in Analytics are ranked by recent ship velocity. Browse the "svines alternatives" section above for the current picks, or visit /alternatives/svines for the full list with editorial commentary on each.