tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
DoseFinding vs markdown
A side-by-side editorial comparison of DoseFinding and markdown — release velocity, themes, recent moves, and the top alternatives to consider.
DoseFinding vs markdown: 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 markdown?
A package that finished, declared itself done, and handed its core function to a successor.
The R markdown package spent 2023 adding real capability — fenced code block attributes, HTML widget rendering, compatibility shims for rmarkdown's document functions. Then 1.13 declared the package feature-complete and maintenance-only, naming litedown as where development continues. Version 2.0 completes that handover: mark(), the package's core function, is now a thin wrapper around litedown::mark(), and users are told to call litedown directly.
DoseFinding vs markdown: 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.
markdown
0.0ANALYTICS
A package that finished, declared itself done, and handed its core function to a successor.
◆ Current state
The R markdown package spent 2023 adding real capability — fenced code block attributes, HTML widget rendering, compatibility shims for rmarkdown's document functions. Then 1.13 declared the package feature-complete and maintenance-only, naming litedown as where development continues. Version 2.0 completes that handover: mark(), the package's core function, is now a thin wrapper around litedown::mark(), and users are told to call litedown directly.
◆ Where it's heading
This is a controlled retirement rather than abandonment. The maintainer closed out the outstanding feature work first, announced the succession explicitly, and only then reduced the package to a compatibility surface. What remains is a stable shim for the installed base while new work happens in a package with a different name and scope.
◆ Prediction
Expect only CRAN-driven fixes here from now on, with any genuinely new rendering capability appearing in litedown instead. The entries state this policy directly, so the main open question is how long the wrapper is kept before deprecation warnings appear.
Alternatives to DoseFinding and markdown
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 markdown.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all DoseFinding alternatives → · See all markdown alternatives →
Recent activity from DoseFinding and markdown
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agoDoseFindingConditional and predictive power for interim analyses
- 1y agomarkdownmark() becomes a thin wrapper around litedown::mark()
- 1y agoDoseFindingModel averaging arrives for dose-response fitting ⚡
- 1y agoDoseFindingPackage moves to openpharma under new maintainership
- 2y agomarkdownPackage declared feature-complete; work moves to litedown ⚡
- 2y agomarkdownAdds compatibility shims for rmarkdown's document functions
- 2y agoDoseFindingCompliance update for R-devel
- 2y agomarkdownFixes verbatim code blocks with language attributes
- 2y agomarkdownFixes raw blocks broken by code-block attribute support
- 2y agomarkdownFenced code blocks gain attributes; HTML widgets render
- 3y agoDoseFindingpowMCTBinCount bug fix
Frequently asked questions
What is the difference between DoseFinding and markdown?
They serve adjacent needs but don't currently overlap on shipped themes. DoseFinding and markdown 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 DoseFinding better than markdown?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DoseFinding and markdown 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 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 markdown?
Top markdown alternatives in Analytics are ranked by recent ship velocity. Browse the "markdown alternatives" section above for the current picks, or visit /alternatives/markdown for the full list with editorial commentary on each.