driveR
A cancer driver prioritization package that ships rarely and mostly to stay installable
Comparison · Infra & APIs
PESTO vs sps
A side-by-side editorial comparison of PESTO and sps — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
PESTO vs sps: at a glance
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.
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.
PESTO vs sps: editorial side-by-side
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.
sps
2.5INFRA · APIS
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 PESTO 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 PESTO or sps.
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
Recent activity from PESTO and sps
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agospsDocumentation polish; switches to tinytest and litedown
- 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
- 9mo agospsFixes extra argument handling in sps_iterator()
- 11mo agospsAdds divisor_method() and a one-unit-at-a-time sampling iterator
- 1y agospsAdds an inclusion-probability vignette and faster partial sorting
- 1y agospsAutomatic tau selection for replicate weights
- 2y agospsAdds becomes_ta() for take-all stratum sample sizes
Frequently asked questions
What is the difference between PESTO 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 PESTO 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 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.
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.