← Back to home
Comparison · Infra & APIs

eratosthenes vs MachineShop

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

Shared themes:r-package

eratosthenes vs MachineShop: at a glance

FeatureeratosthenesMachineShop
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesarchaeology, bayesian-inference, mcmc, input-validationmachine-learning, r-package, model-framework, variable-importance
Last editorial update59m ago23h ago
WebsiteVisit →Visit →

What is eratosthenes?

eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.

eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().

Read the full eratosthenes trajectory →

What is MachineShop?

A mature R modelling framework refining variable importance and resampling controls

MachineShop provides a unified interface over a wide set of R model packages, handling fitting, resampling, performance metrics and variable importance behind one API. Recent releases are narrow and mostly corrective: 3.9.2 removed dead documentation links and fixed a Java parameter in a BART example, 3.9.1 ensured global settings reach compute nodes when varimp() runs in parallel and patched XGBoost model compatibility. The last release with real surface change was 3.9.0, which added offset support to XGBModel and a pool argument to calibration() controlling whether calibration curves are computed on pooled predictions or averaged across resampling iterations.

Read the full MachineShop trajectory →

eratosthenes vs MachineShop: editorial side-by-side

E
eratosthenes
INFRA · APIS
2.5

eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.

◆ Current state

eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().

◆ Where it's heading

The package is moving from research code to something a non-author can run. Consolidating estimation behind one function, then wrapping every input class in a validator, are the two steps that make failures legible instead of cryptic, and the diagnostics added earlier serve the same end for the sampler itself. Nothing in the window changes the underlying model; the work is all about making it usable and its output checkable.

◆ Prediction

With inputs validated and diagnostics in place, the next release is more likely to extend the constraint or assemblage modelling than to keep reworking the interface, though the feed's three sparse tags give little to read a cadence from.

M
MachineShop
INFRA · APIS
0.0

A mature R modelling framework refining variable importance and resampling controls

◆ Current state

MachineShop provides a unified interface over a wide set of R model packages, handling fitting, resampling, performance metrics and variable importance behind one API. Recent releases are narrow and mostly corrective: 3.9.2 removed dead documentation links and fixed a Java parameter in a BART example, 3.9.1 ensured global settings reach compute nodes when varimp() runs in parallel and patched XGBoost model compatibility. The last release with real surface change was 3.9.0, which added offset support to XGBModel and a pool argument to calibration() controlling whether calibration curves are computed on pooled predictions or averaged across resampling iterations.

◆ Where it's heading

Development has concentrated on variable importance and resampling rather than on adding models. 3.8.0 restructured the VariableImportance class to record which method and metric produced it, with an update() method to migrate objects from earlier versions, and extended term-specific p-values to Cox, POLR and survival regression models. 3.7.0 added grouped and stratified resampling to the control objects. The pace has slowed markedly - four releases in the last two years against six in the two before - and the recent content is compatibility work against XGBoost, parsnip, ggplot2 and recipes.

◆ Prediction

Expect the deprecated calibration pooling behaviour to be removed in a future release as the notes state, with the intervening versions continuing to track upstream model package changes.

Alternatives to eratosthenes and MachineShop

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 eratosthenes or MachineShop.

See all eratosthenes alternatives → · See all MachineShop alternatives →

Recent activity from eratosthenes and MachineShop

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

  1. 10d agoeratosthenesInput validators added; seq_check() replaced by seq_diag()
  2. 5mo agoMachineShopDocumentation link cleanup and a BART example fix
  3. 8mo agoMachineShopGlobal settings now reach compute nodes during parallel varimp
  4. 1y agoeratosthenesArtifact p.d.f. estimation consolidated into gibbs_ad_type()
  5. 1y agoeratosthenesMCMC diagnostics arrive: traceplots, histograms, batch-means MCSE
  6. 1y agoMachineShopOffset support for XGBoost and per-iteration calibration curves
  7. 1y agoMachineShopVariable importance objects record their own method and metric
  8. 2y agoMachineShopGrouped and stratified resampling in the control objects
  9. 3y agoMachineShopBackward compatibility for older model objects

Frequently asked questions

What is the difference between eratosthenes and MachineShop?

Both compete on the same themes — r-package — within Infra & APIs. eratosthenes 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 eratosthenes better than MachineShop?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. eratosthenes 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 eratosthenes?

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

What are the best alternatives to MachineShop?

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