ggdist
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
Comparison · Infra & APIs
driveR vs gkwdist
A side-by-side editorial comparison of driveR and gkwdist — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
driveR vs gkwdist: at a glance
What is driveR?
A cancer driver prioritization package that ships rarely and mostly to stay installable
driveR prioritizes cancer driver genes from somatic variant and copy number data, combining coding impact scores, noncoding impact, copy number alteration scores and hotspot annotations into a multi-task learning classification model. Version 0.5.0 added gene-level SCNA data frames as an accepted input to create_features_df(), with an example table shipped alongside, widening the entry point beyond the segment-level format. The same release moved org.Hs.eg.db and both hg19 and hg38 TxDb annotation packages from Imports to Suggests under new CRAN policy, with dependent functions now raising an error when they are absent rather than silently degrading.
What is gkwdist?
gkwdist keeps finding that its distributions were returning the wrong numbers.
The package implements the Generalized Kumaraswamy distribution family and its sub-families. The current release fixes six numerical defects, the most serious being that dgkw() returned zero for every input because internal helpers collided with same-named functions in R's public Rmath.h header. Log-likelihoods for three sub-families were also wrong for data near zero due to clamping instead of working in log space.
driveR vs gkwdist: editorial side-by-side
driveR
0.0INFRA · APIS
A cancer driver prioritization package that ships rarely and mostly to stay installable
◆ Current state
driveR prioritizes cancer driver genes from somatic variant and copy number data, combining coding impact scores, noncoding impact, copy number alteration scores and hotspot annotations into a multi-task learning classification model. Version 0.5.0 added gene-level SCNA data frames as an accepted input to create_features_df(), with an example table shipped alongside, widening the entry point beyond the segment-level format. The same release moved org.Hs.eg.db and both hg19 and hg38 TxDb annotation packages from Imports to Suggests under new CRAN policy, with dependent functions now raising an error when they are absent rather than silently degrading.
◆ Where it's heading
Releases are infrequent and split cleanly between capability and correction. GRCh38 support arrived in 0.4.0 and cancer-type-specific thresholds were refreshed in 0.3.0, while the 0.2.x pair fixed scoring errors serious enough to require retraining: a column name mismatch meant the SCNA score was not being computed at all, and MCR table coordinates needed converting from hg18 to hg19. Both times the bundled classification model and thresholds were rebuilt as a consequence. Since 0.4.0 the changes have been input handling and packaging rather than method.
◆ Prediction
The move of the annotation databases to Suggests suggests a leaner install is the current priority; the entries give no indication of planned model or scoring changes.
gkwdist
2.5INFRA · APIS
gkwdist keeps finding that its distributions were returning the wrong numbers.
◆ Current state
The package implements the Generalized Kumaraswamy distribution family and its sub-families. The current release fixes six numerical defects, the most serious being that dgkw() returned zero for every input because internal helpers collided with same-named functions in R's public Rmath.h header. Log-likelihoods for three sub-families were also wrong for data near zero due to clamping instead of working in log space.
◆ Where it's heading
Every release in this window is correctness work with an unchanged public API — critical MLE fixes in 1.1.3, a CRAN timing-test patch in 1.1.4, numerical corrections in 1.1.5. The recurring theme is that analytically correct formulas were being defeated by implementation details: name collisions, sign errors returning negative infinity where positive was required, and clamping thresholds that destroyed precision in the tails. Test infrastructure added in 1.1.2 validates analytical derivatives against numerical differentiation, which is how several of these were caught.
◆ Prediction
Expect further validation-driven fixes rather than new distributions, since the derivative-checking suite added earlier is still surfacing defects in existing routines.
Alternatives to driveR and gkwdist
Other Infra & APIs 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 driveR or gkwdist.
ipaddress
IP address vectors for R that hit 1.0 and then went quiet.
ltertools
A column-key toolkit for stitching decades of ecological field data into one table.
finnts
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
BayLum
Bayesian luminescence dating that finally replaced its folder-structure input format.
daedalus
An epidemic-economic model teaching its interventions to react to the outbreak itself.
See all driveR alternatives → · See all gkwdist alternatives →
Recent activity from driveR and gkwdist
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6d agogkwdistv1.1.5 — Numerical correctness fixes and componentwise derivative validation
- 2mo agogkwdistv1.1.4 — CRAN fix: skip timing-based tests on CRAN
- 2mo agogkwdistv1.1.3 — Critical MLE Bug Fixes & Numerical Corrections
- 7mo agogkwdistAdds analytical derivative validation across all sub-families
- 7mo agodriveRGene-level copy number input accepted, annotation packages made optional
- 8mo agogkwdistRefactors the C++ backend around stable log-space utilities
- 3y agodriveRCRAN documentation error fixed
- 4y agodriveRGRCh38 genome build supported
- 4y agodriveRCancer-type-specific thresholds updated
- 5y agodriveRMCR coordinates converted to hg19 and the model retrained
- 5y agodriveRCopy number score was never being computed, model rebuilt
Frequently asked questions
What is the difference between driveR and gkwdist?
Both compete on the same themes — r-package — within Infra & APIs. gkwdist 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 driveR better than gkwdist?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gkwdist 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to driveR?
Top driveR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "driveR alternatives" section above for the current picks, or visit /alternatives/driver for the full list with editorial commentary on each.
What are the best alternatives to gkwdist?
Top gkwdist alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gkwdist alternatives" section above for the current picks, or visit /alternatives/gkwdist for the full list with editorial commentary on each.