qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of constants and TAF — release velocity, themes, recent moves, and the top alternatives to consider.
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.
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
TAF is the R tooling behind the ICES Transparent Assessment Framework, which standardizes how fish stock assessments are laid out, sourced and rerun. The 4.3.0 release is the largest in years, adding roughly ten functions covering dependency installation and analysis, software version checks, directory inspection and README drafting. The package has carried zero non-base dependencies since 4.0.0, and the new work is careful not to break that.
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.
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.
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.
TAF is the R tooling behind the ICES Transparent Assessment Framework, which standardizes how fish stock assessments are laid out, sourced and rerun. The 4.3.0 release is the largest in years, adding roughly ten functions covering dependency installation and analysis, software version checks, directory inspection and README drafting. The package has carried zero non-base dependencies since 4.0.0, and the new work is careful not to break that.
The arc runs from analysis runner to project toolkit. Early 3.x releases built out the bootstrap and metadata machinery; 4.0.0 renamed the package and stripped every external dependency; 4.2.0 cleaned up vocabulary that confused users. 4.3.0 turns outward to the people running assessments — install.deps(), pdeps() and check.software() address reproducing someone else's environment, while draft.readme(), taf.example() and dir.tree() address understanding an unfamiliar project.
Expect the follow-up work to harden the new dependency functions rather than add more surface, since 4.3.1 arrived immediately to fix wide2long() compatibility with older R and that batch of ten functions has had little field exposure.
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 TAF.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
A fossil-record simulator that quietly grew a trait-evolution engine.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all constants alternatives → · See all TAF alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. constants and TAF 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. constants and TAF 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.
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.
Top TAF alternatives in Analytics are ranked by recent ship velocity. Browse the "TAF alternatives" section above for the current picks, or visit /alternatives/taf-r for the full list with editorial commentary on each.