← Back to home
Comparison · Analytics

qqman vs treeshap

A side-by-side editorial comparison of qqman and treeshap — release velocity, themes, recent moves, and the top alternatives to consider.

qqman vs treeshap: at a glance

Featureqqmantreeshap
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesgwas, genomics, manhattan-plot, visualizationshap, model explainability, tree ensembles, r package
Last editorial update1h ago11h ago
WebsiteVisit →Visit →

What is qqman?

The Manhattan-plot package for GWAS results, finished and dormant since 2017.

qqman does two things: manhattan() and qq() plots for genome-wide association study results. Its six visible releases run from 2014 to a single 2017 packaging fix, and the last release with any user-facing change shipped in 2015. The archive is non-monotonic — a 0.0.0 tag published after 0.1.1 archives the pre-package standalone script — so version order and publication order disagree.

Read the full qqman trajectory →

What is treeshap?

treeshap keeps widening its tree-model coverage while the SHAP math stays put.

treeshap computes exact SHAP values for tree ensembles in R, reaching each modelling framework through a per-framework unify() adapter. Since returning to CRAN in 2023 it has added GPBoost, ranger survival forests and multi-output models to that adapter layer. Four releases in three years, each dominated by adapter work contributed by users of one specific framework.

Read the full treeshap trajectory →

qqman vs treeshap: editorial side-by-side

Q
qqman
ANALYTICS
0.0

The Manhattan-plot package for GWAS results, finished and dormant since 2017.

◆ Current state

qqman does two things: manhattan() and qq() plots for genome-wide association study results. Its six visible releases run from 2014 to a single 2017 packaging fix, and the last release with any user-facing change shipped in 2015. The archive is non-monotonic — a 0.0.0 tag published after 0.1.1 archives the pre-package standalone script — so version order and publication order disagree.

◆ Where it's heading

The real development window was 2014 to 2015. The 0.1.2 release did the substantive work, replacing the assumption that SNPs are evenly distributed across chromosomes and handing users control of axis limits, labels and log transformation; 0.1.3 then added annotation by p-value threshold and top-SNP-per-chromosome. After that the package stops. Notably, the archival 0.0.0 entry records that the original script had confidence intervals on QQ plots and richer highlighting than the released package ever regained.

◆ Prediction

With one packaging fix in the last decade, these entries support no prediction of further releases. The package reads as complete for its narrow purpose rather than abandoned mid-arc.

T
treeshap
ANALYTICS
0.0

treeshap keeps widening its tree-model coverage while the SHAP math stays put.

◆ Current state

treeshap computes exact SHAP values for tree ensembles in R, reaching each modelling framework through a per-framework unify() adapter. Since returning to CRAN in 2023 it has added GPBoost, ranger survival forests and multi-output models to that adapter layer. Four releases in three years, each dominated by adapter work contributed by users of one specific framework.

◆ Where it's heading

The direction is breadth of model support rather than new explanation methods: every release since the first CRAN submission adds or repairs a unify() backend. Maintenance is community-driven, with named contributors fixing the framework they personally use. Nothing in these entries points at work on the SHAP algorithms themselves.

◆ Prediction

Expect the next release to add or repair another unify() adapter as a contributor brings their own framework, rather than to change how explanations are computed.

Alternatives to qqman and treeshap

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 qqman or treeshap.

See all qqman alternatives → · See all treeshap alternatives →

Recent activity from qqman and treeshap

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3mo agotreeshapGPBoost support lands; xgboost adapter repaired
  2. 2y agotreeshapFixes broken lightgbm.unify examples
  3. 2y agotreeshapMulti-output model explanations added
  4. 2y agotreeshapFirst CRAN release consolidates the unify() adapters
  5. 9y agoqqmanREADME image path fix for pandoc
  6. 11y agoqqmanAnnotate SNPs by p-value threshold or per-chromosome top hit
  7. 11y agoqqmanChromosome ticks stop assuming even SNP spacing; axis control opens up
  8. 12y agoqqmanArchival tag for the pre-package standalone script
  9. 12y agoqqmanVignette touch-up
  10. 12y agoqqmanZenodo archival tag, no code change

Frequently asked questions

What is the difference between qqman and treeshap?

They serve adjacent needs but don't currently overlap on shipped themes. qqman and treeshap 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 qqman better than treeshap?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. qqman and treeshap 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.

What are the best alternatives to qqman?

Top qqman alternatives in Analytics are ranked by recent ship velocity. Browse the "qqman alternatives" section above for the current picks, or visit /alternatives/qqman-r for the full list with editorial commentary on each.

What are the best alternatives to treeshap?

Top treeshap alternatives in Analytics are ranked by recent ship velocity. Browse the "treeshap alternatives" section above for the current picks, or visit /alternatives/treeshap for the full list with editorial commentary on each.