← Back to home
Comparison · Infra & APIs

selection.index vs tidyplots

A side-by-side editorial comparison of selection.index and tidyplots — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:breaking-changes

selection.index vs tidyplots: at a glance

Featureselection.indextidyplots
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesplant-breeding, selection-index, genomic-selection, rcppdata-visualization, r-package, ggplot2, scientific-publishing
Last editorial update1h ago54m ago
WebsiteVisit →Visit →

What is selection.index?

A dormant plant-breeding package returns as a genomic selection index suite

selection.index computes selection indices for plant breeding — weighting several traits into one number breeders can rank on. After two years of silence it shipped 2.0.0 in March 2026, and the package is barely recognisable: snake_case throughout, an Rcpp and RcppEigen computational core, and index families for genomic data, marker data, multi-stage trials and constrained genetic gain sitting beside the original phenotypic ones.

Read the full selection.index trajectory →

What is tidyplots?

tidyplots keeps rebuilding its own foundations rather than layering around them.

tidyplots wraps ggplot2 in a pipe-driven API aimed at publication-ready scientific figures, trading grammar-of-graphics flexibility for a shorter path to a finished plot. It is at 0.4.0 after two years of frequent releases, and almost every one carries a breaking change — the most recent moved multi-panel layout off patchwork and onto ggplot2's own faceting. Statistical annotation, colour schemes and size control have each been reworked at least once.

Read the full tidyplots trajectory →

selection.index vs tidyplots: editorial side-by-side

S
selection.index
INFRA · APIS
0.0

A dormant plant-breeding package returns as a genomic selection index suite

◆ Current state

selection.index computes selection indices for plant breeding — weighting several traits into one number breeders can rank on. After two years of silence it shipped 2.0.0 in March 2026, and the package is barely recognisable: snake_case throughout, an Rcpp and RcppEigen computational core, and index families for genomic data, marker data, multi-stage trials and constrained genetic gain sitting beside the original phenotypic ones.

◆ Where it's heading

The first version series added one function at a time — combinatorial indices, then genetic advance, then mean performance under randomised block designs — against a fixed phenotypic framing. Version 2.0.0 abandons that framing rather than extending it. Genomic and marker information become inputs the package understands, multi-cycle simulation becomes a built-in toolset, and the old combinatorial entry points are replaced by a named lpsi(). The 2.0.1 follow-up is entirely CI and numerical-stability work, which reads like a maintainer bracing a much larger surface.

◆ Prediction

A seventeen-runner CI matrix mirroring every CRAN check flavour, added days after 2.0.0, says the immediate concern is keeping a compiled multi-family package green rather than adding to it. Expect stabilisation releases before anything new.

T
tidyplots
INFRA · APIS
0.0

tidyplots keeps rebuilding its own foundations rather than layering around them.

◆ Current state

tidyplots wraps ggplot2 in a pipe-driven API aimed at publication-ready scientific figures, trading grammar-of-graphics flexibility for a shorter path to a finished plot. It is at 0.4.0 after two years of frequent releases, and almost every one carries a breaking change — the most recent moved multi-panel layout off patchwork and onto ggplot2's own faceting. Statistical annotation, colour schemes and size control have each been reworked at least once.

◆ Where it's heading

The package is converging on ggplot2 rather than abstracting away from it: split_plot() now uses facet_wrap and facet_grid, as_tidyplot() was hard-deprecated on the grounds that converting a ggplot was never a good idea, and releases are timed against upstream ggplot2 versions. The other constant is the statistics surface, which has grown from basic error bars to paired and selected comparisons. Breaking changes are announced plainly and frequently, consistent with a package using 0.x to fix its shape before committing.

◆ Prediction

The patchwork removal is described as something that will eventually break dependent code, so the near-term work is likely completing that migration and settling the split_plot() parameters introduced alongside it. A 1.0 would signal the breaking-change cadence is ending, and nothing here indicates that yet.

Alternatives to selection.index and tidyplots

Other Infra & APIs 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 selection.index or tidyplots.

See all selection.index alternatives → · See all tidyplots alternatives →

Recent activity from selection.index and tidyplots

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5mo agoselection.indexCI expanded to 17 runners after the 2.0.0 rewrite
  2. 5mo agoselection.indexGenomic, marker and multi-stage selection indices on an Rcpp core
  3. 6mo agoselection.indexUnspecified general performance improvements
  4. 7mo agotidyplotstidyplots 0.4.0
  5. 1y agotidyplotstidyplots 0.3.1
  6. 1y agotidyplotstidyplots 0.2.2
  7. 1y agotidyplotstidyplots 0.2.1
  8. 1y agotidyplotstidyplots 0.2.0
  9. 1y agotidyplotstidyplots 0.1.2
  10. 2y agoselection.indexMean performance for randomised block designs
  11. 3y agoselection.indexsel.index() and sel.score.rank() removed for comb.indices()
  12. 4y agoselection.indexGenetic advance calculation added

Frequently asked questions

What is the difference between selection.index and tidyplots?

Both compete on the same themes — breaking-changes — within Infra & APIs. selection.index and tidyplots 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 selection.index better than tidyplots?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. selection.index and tidyplots 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to selection.index?

Top selection.index alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "selection.index alternatives" section above for the current picks, or visit /alternatives/selection-index for the full list with editorial commentary on each.

What are the best alternatives to tidyplots?

Top tidyplots alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "tidyplots alternatives" section above for the current picks, or visit /alternatives/tidyplots for the full list with editorial commentary on each.