tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of r2rtf and spiro — release velocity, themes, recent moves, and the top alternatives to consider.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
r2rtf builds the RTF tables, listings and figures that go into clinical study reports, and its recent releases have been about widening who and what it can serve rather than changing how tables are composed. The 1.2.0 release added internationalization — a SimSun font path for Chinese characters plus hyphenation control — and 1.3.0 followed with write_docx() and write_html(), turning the LibreOffice conversion the package had documented into exported functions.
Cardiopulmonary exercise test data in R, one metabolic cart vendor at a time.
spiro imports and processes cardiopulmonary exercise testing data in R, handling the file formats that metabolic carts from Cosmed, Cortex, Vyntus, and ZAN emit, then interpolating, smoothing, and summarizing them into comparable variables. The bulk of ongoing work is vendor format compatibility rather than analysis features — 0.2.4 fixed Cosmed imports failing in rare cases and Cortex imports on newer devices, and 0.2.2 added English-language Vyntus files after 0.1.2 added French ones. The analysis side, spiro_max(), spiro_smooth() and spiro_plot(), has been stable for some time.
r2rtf builds the RTF tables, listings and figures that go into clinical study reports, and its recent releases have been about widening who and what it can serve rather than changing how tables are composed. The 1.2.0 release added internationalization — a SimSun font path for Chinese characters plus hyphenation control — and 1.3.0 followed with write_docx() and write_html(), turning the LibreOffice conversion the package had documented into exported functions.
Two threads run through the window. One is output reach: RTF remains the composition target, but the artifacts that come out of it now include DOCX and HTML, and page numbering can be made table-relative across multi-page tables. The other is durability under a moving R and font stack — the ANSI/Unicode converter was rebuilt, the LaTeX mapping table generated from code rather than shipped as sysdata, unlist() usage fixed for R 4.5, and graphics-device leaks that produced stray Rplots.pdf closed off.
Having exported DOCX and HTML conversion, the likely next step is filling in what those formats lose relative to RTF — pagination and footnote fidelity are the obvious gaps. The i18n path currently covers Chinese only, so additional font families are the other plausible direction.
spiro imports and processes cardiopulmonary exercise testing data in R, handling the file formats that metabolic carts from Cosmed, Cortex, Vyntus, and ZAN emit, then interpolating, smoothing, and summarizing them into comparable variables. The bulk of ongoing work is vendor format compatibility rather than analysis features — 0.2.4 fixed Cosmed imports failing in rare cases and Cortex imports on newer devices, and 0.2.2 added English-language Vyntus files after 0.1.2 added French ones. The analysis side, spiro_max(), spiro_smooth() and spiro_plot(), has been stable for some time.
This is a mature rOpenSci package whose remaining work is dictated by other people's file formats. Each device firmware revision, each regional language variant, and each ggplot2 release generates maintenance, and that is what fills the changelog. The API itself settled early, with the 0.1.0 rOpenSci review pass renaming the protocol helpers to the pt_* prefix and 0.2.0 replacing the confusingly named spiro_import() with spiro_raw().
Expect the pattern to continue: import fixes as vendor formats shift and periodic plotting updates tracking ggplot2, with no indication of new analysis capability.
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 r2rtf or spiro.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. r2rtf and spiro 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. r2rtf and spiro 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 r2rtf alternatives in Analytics are ranked by recent ship velocity. Browse the "r2rtf alternatives" section above for the current picks, or visit /alternatives/r2rtf for the full list with editorial commentary on each.
Top spiro alternatives in Analytics are ranked by recent ship velocity. Browse the "spiro alternatives" section above for the current picks, or visit /alternatives/spiro for the full list with editorial commentary on each.