r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of dendroNetwork and rbmi — release velocity, themes, recent moves, and the top alternatives to consider.
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
dendroNetwork builds networks of dendrochronological series from similarity between tree-ring measurements, applies community detection to find matching material, and hands the result to Cytoscape for visualisation. That description is all the feed provides: every one of the six visible releases carries the same package abstract as its body, with no record of what changed in any of them. Version 0.5.5 in July 2025 is the most recent.
Reference-based multiple imputation for trials, now shipping without Bayesian support by default.
rbmi implements reference-based multiple imputation for longitudinal clinical trial data with missing values — the estimand machinery regulators expect for handling intercurrent events and dropout. The consequential recent change was 1.3.0 moving rstan from a hard dependency to Suggests, which takes Bayesian imputation out of the default install. Since then the work has been documentation and nomenclature discipline: 1.6.1 standardized on MNAR over a mixed NMAR/MNAR vocabulary and deprecated the nmar.rm argument accordingly.
dendroNetwork builds networks of dendrochronological series from similarity between tree-ring measurements, applies community detection to find matching material, and hands the result to Cytoscape for visualisation. That description is all the feed provides: every one of the six visible releases carries the same package abstract as its body, with no record of what changed in any of them. Version 0.5.5 in July 2025 is the most recent.
What the timestamps show is more informative than the text. Versions 0.5.0 through 0.5.3 were all published within two minutes of each other on 12 April 2024, and in descending version order, which is the signature of a release history backfilled in one pass rather than four separate releases. Real releases follow at 0.5.4 a fortnight later and 0.5.5 fifteen months after that. Development is slow and, on this evidence, undocumented.
No prediction is supportable from these entries — none of them describe a change. Any read on where this package is heading would need the NEWS file or the commit history rather than the feed.
rbmi implements reference-based multiple imputation for longitudinal clinical trial data with missing values — the estimand machinery regulators expect for handling intercurrent events and dropout. The consequential recent change was 1.3.0 moving rstan from a hard dependency to Suggests, which takes Bayesian imputation out of the default install. Since then the work has been documentation and nomenclature discipline: 1.6.1 standardized on MNAR over a mixed NMAR/MNAR vocabulary and deprecated the nmar.rm argument accordingly.
The package is optimizing for adoption friction over feature breadth. Dropping a compiled Stan dependency from the default install, deprecating a bespoke seed argument in favor of base set.seed(), and aligning lsmeans() behavior and weight naming with emmeans all point the same direction — behave like a conventional R package rather than a specialized one. Documentation work in 1.6.1 covering @return on every exported function and executable examples reads as preparation for validation scrutiny rather than user demand.
Given the FAQ vignette's validation statement and the recent documentation completeness pass, the next work is more likely qualification and estimand documentation than new imputation methods.
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 dendroNetwork or rbmi.
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
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
Six years since the last functional change, and Google renamed the service it wraps in the release before that
See all dendroNetwork alternatives → · See all rbmi alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. rbmi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. rbmi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top dendroNetwork alternatives in Analytics are ranked by recent ship velocity. Browse the "dendroNetwork alternatives" section above for the current picks, or visit /alternatives/dendronetwork for the full list with editorial commentary on each.
Top rbmi alternatives in Analytics are ranked by recent ship velocity. Browse the "rbmi alternatives" section above for the current picks, or visit /alternatives/rbmi for the full list with editorial commentary on each.