qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of camtraptor and quantities — release velocity, themes, recent moves, and the top alternatives to consider.
A camera-trap data reader converging on the Camtrap DP standard, one exchange field at a time.
camtraptor reads Camera Trap Data Packages and turns them into analysis-ready tables for R users. The recent releases have been about what those tables carry: get_record_table() now returns deployment coordinates plus clock and solar time in radians, and get_custom_effort() reports effort per deployment rather than pooled. Earlier work went into reading Camtrap DP files written by other tools.
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.
camtraptor reads Camera Trap Data Packages and turns them into analysis-ready tables for R users. The recent releases have been about what those tables carry: get_record_table() now returns deployment coordinates plus clock and solar time in radians, and get_custom_effort() reports effort per deployment rather than pooled. Earlier work went into reading Camtrap DP files written by other tools.
The package is moving from format plumbing toward analysis convenience. The 2023-2024 releases were almost entirely about correctly ingesting Camtrap DP 1.0 and packages produced by the GBIF IPT; the 2025 pair instead adds columns ecologists would otherwise compute themselves. Releases come in bursts tied to specific issue reports, with long gaps between.
Expect continued issue-driven column and argument additions to the get_* family; nothing in these entries points to a change in the underlying reader.
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.
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 camtraptor or quantities.
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 camtraptor alternatives → · See all quantities alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. camtraptor and quantities 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. camtraptor and quantities 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 camtraptor alternatives in Analytics are ranked by recent ship velocity. Browse the "camtraptor alternatives" section above for the current picks, or visit /alternatives/camtraptor for the full list with editorial commentary on each.
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.