Buildkite
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
Comparison · Infra & APIs
admtools vs onemap
A side-by-side editorial comparison of admtools and onemap — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:interoperability
admtools vs onemap: at a glance
What is admtools?
The age-depth engine under a small stratigraphy stack, growing one adapter at a time
admtools estimates and manipulates age-depth models, with the generics time_to_strat() and strat_to_time() as the transformation layer a small stratigraphy stack is built on. Since 0.1.0 it has accumulated the S3 vocabulary that work needs — sac for sediment accumulation curves, timelist and stratlist for time- and height-associated data — and then adapters outward: pre_paleoTS for StratPal and paleoTS in 0.4.0, FossilSim taxonomy and fossils objects in 0.5.0, and age-to-time transformation for FossilSim in 0.6.0. Version 0.5.0 also added what it calls basic functionality for depth-depth models alongside the age-depth ones.
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.
admtools vs onemap: editorial side-by-side
admtools
0.0INFRA · APIS
The age-depth engine under a small stratigraphy stack, growing one adapter at a time
◆ Current state
admtools estimates and manipulates age-depth models, with the generics time_to_strat() and strat_to_time() as the transformation layer a small stratigraphy stack is built on. Since 0.1.0 it has accumulated the S3 vocabulary that work needs — sac for sediment accumulation curves, timelist and stratlist for time- and height-associated data — and then adapters outward: pre_paleoTS for StratPal and paleoTS in 0.4.0, FossilSim taxonomy and fossils objects in 0.5.0, and age-to-time transformation for FossilSim in 0.6.0. Version 0.5.0 also added what it calls basic functionality for depth-depth models alongside the age-depth ones.
◆ Where it's heading
This package moves in step with StratPal, from the same group: admtools 0.4.0 shipped its pre_paleoTS transformations fifty-seven minutes before StratPal released the class itself, and both took on FossilSim within a month of each other in spring 2025. The pattern is consistent — establish generics, define classes, then connect to whatever package the field already uses. The depth-depth work is the one thread pointing inward rather than outward, and it is still described as basic.
◆ Prediction
Depth-depth models are the obvious thing to finish, since they mirror age-depth machinery the package already has; expect any release here to be shadowed by a matching change in StratPal within weeks either 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.
Alternatives to admtools and onemap
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 admtools or onemap.
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
See all admtools alternatives → · See all onemap alternatives →
Recent activity from admtools and onemap
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agoadmtoolsAge-to-time transformation for FossilSim integration
- 1y agoadmtoolsDepth-depth models and FossilSim object transformations
- 1y agoonemapMAPpoly announcement added to README and load message
- 1y agoadmtoolspre_paleoTS transformations and age-depth model anchoring
- 1y agoadmtoolsMore sedimentation-rate generator options and sac utilities
- 2y agoadmtoolstimelist and stratlist classes; unified transformation syntax
- 2y agoadmtoolsMultiple tie points, sedimentation-rate estimation and the sac class
- 3y agoonemapExports to VIEWpoly and QTLpoly; marker ordering and map summaries
- 3y agoonemapTwo-point marker filtering and memory reduction
- 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 admtools and onemap?
Both compete on the same themes — interoperability — within Infra & APIs. admtools and onemap 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 admtools better than onemap?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. admtools and onemap 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 admtools?
Top admtools alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "admtools alternatives" section above for the current picks, or visit /alternatives/admtools for the full list with editorial commentary on each.
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.