← Back to home
Comparison · Analytics

rtflite vs waywiser

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

rtflite vs waywiser: at a glance

Featurertflitewaywiser
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-reporting, python, document-conversion, rtfspatial-statistics, model-assessment, tidymodels, cran-compliance
Last editorial update41m ago2h ago
WebsiteVisit →Visit →

What is rtflite?

rtflite stopped being an RTF writer and became the conversion layer for clinical table output.

rtflite generates the RTF tables clinical study reports are built from, a Python answer to the R tooling that has owned this niche. Over one dense month it grew a full export path: DOCX in 2.2.0, DOCX concatenation in 2.3.0, a configurable LibreOffice converter in 2.4.0, and HTML plus PDF in 2.5.0. The three releases since have been documentation, test infrastructure, and typing work — the feature push has stopped and consolidation has started.

Read the full rtflite 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 →

rtflite vs waywiser: editorial side-by-side

R
rtflite
ANALYTICS
0.0

rtflite stopped being an RTF writer and became the conversion layer for clinical table output.

◆ Current state

rtflite generates the RTF tables clinical study reports are built from, a Python answer to the R tooling that has owned this niche. Over one dense month it grew a full export path: DOCX in 2.2.0, DOCX concatenation in 2.3.0, a configurable LibreOffice converter in 2.4.0, and HTML plus PDF in 2.5.0. The three releases since have been documentation, test infrastructure, and typing work — the feature push has stopped and consolidation has started.

◆ Where it's heading

Every format addition routes through the same LibreOffice converter rather than a per-format implementation, and 2.4.0's breaking change made that converter an injectable object you can configure and reuse. That is the shape of a package expecting to run inside a pipeline that produces hundreds of tables, not one that converts a document at a time. The recent quiet — snapshot tests moved onto `pytest-r-snapshot`, docs migrated, pandas and pyarrow dropped from dev dependencies — reads as work to stay dependency-light while the surface stabilizes.

◆ Prediction

With the export matrix filled in and three consecutive infrastructure-only releases, the next substantive change is most likely on the input side — table construction and pagination — since `page_by` and `subline_by` are the only feature area still generating bug reports in these notes.

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

See all rtflite alternatives → · See all waywiser alternatives →

Recent activity from rtflite and waywiser

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

  1. 4mo agortfliteMulti-section body typing tightened; pandas dropped from dev deps
  2. 7mo agortfliteAPI reference renders Pydantic field metadata
  3. 7mo agortfliteDocumentation site migrated to Zensical
  4. 7mo agortfliteSnapshot tests moved to pytest-r-snapshot
  5. 7mo agortfliteHTML and PDF export complete the output matrix
  6. 7mo agortfliteLibreOffice conversion becomes an injectable converter object
  7. 1y agowaywiserStops downloading data during CRAN checks
  8. 1y agowaywiserVignettes no longer write to CRAN directories
  9. 1y agowaywiserKeeps the R version floor below 4.1
  10. 2y agowaywiserNaN results become NA; raster metrics dispatch correctly
  11. 2y agowaywiserGuards against ignored grid arguments; faster on sf data
  12. 2y agowaywiserFixes wrong observation counts and ignored grid units

Frequently asked questions

What is the difference between rtflite and waywiser?

They serve adjacent needs but don't currently overlap on shipped themes. rtflite 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 rtflite better than waywiser?

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

Top rtflite alternatives in Analytics are ranked by recent ship velocity. Browse the "rtflite alternatives" section above for the current picks, or visit /alternatives/rtflite 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.