nabla
nabla dropped its C++ engine to chase exact derivatives at any order.
Comparison · Analytics
compositional.mle vs tulpa
A side-by-side editorial comparison of compositional.mle and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
compositional.mle vs tulpa: at a glance
What is compositional.mle?
An MLE package rebuilt around composable solvers, then renamed to match.
compositional.mle performs numerical maximum likelihood estimation in R, with the optimisation strategy expressed as composed pieces rather than configured up front. It began in November 2025 as numerical.mle, a configuration-object package with fixed solvers. The v0.2.0 rewrite replaced that with solver factories sharing a uniform signature and operators for chaining and racing them, and renamed the package accordingly. The two most recent releases are CRAN submission work.
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.
compositional.mle vs tulpa: editorial side-by-side
compositional.mle
0.0ANALYTICS
An MLE package rebuilt around composable solvers, then renamed to match.
◆ Current state
compositional.mle performs numerical maximum likelihood estimation in R, with the optimisation strategy expressed as composed pieces rather than configured up front. It began in November 2025 as numerical.mle, a configuration-object package with fixed solvers. The v0.2.0 rewrite replaced that with solver factories sharing a uniform signature and operators for chaining and racing them, and renamed the package accordingly. The two most recent releases are CRAN submission work.
◆ Where it's heading
The arc is a design idea overtaking an implementation: version 0.1.0 exposed configuration functions and named solvers, version 0.2.0 turned solvers into values that can be sequenced with %>>%, raced with %|%, restarted, or conditionally refined, and separated the statistical problem from the optimisation strategy. Since then all effort has gone into CRAN acceptance, dead code removal, policy compliance, validation fixes. That is a package that redesigned itself early and is now trying to get through the door.
◆ Prediction
With the composable API settled, the next work will most likely be additional solvers and transformers plugged into the existing operators rather than another redesign.
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 compositional.mle 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 compositional.mle or tulpa.
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.
lazyeval
A package retired in 2017 just got rewritten against R's public C API.
See all compositional.mle alternatives → · See all tulpa alternatives →
Recent activity from compositional.mle 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
- 6mo agocompositional.mleParallel racing fixed under the future package
- 6mo agocompositional.mleDead code removed and CRAN policy compliance work
- 8mo agocompositional.mleSolvers become composable values, and the package is renamed ⚡
- 8mo agocompositional.mleFirst release as numerical.mle, built on configuration objects
Frequently asked questions
What is the difference between compositional.mle and tulpa?
They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 6.3 vs 0.0), 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 compositional.mle 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 0.0), 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 compositional.mle?
Top compositional.mle alternatives in Analytics are ranked by recent ship velocity. Browse the "compositional.mle alternatives" section above for the current picks, or visit /alternatives/compositional-mle 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.