fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
A side-by-side editorial comparison of sccore and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.
Shared plumbing for the Kharchenko single-cell stack, updated once a year
sccore is the utility layer under the Kharchenko lab's single-cell packages — embedding plots, dot plots, parallel apply helpers and distance metrics that the downstream tools depend on rather than a tool researchers drive directly. The recent releases fix the Jensen-Shannon distance computation between matrix columns and add optional OpenMP support to the RcppArmadillo build. Cadence is roughly one CRAN release a year.
soilDBdata exists so soilDB's tests can run without a NASIS connection.
soilDBdata is a data-only package supplying NASIS and gSSURGO sample datasets as .sqlite assets, installed separately by soilDB's GitHub Actions so unit tests that would otherwise need database access can run. It began as a proof of concept carrying MT663 pedon and component tables used in soil survey coursework, and its most recent release adds a Marshall Islands FY26 gSSURGO dataset. Releases are infrequent and driven by what the parent package needs to test.
sccore is the utility layer under the Kharchenko lab's single-cell packages — embedding plots, dot plots, parallel apply helpers and distance metrics that the downstream tools depend on rather than a tool researchers drive directly. The recent releases fix the Jensen-Shannon distance computation between matrix columns and add optional OpenMP support to the RcppArmadillo build. Cadence is roughly one CRAN release a year.
Work splits cleanly into two streams: keeping the compiled build acceptable to CRAN as its Makevars policy shifts, and small correctness or interoperability fixes to the plotting and distance helpers. The interoperability thread is the one with direction — embeddingPlot() learning to read Seurat objects in 1.0.6 points at meeting users in the dominant single-cell framework rather than requiring the lab's own object types.
Expect the next release to be driven by a CRAN toolchain requirement or a downstream package's needs, with any user-facing change likely another interoperability or plotting fix rather than new capability.
soilDBdata is a data-only package supplying NASIS and gSSURGO sample datasets as .sqlite assets, installed separately by soilDB's GitHub Actions so unit tests that would otherwise need database access can run. It began as a proof of concept carrying MT663 pedon and component tables used in soil survey coursework, and its most recent release adds a Marshall Islands FY26 gSSURGO dataset. Releases are infrequent and driven by what the parent package needs to test.
Development follows soilDB rather than leading it: assets get bumped when a soilDB version changes, and purpose lists are updated when soilDB adds a table. The one release that changed what testing is possible was v0.1.1, which added selected-set _View_1 tables alongside whole tables so both SS=TRUE and SS=FALSE code paths could be exercised. Four-year gaps between releases are normal here and do not indicate abandonment — a fixture package only needs to move when the fixtures go stale.
The recent addition is a new geography rather than a new table structure, so further releases most likely continue broadening dataset coverage as soilDB gains regions to test against.
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 sccore or soilDBdata.
Pattern fills for ggplot2, hardened against the ways users write sizes
gcube's recent releases are all packaging metadata, not simulation code
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats keeps widening what a coefficient or Likert plot can be
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
State-space data simulation for R, filled in one function at a time
See all sccore alternatives → · See all soilDBdata alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. sccore and soilDBdata 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. sccore and soilDBdata 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 sccore alternatives in Analytics are ranked by recent ship velocity. Browse the "sccore alternatives" section above for the current picks, or visit /alternatives/sccore for the full list with editorial commentary on each.
Top soilDBdata alternatives in Analytics are ranked by recent ship velocity. Browse the "soilDBdata alternatives" section above for the current picks, or visit /alternatives/soildbdata for the full list with editorial commentary on each.