← Back to home
Comparison · Analytics

compositional.mle vs TrialEmulation

A side-by-side editorial comparison of compositional.mle and TrialEmulation — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

compositional.mle vs TrialEmulation: at a glance

Featurecompositional.mleTrialEmulation
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmaximum-likelihood, optimization, functional-api, crancausal-inference, target-trial-emulation, duckdb, maintenance
Last editorial update39m ago42m ago
WebsiteVisit →Visit →

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.

Read the full compositional.mle trajectory →

What is TrialEmulation?

Target trial emulation held steady by dependency maintenance, not new methods.

TrialEmulation implements target trial emulation from observational data, using duckdb to handle the expanded per-period datasets that approach generates. Every release in the visible window is upkeep: two consecutive releases removing the archived parglm dependency, two fixing tests against testthat updates, and two tracking duckdb sampling changes. No methodological work appears in the feed since before February 2025.

Read the full TrialEmulation trajectory →

compositional.mle vs TrialEmulation: editorial side-by-side

C0.0

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.

T0.0

Target trial emulation held steady by dependency maintenance, not new methods.

◆ Current state

TrialEmulation implements target trial emulation from observational data, using duckdb to handle the expanded per-period datasets that approach generates. Every release in the visible window is upkeep: two consecutive releases removing the archived parglm dependency, two fixing tests against testthat updates, and two tracking duckdb sampling changes. No methodological work appears in the feed since before February 2025.

◆ Where it's heading

The package is being kept installable rather than extended. Its dependency surface, duckdb for storage, parglm for fitting, testthat for checks, generates most of the release traffic, and CRAN archiving parglm forced two separate releases three months apart to fully excise it. The version numbering, still in the 0.0.4.x range after years, suggests the maintainers do not consider the API settled enough to promote.

◆ Prediction

Further releases will most likely be triggered by upstream dependency changes; the entries give no signal on when methodological work resumes.

Alternatives to compositional.mle and TrialEmulation

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 TrialEmulation.

See all compositional.mle alternatives → · See all TrialEmulation alternatives →

Recent activity from compositional.mle and TrialEmulation

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4mo agoTrialEmulationDocumentation references to the archived parglm removed
  2. 6mo agocompositional.mleParallel racing fixed under the future package
  3. 6mo agocompositional.mleDead code removed and CRAN policy compliance work
  4. 7mo agoTrialEmulationparglm dependency dropped after CRAN archiving
  5. 8mo agocompositional.mleSolvers become composable values, and the package is renamed
  6. 8mo agocompositional.mleFirst release as numerical.mle, built on configuration objects
  7. 9mo agoTrialEmulationTest fixes for updated testthat, plus link updates
  8. 9mo agoTrialEmulationCompatibility fixes ahead of testthat 3.3.0
  9. 1y agoTrialEmulationTests updated for duckdb 1.3.0 sampling; R 4.1 now required
  10. 1y agoTrialEmulationTests updated for duckdb 1.2.0 sampling changes

Frequently asked questions

What is the difference between compositional.mle and TrialEmulation?

Both compete on the same themes — r-package — within Analytics. compositional.mle and TrialEmulation are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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 TrialEmulation?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. compositional.mle and TrialEmulation are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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 TrialEmulation?

Top TrialEmulation alternatives in Analytics are ranked by recent ship velocity. Browse the "TrialEmulation alternatives" section above for the current picks, or visit /alternatives/trialemulation for the full list with editorial commentary on each.