Buildkite
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
Comparison · Infra & APIs
onemap vs vimp
A side-by-side editorial comparison of onemap and vimp — release velocity, themes, recent moves, and the top alternatives to consider.
onemap vs vimp: at a glance
What is onemap?
A genetic-mapping mainstay that now points new users toward MAPpoly at load time
OneMap constructs genetic linkage maps for experimental crosses, and its 3.x line turned it into a hub in a wider mapping toolchain: export functions for VIEWpoly and QTLpoly, summary and interactive ordering functions adapted from MAPpoly, and retention of reference and alternative allele information from imported VCFs. The most recent release, 3.2.0 in January 2025, adds an announcement about MAPpoly to the README and the package load message, fixes a subscript-out-of-bounds warning in rf_2pts and refreshes vignettes and tests.
What is vimp?
Algorithm-agnostic variable importance, settled since 2022 and now answering CRAN checks
vimp performs inference on variable importance measures that do not depend on the fitting algorithm, using sample-splitting so tests stay valid under the zero-importance null. The statistical design settled in 2022: predictiveness measures gained their own S3 class, point estimation was decoupled from inference through the final_point_estimate argument, and method and family moved to the outer functions so binary outcomes work. The two 2025 releases are a CRAN documentation fix and an edge-case correction for cutoff-based measures when every prediction is the same value.
onemap vs vimp: editorial side-by-side
onemap
0.0INFRA · APIS
A genetic-mapping mainstay that now points new users toward MAPpoly at load time
◆ Current state
OneMap constructs genetic linkage maps for experimental crosses, and its 3.x line turned it into a hub in a wider mapping toolchain: export functions for VIEWpoly and QTLpoly, summary and interactive ordering functions adapted from MAPpoly, and retention of reference and alternative allele information from imported VCFs. The most recent release, 3.2.0 in January 2025, adds an announcement about MAPpoly to the README and the package load message, fixes a subscript-out-of-bounds warning in rf_2pts and refreshes vignettes and tests.
◆ Where it's heading
Versions 3.0.0 and 3.1.0 were driven by a benchmarking preprint on genotyping-by-sequencing best practice, and their content follows directly: marker filtering from two-point estimates, memory reduction after filtering, and optimisation of find_bins and map_avoid_unlinked. What has happened since is signposting rather than capability — a package that spent two releases integrating with MAPpoly now tells users about it every time it loads. The pre-3.0 tags are backfilled, with versions 2.3 through 2.7 sharing a single August 2021 timestamp, so their order carries no information.
◆ Prediction
The load-message announcement suggests attention is flowing toward the MAPpoly side of the toolchain; expect maintenance and compatibility releases here rather than new mapping algorithms.
vimp
0.0INFRA · APIS
Algorithm-agnostic variable importance, settled since 2022 and now answering CRAN checks
◆ Current state
vimp performs inference on variable importance measures that do not depend on the fitting algorithm, using sample-splitting so tests stay valid under the zero-importance null. The statistical design settled in 2022: predictiveness measures gained their own S3 class, point estimation was decoupled from inference through the final_point_estimate argument, and method and family moved to the outer functions so binary outcomes work. The two 2025 releases are a CRAN documentation fix and an edge-case correction for cutoff-based measures when every prediction is the same value.
◆ Where it's heading
Substantive development ended in 2022, followed by one narrow addition — a cluster bootstrap for correlated data in 2023 — and two housekeeping releases. What remains visible are careful decisions about the boundary between estimation and inference, including the warning that a Wald interval will not be centred on the point estimate when the full-data or averaged option is used. The maintainer is keeping the package correct and installable rather than extending it.
◆ Prediction
Expect maintenance releases keyed to CRAN check changes; new predictiveness measures are the plausible extension, since the S3 class added in 2.3.0 was introduced specifically to make adding them simpler.
Alternatives to onemap and vimp
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 onemap or vimp.
Cursor
Cursor's agents stop waiting to be asked - they subscribe, and they hold a goal until it's done.
incident.io
Nexus does the diagnosis; the agent is now reaching into the status page too.
Warp
Warp turned its quarter of software-factory essays into infrastructure you can buy.
Okta
Okta's developer blog is a Cross App Access campaign, now diluted by advocacy-team storytelling.
tealeaves
A leaf-temperature model that finished its job in 2020 and has stayed finished
Recent activity from onemap and vimp
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11mo agovimpUpdate PPV, NPV, Sensitivity, Specificity
- 1y agovimpFix documentation NOTEs
- 1y agoonemapMAPpoly announcement added to README and load message
- 2y agovimpAdd cluster bootstrap
- 3y agoonemapExports to VIEWpoly and QTLpoly; marker ordering and map summaries
- 3y agovimpEnhanced VIM point estimation
- 3y agoonemapTwo-point marker filtering and memory reduction
- 3y agovimpS3 class for predictiveness measures
- 4y agovimpSpecify 'method' and 'family' in outer functions
- 4y agoonemapPSOCK and FORK parallelization choice; vcfR as an import
- 5y agoonemaphmm=FALSE option for ordering algorithms
- 5y agoonemapMDSMap dependency removed
Frequently asked questions
What is the difference between onemap and vimp?
They serve adjacent needs but don't currently overlap on shipped themes. onemap and vimp 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 onemap better than vimp?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. onemap and vimp 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 onemap?
Top onemap alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "onemap alternatives" section above for the current picks, or visit /alternatives/onemap for the full list with editorial commentary on each.
What are the best alternatives to vimp?
Top vimp alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "vimp alternatives" section above for the current picks, or visit /alternatives/vimp for the full list with editorial commentary on each.