← Back to home
Comparison · Infra & APIs

BayesianMCPMod vs sps

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

Shared themes:r-package

BayesianMCPMod vs sps: at a glance

FeatureBayesianMCPModsps
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesclinical-trials, dose-finding, bayesian-statistics, r-packager-package, survey-sampling, sequential-poisson, performance
Last editorial update1h ago2h ago
WebsiteVisit →Visit →

What is BayesianMCPMod?

A Bayesian dose-finding package extends from continuous endpoints to binary ones

BayesianMCPMod implements the Bayesian form of MCP-Mod for dose-finding trials, combining a multiple-comparison test for dose-response signal with model fitting for dose selection. Version 1.3.0 added functions and vignettes for the binary endpoint case, opening the package beyond the continuous endpoints it was built around, and 1.3.2 followed with Firth's penalized regression to handle separation in those binary fits. The same 1.3.0 release let assessDesign() accept custom simulated data and custom model estimates, which moves simulation control out of the package and into the user's hands.

Read the full BayesianMCPMod trajectory →

What is sps?

sps keeps sanding down sequential Poisson sampling rather than adding to it.

The package implements sequential Poisson sampling for survey design, covering inclusion probabilities, proportional allocation, replicate weights, and take-all strata. Recent releases are small and tightly scoped: a divisor method helper, an iterator that draws a sample one unit at a time, automatic selection of the replicate-weight parameter, and repeated performance work on inclusion probability calculation.

Read the full sps trajectory →

BayesianMCPMod vs sps: editorial side-by-side

B
BayesianMCPMod
INFRA · APIS
0.0

A Bayesian dose-finding package extends from continuous endpoints to binary ones

◆ Current state

BayesianMCPMod implements the Bayesian form of MCP-Mod for dose-finding trials, combining a multiple-comparison test for dose-response signal with model fitting for dose selection. Version 1.3.0 added functions and vignettes for the binary endpoint case, opening the package beyond the continuous endpoints it was built around, and 1.3.2 followed with Firth's penalized regression to handle separation in those binary fits. The same 1.3.0 release let assessDesign() accept custom simulated data and custom model estimates, which moves simulation control out of the package and into the user's hands.

◆ Where it's heading

Each release has widened the estimands and data shapes the framework accepts rather than changing its statistical core. 1.0.2 added non-monotonic beta and quadratic model shapes; 1.1.0 introduced getMED() for the minimally efficacious dose and parallel execution through the future framework; 1.2.0 switched the posterior and contrast functions from a standard deviation vector to a full covariance matrix and supported non-zero off-diagonals in the MCP step. The binary endpoint work is the same pattern applied to the outcome type, and the Firth addition shows the follow-through of a maintainer who has hit the separation problem in practice.

◆ Prediction

Expect the binary endpoint arm to keep filling in - more diagnostics and design assessment coverage matching what the continuous case already has - since 1.3.2 addressed a specific estimation failure rather than adding a new capability.

S
sps
INFRA · APIS
2.5

sps keeps sanding down sequential Poisson sampling rather than adding to it.

◆ Current state

The package implements sequential Poisson sampling for survey design, covering inclusion probabilities, proportional allocation, replicate weights, and take-all strata. Recent releases are small and tightly scoped: a divisor method helper, an iterator that draws a sample one unit at a time, automatic selection of the replicate-weight parameter, and repeated performance work on inclusion probability calculation.

◆ Where it's heading

Development is consolidation rather than expansion. Most releases either speed up an existing routine or remove a decision the user previously had to make by hand, such as picking the smallest parameter that keeps replicate weights non-negative. Documentation and tooling get comparable attention to the algorithms, with a dedicated vignette on inclusion probabilities and a recent switch of test and documentation infrastructure. The API surface has been essentially stable across the window.

◆ Prediction

Expect continued small ergonomic and performance releases against the existing function set rather than new sampling designs, which is the pattern every release in this window follows.

Alternatives to BayesianMCPMod and sps

Other Infra & APIs 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 BayesianMCPMod or sps.

See all BayesianMCPMod alternatives → · See all sps alternatives →

Recent activity from BayesianMCPMod and sps

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

  1. 1mo agospsDocumentation polish; switches to tinytest and litedown
  2. 3mo agoBayesianMCPModFirth penalized regression handles separation in binary endpoints
  3. 5mo agoBayesianMCPModRegression fix for missing future.apply, plus credible band options
  4. 5mo agoBayesianMCPModBinary endpoint support opens the framework past continuous outcomes
  5. 9mo agospsFixes extra argument handling in sps_iterator()
  6. 11mo agoBayesianMCPModCovariance matrices replace standard deviation vectors in the MCP step
  7. 11mo agospsAdds divisor_method() and a one-unit-at-a-time sampling iterator
  8. 1y agospsAdds an inclusion-probability vignette and faster partial sorting
  9. 1y agoBayesianMCPModMinimally efficacious dose estimation and parallel execution
  10. 1y agoBayesianMCPModNon-monotonic beta and quadratic dose-response shapes
  11. 1y agospsAutomatic tau selection for replicate weights
  12. 2y agospsAdds becomes_ta() for take-all stratum sample sizes

Frequently asked questions

What is the difference between BayesianMCPMod and sps?

Both compete on the same themes — r-package — within Infra & APIs. sps is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 BayesianMCPMod better than sps?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. sps is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to BayesianMCPMod?

Top BayesianMCPMod alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "BayesianMCPMod alternatives" section above for the current picks, or visit /alternatives/bayesianmcpmod for the full list with editorial commentary on each.

What are the best alternatives to sps?

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