qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
Comparison · Analytics
austraits vs TwoSampleMR
A side-by-side editorial comparison of austraits and TwoSampleMR — release velocity, themes, recent moves, and the top alternatives to consider.
austraits vs TwoSampleMR: at a glance
What is austraits?
The R client for AusTraits spends its releases chasing the dataset it reads.
austraits is the R access layer for the AusTraits plant trait database, and its release history is almost entirely a record of keeping pace with two upstream systems it does not control: the austraits.build data releases and the Zenodo archive that hosts them. The most recent release adds a version-dispatch layer so the same package can read both v4.x and v5.0.0 data. Three of the four visible tags were backfilled to GitHub within 23 minutes of each other, so version order and publication order do not agree.
What is TwoSampleMR?
The flagship Mendelian randomization package is auditing its own estimators, one bootstrap at a time.
TwoSampleMR is the MRC-IEU package for two-sample Mendelian randomization against OpenGWAS. Its 2026 releases are a sustained correctness review rather than feature work: 0.7.9 fixed bootstrap standard errors in mr_mode() and mr_rucker_bootstrap() that had been inflated since v0.6.30, and repaired two Rucker functions that were returning malformed objects. Point estimates were not affected by the bootstrap bug.
austraits vs TwoSampleMR: editorial side-by-side
austraits
0.0ANALYTICS
The R client for AusTraits spends its releases chasing the dataset it reads.
◆ Current state
austraits is the R access layer for the AusTraits plant trait database, and its release history is almost entirely a record of keeping pace with two upstream systems it does not control: the austraits.build data releases and the Zenodo archive that hosts them. The most recent release adds a version-dispatch layer so the same package can read both v4.x and v5.0.0 data. Three of the four visible tags were backfilled to GitHub within 23 minutes of each other, so version order and publication order do not agree.
◆ Where it's heading
The package is converging on a stable public vocabulary and a versioned internal. Sites became locations across every join, plot and extract function; the extract_ and print family filled out at 1.0.0; and by 2.2.2 the core functions each carry a switch on the detected data version rather than assuming one schema. The visible cost of that is dependency churn — plotting packages moved to Suggests, which the notes admit can leave core functions unable to run.
◆ Prediction
Given that every release so far has been triggered by an upstream austraits.build or Zenodo change, the next one most likely follows the next data release rather than any independent roadmap. The entries do not indicate new analysis capability being planned in the client itself.
TwoSampleMR
0.0ANALYTICS
The flagship Mendelian randomization package is auditing its own estimators, one bootstrap at a time.
◆ Current state
TwoSampleMR is the MRC-IEU package for two-sample Mendelian randomization against OpenGWAS. Its 2026 releases are a sustained correctness review rather than feature work: 0.7.9 fixed bootstrap standard errors in mr_mode() and mr_rucker_bootstrap() that had been inflated since v0.6.30, and repaired two Rucker functions that were returning malformed objects. Point estimates were not affected by the bootstrap bug.
◆ Where it's heading
The pattern across these releases is a package being read line by line — a copy-paste weight vector in ldsc_rg(), chunking that produced zero splits for short SNP lists, penalisation recycled across the wrong SNPs, dead code paths removed, and regression tests added behind each fix. Alongside it runs a mechanical modernization pass: seq_len() for loop indices, tidyr in place of reshape2, current ggplot2 idioms, and the OpenGWAS URL migration. Feature work is limited to forest plot presentation.
◆ Prediction
Expect the audit to continue through the remaining bootstrap and jackknife routines, with releases staying in the 0.7.x patch range and each fix arriving with its own regression test.
Alternatives to austraits and TwoSampleMR
Other Analytics 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 austraits or TwoSampleMR.
constants
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
ggdemetra
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
fossilsim
A fossil-record simulator that quietly grew a trait-evolution engine.
tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
tern.mmrm
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all austraits alternatives → · See all TwoSampleMR alternatives →
Recent activity from austraits and TwoSampleMR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoTwoSampleMRBootstrap standard errors corrected in mode and Rucker estimators
- 2mo agoTwoSampleMRWrong weight vector and chunking fixes across the estimator set
- 2mo agoTwoSampleMRDeprecated ggplot2 idioms and dead code removed
- 3mo agoTwoSampleMROpenGWAS URLs migrated and Wald ratio warnings quieted
- 4mo agoTwoSampleMRCategorized forest plots aligned with the published figures
- 4mo agoTwoSampleMRFurther internal code optimizations
- 2y agoaustraitsSupport for AusTraits 5.0.0 data and the rebuilt Zenodo API
- 3y agoaustraitsextract_taxa, lookup_trait and print methods arrive
- 3y agoaustraitsVignette build and extract_ function polish
- 3y agoaustraitssite becomes location across the API; AusTraits 3.0.2+ support
Frequently asked questions
What is the difference between austraits and TwoSampleMR?
They serve adjacent needs but don't currently overlap on shipped themes. austraits and TwoSampleMR 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 austraits better than TwoSampleMR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. austraits and TwoSampleMR 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 Analytics products to evaluate alongside.
What are the best alternatives to austraits?
Top austraits alternatives in Analytics are ranked by recent ship velocity. Browse the "austraits alternatives" section above for the current picks, or visit /alternatives/austraits-r for the full list with editorial commentary on each.
What are the best alternatives to TwoSampleMR?
Top TwoSampleMR alternatives in Analytics are ranked by recent ship velocity. Browse the "TwoSampleMR alternatives" section above for the current picks, or visit /alternatives/twosamplemr for the full list with editorial commentary on each.