driveR
A cancer driver prioritization package that ships rarely and mostly to stay installable
Comparison · Infra & APIs
missSBM vs PESTO
A side-by-side editorial comparison of missSBM and PESTO — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
missSBM vs PESTO: at a glance
What is missSBM?
missSBM returns after four dormant years with a stricter API and a new refinement step.
The package fits stochastic block models to networks with missing data, covering both missing-at-random and informative sampling designs. After a run of releases from 2019 to 2022, the feed goes quiet until this year's 1.1.0, which breaks the control interface, exposes the block split and merge operations as testable instance methods, and adds a node-swap refinement pass that runs after variational convergence.
What is PESTO?
A calibration toolkit that found its core PEST++ bridge had never actually run
PESTO wraps PEST++ inversion for APSIM crop models from R. Version 0.10.0 rebuilt the PEST++ invocation layer after the maintainer found the shell-out had never executed: control variables were passed as /h :name=value, a syntax PEST++ has never accepted. Fifteen defects were present since the initial April 2026 release and shipped in every version after it. 0.10.1 followed with APSIM binary discovery via APSIM_EXE_PATH and a benchmark battery against real PEST 18, pestpp-ies 5.2.16 and native APSIM that reproduced the prior baseline at 0.0% deviation on every accuracy metric.
missSBM vs PESTO: editorial side-by-side
missSBM
2.5INFRA · APIS
missSBM returns after four dormant years with a stricter API and a new refinement step.
◆ Current state
The package fits stochastic block models to networks with missing data, covering both missing-at-random and informative sampling designs. After a run of releases from 2019 to 2022, the feed goes quiet until this year's 1.1.0, which breaks the control interface, exposes the block split and merge operations as testable instance methods, and adds a node-swap refinement pass that runs after variational convergence.
◆ Where it's heading
The new release is maintenance-driven in the best sense: it targets the parts of the codebase that were hard to test or easy to misuse. Replacing free-form control lists with a function of named, defaulted arguments turns silent typos into errors, and pulling the exploration logic out of the collection class makes the search algorithm independently testable without changing it. The polish step addresses a known weakness, reaching individually misclassified nodes that split and merge moves cannot fix.
◆ Prediction
Given the gap before this release, the near-term question is whether the cadence resumes at all; the refactoring it contains would support further algorithmic work if it does.
PESTO
0.0INFRA · APIS
A calibration toolkit that found its core PEST++ bridge had never actually run
◆ Current state
PESTO wraps PEST++ inversion for APSIM crop models from R. Version 0.10.0 rebuilt the PEST++ invocation layer after the maintainer found the shell-out had never executed: control variables were passed as /h :name=value, a syntax PEST++ has never accepted. Fifteen defects were present since the initial April 2026 release and shipped in every version after it. 0.10.1 followed with APSIM binary discovery via APSIM_EXE_PATH and a benchmark battery against real PEST 18, pestpp-ies 5.2.16 and native APSIM that reproduced the prior baseline at 0.0% deviation on every accuracy metric.
◆ Where it's heading
The arc runs from packaging discipline toward working software, and the ordering is unusual. Releases 0.4.0 and 0.4.1 were governance and metadata passes: citation files, code of conduct, canonical URL migration to AAGI. 0.7.0 broadened the forward-model templates to ODE, crop-growth and SEIR forms and promoted the observation schema to public API. Only at 0.10.0 did the project ground itself against the actual USGS sources and a real pestpp binary, which is precisely when the defects surfaced.
◆ Prediction
Expect the next releases to widen the real-engine test matrix - more PEST++ variants and pinned APSIM versions exercised in CI - rather than add new forward-model families, since verification is now the stated priority in every release note.
Alternatives to missSBM and PESTO
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 missSBM or PESTO.
metR
A meteorology ggplot2 extension where the netCDF reader became the main event
IsoriX
An isotope geolocation package still recovering from the r-spatial retirement
fdacluster
Functional data clustering grew from one algorithm into a comparable suite
profoc
A forecast combination package that spun its profiler out into its own project
adjustedCurves
A survival curve package spending release after release correcting its own estimates
See all missSBM alternatives → · See all PESTO alternatives →
Recent activity from missSBM and PESTO
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 26d agomissSBMReplaces raw control lists with missSBM_param(), adds polish()
- 1mo agoPESTOAPSIM auto-discovery and a full real-engine benchmark pass
- 1mo agoPESTOPEST++ invocation layer rebuilt after 15 defects left it non-functional ⚡
- 2mo agoPESTOODE, crop-growth and SEIR forward-model templates enter the public API
- 2mo agoPESTOValidation delegation and import hygiene pass
- 2mo agoPESTORepository governance and citation metadata migration
- 3y agomissSBMAdapts to Matrix 1.4-2 and fixes HTML5 documentation
- 4y agomissSBMFixes linking against nloptR 2.0.0
- 5y agomissSBMRelaxes CRAN test tolerances to avoid random failures
- 5y agomissSBMRewrites optimisation in C++ armadillo with sparse matrices
- 5y agomissSBMRenames core functions and interfaces with the sbm package
Frequently asked questions
What is the difference between missSBM and PESTO?
Both compete on the same themes — r-package — within Infra & APIs. missSBM 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 missSBM better than PESTO?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. missSBM 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 missSBM?
Top missSBM alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "missSBM alternatives" section above for the current picks, or visit /alternatives/misssbm for the full list with editorial commentary on each.
What are the best alternatives to PESTO?
Top PESTO alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PESTO alternatives" section above for the current picks, or visit /alternatives/pesto for the full list with editorial commentary on each.