qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of austraits and r-datetimeoffset — release velocity, themes, recent moves, and the top alternatives to consider.
The R client for AusTraits spends its releases chasing the dataset it reads.
austraits is the R access layer for the AusTraits plant trait database, and its release history is almost entirely a record of keeping pace with two upstream systems it does not control: the austraits.build data releases and the Zenodo archive that hosts them. The most recent release adds a version-dispatch layer so the same package can read both v4.x and v5.0.0 data. Three of the four visible tags were backfilled to GitHub within 23 minutes of each other, so version order and publication order do not agree.
A datetime type built for the messy metadata formats everyone else rounds off.
datetimeoffset provides a vctrs record type for datetimes with optional UTC offsets, possibly heterogeneous time zones, and missing components — the shapes that appear in PDF, XMP and exiftool metadata. Its value sits in the format family around that type: ISO 8601, EDTF, pdfmark, exiftool, nanotime and strftime output. The 1.0.0 release is a dependency bump, not a feature milestone.
austraits is the R access layer for the AusTraits plant trait database, and its release history is almost entirely a record of keeping pace with two upstream systems it does not control: the austraits.build data releases and the Zenodo archive that hosts them. The most recent release adds a version-dispatch layer so the same package can read both v4.x and v5.0.0 data. Three of the four visible tags were backfilled to GitHub within 23 minutes of each other, so version order and publication order do not agree.
The package is converging on a stable public vocabulary and a versioned internal. Sites became locations across every join, plot and extract function; the extract_ and print family filled out at 1.0.0; and by 2.2.2 the core functions each carry a switch on the detected data version rather than assuming one schema. The visible cost of that is dependency churn — plotting packages moved to Suggests, which the notes admit can leave core functions unable to run.
Given that every release so far has been triggered by an upstream austraits.build or Zenodo change, the next one most likely follows the next data release rather than any independent roadmap. The entries do not indicate new analysis capability being planned in the client itself.
datetimeoffset provides a vctrs record type for datetimes with optional UTC offsets, possibly heterogeneous time zones, and missing components — the shapes that appear in PDF, XMP and exiftool metadata. Its value sits in the format family around that type: ISO 8601, EDTF, pdfmark, exiftool, nanotime and strftime output. The 1.0.0 release is a dependency bump, not a feature milestone.
Growth has come by adding output dialects and loosening parsing rather than by changing the core record. Recent releases handle TOML's ISO 8601 subset and times with no associated date, both narrow gaps in an otherwise settled design. The package tracks the clock package closely and much of its release traffic is keeping that alignment.
Further format dialects and parser edge cases are the likely path; the 1.0.0 label suggests the author considers the record type itself stable.
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 austraits or r-datetimeoffset.
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.
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 austraits alternatives → · See all r-datetimeoffset alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. austraits and r-datetimeoffset 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. austraits and r-datetimeoffset 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 austraits alternatives in Analytics are ranked by recent ship velocity. Browse the "austraits alternatives" section above for the current picks, or visit /alternatives/austraits-r for the full list with editorial commentary on each.
Top r-datetimeoffset alternatives in Analytics are ranked by recent ship velocity. Browse the "r-datetimeoffset alternatives" section above for the current picks, or visit /alternatives/datetimeoffset for the full list with editorial commentary on each.