← Back to home
Comparison · Infra & APIs

netdiffuseR vs selection.index

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

Shared themes:simulation

netdiffuseR vs selection.index: at a glance

FeaturenetdiffuseRselection.index
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesnetwork-analysis, diffusion, contagion, multi-adoptionplant-breeding, selection-index, genomic-selection, rcpp
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is netdiffuseR?

Network diffusion analysis returns from a seven-year gap able to track several behaviours at once

netdiffuseR analyses how behaviours spread through networks — exposure, adoption timing, thresholds, and simulation of diffusion processes. Its feed has a hole: four releases from 2024 to 2026 sit directly on top of three from 2016 and 2017, with the intervening versions absent. The current line is being maintained by a widening group of contributors and, at 1.24.0, was explicitly brought back to CRAN.

Read the full netdiffuseR 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 →

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

N
netdiffuseR
INFRA · APIS
0.0

Network diffusion analysis returns from a seven-year gap able to track several behaviours at once

◆ Current state

netdiffuseR analyses how behaviours spread through networks — exposure, adoption timing, thresholds, and simulation of diffusion processes. Its feed has a hole: four releases from 2024 to 2026 sit directly on top of three from 2016 and 2017, with the intervening versions absent. The current line is being maintained by a widening group of contributors and, at 1.24.0, was explicitly brought back to CRAN.

◆ Where it's heading

The recent releases read as institutional rather than exploratory: CI fixes, CRAN-readiness passes, contributed PRs from new names, bundled teaching datasets. The one structural move is 1.23.0, named for multi-adoption, which alongside a refactor of the exposure and rdiffnet internals adds a function for splitting behaviours apart — the package handling several diffusing behaviours where its object model previously carried one.

◆ Prediction

With CRAN presence restored and a dataset for a teaching game added in the newest release, the near-term direction looks like classroom and workshop use rather than new method surface. Whether multi-adoption gets its own analysis functions, rather than a splitter, is the open question these notes do not answer.

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

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

Recent activity from netdiffuseR and selection.index

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

  1. 4mo agonetdiffuseREpidemic game dataset added ahead of a CRAN submission
  2. 5mo agoselection.indexCI expanded to 17 runners after the 2.0.0 rewrite
  3. 5mo agoselection.indexGenomic, marker and multi-stage selection indices on an Rcpp core
  4. 6mo agoselection.indexUnspecified general performance improvements
  5. 8mo agonetdiffuseRBack on CRAN with an adoption-timing diagnostic
  6. 1y agonetdiffuseRMulti-adoption: splitting several behaviours out of one network
  7. 1y agonetdiffuseRCRAN v1.22.6
  8. 2y agoselection.indexMean performance for randomised block designs
  9. 3y agoselection.indexsel.index() and sel.score.rank() removed for comb.indices()
  10. 4y agoselection.indexGenetic advance calculation added
  11. 8y agonetdiffuseRigraph-standard plotting and repeated diffusion simulations
  12. 9y agonetdiffuseRBootstrapping, mentor matching, and Bass model fitting

Frequently asked questions

What is the difference between netdiffuseR and selection.index?

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

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

Top netdiffuseR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "netdiffuseR alternatives" section above for the current picks, or visit /alternatives/netdiffuser 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.