tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of posteriordb and r2rtf — release velocity, themes, recent moves, and the top alternatives to consider.
A reference posterior database that hit 1.0 with a paper, and is now graded on the statistics it ships.
posteriordb distributes Bayesian models with data and reference posterior draws so inference algorithms can be benchmarked against a common target. It reached 1.0.0 alongside a published paper, and ships both R and Python access. Recent work is about the metadata around the draws — licences, machine-readable dataset descriptors, and additional summary statistics.
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.
posteriordb distributes Bayesian models with data and reference posterior draws so inference algorithms can be benchmarked against a common target. It reached 1.0.0 alongside a published paper, and ships both R and Python access. Recent work is about the metadata around the draws — licences, machine-readable dataset descriptors, and additional summary statistics.
The database is maturing from a model collection into a citable benchmark asset: licence information per model, a Croissant metadata file for dataset discovery, and summary statistics like mean squared value and lag-1 autocorrelation that let users judge whether reference draws are good enough for their comparison. Earlier releases were about content and correctness; current ones are about making the content machine-readable and verifiable.
Further work should continue on draw-quality diagnostics and metadata rather than model count, since the last two releases both added ways to assess the reference draws instead of adding posteriors.
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 posteriordb 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 posteriordb 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. posteriordb 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. posteriordb 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 posteriordb alternatives in Analytics are ranked by recent ship velocity. Browse the "posteriordb alternatives" section above for the current picks, or visit /alternatives/posteriordb 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.