tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
DoseFinding vs git2rdata
A side-by-side editorial comparison of DoseFinding and git2rdata — release velocity, themes, recent moves, and the top alternatives to consider.
DoseFinding vs git2rdata: 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 git2rdata?
git2rdata keeps sharpening one idea: a data frame that produces a readable git diff.
git2rdata stores data frames as plain text plus a metadata sidecar so that version control sees meaningful line-level diffs instead of binary churn. The recent releases have all pushed on the metadata half of that pair: 0.4.1 added `update_metadata()`, 0.5.1 made arbitrary data frame metadata round-trip through storage, and 0.5.2 adds a `convert` argument that records column conversions in the metadata and reverses them on read.
DoseFinding vs git2rdata: 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.
git2rdata
0.0ANALYTICS
git2rdata keeps sharpening one idea: a data frame that produces a readable git diff.
◆ Current state
git2rdata stores data frames as plain text plus a metadata sidecar so that version control sees meaningful line-level diffs instead of binary churn. The recent releases have all pushed on the metadata half of that pair: 0.4.1 added `update_metadata()`, 0.5.1 made arbitrary data frame metadata round-trip through storage, and 0.5.2 adds a `convert` argument that records column conversions in the metadata and reverses them on read.
◆ Where it's heading
The file format itself settled years ago — the last breaking change was the 0.2.0 hash rework — and development since has been about what travels alongside the data. Storage decisions that used to be implicit are becoming declarative and recorded: significant digits in 0.5.0, arbitrary attributes in 0.5.1, type conversions in 0.5.2. The other steady thread is determinism, from C-locale sorting through `icuSetCollate()`, because unstable ordering is what turns a one-row change into a whole-file diff.
◆ Prediction
The metadata system has absorbed digits, attributes and conversions in three consecutive releases, so the next likely addition is another storage decision moved into metadata rather than any change to the on-disk format.
Alternatives to DoseFinding and git2rdata
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 git2rdata.
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 git2rdata alternatives →
Recent activity from DoseFinding and git2rdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agogit2rdataColumn conversions recorded in metadata and reversed on read
- 8mo agogit2rdataData frame metadata now round-trips through storage
- 1y agoDoseFindingConditional and predictive power for interim analyses
- 1y agoDoseFindingModel averaging arrives for dose-response fitting ⚡
- 1y agogit2rdataSignificant digits become an explicit storage option
- 1y agogit2rdataupdate_metadata() for editing a stored object's description
- 1y agoDoseFindingPackage moves to openpharma under new maintainership
- 2y agoDoseFindingCompliance update for R-devel
- 3y agoDoseFindingpowMCTBinCount bug fix
- 4y agogit2rdataNon-optimised files switch to CSV; verify_vc() added
- 4y agogit2rdataStandardised sorting via icuSetCollate()
Frequently asked questions
What is the difference between DoseFinding and git2rdata?
They serve adjacent needs but don't currently overlap on shipped themes. DoseFinding and git2rdata 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 git2rdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DoseFinding and git2rdata 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 git2rdata?
Top git2rdata alternatives in Analytics are ranked by recent ship velocity. Browse the "git2rdata alternatives" section above for the current picks, or visit /alternatives/git2rdata for the full list with editorial commentary on each.