qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of quantities and watina — release velocity, themes, recent moves, and the top alternatives to consider.
The glue package that makes R carry units and uncertainty through the same calculation.
quantities combines the units and errors packages into one class so values keep both their measurement units and their uncertainty through arithmetic, subsetting and data frame operations. Recent releases have been narrow: fixes to the covariance and correlation implementations, and performance work on the data.frame methods. Most of the release traffic is coordination with its two parent packages.
A groundwater database client that has started doing the domain analysis too
watina is the R interface to the Watina groundwater monitoring database, and its history is mostly about making data retrieval correct: filter depths guessed conservatively when missing, spatial masking, aggregation methods per observation well, and a long series of fixes to keep the lazy database queries working across dbplyr versions. The most recent release moves past retrieval into interpretation, adding ionic ratio calculation and a Van Wirdum diagram to plot chemistry data.
quantities combines the units and errors packages into one class so values keep both their measurement units and their uncertainty through arithmetic, subsetting and data frame operations. Recent releases have been narrow: fixes to the covariance and correlation implementations, and performance work on the data.frame methods. Most of the release traffic is coordination with its two parent packages.
The design settled with 0.2.0, which made uncertainty unit-aware and added correlation and covariance support for quantities objects. Since then the package behaves like the integration layer it is — releasing when units, errors, dplyr or ggplot2 shift underneath it rather than on its own schedule. Several releases consist only of test repairs against upstream changes.
Expect the next release to follow a units or errors change rather than introduce new behaviour of its own.
watina is the R interface to the Watina groundwater monitoring database, and its history is mostly about making data retrieval correct: filter depths guessed conservatively when missing, spatial masking, aggregation methods per observation well, and a long series of fixes to keep the lazy database queries working across dbplyr versions. The most recent release moves past retrieval into interpretation, adding ionic ratio calculation and a Van Wirdum diagram to plot chemistry data.
The package is drifting from a database client toward a domain toolkit. Early releases fought the data layer — connection handling moved to inbodb, sorting semantics changed, defunct dbplyr calls worked around. Recent work assumes retrieval is solved and adds hydrochemical analysis on top, along with defensive handling for the physically impossible inputs that analysis exposes, such as zero conductivity in the warehouse.
Expect further chemistry analysis and plotting helpers rather than new retrieval functions, since that is where the newest release invested and where the accompanying vignette points.
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 quantities or watina.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
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.
See all quantities alternatives → · See all watina alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. quantities and watina 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. quantities and watina 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 quantities alternatives in Analytics are ranked by recent ship velocity. Browse the "quantities alternatives" section above for the current picks, or visit /alternatives/quantities for the full list with editorial commentary on each.
Top watina alternatives in Analytics are ranked by recent ship velocity. Browse the "watina alternatives" section above for the current picks, or visit /alternatives/watina-r for the full list with editorial commentary on each.