r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of dfms and forestly — release velocity, themes, recent moves, and the top alternatives to consider.
Peer-reviewed, feature-complete, and now able to hand its models to other forecasting engines.
dfms estimates dynamic factor models in R, the workhorse for nowcasting economic activity from ragged, mixed-frequency data. The package worked through the Banbura and Modugno (2014) specification in stages — quarterly variables in 0.3.0, AR(1) idiosyncratic errors combined with mixed frequency in 0.4.0 — then declared 1.0.0 feature-complete on completing rOpenSci peer review, adding news decomposition to attribute forecast revisions to specific data releases. Version 1.0.1 adds convert(), which exports fitted models to dlm or KFAS state-space objects.
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
forestly renders adverse-event forest plots as interactive reactable widgets — filterable by AE category, with sliders for incidence thresholds and a toggle for the risk-difference column. Version 0.1.3 added `rtf_static_forestly()` for static RTF output, and 0.1.4 has been about giving the display owner control over what reviewers see: the CSV download button, the AE filter label, and the diff toggle can each be switched off.
dfms estimates dynamic factor models in R, the workhorse for nowcasting economic activity from ragged, mixed-frequency data. The package worked through the Banbura and Modugno (2014) specification in stages — quarterly variables in 0.3.0, AR(1) idiosyncratic errors combined with mixed frequency in 0.4.0 — then declared 1.0.0 feature-complete on completing rOpenSci peer review, adding news decomposition to attribute forecast revisions to specific data releases. Version 1.0.1 adds convert(), which exports fitted models to dlm or KFAS state-space objects.
The package has finished the implementation programme it set out in its 2023 vignette and is now working on the edges: interoperability with other state-space packages rather than more estimation methods of its own. The convert() function is the clearest signal — instead of implementing smoothing and prediction intervals natively, it hands the model to packages that already have them. The rOpenSci move also puts it on a review-backed, documented footing that research users can cite.
Expect continued interoperability and diagnostic work rather than new estimators, since the maintainer has explicitly scoped the package as complete. Bug fixes against RcppArmadillo releases will likely remain the other recurring driver.
forestly renders adverse-event forest plots as interactive reactable widgets — filterable by AE category, with sliders for incidence thresholds and a toggle for the risk-difference column. Version 0.1.3 added `rtf_static_forestly()` for static RTF output, and 0.1.4 has been about giving the display owner control over what reviewers see: the CSV download button, the AE filter label, and the diff toggle can each be switched off.
The arc runs from a fixed interactive widget toward a configurable one with two output modes. Nearly every new argument in the last two releases exists to remove something from the display or relabel it, which suggests the users driving development are producing outputs for others to review under conventions they do not control. The x-axis range, column header, figure header and slider range arguments point the same way — this is a tool being fitted into standardised reporting rather than used ad hoc.
Given that the last two releases have consisted almost entirely of display-control arguments, the next is likely more of the same, applied to whichever parts of the interactive layout are still fixed.
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 dfms or forestly.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all dfms alternatives → · See all forestly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dfms and forestly 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. dfms and forestly 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 dfms alternatives in Analytics are ranked by recent ship velocity. Browse the "dfms alternatives" section above for the current picks, or visit /alternatives/dfms for the full list with editorial commentary on each.
Top forestly alternatives in Analytics are ranked by recent ship velocity. Browse the "forestly alternatives" section above for the current picks, or visit /alternatives/forestly for the full list with editorial commentary on each.