pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
Comparison · Infra & APIs
selection.index vs usmap
A side-by-side editorial comparison of selection.index and usmap — release velocity, themes, recent moves, and the top alternatives to consider.
selection.index vs usmap: at a glance
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.
What is usmap?
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.
selection.index vs usmap: editorial side-by-side
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.
usmap
0.0INFRA · APIS
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
◆ Current state
usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.
◆ Where it's heading
The package has separated what it draws from how it draws, and that separation is what makes the recent releases possible: annual map vintages ship in usmapdata without touching usmap, and Puerto Rico could be backfilled into every existing year at once. The remaining work is coverage and defaults rather than architecture, and the Puerto Rico exclusion default is already governed by an environment variable rather than a code change.
◆ Prediction
Expect the annual map vintage to keep arriving through usmapdata, with usmap itself changing only where a new territory or a projection default needs handling.
Alternatives to selection.index and usmap
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 usmap.
ggalign
Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.
prioritizr
Conservation planning absorbs the literature's target-setting rules as code.
jSDM
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
rsofun
An ecosystem model starts tracking carbon isotopes and land-use change.
trackeR
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
See all selection.index alternatives → · See all usmap alternatives →
Recent activity from selection.index and usmap
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 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
- 11mo agousmapPuerto Rico added across every usmap function and map year
- 1y agousmapdata_year parameter threaded through the plotting functions
- 2y agousmapPopulation and poverty data refreshed; ggplot2 3.5 legend fix
- 2y agousmapMap data becomes sf; usmap_transform() returns geometry ⚡
- 2y agousmapDocumentation links updated
- 2y agousmapMap data extracted to a companion usmapdata 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 selection.index and usmap?
They serve adjacent needs but don't currently overlap on shipped themes. selection.index and usmap 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 usmap?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. selection.index and usmap 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 usmap?
Top usmap alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "usmap alternatives" section above for the current picks, or visit /alternatives/usmap for the full list with editorial commentary on each.