tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of DoseFinding and taxizedb — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
taxizedb queries taxonomic databases locally rather than through rate-limited web APIs, which is what makes it usable for millions of name lookups. Version 0.2.0 established the current design: every source stored as SQLite, no credentials or ports needed, plus name-to-ID mapping functions and ports of the core taxize verbs. The most recent release changes how those databases arrive — instead of downloading a preprocessed SQLite file from the cloud, db_download_*() now fetches raw data and converts it locally for every source, because the cloud path kept breaking.
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.
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.
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.
taxizedb queries taxonomic databases locally rather than through rate-limited web APIs, which is what makes it usable for millions of name lookups. Version 0.2.0 established the current design: every source stored as SQLite, no credentials or ports needed, plus name-to-ID mapping functions and ports of the core taxize verbs. The most recent release changes how those databases arrive — instead of downloading a preprocessed SQLite file from the cloud, db_download_*() now fetches raw data and converts it locally for every source, because the cloud path kept breaking.
The package is trading convenience for independence. Each release removes another thing that has to be working elsewhere for the package to function: hosted database preparation is gone, and where a provider disappears the package documents it rather than pretending otherwise — db_download_tpl() is now defunct because The Plant List no longer exists, though previously downloaded copies still query fine. Release cadence is slow, with multi-year gaps and a maintainer handover in 2023.
Expect further releases to track data sources appearing and disappearing rather than adding features, since that has driven every recent change. Local conversion also shifts cost onto users, so build time and memory for the larger sources are the plausible next thing to need attention.
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 taxizedb.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all DoseFinding alternatives → · See all taxizedb alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. DoseFinding and taxizedb 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. DoseFinding and taxizedb 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 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.
Top taxizedb alternatives in Analytics are ranked by recent ship velocity. Browse the "taxizedb alternatives" section above for the current picks, or visit /alternatives/taxizedb for the full list with editorial commentary on each.