qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of camtraptor and tern.rbmi — 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.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
tern.rbmi renders the output of {rbmi} reference-based multiple imputation analyses into tern tables for clinical reporting. Its three most recent releases exist to satisfy CRAN: restricting vignette builds to gcc, adding V8 to Suggests, and a plain resubmission. No user-facing functionality has changed in the visible window, and the three older entries now backfilled are version-bump automation.
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.
tern.rbmi renders the output of {rbmi} reference-based multiple imputation analyses into tern tables for clinical reporting. Its three most recent releases exist to satisfy CRAN: restricting vignette builds to gcc, adding V8 to Suggests, and a plain resubmission. No user-facing functionality has changed in the visible window, and the three older entries now backfilled are version-bump automation.
This is a thin adapter package and behaves like one — it moves when CRAN or an upstream dependency forces it to. Between 2022 and 2024 the feed shows only version bumps, and the 2025 releases are packaging concerns rather than analysis changes. The newly surfaced 2022 entries reinforce rather than change that reading.
Expect the next release to be triggered by a CRAN check failure or an {rbmi} update rather than by new tabulation features.
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 tern.rbmi.
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.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all camtraptor alternatives → · See all tern.rbmi 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 tern.rbmi 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 tern.rbmi 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 tern.rbmi alternatives in Analytics are ranked by recent ship velocity. Browse the "tern.rbmi alternatives" section above for the current picks, or visit /alternatives/tern-rbmi for the full list with editorial commentary on each.