← Back to home
Comparison · Infra & APIs

onemap vs PowerTOST

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

onemap vs PowerTOST: at a glance

FeatureonemapPowerTOST
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesgenetic-mapping, linkage-analysis, genotyping-by-sequencing, mappolybioequivalence, sample-size, regulatory, pharmacometrics
Last editorial update2h ago2h ago
WebsiteVisit →Visit →

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.

Read the full onemap trajectory →

What is PowerTOST?

A bioequivalence sample-size workhorse whose news is which regulator it now covers

PowerTOST computes power and sample size for bioequivalence and its changelog reads as a record of regulatory divergence more than statistical development. Version 1.5-3 added the Gulf Co-operation Council as a regulator setting; 1.5-4 and 1.5-6 stripped 'FDA' out of the narrow-therapeutic-index function names once China's CDE began requiring the same evaluation. The most recent release, 1.5-7, is a single fix to how nvec() splits a total sample size across sequences.

Read the full PowerTOST trajectory →

onemap vs PowerTOST: editorial side-by-side

O
onemap
INFRA · APIS
0.0

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.

P
PowerTOST
INFRA · APIS
0.0

A bioequivalence sample-size workhorse whose news is which regulator it now covers

◆ Current state

PowerTOST computes power and sample size for bioequivalence and its changelog reads as a record of regulatory divergence more than statistical development. Version 1.5-3 added the Gulf Co-operation Council as a regulator setting; 1.5-4 and 1.5-6 stripped 'FDA' out of the narrow-therapeutic-index function names once China's CDE began requiring the same evaluation. The most recent release, 1.5-7, is a single fix to how nvec() splits a total sample size across sequences.

◆ Where it's heading

The package is in long maintenance with a widening regulatory surface: the statistical methods are settled, and releases arrive when an agency publishes a framework that can be expressed as a settings variant of an existing method. Function naming has been deliberately decoupled from any single agency, with the deprecated FDA-suffixed aliases carried for years before removal. Cadence has slowed to roughly one release every eighteen months.

◆ Prediction

The next release is most likely another regulator setting or a small fix; on the deprecation notice already given, the power.NTIDFDA()-style aliases are the obvious removal candidate.

Alternatives to onemap and PowerTOST

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

See all onemap alternatives → · See all PowerTOST alternatives →

Recent activity from onemap and PowerTOST

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

  1. 10mo agoPowerTOSTFix for splitting total sample size across sequences
  2. 1y agoonemapMAPpoly announcement added to README and load message
  3. 2y agoPowerTOSTNTID functions renamed off the FDA acronym; GCC guidance in vignettes
  4. 3y agoonemapExports to VIEWpoly and QTLpoly; marker ordering and map summaries
  5. 3y agoonemapTwo-point marker filtering and memory reduction
  6. 4y agoPowerTOSTpower.NTID() aliases added; FDA-suffixed names deprecated
  7. 4y agoonemapPSOCK and FORK parallelization choice; vcfR as an import
  8. 5y agoonemaphmm=FALSE option for ordering algorithms
  9. 5y agoonemapMDSMap dependency removed
  10. 5y agoPowerTOSTGulf Co-operation Council added as a regulator setting
  11. 5y agoPowerTOSTMaintenance release with vignette and documentation clarifications
  12. 5y agoPowerTOSTstringsAsFactors fix for older R in a vignette example

Frequently asked questions

What is the difference between onemap and PowerTOST?

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

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

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