compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
Comparison · Analytics
revdbayes vs tulpa
A side-by-side editorial comparison of revdbayes and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
revdbayes vs tulpa: at a glance
What is revdbayes?
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
revdbayes performs Bayesian extreme value analysis using ratio-of-uniforms sampling, giving random samples rather than MCMC chains. Every entry in the visible window is filed under bug fixes and minor improvements. The most recent, 1.5.7, strips missing values before fitting the generalised Pareto MLE; the two before it are an Rcpp compatibility patch and a response to CRAN check failures that turned out to be false positives.
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.
revdbayes vs tulpa: editorial side-by-side
revdbayes
0.0ANALYTICS
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
◆ Current state
revdbayes performs Bayesian extreme value analysis using ratio-of-uniforms sampling, giving random samples rather than MCMC chains. Every entry in the visible window is filed under bug fixes and minor improvements. The most recent, 1.5.7, strips missing values before fitting the generalised Pareto MLE; the two before it are an Rcpp compatibility patch and a response to CRAN check failures that turned out to be false positives.
◆ Where it's heading
The methods are settled and the release traffic is external: Rcpp issues, CRAN platform checks, documentation anchor requirements. Two of the six releases exist only because CRAN's check farm flagged something, and one of those flags resolved itself. Sibling package profileCI from the same maintainer has been more active, which suggests attention has moved to newer work rather than away from R entirely.
◆ Prediction
Expect further small releases driven by Rcpp or CRAN check changes rather than by the sampling methods.
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 revdbayes 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 revdbayes 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.
lazyeval
A package retired in 2017 just got rewritten against R's public C API.
See all revdbayes alternatives → · See all tulpa alternatives →
Recent activity from revdbayes 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
- 4mo agorevdbayesMissing values now removed before generalised Pareto MLE fitting
- 7mo agorevdbayesRcpp patch applied to avoid masking Rf_error()
- 7mo agorevdbayesPatch for macOS CRAN check errors that proved to be false positives
- 2y agorevdbayesArgument documentation corrected; Rd link anchors fixed
- 2y agorevdbayesRcpp warning fix plus Rd itemize corrections
- 2y agorevdbayesC++11 specification dropped to clear a CRAN note
Frequently asked questions
What is the difference between revdbayes 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 revdbayes 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 revdbayes?
Top revdbayes alternatives in Analytics are ranked by recent ship velocity. Browse the "revdbayes alternatives" section above for the current picks, or visit /alternatives/revdbayes 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.