r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
pharmaverseadam vs xplainfi
A side-by-side editorial comparison of pharmaverseadam and xplainfi — release velocity, themes, recent moves, and the top alternatives to consider.
pharmaverseadam vs xplainfi: at a glance
What is pharmaverseadam?
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.
What is xplainfi?
xplainfi treats feature importance as an estimate with error bars, not a number.
xplainfi implements feature importance methods for mlr3 — perturbation-based PFI, CFI and RFI, refit-based LOCO and WVIM, and SAGE. Its defining choice is that importance scores come with inference attached: several confidence-interval methods, including the Nadeau-Bengio correction and a distribution-free option added in 1.1.0. It declared itself released at 1.0.0 in January 2026.
pharmaverseadam vs xplainfi: editorial side-by-side
pharmaverseadam
0.0ANALYTICS
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
◆ Current state
pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.
◆ Where it's heading
Coverage tracks the pharmaverse's own therapeutic-area expansion with a lag of one release: pediatrics arrived in 1.1.0, metabolic in 1.2.0, neurology in 1.3.0. The other consistent thread is a slow move off development versions — 1.1.0 and 1.2.0 both had to pin unreleased upstream builds to get working templates, while 1.3.0 cites released versions throughout. Reorganising the reference page by therapeutic area is the same maturation showing up in documentation.
◆ Prediction
Expect the next release to follow the established pattern — a refresh against current upstream versions plus datasets from whichever admiral therapeutic-area package reaches a stable release next.
xplainfi
2.5ANALYTICS
xplainfi treats feature importance as an estimate with error bars, not a number.
◆ Current state
xplainfi implements feature importance methods for mlr3 — perturbation-based PFI, CFI and RFI, refit-based LOCO and WVIM, and SAGE. Its defining choice is that importance scores come with inference attached: several confidence-interval methods, including the Nadeau-Bengio correction and a distribution-free option added in 1.1.0. It declared itself released at 1.0.0 in January 2026.
◆ Where it's heading
Two lines of work run in parallel. The statistical side keeps adding inference options — variance corrections, conditional predictive impact, and the Lei et al. observation-wise loss-difference test — while the computational side attacks the cost of refit-based methods, most recently with a batch_size argument that parallelises refits and a default of one refit per resampling iteration. Support for pre-trained learners in 1.1.0 removes the refit requirement entirely in some workflows.
◆ Prediction
The stated reasoning that budget is better spent on resampling iterations than repeated refits suggests n_repeats may be removed from WVIM and LOCO outright, as the release notes hint.
Alternatives to pharmaverseadam and xplainfi
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 pharmaverseadam or xplainfi.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
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
See all pharmaverseadam alternatives → · See all xplainfi alternatives →
Recent activity from pharmaverseadam and xplainfi
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21d agoxplainfiRefits parallelise; repeated refits deprioritised in favour of resampling
- 5mo agoxplainfiPre-trained learners supported; distribution-free inference added
- 5mo agopharmaverseadamNeurology and anti-drug antibody datasets added
- 6mo agoxplainfiVersion bumped to mark the package as released
- 9mo agoxplainfiConfidence intervals arrive for feature importance scores
- 11mo agopharmaverseadamMetabolic therapeutic area datasets arrive
- 1y agopharmaverseadamPediatric ADVS added in an ad-hoc refresh
- 2y agopharmaverseadam1.0 declares the dataset collection stable
- 2y agopharmaverseadamFirst release of the ADaM dataset collection
Frequently asked questions
What is the difference between pharmaverseadam and xplainfi?
They serve adjacent needs but don't currently overlap on shipped themes. xplainfi 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 pharmaverseadam better than xplainfi?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. xplainfi 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 pharmaverseadam?
Top pharmaverseadam alternatives in Analytics are ranked by recent ship velocity. Browse the "pharmaverseadam alternatives" section above for the current picks, or visit /alternatives/pharmaverseadam for the full list with editorial commentary on each.
What are the best alternatives to xplainfi?
Top xplainfi alternatives in Analytics are ranked by recent ship velocity. Browse the "xplainfi alternatives" section above for the current picks, or visit /alternatives/xplainfi for the full list with editorial commentary on each.