tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of graphicalMCP and r2rtf — release velocity, themes, recent moves, and the top alternatives to consider.
graphicalMCP is a narrow statistical tool being hardened rather than grown.
graphicalMCP implements graphical multiple comparison procedures — the method used to control family-wise error across several endpoints in a clinical trial. The package moved under the openpharma organisation in 0.2.6, picked up Hochberg tests and internal validation in 0.2.8, and its most recent release fixes a case where graph testing by closure disagreed with the rejection-based path. Releases are roughly annual and short.
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.
graphicalMCP implements graphical multiple comparison procedures — the method used to control family-wise error across several endpoints in a clinical trial. The package moved under the openpharma organisation in 0.2.6, picked up Hochberg tests and internal validation in 0.2.8, and its most recent release fixes a case where graph testing by closure disagreed with the rejection-based path. Releases are roughly annual and short.
The changelog reads as a package settling into reference-implementation status: procedure coverage widened once, then the work turned to proving the two computational routes through the same graph agree with each other. That agreement is the whole promise of this kind of tool, since the closure-based calculation is the definition and the rejection-based one is the fast path everyone actually runs. The openpharma move points the same direction — shared maintenance rather than a single author's project.
The entries show no feature roadmap, only correctness and validation work, so the next release is most likely another consistency or precision fix rather than a new procedure.
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.
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 graphicalMCP or r2rtf.
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.
See all graphicalMCP alternatives → · See all r2rtf alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. graphicalMCP and r2rtf 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. graphicalMCP and r2rtf 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 graphicalMCP alternatives in Analytics are ranked by recent ship velocity. Browse the "graphicalMCP alternatives" section above for the current picks, or visit /alternatives/graphicalmcp for the full list with editorial commentary on each.
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.