PurpleAir
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
A side-by-side editorial comparison of qtl2 and quantmod — release velocity, themes, recent moves, and the top alternatives to consider.
The standard QTL mapping package in R opened its genome scan to user-supplied likelihood models.
qtl2 is the R toolkit for QTL mapping in experimental crosses, covering genotype probability calculation, genome scans with and without polygenic effects, permutation testing, SNP association, and the plotting that goes with them. The last year of work has pushed hard in two directions: tooling for high-throughput expression and protein QTL studies, and a generalisation of the scan engine itself so the log-likelihood being maximised can be supplied by the user. Note that the release history reached this feed out of order, so feed position is not a reliable guide to which release came first.
The R finance workhorse spends its releases absorbing what data vendors break
quantmod pulls market data into R and charts it, and has been in maintenance for years. The last six releases are dominated by upstream breakage: Yahoo Finance crumb authentication, a batch-size ceiling dropping from 199 to 99 symbols, GDPR consent failures, repeated URL changes at FRED and OANDA. Genuine additions are rare and small — a ClOp() return function, an intraday endpoint, better ambiguous-column detection.
qtl2 is the R toolkit for QTL mapping in experimental crosses, covering genotype probability calculation, genome scans with and without polygenic effects, permutation testing, SNP association, and the plotting that goes with them. The last year of work has pushed hard in two directions: tooling for high-throughput expression and protein QTL studies, and a generalisation of the scan engine itself so the log-likelihood being maximised can be supplied by the user. Note that the release history reached this feed out of order, so feed position is not a reliable guide to which release came first.
The eQTL and pQTL direction is the clearest thread — cis-trans plots, hotspot counting over a sliding window, multi-trait scan heat maps, and genome-wide genotype plots all arrived together, which is the toolkit an experiment with thousands of traits needs rather than one with a handful. Running underneath it is a steady generalisation of the core: a scan function that accepts an arbitrary likelihood, permutations that work with alternative scan functions, full variance-covariance output from single-position fits. Performance and parallelism get attention each cycle, including a more considerate default that leaves one core free. The rest is the ordinary maintenance of a long-lived package — renames to avoid tidyverse collisions, compiler warnings, and correctness fixes on specific cross types.
With scan1gen and permutation support for alternative scan functions in place, the natural next step is more model types built on that hook rather than more special-cased scan functions; the entries do not indicate which models are planned.
quantmod pulls market data into R and charts it, and has been in maintenance for years. The last six releases are dominated by upstream breakage: Yahoo Finance crumb authentication, a batch-size ceiling dropping from 199 to 99 symbols, GDPR consent failures, repeated URL changes at FRED and OANDA. Genuine additions are rare and small — a ClOp() return function, an intraday endpoint, better ambiguous-column detection.
The pattern is a package whose cadence is set by other people's API changes rather than its own roadmap. Releases arrive when a data source breaks, and the changelog reads as a list of reports from users who hit the failure first. The FRED API key requirement in the latest release is the same story again — a free source adding registration, and quantmod adding an argument and a nudge to comply. Deprecation work on as.zoo.data.frame has been running since at least 0.4.27 without completing.
Nothing in these entries points to a planned feature; the next release will most likely be triggered by whichever vendor endpoint changes first.
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 qtl2 or quantmod.
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
A board game graphics package runs one of the most disciplined deprecation cycles in R.
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.
A scientific-text analysis package moved from counting citations to classifying argument structure.
The teaching arm of an R reliability suite keeps pace with whatever its analysis siblings ship.
See all qtl2 alternatives → · See all quantmod alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. qtl2 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. qtl2 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 Analytics products to evaluate alongside.
Top qtl2 alternatives in Analytics are ranked by recent ship velocity. Browse the "qtl2 alternatives" section above for the current picks, or visit /alternatives/qtl2 for the full list with editorial commentary on each.
Top quantmod alternatives in Analytics are ranked by recent ship velocity. Browse the "quantmod alternatives" section above for the current picks, or visit /alternatives/quantmod for the full list with editorial commentary on each.