compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
Comparison · Analytics
nabla vs tulpaObs
A side-by-side editorial comparison of nabla and tulpaObs — release velocity, themes, recent moves, and the top alternatives to consider.
nabla vs tulpaObs: at a glance
What is nabla?
nabla dropped its C++ engine to chase exact derivatives at any order.
nabla does forward-mode automatic differentiation in R using dual numbers, returning derivatives exact to machine precision rather than approximated by finite differences. It shipped as dualr in January 2026, then a day later released 0.5.0 under a changed identity: derivatives generalise from a hardcoded second order to arbitrary order through recursive nesting, and the Rcpp and C++ fast paths are deleted so the package is pure R. The current release, 0.7.1, is CRAN resubmission cleanup.
What is tulpaObs?
An occupancy-modeling package that just deleted its own duplicate vocabulary for diagnostics.
tulpaObs is the ecological occupancy and abundance modeling layer built on the tulpa engine, releasing at high frequency and with version numbers that do not advance monotonically in publication order. The current window covers three strands: a breaking consolidation of its diagnostic surface onto generics the engine now owns, the completion of simulation-based-calibration registration across all 27 model families, and a correctness fix that materially moves previously reported information criteria. Several releases exist only to pin a new engine version and record what that change does when measured from this side.
nabla vs tulpaObs: editorial side-by-side
nabla
0.0ANALYTICS
nabla dropped its C++ engine to chase exact derivatives at any order.
◆ Current state
nabla does forward-mode automatic differentiation in R using dual numbers, returning derivatives exact to machine precision rather than approximated by finite differences. It shipped as dualr in January 2026, then a day later released 0.5.0 under a changed identity: derivatives generalise from a hardcoded second order to arbitrary order through recursive nesting, and the Rcpp and C++ fast paths are deleted so the package is pure R. The current release, 0.7.1, is CRAN resubmission cleanup.
◆ Where it's heading
The 0.5.0 release note states the positioning explicitly: exact machine-precision derivatives at any order, not speed. Removing compiled code to make that claim coherent is an unusual direction, most numerical R packages move the other way, and it commits the package to a niche where correctness beats throughput. The old second-order API survives as deprecated thin wrappers, so the pivot was made without stranding early users. The rapid rename and version jump suggest identity was settled late.
◆ Prediction
Expect CRAN acceptance to be followed by work on the optimiser and MLE integration paths, where arbitrary-order derivatives have the clearest use.
tulpaObs
6.3ANALYTICS
An occupancy-modeling package that just deleted its own duplicate vocabulary for diagnostics.
◆ Current state
tulpaObs is the ecological occupancy and abundance modeling layer built on the tulpa engine, releasing at high frequency and with version numbers that do not advance monotonically in publication order. The current window covers three strands: a breaking consolidation of its diagnostic surface onto generics the engine now owns, the completion of simulation-based-calibration registration across all 27 model families, and a correctness fix that materially moves previously reported information criteria. Several releases exist only to pin a new engine version and record what that change does when measured from this side.
◆ Where it's heading
The package is systematically removing the parallel names it had accumulated for concepts owned elsewhere, and the registration work is closing rather than expanding — the SBC scope reached its final family in this window. Its cadence is tightly coupled to the engine's, to the point where the interesting content of some releases is a dependency floor plus a measurement. With the breaking rename and the registration scope both behind it, the surface work looks close to finished.
◆ Prediction
Expect the follow-on releases to be consolidation rather than expansion — registry branches, regenerated documentation, engine pins — with the next substantive move most likely a new model family beyond the original registration scope.
Alternatives to nabla and tulpaObs
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 nabla or tulpaObs.
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 nabla alternatives → · See all tulpaObs alternatives →
Recent activity from nabla and tulpaObs
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agotulpaObsAGENTS.md added as the Codex-facing counterpart to CLAUDE.md
- 1d agotulpaObsSBC helper now handles any response rank, fixing 4D families
- 1d agotulpaObsms_abun() registered for SBC, closing the 27-family scope
- 1d agotulpaObsSBC registry gains the ms_abun() ranked-quantity branch
- 5d agotulpaObsEvery diagnostic becomes one verb dispatched on the fit (breaking) ⚡
- 5d agotulpaObsInformation criteria now score random effects the fit carried
- 5mo agonablaCRAN resubmission cleanup after reviewer feedback
- 6mo agonablaArbitrary-order exact derivatives arrive; compiled code removed ⚡
- 6mo agonablaFirst release as dualr: dual-number autodiff with MLE helpers
Frequently asked questions
What is the difference between nabla and tulpaObs?
They serve adjacent needs but don't currently overlap on shipped themes. tulpaObs 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 nabla better than tulpaObs?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tulpaObs 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 nabla?
Top nabla alternatives in Analytics are ranked by recent ship velocity. Browse the "nabla alternatives" section above for the current picks, or visit /alternatives/nabla for the full list with editorial commentary on each.
What are the best alternatives to tulpaObs?
Top tulpaObs alternatives in Analytics are ranked by recent ship velocity. Browse the "tulpaObs alternatives" section above for the current picks, or visit /alternatives/tulpaobs for the full list with editorial commentary on each.