constants
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
A side-by-side editorial comparison of camtraptor and qqman — 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 Manhattan-plot package for GWAS results, finished and dormant since 2017.
qqman does two things: manhattan() and qq() plots for genome-wide association study results. Its six visible releases run from 2014 to a single 2017 packaging fix, and the last release with any user-facing change shipped in 2015. The archive is non-monotonic — a 0.0.0 tag published after 0.1.1 archives the pre-package standalone script — so version order and publication order disagree.
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.
qqman does two things: manhattan() and qq() plots for genome-wide association study results. Its six visible releases run from 2014 to a single 2017 packaging fix, and the last release with any user-facing change shipped in 2015. The archive is non-monotonic — a 0.0.0 tag published after 0.1.1 archives the pre-package standalone script — so version order and publication order disagree.
The real development window was 2014 to 2015. The 0.1.2 release did the substantive work, replacing the assumption that SNPs are evenly distributed across chromosomes and handing users control of axis limits, labels and log transformation; 0.1.3 then added annotation by p-value threshold and top-SNP-per-chromosome. After that the package stops. Notably, the archival 0.0.0 entry records that the original script had confidence intervals on QQ plots and richer highlighting than the released package ever regained.
With one packaging fix in the last decade, these entries support no prediction of further releases. The package reads as complete for its narrow purpose rather than abandoned mid-arc.
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 qqman.
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.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all camtraptor alternatives → · See all qqman alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. camtraptor and qqman 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 qqman 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 qqman alternatives in Analytics are ranked by recent ship velocity. Browse the "qqman alternatives" section above for the current picks, or visit /alternatives/qqman-r for the full list with editorial commentary on each.