r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
DoseFinding vs textreuse
A side-by-side editorial comparison of DoseFinding and textreuse — release velocity, themes, recent moves, and the top alternatives to consider.
DoseFinding vs textreuse: at a glance
What is DoseFinding?
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
DoseFinding implements MCP-Mod and related dose-response methodology for clinical trial design and analysis. In 2024 it changed hands — Marius Thomas took over as maintainer, Novartis was recorded as copyright holder and funder, and the package moved to the openpharma GitHub organisation with roxygen documentation and a proper NEWS file. The two releases since have added substantive methodology: model averaging for dose-response fitting in 1.3-1, and conditional and predictive power for interim analyses in 1.4-1.
What is textreuse?
A dormant text-matching package revived, shipped as 1.0.0, and kept current with the tidyverse.
textreuse detects reused and quoted passages across document collections using minhash and locality-sensitive hashing, with local alignment for inspecting the matches it finds. After years of inactivity, the package reached a 1.0.0 CRAN release in May 2026 that folded accumulated feature work into one version — encoding control on corpus construction, deterministic skipped-document bookkeeping, and an align_local() that returns an empty alignment instead of erroring on non-matching texts. The 1.0.2 release since then is pure compatibility maintenance.
DoseFinding vs textreuse: editorial side-by-side
DoseFinding
0.0ANALYTICS
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
◆ Current state
DoseFinding implements MCP-Mod and related dose-response methodology for clinical trial design and analysis. In 2024 it changed hands — Marius Thomas took over as maintainer, Novartis was recorded as copyright holder and funder, and the package moved to the openpharma GitHub organisation with roxygen documentation and a proper NEWS file. The two releases since have added substantive methodology: model averaging for dose-response fitting in 1.3-1, and conditional and predictive power for interim analyses in 1.4-1.
◆ Where it's heading
The pattern before the handover was maintenance — R-devel compliance, a bug fix, a link. After it, each release carries a named methodological addition with an acknowledged contributor, plus documentation to match: a longitudinal analysis vignette shipped alongside the interim power work. Housekeeping continues underneath, mostly clearing deprecated ggplot2 interfaces, aes_string in one release and qplot in the next.
◆ Prediction
Given the last two releases each added one method with a supporting vignette, expect the next to follow the same shape. Both additions so far extend the package beyond fixed dose-response fitting, so adaptive and interim methodology is the more likely direction.
textreuse
2.5ANALYTICS
A dormant text-matching package revived, shipped as 1.0.0, and kept current with the tidyverse.
◆ Current state
textreuse detects reused and quoted passages across document collections using minhash and locality-sensitive hashing, with local alignment for inspecting the matches it finds. After years of inactivity, the package reached a 1.0.0 CRAN release in May 2026 that folded accumulated feature work into one version — encoding control on corpus construction, deterministic skipped-document bookkeeping, and an align_local() that returns an empty alignment instead of erroring on non-matching texts. The 1.0.2 release since then is pure compatibility maintenance.
◆ Where it's heading
The arc here is restoration rather than expansion. The work has gone into making the package survivable — silencing deprecated dplyr and tidyr selection and many-to-many join warnings, moving from dead Travis and AppVeyor configs to GitHub Actions, and validating across five R platform and version combinations. Release notes now lead with verification evidence rather than features, which is the signature of a maintainer stabilizing an inherited codebase.
◆ Prediction
Expect continued compatibility releases tracking tidyverse deprecations; nothing in these entries indicates new hashing or alignment capability is planned.
Alternatives to DoseFinding and textreuse
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 DoseFinding or textreuse.
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul
crul took mocking back from webmockr and made it a property of the client itself
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
cloudml
Six years since the last functional change, and Google renamed the service it wraps in the release before that
See all DoseFinding alternatives → · See all textreuse alternatives →
Recent activity from DoseFinding and textreuse
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 20d agotextreuseCompatibility pass for current dplyr and tidyr
- 3mo agotextreuseCRAN resubmission fixing a moved README URL
- 3mo agotextreuse1.0.0 consolidates years of accumulated feature work
- 1y agoDoseFindingConditional and predictive power for interim analyses
- 1y agoDoseFindingModel averaging arrives for dose-response fitting ⚡
- 1y agoDoseFindingPackage moves to openpharma under new maintainership
- 2y agoDoseFindingCompliance update for R-devel
- 3y agoDoseFindingpowMCTBinCount bug fix
- 10y agotextreuseMinhashes split out from hashes in document objects
Frequently asked questions
What is the difference between DoseFinding and textreuse?
They serve adjacent needs but don't currently overlap on shipped themes. textreuse 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.
Is DoseFinding better than textreuse?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. textreuse 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.
What are the best alternatives to DoseFinding?
Top DoseFinding alternatives in Analytics are ranked by recent ship velocity. Browse the "DoseFinding alternatives" section above for the current picks, or visit /alternatives/dosefinding for the full list with editorial commentary on each.
What are the best alternatives to textreuse?
Top textreuse alternatives in Analytics are ranked by recent ship velocity. Browse the "textreuse alternatives" section above for the current picks, or visit /alternatives/textreuse for the full list with editorial commentary on each.