nabla
nabla dropped its C++ engine to chase exact derivatives at any order.
Comparison · Analytics
compositional.mle vs tulpaObs
A side-by-side editorial comparison of compositional.mle and tulpaObs — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
compositional.mle vs tulpaObs: 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 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.
compositional.mle vs tulpaObs: 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.
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 compositional.mle 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 compositional.mle 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 compositional.mle alternatives → · See all tulpaObs alternatives →
Recent activity from compositional.mle 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
- 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 tulpaObs?
Both compete on the same themes — r-package — within Analytics. 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 compositional.mle 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 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 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.