← Back to home
Comparison · Infra & APIs

selection.index vs sits

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

selection.index vs sits: at a glance

Featureselection.indexsits
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesplant-breeding, selection-index, genomic-selection, rcppearth-observation, remote-sensing, machine-learning, r-package
Last editorial update2h 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 sits?

An R package for satellite time series just grew a Python API.

sits classifies satellite image time series — building data cubes from cloud archives, training deep learning models on them, and producing land-cover maps. The releases here are dense feature lists in a steady 1.5.x line, and two themes recur in every one: more source collections wired in, and more of the classification pipeline made parallel or chunked. Version 1.5.3 added pysits, a Python API onto the same engine.

Read the full sits trajectory →

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

An R package for satellite time series just grew a Python API.

◆ Current state

sits classifies satellite image time series — building data cubes from cloud archives, training deep learning models on them, and producing land-cover maps. The releases here are dense feature lists in a steady 1.5.x line, and two themes recur in every one: more source collections wired in, and more of the classification pipeline made parallel or chunked. Version 1.5.3 added pysits, a Python API onto the same engine.

◆ Where it's heading

The package is positioning itself as the interface layer to Earth observation archives rather than as an algorithm library. Each release absorbs another provider — Planetary Computer, Digital Earth Africa and Australia, CDSE, TERRASCOPE, Open Geo Hub, PLANET — so the differentiator is coverage and the uniform cube abstraction over it. The Python API extends the same logic to the language most of that community actually works in. Alongside, the work is increasingly about scale: chunk parallelisation, multicores sampling, GPU classification, WebGL rendering.

◆ Prediction

With collections still being added release over release, expect more providers and continued performance work on the classification and regularisation paths. The open question the entries do not answer is how far pysits tracks the R API, since it appears once and is not mentioned again in later releases.

Alternatives to selection.index and sits

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

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

Recent activity from selection.index and sits

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

  1. 5mo agoselection.indexCI expanded to 17 runners after the 2.0.0 rewrite
  2. 5mo agoselection.indexGenomic, marker and multi-stage selection indices on an Rcpp core
  3. 6mo agoselection.indexUnspecified general performance improvements
  4. 7mo agositsSNIC segmentation, imputation helpers and QGIS palette export
  5. 8mo agositsOne-line hotfix for a CRAN compiler requirement
  6. 11mo agositsHotfix: TAE embeddings, MPC token handling, texture divide-by-zero
  7. 11mo agositsA Python API arrives, alongside SAR texture measures
  8. 1y agositsExclusion masks, multiple tiling systems and faster segment classification
  9. 1y agositsFour more archives wired in, including Digital Earth Africa
  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 sits?

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

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

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