qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of dietr and omopsketch — release velocity, themes, recent moves, and the top alternatives to consider.
A fish diet package whose release history is really a record of surviving rfishbase.
dietr computes diet and trophic indices for fish from FishBase-style data, including electivity measures and composite indices. Its recent releases exist because upstream rfishbase changes repeatedly broke it — the latest pair restore functionality after a break severe enough to get the package removed from CRAN, while adding GII, MFI and Windell significance to the composite indices. The 1.1.6-1 patch restates the same notes as 1.1.6.
Health-data characterisation tooling maturing through steady issue-by-issue tightening.
OmopSketch summarises and characterises OMOP Common Data Model databases — clinical records, observation periods, concept counts and missing data. Recent releases have tightened the semantics of those summaries: only records within observation are counted, study ranges are trimmed consistently, and a collect() was removed so more of the work stays in the database. Development is dominated by a single contributor working through numbered issues.
dietr computes diet and trophic indices for fish from FishBase-style data, including electivity measures and composite indices. Its recent releases exist because upstream rfishbase changes repeatedly broke it — the latest pair restore functionality after a break severe enough to get the package removed from CRAN, while adding GII, MFI and Windell significance to the composite indices. The 1.1.6-1 patch restates the same notes as 1.1.6.
Almost every release in this window names an upstream dependency as its cause: rfishbase updates in four of them, duckdb in another. The genuine methodological additions arrive bundled inside those repair releases rather than on their own. That is a fragile position for a package whose core value is convenient access to a remote database.
The next release most likely follows the next rfishbase change; new indices will probably continue to ride along with compatibility repairs.
OmopSketch summarises and characterises OMOP Common Data Model databases — clinical records, observation periods, concept counts and missing data. Recent releases have tightened the semantics of those summaries: only records within observation are counted, study ranges are trimmed consistently, and a collect() was removed so more of the work stays in the database. Development is dominated by a single contributor working through numbered issues.
The package is moving from producing summaries toward producing defensible ones. Interval-based arguments replaced the narrower year argument, table output gained a datatable option, and the vignette now demonstrates a full characterisation feeding a Shiny app. The pattern is refinement of existing summarise* functions rather than new analytic surface.
Expect continued tightening of the summarise* family and its table output options; with only three releases visible, the cadence itself is hard to read.
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 dietr or omopsketch.
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 dietr alternatives → · See all omopsketch alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. dietr and omopsketch 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. dietr and omopsketch 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 dietr alternatives in Analytics are ranked by recent ship velocity. Browse the "dietr alternatives" section above for the current picks, or visit /alternatives/dietr-r for the full list with editorial commentary on each.
Top omopsketch alternatives in Analytics are ranked by recent ship velocity. Browse the "omopsketch alternatives" section above for the current picks, or visit /alternatives/omopsketch for the full list with editorial commentary on each.