PurpleAir
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
A side-by-side editorial comparison of qtl2 and scimesh — 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.
A C++ mesh renderer grinding through CRAN's gate, one policy fix at a time
scimesh is a C++ scientific mesh rendering library with an R binding, released in tight bursts by the dfsp-spirit neuroimaging group. The last month is dominated by CRAN admission work: stripped debug symbols, assert removal in vendored third-party code, vignette index fixes. Around that compliance grind sit genuine additions — an rgl-to-scimesh auto-conversion path, a camera_orbit helper for video, contrast as a render option.
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.
scimesh is a C++ scientific mesh rendering library with an R binding, released in tight bursts by the dfsp-spirit neuroimaging group. The last month is dominated by CRAN admission work: stripped debug symbols, assert removal in vendored third-party code, vignette index fixes. Around that compliance grind sit genuine additions — an rgl-to-scimesh auto-conversion path, a camera_orbit helper for video, contrast as a render option.
The tag stream is non-monotonic — 0.2.5, 0.2.3 and 0.2.6 land within 40 seconds of each other, and 0.2.8 precedes nothing — so version order here says nothing about what shipped when. Read as a whole, the arc is a C++ codebase being domesticated for R distribution: the rendering features are largely settled, and the effort has moved to making an >5MB-adjacent C++ package survive R CMD check --as-cran. The R vignette has been restructured twice in three weeks.
Expect continued CRAN-review round-trips at 0.3.x until acceptance, with feature work confined to the CLI renderer examples rather than the core library.
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 scimesh.
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 scimesh alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. scimesh is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. scimesh is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 scimesh alternatives in Analytics are ranked by recent ship velocity. Browse the "scimesh alternatives" section above for the current picks, or visit /alternatives/scimesh for the full list with editorial commentary on each.