r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of c3dr and pharmaverseadam — release velocity, themes, recent moves, and the top alternatives to consider.
A biomechanics C3D reader graduated through rOpenSci review to CRAN, then learned to write force plates.
c3dr reads and writes C3D motion-capture files in R, wrapping the EZC3D library. It cleared rOpenSci peer review and moved into the rOpenSci organisation in April 2025, reached CRAN a month later, and shipped force-platform export in c3d_write() in August. Releases are close together and each one has a clear single purpose.
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.
c3dr reads and writes C3D motion-capture files in R, wrapping the EZC3D library. It cleared rOpenSci peer review and moved into the rOpenSci organisation in April 2025, reached CRAN a month later, and shipped force-platform export in c3d_write() in August. Releases are close together and each one has a clear single purpose.
The package is filling in the write side of the read/write pair. Reading was in place from the start; 0.2.0 extends c3d_write() to force-platform data on a direct user request, and the accompanying work preserves matrix structure on import and tracks upstream EZC3D changes. The review-era releases hardened validation and error messages, so the current cycle can be spent on capability rather than polish.
Expect further coverage of C3D block types in the writer and continued tracking of EZC3D releases; the changelog gives no signal of analysis features beyond file I/O.
pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.
Coverage tracks the pharmaverse's own therapeutic-area expansion with a lag of one release: pediatrics arrived in 1.1.0, metabolic in 1.2.0, neurology in 1.3.0. The other consistent thread is a slow move off development versions — 1.1.0 and 1.2.0 both had to pin unreleased upstream builds to get working templates, while 1.3.0 cites released versions throughout. Reorganising the reference page by therapeutic area is the same maturation showing up in documentation.
Expect the next release to follow the established pattern — a refresh against current upstream versions plus datasets from whichever admiral therapeutic-area package reaches a stable release next.
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 c3dr or pharmaverseadam.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all c3dr alternatives → · See all pharmaverseadam alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. c3dr and pharmaverseadam 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. c3dr and pharmaverseadam 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 c3dr alternatives in Analytics are ranked by recent ship velocity. Browse the "c3dr alternatives" section above for the current picks, or visit /alternatives/c3dr for the full list with editorial commentary on each.
Top pharmaverseadam alternatives in Analytics are ranked by recent ship velocity. Browse the "pharmaverseadam alternatives" section above for the current picks, or visit /alternatives/pharmaverseadam for the full list with editorial commentary on each.