nflreadr
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
Comparison · Analytics
forrel vs PurpleAir
A side-by-side editorial comparison of forrel and PurpleAir — release velocity, themes, recent moves, and the top alternatives to consider.
forrel vs PurpleAir: at a glance
What is forrel?
forrel is getting faster at the simulations forensic kinship work actually spends its time on.
forrel handles forensic pedigree analysis: kinship likelihood ratios, profile simulation, relationship checking, and missing person calculations. Version 1.9.0 synced with pedtools 2.11.0's loop handling, which the release notes credit with enabling complex pedigrees that were previously intractable, and moved profileSim() to mirai for parallelism. It also added fEstimate() for inbreeding coefficients and parentChildLikelihood() as a fast path for the simplest case.
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.
forrel vs PurpleAir: editorial side-by-side
forrel
0.0ANALYTICS
forrel is getting faster at the simulations forensic kinship work actually spends its time on.
◆ Current state
forrel handles forensic pedigree analysis: kinship likelihood ratios, profile simulation, relationship checking, and missing person calculations. Version 1.9.0 synced with pedtools 2.11.0's loop handling, which the release notes credit with enabling complex pedigrees that were previously intractable, and moved profileSim() to mirai for parallelism. It also added fEstimate() for inbreeding coefficients and parentChildLikelihood() as a fast path for the simplest case.
◆ Where it's heading
Two long threads run through the window. One is making the common operations cheap: faster simulations through reorganized likelihood calculations, a dedicated parent-child path, dropped map attribute preservation, log-likelihoods to avoid underflow in kinshipLR(). The other is making relationship checking presentable, with checkPairwise() growing ggplot2 and plotly output, verbal relationship descriptions, and bootstrap p-values. Reference data is maintained alongside both, with the FORCE SNP panel completed and an X-chromosomal counterpart added.
◆ Prediction
With profileSim() on mirai and the loop handling synced, the next likely step is extending mirai parallelism to the other simulation-heavy functions such as exclusionPower() and the bootstrap in checkPairwise().
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 forrel 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 forrel 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 forrel alternatives → · See all PurpleAir alternatives →
Recent activity from forrel and PurpleAir
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoforrelmirai parallelism and faster profile simulation
- 3mo agoPurpleAirWeekly averages fixed again; API key argument dropped
- 10mo agoPurpleAirLocal sensor discovery, and averaging intervals corrected
- 1y agoforrelFORCE SNP panel completed and X-chromosomal set added
- 1y agoforrelrankProfiles() and access to special lumping
- 1y agoforrelacrossComps argument and readFam() unexported
- 1y agoPurpleAirBounding box sensor queries fixed
- 1y agoforrelcheckPairwise() overhauled with p-values and new plot backends
- 2y agoforrelFamilias interoperability split into pedFamilias
Frequently asked questions
What is the difference between forrel and PurpleAir?
They serve adjacent needs but don't currently overlap on shipped themes. forrel 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 forrel better than PurpleAir?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. forrel 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 forrel?
Top forrel alternatives in Analytics are ranked by recent ship velocity. Browse the "forrel alternatives" section above for the current picks, or visit /alternatives/forrel 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.