← Back to home
Comparison · Analytics

r2rtf vs waywiser

A side-by-side editorial comparison of r2rtf and waywiser — release velocity, themes, recent moves, and the top alternatives to consider.

r2rtf vs waywiser: at a glance

Featurer2rtfwaywiser
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-reporting, rtf, internationalization, document-conversionspatial-statistics, model-assessment, tidymodels, cran-compliance
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is r2rtf?

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.

Read the full r2rtf trajectory →

What is waywiser?

Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.

waywiser provides spatial model assessment metrics in a tidymodels idiom — spatial autocorrelation measures, area of applicability, and multi-scale assessment of predictions. The substantive work landed in 0.3.0 through 0.5.0, and the recent releases are consolidation: 0.6.0 made metric functions return NA everywhere they previously returned NaN, because macOS disagreed with every other platform, and taught ww_multi_scale() to handle classification and class probability metrics correctly when given rasters. The three releases since are entirely CRAN policy compliance — no internet downloads during checks, no writing to directories, no syntax that would raise the R version floor.

Read the full waywiser trajectory →

r2rtf vs waywiser: editorial side-by-side

R
r2rtf
ANALYTICS
0.0

The clinical-report table engine learned Chinese, then learned to leave RTF entirely

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

W
waywiser
ANALYTICS
0.0

Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.

◆ Current state

waywiser provides spatial model assessment metrics in a tidymodels idiom — spatial autocorrelation measures, area of applicability, and multi-scale assessment of predictions. The substantive work landed in 0.3.0 through 0.5.0, and the recent releases are consolidation: 0.6.0 made metric functions return NA everywhere they previously returned NaN, because macOS disagreed with every other platform, and taught ww_multi_scale() to handle classification and class probability metrics correctly when given rasters. The three releases since are entirely CRAN policy compliance — no internet downloads during checks, no writing to directories, no syntax that would raise the R version floor.

◆ Where it's heading

The package has reached the point where the interesting bugs are cross-platform and cross-package rather than statistical. Its main function, ww_multi_scale(), has been the focus of nearly every release since 0.4.0, working through units handling, aggregation ordering, raster inputs and metric-type dispatch. The dependency on vip and the tidymodels metric machinery means a share of releases exist only to track breaking changes elsewhere.

◆ Prediction

Expect the next substantive release to continue on ww_multi_scale() edge cases, given that it has absorbed most of the fixes in this window. The recent run of CRAN-compliance patches suggests no feature work is currently in flight.

Alternatives to r2rtf and waywiser

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 waywiser.

See all r2rtf alternatives → · See all waywiser alternatives →

Recent activity from r2rtf and waywiser

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 7mo agor2rtfDOCX and HTML output become exported functions
  2. 11mo agor2rtfChinese character support arrives via an i18n font path
  3. 1y agowaywiserStops downloading data during CRAN checks
  4. 1y agor2rtfText colour fixed for figures encoded into RTF
  5. 1y agowaywiserVignettes no longer write to CRAN directories
  6. 1y agowaywiserKeeps the R version floor below 4.1
  7. 1y agor2rtfFootnote handling fixed for R 4.5.0
  8. 1y agor2rtfUnicode converter rebuilt and mapping table made inspectable
  9. 2y agowaywiserNaN results become NA; raster metrics dispatch correctly
  10. 2y agowaywiserGuards against ignored grid arguments; faster on sf data
  11. 2y agor2rtfUTF-8 conversion fix and LibreOffice 7.6 support
  12. 2y agowaywiserFixes wrong observation counts and ignored grid units

Frequently asked questions

What is the difference between r2rtf and waywiser?

They serve adjacent needs but don't currently overlap on shipped themes. r2rtf and waywiser 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.

Is r2rtf better than waywiser?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. r2rtf and waywiser 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.

What are the best alternatives to r2rtf?

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.

What are the best alternatives to waywiser?

Top waywiser alternatives in Analytics are ranked by recent ship velocity. Browse the "waywiser alternatives" section above for the current picks, or visit /alternatives/waywiser for the full list with editorial commentary on each.