nflreadr
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
Comparison · Analytics
probmed vs PurpleAir
A side-by-side editorial comparison of probmed and PurpleAir — release velocity, themes, recent moves, and the top alternatives to consider.
probmed vs PurpleAir: at a glance
What is probmed?
probmed went from one probabilistic effect size to a family of them in sixteen days.
probmed computes P_med, a scale-free probabilistic effect size for causal mediation, as part of the Data-Wise mediationverse alongside medfit, medsim and RMediation. Three releases in three weeks took it from a single estimator to four additional families built on a shared cross-fitted corner-EIF core, covering gauge-calibrated, incremental-elasticity and Sobol variance-share versions of the proportion mediated. Distribution is GitHub and r-universe rather than CRAN, with a load-bearing Remotes pin on medfit.
What is PurpleAir?
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
PurpleAir is a small R client for the PurpleAir air quality sensor API, covering sensor queries, historical readings, and — more recently — finding a sensor on the local network by IP address and id. Authentication has been simplified to an environment variable only, with the redundant key argument removed. The package is maintained reactively, and most of what ships is correctness work on the queries it already makes.
probmed vs PurpleAir: editorial side-by-side
probmed
0.0ANALYTICS
probmed went from one probabilistic effect size to a family of them in sixteen days.
◆ Current state
probmed computes P_med, a scale-free probabilistic effect size for causal mediation, as part of the Data-Wise mediationverse alongside medfit, medsim and RMediation. Three releases in three weeks took it from a single estimator to four additional families built on a shared cross-fitted corner-EIF core, covering gauge-calibrated, incremental-elasticity and Sobol variance-share versions of the proportion mediated. Distribution is GitHub and r-universe rather than CRAN, with a load-bearing Remotes pin on medfit.
◆ Where it's heading
The pace is manuscript-driven — estimators arrive with their citations attached and vignettes alongside, and the 0.1.0 notes correct the estimand itself against a manuscript definition rather than fixing a bug in code. Each release adds inference machinery as well as point estimates: percentile-bootstrap intervals and Fieller sets in 0.3.0, a deterministic MBCO interval in 0.2.0 that avoids resampling entirely. The gauge residual and the pmed_sensitivity() helper suggest a growing concern with when the estimand does not decompose at all.
◆ Prediction
0.3.0 shipped a sensitivity helper for shared mediator-outcome confounding and a diagnostic that flags non-decomposability, so the next release most likely extends that diagnostic side rather than adding a fifth estimator family.
PurpleAir
0.0ANALYTICS
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
◆ Current state
PurpleAir is a small R client for the PurpleAir air quality sensor API, covering sensor queries, historical readings, and — more recently — finding a sensor on the local network by IP address and id. Authentication has been simplified to an environment variable only, with the redundant key argument removed. The package is maintained reactively, and most of what ships is correctness work on the queries it already makes.
◆ Where it's heading
The recurring theme is time aggregation. Weekly, monthly and yearly average intervals were wrong and fixed in one release; the weekly average was wrong again and fixed in the next. For an air quality package that is not incidental — averaging window is what turns a stream of sensor readings into an exposure estimate, and downstream analyses inherit the error silently. The other thread is failing earlier and more clearly: explicit errors for spatial inputs the sensor query does not accept, better index parsing so malformed requests never reach the API, and handling for history calls that return nothing. Local sensor discovery is the one genuine capability addition, opening a path that does not depend on the cloud API at all.
◆ Prediction
On this record, further aggregation and input-validation fixes are the likeliest next releases; whether local network access grows past discovery into full local data retrieval is not something the entries indicate.
Alternatives to probmed and PurpleAir
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 probmed or PurpleAir.
susier
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
UCell
A rank-based gene signature scorer that has grown by adapting to whatever object format single-cell R uses next
detectseparation
A diagnostic package that generalized past its own name, then learned to say which kind of separation it found
brglm2
A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression
bayestools
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
See all probmed alternatives → · See all PurpleAir alternatives →
Recent activity from probmed and PurpleAir
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoprobmedFour estimator families on a cross-fitted corner-EIF core ⚡
- 2mo agoprobmedParallel mediators and a resampling-free MBCO interval ⚡
- 2mo agoprobmedFirst release: pmed() with the estimand corrected
- 3mo agoPurpleAirWeekly averages fixed again; API key argument dropped
- 10mo agoPurpleAirLocal sensor discovery, and averaging intervals corrected
- 1y agoPurpleAirBounding box sensor queries fixed
Frequently asked questions
What is the difference between probmed and PurpleAir?
They serve adjacent needs but don't currently overlap on shipped themes. probmed and PurpleAir 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 probmed better than PurpleAir?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. probmed and PurpleAir 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 probmed?
Top probmed alternatives in Analytics are ranked by recent ship velocity. Browse the "probmed alternatives" section above for the current picks, or visit /alternatives/probmed for the full list with editorial commentary on each.
What are the best alternatives to PurpleAir?
Top PurpleAir alternatives in Analytics are ranked by recent ship velocity. Browse the "PurpleAir alternatives" section above for the current picks, or visit /alternatives/purpleair for the full list with editorial commentary on each.