qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
Comparison · Analytics
constants vs TwoSampleMR
A side-by-side editorial comparison of constants and TwoSampleMR — release velocity, themes, recent moves, and the top alternatives to consider.
constants vs TwoSampleMR: at a glance
What is constants?
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
constants exposes the CODATA recommended values of the physical constants to R, as a data frame plus symbol lists that carry units, uncertainties, or both. The package reached 1.0.0 on the 2018 CODATA release and has shipped once since, purely to track a units package update. Its surface is small and its release cadence is bound to CODATA, which revises every few years.
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.
constants vs TwoSampleMR: editorial side-by-side
constants
0.0ANALYTICS
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
◆ Current state
constants exposes the CODATA recommended values of the physical constants to R, as a data frame plus symbol lists that carry units, uncertainties, or both. The package reached 1.0.0 on the 2018 CODATA release and has shipped once since, purely to track a units package update. Its surface is small and its release cadence is bound to CODATA, which revises every few years.
◆ Where it's heading
The direction set at 1.0.0 was to stop being a curated convenience wrapper and become a mechanical mirror of NIST. Hand-crafted symbol names were replaced with NIST's own ASCII symbols, categories adopted NIST's, and uncertainty switched from relative to absolute — all framed by the maintainer as necessary to make future CODATA updates routine. On top of that the package gained a correlation matrix and optional integration with the quantities package, moving it from a lookup table toward something that can propagate uncertainty.
◆ Prediction
Having rebuilt the symbol table specifically so CODATA revisions become mechanical, the next substantive release most likely tracks a new CODATA dataset rather than adding API. The experimental correlated-value support, disabled by default at 1.0.0, is the one part these entries flag as unfinished.
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 constants 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 constants or TwoSampleMR.
austraits
The R client for AusTraits spends its releases chasing the dataset it reads.
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 constants alternatives → · See all TwoSampleMR alternatives →
Recent activity from constants 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
- 5y agoconstantsCompatibility fix for units 0.7-0
- 5y agoconstantsconstants 1.0.0 ⚡
- 8y agoconstantsUnit handling fixes ahead of the 1.0.0 rebuild
Frequently asked questions
What is the difference between constants and TwoSampleMR?
They serve adjacent needs but don't currently overlap on shipped themes. constants 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 constants better than TwoSampleMR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. constants 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 constants?
Top constants alternatives in Analytics are ranked by recent ship velocity. Browse the "constants alternatives" section above for the current picks, or visit /alternatives/constants-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.