← Back to home
Comparison · Infra & APIs

logbin vs onemap

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

logbin vs onemap: at a glance

Featurelogbinonemap
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesrelative-risk, log-binomial, glm-compatibility, em-algorithmgenetic-mapping, linkage-analysis, genotyping-by-sequencing, mappoly
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is logbin?

Relative-risk regression that converges where glm fails, under an unreadable tag order

logbin fits log-binomial models to estimate relative risk, a fit standard glm frequently fails to converge on because of the constrained parameter space. Its answer is a choice of algorithms — adaptive barrier, combinatorial EM, and expectation-maximisation on an overparameterised model — selected through a method argument and optionally accelerated with turboEM. The most recent release, in April 2025, replaces the variance-covariance calculation in summary.logbin so it matches summary.glm, and adds a testthat suite.

Read the full logbin trajectory →

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 →

logbin vs onemap: editorial side-by-side

L
logbin
INFRA · APIS
0.0

Relative-risk regression that converges where glm fails, under an unreadable tag order

◆ Current state

logbin fits log-binomial models to estimate relative risk, a fit standard glm frequently fails to converge on because of the constrained parameter space. Its answer is a choice of algorithms — adaptive barrier, combinatorial EM, and expectation-maximisation on an overparameterised model — selected through a method argument and optionally accelerated with turboEM. The most recent release, in April 2025, replaces the variance-covariance calculation in summary.logbin so it matches summary.glm, and adds a testthat suite.

◆ Where it's heading

The method work concluded in 2021 and the package has since been aligned with base R conventions rather than extended: the vcov calculation now mirrors glm's, and earlier releases added the contrasts, qr, R and effects components so standard glm S3 methods such as influence() and plot() work on logbin objects. Be warned that the feed's tag order is unusable — versions 2.0, 2.0.1, 2.0.2 and 2.0.4 were all pushed within ninety seconds on 23 July 2021 in non-monotonic order, while 2.0.3 carries a 2017 timestamp and restates 2.0.2's notes. Read the bodies, not the sequence.

◆ Prediction

Expect continued alignment with glm conventions and occasional CRAN maintenance; the algorithm set has been stable for four years and nothing in these entries suggests another is planned.

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.

Alternatives to logbin 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 logbin or onemap.

See all logbin alternatives → · See all onemap alternatives →

Recent activity from logbin and onemap

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

  1. 1y agologbinvcov in summary.logbin now matches summary.glm
  2. 1y agoonemapMAPpoly announcement added to README and load message
  3. 3y agoonemapExports to VIEWpoly and QTLpoly; marker ordering and map summaries
  4. 3y agoonemapTwo-point marker filtering and memory reduction
  5. 4y agoonemapPSOCK and FORK parallelization choice; vcfR as an import
  6. 5y agoonemaphmm=FALSE option for ordering algorithms
  7. 5y agoonemapMDSMap dependency removed
  8. 5y agologbinFactor reparameterisation fix and faster parameter expansion
  9. 5y agologbinVersion bump to satisfy a CRAN check
  10. 5y agologbinmethod and accelerate options: adaptive barrier, CEM, EM, turboEM
  11. 5y agologbinglm S3 method support via contrasts, qr, R and effects components
  12. 5y agologbinJournal of Statistical Software citation added

Frequently asked questions

What is the difference between logbin and onemap?

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

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

Top logbin alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "logbin alternatives" section above for the current picks, or visit /alternatives/logbin 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.