← Back to home
Comparison · Infra & APIs

selection.index vs ShortForm

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

selection.index vs ShortForm: at a glance

Featureselection.indexShortForm
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesplant-breeding, selection-index, genomic-selection, rcpppsychometrics, scale-construction, optimization-algorithms, lavaan
Last editorial update40m ago4h 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 ShortForm?

Automated scale shortening with lavaan, spending its releases repairing its own search algorithms.

ShortForm automates the creation of short-form psychometric scales by searching for well-fitting subsets of items, using ant colony optimization, simulated annealing and Tabu search over lavaan models. The recent releases are corrective: 0.5.7 fixed the ant colony algorithm failing to update its best model and the simulated annealing routine mis-specifying models containing factor relationships or outcome variables, and 0.5.8 fixed Tabu search under parallel workflows and with multidimensional models. Each release note carries an explicit roadmap listing refactoring for 0.6.0 and input standardisation for 0.7.0, neither of which has shipped.

Read the full ShortForm trajectory →

selection.index vs ShortForm: 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
ShortForm
INFRA · APIS
0.0

Automated scale shortening with lavaan, spending its releases repairing its own search algorithms.

◆ Current state

ShortForm automates the creation of short-form psychometric scales by searching for well-fitting subsets of items, using ant colony optimization, simulated annealing and Tabu search over lavaan models. The recent releases are corrective: 0.5.7 fixed the ant colony algorithm failing to update its best model and the simulated annealing routine mis-specifying models containing factor relationships or outcome variables, and 0.5.8 fixed Tabu search under parallel workflows and with multidimensional models. Each release note carries an explicit roadmap listing refactoring for 0.6.0 and input standardisation for 0.7.0, neither of which has shipped.

◆ Where it's heading

The defects being fixed are in the search itself rather than around it. An optimizer that does not correctly retain its best candidate, and a search that mis-specifies models after the first iteration, both produce plausible-looking short forms that are not the ones the method should have found, which is a harder class of problem to notice than a crash. Alongside that the package is shedding dependencies, with ggplot2, ggrepel and tidyr dropped from the plotting methods in 0.5.8. The stated intent to refactor the major functions and standardise their arguments suggests the maintainer regards the current interface as the obstacle to further work.

◆ Prediction

The roadmap repeated across these notes points to a 0.6.0 focused on refactoring the major functions, with argument and output standardisation deferred to 0.7.0. On the evidence of this window, more unit tests and further algorithm-level fixes are likelier to arrive first than either milestone.

Alternatives to selection.index and ShortForm

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

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

Recent activity from selection.index and ShortForm

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

  1. 3mo agoShortFormTabu search fixed for parallel and multidimensional models
  2. 3mo agoShortFormAnt colony search failed to retain its best model
  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 agoselection.indexUnspecified general performance improvements
  6. 1y agoShortFormlavaan model specification defaults made forgiving
  7. 2y agoShortFormCompatibility fixes for a new lavaan release
  8. 2y agoShortFormAdapted to changed lavaan error and warning messages
  9. 2y agoShortFormDefault specification tweaks and documentation fixes
  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 ShortForm?

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

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

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