metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of logrx and pharmaversesdtm — release velocity, themes, recent moves, and the top alternatives to consider.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
logrx produces execution logs for R scripts in regulated clinical work, recording what ran, what it returned, and which unapproved packages or functions were used. Its release notes are raw merged-PR lists rather than written changelogs, which makes the substance hard to read from the feed. The most recent release, 0.2.2 in June 2023, exists to track tidyselect and dplyr changes.
pharmaversesdtm is the test-data layer every pharmaverse package now builds against.
The package ships example SDTM datasets and has grown one therapeutic area at a time — ophthalmology, oncology response criteria, vaccines, metabolic, neurology, and now lymphoma under Lugano 2014. Sibling packages keep moving their internal test data here, so its release notes double as a record of what the rest of the pharmaverse is building.
logrx produces execution logs for R scripts in regulated clinical work, recording what ran, what it returned, and which unapproved packages or functions were used. Its release notes are raw merged-PR lists rather than written changelogs, which makes the substance hard to read from the feed. The most recent release, 0.2.2 in June 2023, exists to track tidyselect and dplyr changes.
Feature work concentrated in the 0.1 line — return codes, a results writer, a to_report parameter, and logging of unapproved package and function use — and the 0.2 releases have been compatibility maintenance and hotfixes. Three years of silence in a pharmaverse that has otherwise kept shipping suggests the package reached the shape its users needed rather than that it was abandoned mid-design.
Nothing in these entries points to planned work; the likeliest trigger for a release is a breaking change in tidyverse dependencies, which is what produced the last one.
The package ships example SDTM datasets and has grown one therapeutic area at a time — ophthalmology, oncology response criteria, vaccines, metabolic, neurology, and now lymphoma under Lugano 2014. Sibling packages keep moving their internal test data here, so its release notes double as a record of what the rest of the pharmaverse is building.
Two kinds of work alternate: adding domains and biomarkers for a new indication, and making the existing data easier to reach — CSV copies under inst/extdata for non-R programmers, a datasets preview vignette, reference pages categorised by therapeutic area, variable-by-variable breakdowns. Consistency fixes against CDISC terminology and SDTM guidelines run through every release.
New therapeutic areas will keep arriving in step with the admiral extension packages that need them; the neurology and metabolic datasets landed just ahead of admiralneuro and admiralmetabolic needing them, and lymphoma looks like the next in that sequence.
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 logrx or pharmaversesdtm.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
See all logrx alternatives → · See all pharmaversesdtm alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — pharmaverse, clinical-trials — within Analytics. logrx and pharmaversesdtm 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. logrx and pharmaversesdtm 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 logrx alternatives in Analytics are ranked by recent ship velocity. Browse the "logrx alternatives" section above for the current picks, or visit /alternatives/logrx for the full list with editorial commentary on each.
Top pharmaversesdtm alternatives in Analytics are ranked by recent ship velocity. Browse the "pharmaversesdtm alternatives" section above for the current picks, or visit /alternatives/pharmaversesdtm for the full list with editorial commentary on each.