compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
Comparison · Analytics
libr vs tulpa
A side-by-side editorial comparison of libr and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
libr vs tulpa: at a glance
What is libr?
The SAS datastep clone for R just got roughly nineteen times faster.
libr gives R users SAS-style data libraries and a datastep() construct, sitting alongside logr, reporter and procs in the r-sassy suite for analysts moving clinical workflows off SAS. Most of its release history is narrow bug-fixing in the libname() readers, particularly the sas7bdat engine. The exception dominates the window: a single 2026 release that rewrote datastep() performance and cut the installed package to a quarter of its former size.
What is tulpa?
A Bayesian spatial engine reshaping itself so downstream packages own their own diagnostics.
tulpa is the C++/R inference engine sitting under a family of ecological occupancy packages, tagging releases several times a week in the 0.0.x range. The current window splits cleanly in two: an API move that turns its calibration and goodness-of-fit entry points into S3 generics, and a run of numerical-correctness work in the nested-Laplace grid. A notable share of releases exist to record a measurement that produced no code change at all.
libr vs tulpa: editorial side-by-side
libr
2.5ANALYTICS
The SAS datastep clone for R just got roughly nineteen times faster.
◆ Current state
libr gives R users SAS-style data libraries and a datastep() construct, sitting alongside logr, reporter and procs in the r-sassy suite for analysts moving clinical workflows off SAS. Most of its release history is narrow bug-fixing in the libname() readers, particularly the sas7bdat engine. The exception dominates the window: a single 2026 release that rewrote datastep() performance and cut the installed package to a quarter of its former size.
◆ Where it's heading
Two threads run through these entries — steady correctness work on SAS file import, and a much less frequent but far more consequential push on making datastep() viable at real data volumes. The recent fix to empty-variable typing suggests the sas7bdat reader is still where edge cases surface. Having addressed both speed and package size in one release, the obvious remaining pressure is correctness and coverage of SAS semantics rather than throughput.
◆ Prediction
Expect the next releases to continue narrowing sas7bdat import edge cases, with any further datastep() work aimed at supporting more SAS syntax rather than at speed.
tulpa
6.3ANALYTICS
A Bayesian spatial engine reshaping itself so downstream packages own their own diagnostics.
◆ Current state
tulpa is the C++/R inference engine sitting under a family of ecological occupancy packages, tagging releases several times a week in the 0.0.x range. The current window splits cleanly in two: an API move that turns its calibration and goodness-of-fit entry points into S3 generics, and a run of numerical-correctness work in the nested-Laplace grid. A notable share of releases exist to record a measurement that produced no code change at all.
◆ Where it's heading
The generics conversion and the new cross-Hessian return value point the same way: the engine is being reshaped into something downstream packages extend rather than wrap, with the extension points made explicit. The correctness fixes cluster tightly on the joint nested-Laplace driver — indefinite Hessians hitting negative pivots, chunk counts read from live machine load, grid cells silently dropped from a fit — which is where the remaining risk visibly sits. Reported numbers have moved more than once in this window, so the project is still finding cases where earlier answers were wrong rather than merely imprecise.
◆ Prediction
Expect the rest of the diagnostics layer to finish migrating onto generics, and continued hardening of the batched joint driver's dense path, which is the one route that recently diverged from its own single-species equivalent.
Alternatives to libr and tulpa
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 libr or tulpa.
nabla
nabla dropped its C++ engine to chase exact derivatives at any order.
snowflakeauth
Eight months from first release to keyring caching and workload identity.
kwb.geosalz
A research-project workflow package where the interesting work is in the plumbing.
cyclocomp
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
revdbayes
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
Recent activity from libr and tulpa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agotulpatulpa_re_aghq() exposes the mode/theta cross-Hessian
- 4d agotulpaDense batched joint path could silently drop a grid cell
- 5d agotulpaCalibration and goodness-of-fit entry points become S3 generics ⚡
- 6d agotulpaCUDA backend had two definitions; link order decided if it ran
- 6d agotulpaHyperparameter bounds now flag when they leave the node range
- 7d agotulpaNeither candidate outer-cell rule promoted, decided on coverage
- 11d agolibrsas7bdat import no longer types empty variables as logical
- 3mo agolibrdatastep() runs 83K rows in 21.6 seconds instead of 6.7 minutes ⚡
- 5mo agolibrTest data removed to reduce package size
- 2y agolibrlibname() no longer fails on an empty dataset
- 2y agolibrlib_write() detects dataset changes again
- 2y agolibrlibname() handles file names containing multiple dots
Frequently asked questions
What is the difference between libr and tulpa?
They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is libr better than tulpa?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tulpa is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to libr?
Top libr alternatives in Analytics are ranked by recent ship velocity. Browse the "libr alternatives" section above for the current picks, or visit /alternatives/libr for the full list with editorial commentary on each.
What are the best alternatives to tulpa?
Top tulpa alternatives in Analytics are ranked by recent ship velocity. Browse the "tulpa alternatives" section above for the current picks, or visit /alternatives/tulpa for the full list with editorial commentary on each.