← Back to home
Comparison · Infra & APIs

nuggets vs selection.index

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

nuggets vs selection.index: at a glance

Featurenuggetsselection.index
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themespattern-mining, association-rules, performance, r-packageplant-breeding, selection-index, genomic-selection, rcpp
Last editorial update16h ago1d ago
WebsiteVisit →Visit →

What is nuggets?

A pattern-mining package that keeps making its own search cheaper rather than wider.

nuggets is an R package for searching data for conditional patterns - association rules, contrast patterns, correlations - through its dig*() family. The 2.2.x line has settled into a steady rhythm of making that search faster and more inspectable rather than adding new pattern types. 2.2.3 adds permute(), improves axiom-based filtering in the excluded argument, and attaches a search_stats attribute to every dig*() result, so the cost of a search is now reported alongside its output.

Read the full nuggets trajectory →

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 →

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

N
nuggets
INFRA · APIS
5.0

A pattern-mining package that keeps making its own search cheaper rather than wider.

◆ Current state

nuggets is an R package for searching data for conditional patterns - association rules, contrast patterns, correlations - through its dig*() family. The 2.2.x line has settled into a steady rhythm of making that search faster and more inspectable rather than adding new pattern types. 2.2.3 adds permute(), improves axiom-based filtering in the excluded argument, and attaches a search_stats attribute to every dig*() result, so the cost of a search is now reported alongside its output.

◆ Where it's heading

The arc since 2.1.0 runs toward a leaner, faster core. Dependencies went first - Shiny moved to Suggests, BH and RcppThread dropped - then the search itself: 2.2.2 brought a sparse bit chain, and 2.2.3 adds condition-prefix handling and caching of conjunction supports. New user-facing surface arrives in small, single-function increments (dig_ancestors(), cluster_associations(), now permute()) rather than in themed releases. The search_stats attribute is the first move toward letting users see why a search was expensive rather than only how long it took.

◆ Prediction

Expect the next release to continue in the same shape - another caching or pruning refinement to the dig*() core plus one or two helper functions. The search_stats attribute is the kind of instrumentation that usually precedes tuning controls, so surfacing knobs for the new prefix and support caches is the plausible follow-up.

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.

Alternatives to nuggets and selection.index

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 nuggets or selection.index.

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

Recent activity from nuggets and selection.index

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

  1. 1d agonuggetspermute() added; dig*() caches conjunction supports, reports search_stats
  2. 1mo agonuggetsSparse bit chain speeds dig(); explore() gains clustering
  3. 2mo agonuggetspartition() gains .subsets; geom_diamond() layout improved
  4. 5mo agonuggetsexplore() covers contrasts and correlations; dig_ancestors() added
  5. 5mo agoselection.indexCI expanded to 17 runners after the 2.0.0 rewrite
  6. 5mo agoselection.indexGenomic, marker and multi-stage selection indices on an Rcpp core
  7. 6mo agonuggetsCritical explore() bug fixed; is_logicalish() added
  8. 6mo agonuggetsShiny deps moved to Suggests; BH and RcppThread dropped
  9. 6mo agoselection.indexUnspecified general performance improvements
  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 nuggets and selection.index?

They serve adjacent needs but don't currently overlap on shipped themes. nuggets is currently shipping more aggressively (velocity 5.0 vs 0.0), 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.

Is nuggets better than selection.index?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nuggets is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to nuggets?

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

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.