HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
driveR vs IsoriX
A side-by-side editorial comparison of driveR and IsoriX — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
driveR vs IsoriX: 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 IsoriX?
An isotope geolocation package still recovering from the r-spatial retirement
IsoriX builds isoscapes and assigns organisms to geographic origin from stable isotope data. Its recent history is defined by the October 2023 retirement of the old R spatial stack: version 0.9.1 recoded substantial parts of the package to drop raster and sp, 0.9.2 restored capabilities that migration had broken - saving and reloading IsoriX objects, and plotting ocean masks containing holes - and documented the new plotting calls that replace the old sp.polygons and sp.points idioms. Since then 0.9.3 revised the bundled bat calibration datasets and 0.9.4 moved the documentation off bookdown.org.
driveR vs IsoriX: 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.
IsoriX
0.0INFRA · APIS
An isotope geolocation package still recovering from the r-spatial retirement
◆ Current state
IsoriX builds isoscapes and assigns organisms to geographic origin from stable isotope data. Its recent history is defined by the October 2023 retirement of the old R spatial stack: version 0.9.1 recoded substantial parts of the package to drop raster and sp, 0.9.2 restored capabilities that migration had broken - saving and reloading IsoriX objects, and plotting ocean masks containing holes - and documented the new plotting calls that replace the old sp.polygons and sp.points idioms. Since then 0.9.3 revised the bundled bat calibration datasets and 0.9.4 moved the documentation off bookdown.org.
◆ Where it's heading
Two years of the visible history have gone on infrastructure the science did not ask for. The 0.9.1 notes are unusually candid, warning users that the surrounding package landscape was still in flux and that incompatibility bugs were likely to keep surfacing, which 0.9.2 then confirmed. Only in 0.9.3 does domain work reappear: the bat fur isotope values in the calibration and assignment datasets were corrected to align with current keratin reference material normalisation, so results computed against the old datasets are not comparable with new ones.
◆ Prediction
With the spatial migration settled and the documentation rehomed, the next release is more likely to return to isoscape functionality than to infrastructure, though the entries do not name a specific feature.
Alternatives to driveR and IsoriX
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 IsoriX.
bsvarSIGNs
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
estimatr
Fast design-based estimators for experiments, coasting on CRAN patches.
ggdist
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
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.
See all driveR alternatives → · See all IsoriX alternatives →
Recent activity from driveR and IsoriX
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7mo agoIsoriXDocumentation rehomed after bookdown.org shutdown
- 7mo agodriveRGene-level copy number input accepted, annotation packages made optional
- 1y agoIsoriXCalibration datasets corrected to current keratin reference standards
- 2y agoIsoriXSaving objects and masked plotting restored after the spatial migration
- 2y agoIsoriXv0.9.1.9999
- 2y agoIsoriXPackage recoded to drop the retiring spatial dependencies
- 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
- 5y agoIsoriXCRAN release version 0.5
Frequently asked questions
What is the difference between driveR and IsoriX?
Both compete on the same themes — r-package — within Infra & APIs. driveR and IsoriX 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 driveR better than IsoriX?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. driveR and IsoriX 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 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 IsoriX?
Top IsoriX alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "IsoriX alternatives" section above for the current picks, or visit /alternatives/isorix for the full list with editorial commentary on each.