mice
mice can finally predict, not just estimate, from multiply imputed data.
Comparison · Infra & APIs
gofedf vs selection.index
A side-by-side editorial comparison of gofedf and selection.index — release velocity, themes, recent moves, and the top alternatives to consider.
gofedf vs selection.index: at a glance
What is gofedf?
A two-test goodness-of-fit package opens itself up to any weight function
gofedf runs goodness-of-fit tests built on the empirical distribution function. Its three releases trace a short, clean arc: existence in 2023, then p-values computed from an analytical solution of the integral equation in 2024, then in 2026 a user-supplied weight function that replaces the fixed menu. Cramer-von Mises and Anderson-Darling are now two points in a family rather than the two options.
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.
gofedf vs selection.index: editorial side-by-side
gofedf
0.0INFRA · APIS
A two-test goodness-of-fit package opens itself up to any weight function
◆ Current state
gofedf runs goodness-of-fit tests built on the empirical distribution function. Its three releases trace a short, clean arc: existence in 2023, then p-values computed from an analytical solution of the integral equation in 2024, then in 2026 a user-supplied weight function that replaces the fixed menu. Cramer-von Mises and Anderson-Darling are now two points in a family rather than the two options.
◆ Where it's heading
The package is generalising rather than accumulating. Each release removed a hard-coded decision: first how eigenvalues are computed, offering both the analytical route and a matrix approximation; then which weight function defines the statistic at all. The maintainer's own framing in 1.1.0 is a contrast against what earlier versions would not let you do, which is the shape of a package aiming to become a framework.
◆ Prediction
An arbitrary weight function is the extensibility point that matters for EDF tests; what it lacks is calibration guidance, since Type I error behaviour was the argued benefit of the analytical eigenvalue route. Documented recommendations or diagnostics for user-chosen weights are the natural follow-up, though the entries do not announce one.
selection.index
0.0INFRA · APIS
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 gofedf 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 gofedf or selection.index.
PINstimation
A market-microstructure toolkit that keeps adding estimators as the papers land.
nzilbb.vowels
A vowel-analysis package trimming dependencies after an email address got it archived.
emuR
The R half of the EMU speech database system, fixing what was quietly broken.
BAS
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all gofedf alternatives → · See all selection.index alternatives →
Recent activity from gofedf and selection.index
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agogofedfUser-supplied weight functions for Cramer-von Mises tests ⚡
- 5mo agoselection.indexCI expanded to 17 runners after the 2.0.0 rewrite
- 5mo agoselection.indexGenomic, marker and multi-stage selection indices on an Rcpp core ⚡
- 6mo agoselection.indexUnspecified general performance improvements
- 1y agogofedfp-values from an analytical eigenvalue solution
- 2y agogofedfFirst release of the gofedf package ⚡
- 2y agoselection.indexMean performance for randomised block designs
- 3y agoselection.indexsel.index() and sel.score.rank() removed for comb.indices()
- 4y agoselection.indexGenetic advance calculation added
Frequently asked questions
What is the difference between gofedf and selection.index?
They serve adjacent needs but don't currently overlap on shipped themes. gofedf 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 gofedf better than selection.index?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gofedf 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 gofedf?
Top gofedf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gofedf alternatives" section above for the current picks, or visit /alternatives/gofedf 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.