cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
A side-by-side editorial comparison of ddpcr and fmtr — release velocity, themes, recent moves, and the top alternatives to consider.
A decade-old droplet PCR analysis package woken up for one compatibility release
ddpcr reads droplet digital PCR data exported from Bio-Rad's QuantaSoft, classifies droplets and ships a Shiny interface over the analysis. It has been on CRAN since 2016 alongside an F1000Research paper. The last ten years of releases are almost entirely about keeping pace with QuantaSoft export formats and with churn in its own R dependencies.
Rebuilding SAS's formatting layer in R, one format specification at a time
fmtr applies formats to R data the way SAS applies them: named format catalogues, format lists, and an fapply() that maps a specification onto a vector. It is part of a family of packages that reconstruct SAS reporting idioms in R, and it shares infrastructure with them — labels.data.frame() was moved out to the common package, which fmtr now depends on. The recent releases have been closing specific gaps against SAS's own format vocabulary.
ddpcr reads droplet digital PCR data exported from Bio-Rad's QuantaSoft, classifies droplets and ships a Shiny interface over the analysis. It has been on CRAN since 2016 alongside an F1000Research paper. The last ten years of releases are almost entirely about keeping pace with QuantaSoft export formats and with churn in its own R dependencies.
This is a maintained-not-developed package, and the release history shows it plainly: a burst of real work through 2016 and 2017, then long silences broken by releases whose stated purpose is staying on CRAN. The 2026 release fits the same shape but does more than the 2023 pair did, adding support for a QuantaSoft variant and finally retiring dplyr code written against a tidy evaluation style that has been outdated for years.
Nothing in the entries points to new analysis capability; the pattern suggests the package surfaces again only when a QuantaSoft export change or a dependency deprecation forces it.
fmtr applies formats to R data the way SAS applies them: named format catalogues, format lists, and an fapply() that maps a specification onto a vector. It is part of a family of packages that reconstruct SAS reporting idioms in R, and it shares infrastructure with them — labels.data.frame() was moved out to the common package, which fmtr now depends on. The recent releases have been closing specific gaps against SAS's own format vocabulary.
The direction is parity, pursued in small increments. Quarter format codes were added because base R has none; the SAS best. format was reimplemented, then hardened against the variations people actually write; statistical summary helpers like fmt_mean_sd() and fmt_mean_stderr() cover the cell contents clinical tables need. The structural work is largely behind it, including the breaking 2022 move that handed labelling to a sibling package, so what remains is vocabulary coverage.
The pattern of adding a SAS format, then a release to handle its variants, suggests the next releases continue filling in format codes and summary helpers rather than changing how formats are applied.
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 ddpcr or fmtr.
A choice-based IRT model published once in 2019 and kept compiling ever since
The R engine behind MetaboAnalyst closes the gap from raw spectra to biological interpretation
Standardised coefficients for models where standardising everything is wrong — but the feed only links out
Stream-network spatial models learning to run on data that no longer fits in memory
Bioconductor's installer, frozen at 1.30.x and tuned almost entirely through environment variables
Decision curve analysis, settled since 2022 and now moving only when its neighbours do
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ddpcr and fmtr 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ddpcr and fmtr 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.
Top ddpcr alternatives in Analytics are ranked by recent ship velocity. Browse the "ddpcr alternatives" section above for the current picks, or visit /alternatives/ddpcr for the full list with editorial commentary on each.
Top fmtr alternatives in Analytics are ranked by recent ship velocity. Browse the "fmtr alternatives" section above for the current picks, or visit /alternatives/fmtr for the full list with editorial commentary on each.