metR
A meteorology ggplot2 extension where the netCDF reader became the main event
Comparison · Infra & APIs
dataSDA vs driveR
A side-by-side editorial comparison of dataSDA and driveR — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
dataSDA vs driveR: at a glance
What is dataSDA?
dataSDA grew from a dataset collection into a symbolic-data conversion toolkit.
The package now carries 105 documented datasets in interval, histogram, modal, and mixed symbolic formats, drawn from other R packages, the Billard and Diday textbooks, and public sources such as the Portuguese air quality network. Alongside the data it has accumulated conversion functions between the MM, RSDA, iGAP, SODAS, and ARRAY representations, CSV read and write support, and a keyword search over the catalogue.
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.
dataSDA vs driveR: editorial side-by-side
dataSDA
2.5INFRA · APIS
dataSDA grew from a dataset collection into a symbolic-data conversion toolkit.
◆ Current state
The package now carries 105 documented datasets in interval, histogram, modal, and mixed symbolic formats, drawn from other R packages, the Billard and Diday textbooks, and public sources such as the Portuguese air quality network. Alongside the data it has accumulated conversion functions between the MM, RSDA, iGAP, SODAS, and ARRAY representations, CSV read and write support, and a keyword search over the catalogue.
◆ Where it's heading
The arc across this window runs from cataloguing to tooling. Early releases added datasets and then spent two consecutive releases fixing format documentation across all 105 of them. Later releases shift to functions: format converters, symbolic CSV I/O, and most recently a diagnostic that flags zero-width intervals before they reach tools that divide by interval width. That last addition is the clearest signal of intent — the package is starting to guard the analyses downstream of it, not just supply inputs.
◆ Prediction
Expect further validation helpers in the mould of the zero-width check, since interval data has several degenerate shapes that break downstream methods silently.
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.
Alternatives to dataSDA and driveR
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 dataSDA or driveR.
IsoriX
An isotope geolocation package still recovering from the r-spatial retirement
fdacluster
Functional data clustering grew from one algorithm into a comparable suite
profoc
A forecast combination package that spun its profiler out into its own project
adjustedCurves
A survival curve package spending release after release correcting its own estimates
mize
A numerical optimization toolkit that has been feature-complete and quiet since 2017
See all dataSDA alternatives → · See all driveR alternatives →
Recent activity from dataSDA and driveR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 9d agodataSDACorrects dataset references and citations
- 2mo agodataSDAAdds zero-width interval diagnostics for symbolic data
- 5mo agodataSDAAdds symbolic format converters, CSV I/O, and 11 interval series
- 5mo agodataSDAFixes column metadata for 19 interval datasets
- 5mo agodataSDACompletes format documentation across all 105 datasets
- 5mo agodataSDAAdds 17 datasets from R packages and reference texts
- 7mo agodriveRGene-level copy number input accepted, annotation packages made optional
- 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 dataSDA and driveR?
Both compete on the same themes — r-package — within Infra & APIs. dataSDA 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 dataSDA better than driveR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dataSDA 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 dataSDA?
Top dataSDA alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dataSDA alternatives" section above for the current picks, or visit /alternatives/datasda for the full list with editorial commentary on each.
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.