← Back to home
Comparison · Infra & APIs

selection.index vs statsExpressions

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

selection.index vs statsExpressions: at a glance

Featureselection.indexstatsExpressions
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesplant-breeding, selection-index, genomic-selection, rcppstatistics, easystats, ggstatsplot, backend
Last editorial update1h ago1h 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 statsExpressions?

A statistics backend whose release history is mostly other people's weather

statsExpressions produces the tidy dataframes and plotmath expressions that ggstatsplot prints onto plots, and that position defines its changelog. Six of its ten most recent versions exist to absorb API changes in easystats, dplyr or purrr. Version 2.0.0 is the exception, cut to accompany ggstatsplot's own 1.0.0 and carrying pairwise Fisher's exact post hocs for contingency tables.

Read the full statsExpressions trajectory →

selection.index vs statsExpressions: 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.

S
statsExpressions
INFRA · APIS
0.0

A statistics backend whose release history is mostly other people's weather

◆ Current state

statsExpressions produces the tidy dataframes and plotmath expressions that ggstatsplot prints onto plots, and that position defines its changelog. Six of its ten most recent versions exist to absorb API changes in easystats, dplyr or purrr. Version 2.0.0 is the exception, cut to accompany ggstatsplot's own 1.0.0 and carrying pairwise Fisher's exact post hocs for contingency tables.

◆ Where it's heading

This is a component settling into place beneath a larger package rather than a product with its own roadmap. New statistical content arrives rarely and narrowly — an exact-p toggle, one post-hoc function — while the recurring work is keeping expressions correct as the easystats stack shifts underneath. The one bug class it keeps returning to is rendering: p-values of exactly zero, decimal commas that plotmath parses as list separators.

◆ Prediction

Coupled this tightly, the next release is most likely another compatibility pass timed to an easystats or ggstatsplot version rather than new tests. Nothing in these entries signals an independent feature direction.

Alternatives to selection.index and statsExpressions

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 statsExpressions.

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

Recent activity from selection.index and statsExpressions

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

  1. 3mo agostatsExpressionsPairwise Fisher's post hocs for contingency tables
  2. 4mo agostatsExpressionsInternal maintenance only, no user-facing changes
  3. 5mo agoselection.indexCI expanded to 17 runners after the 2.0.0 rewrite
  4. 5mo agoselection.indexGenomic, marker and multi-stage selection indices on an Rcpp core
  5. 6mo agostatsExpressionsAdapts to dplyr 1.2.0 and purrr 1.2.1
  6. 6mo agostatsExpressionsAdapts to changes in the easystats packages
  7. 6mo agoselection.indexUnspecified general performance improvements
  8. 1y agostatsExpressionsFixes p-value rendering when p is exactly zero
  9. 1y agostatsExpressionscentrality_description() follows the new easystats API
  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 statsExpressions?

They serve adjacent needs but don't currently overlap on shipped themes. selection.index and statsExpressions 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 statsExpressions?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. selection.index and statsExpressions 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 statsExpressions?

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