fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
Comparison · Analytics
PurpleAir vs robma
A side-by-side editorial comparison of PurpleAir and robma — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
PurpleAir vs robma: at a glance
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.
What is robma?
RoBMA 4.0 tears out its own constructor surface and rebuilds on one class hierarchy
RoBMA fits robust Bayesian model-averaged meta-analyses that adjust for publication bias. The 3.x line grew by accretion: separate constructors for each model family (RoBMA.reg, NoBMA, BiBMA and their .reg variants), a spike-and-slab algorithm in 3.3.0 that made estimation fast enough to matter, then a steady stream of post-estimation tooling gated on that algorithm — heterogeneity summaries, residuals, funnel plots, z-curve conversion, predict, extract, pooled and adjusted effects. Version 4.0.0 in May 2026 collapses all of it into a unified brma class hierarchy.
PurpleAir vs robma: editorial side-by-side
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.
robma
0.0ANALYTICS
RoBMA 4.0 tears out its own constructor surface and rebuilds on one class hierarchy
◆ Current state
RoBMA fits robust Bayesian model-averaged meta-analyses that adjust for publication bias. The 3.x line grew by accretion: separate constructors for each model family (RoBMA.reg, NoBMA, BiBMA and their .reg variants), a spike-and-slab algorithm in 3.3.0 that made estimation fast enough to matter, then a steady stream of post-estimation tooling gated on that algorithm — heterogeneity summaries, residuals, funnel plots, z-curve conversion, predict, extract, pooled and adjusted effects. Version 4.0.0 in May 2026 collapses all of it into a unified brma class hierarchy.
◆ Where it's heading
The 3.x series solved the modeling problem and left an interface problem behind: a caller had to know which of six constructors matched their data type, and argument names differed across them. 4.0.0 resolves that by making the model family a set of arguments rather than a function name, and by standardizing input naming on metafor-style conventions. It shipped one day after BayesTools 0.3.0, the author's own upstream infrastructure package, whose new standardization and prior-transformation machinery this rewrite depends on.
◆ Prediction
A rewrite this wide usually needs a follow-up, so expect 4.0.x patches addressing migration gaps as users hit the removed constructors and renamed arguments.
Alternatives to PurpleAir and robma
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 PurpleAir or robma.
gcube
gcube's recent releases are all packaging metadata, not simulation code
cubist
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats
ggstats keeps widening what a coefficient or Likert plot can be
ecodive
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
simStateSpace
State-space data simulation for R, filled in one function at a time
See all PurpleAir alternatives → · See all robma alternatives →
Recent activity from PurpleAir and robma
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agoPurpleAirWeekly averages fixed again; API key argument dropped
- 3mo agorobmaUnifies six model constructors into one brma class hierarchy ⚡
- 8mo agorobmaRoBMA 3.6.1
- 10mo agoPurpleAirLocal sensor discovery, and averaging intervals corrected
- 11mo agorobmaRoBMA 3.6.0
- 1y agorobmaRoBMA 3.5.1
- 1y agorobmaRoBMA 3.5.0
- 1y agorobmaRoBMA 3.4.0
- 1y agoPurpleAirBounding box sensor queries fixed
Frequently asked questions
What is the difference between PurpleAir and robma?
Both compete on the same themes — r-package — within Analytics. PurpleAir and robma 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 PurpleAir better than robma?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. PurpleAir and robma 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 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.
What are the best alternatives to robma?
Top robma alternatives in Analytics are ranked by recent ship velocity. Browse the "robma alternatives" section above for the current picks, or visit /alternatives/robma for the full list with editorial commentary on each.