← Back to home
Comparison · Analytics

quanteda vs susier

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

Shared themes:r-package

quanteda vs susier: at a glance

Featurequantedasusier
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themestext-analysis, natural-language-processing, r-package, torchr-package, statistical-genetics, fine-mapping, cpp-bindings
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

What is quanteda?

Text analysis in R keeps optimising its token internals — and builds a path out to torch

quanteda is a mature framework for quantitative text analysis in R. Since the 4.0 rewrite around external-pointer tokens objects, releases have concentrated on the internals: recompilation control, memory reduction on concatenation, type-table consistency between tokens and dfm objects. The newest release adds tokens_recompile() for explicit ID reassignment, stops query functions from recompiling implicitly, and returns dense rather than sparse tensors from as.tensor() with arguments passed through to torch.

Read the full quanteda trajectory →

What is susier?

Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs

susieR implements the Sum of Single Effects regression model for variable selection and fine-mapping, widely used in statistical genetics. The recent releases are a tight run of correctness work concentrated in one area: null effect trimming. Version 0.15.55 fixed trimming under the Servin-Stephens residual variance method, 0.15.56 fixed it again for non-uniform prior weights fourteen minutes later, 0.15.57 corrected an ELBO null space term for RSS with X and a matrix symmetry check, and 0.15.58 addressed an alpha0/beta0 issue. Version 0.16.0 migrates the C++ bindings from Rcpp to cpp11 with cpp11armadillo.

Read the full susier trajectory →

quanteda vs susier: editorial side-by-side

Q
quanteda
ANALYTICS
2.5

Text analysis in R keeps optimising its token internals — and builds a path out to torch

◆ Current state

quanteda is a mature framework for quantitative text analysis in R. Since the 4.0 rewrite around external-pointer tokens objects, releases have concentrated on the internals: recompilation control, memory reduction on concatenation, type-table consistency between tokens and dfm objects. The newest release adds tokens_recompile() for explicit ID reassignment, stops query functions from recompiling implicitly, and returns dense rather than sparse tensors from as.tensor() with arguments passed through to torch.

◆ Where it's heading

Two threads run in parallel. The dominant one is performance and correctness housekeeping on the tokens_xptr representation introduced in 4.0 — each release closes another case where the external-pointer path diverged from the plain tokens path. The quieter thread points outward: as.matrix() returning a document-by-position integer matrix and as.tensor() handing off to torch::torch_tensor() make the tokenised corpus directly consumable by neural models rather than only by quanteda's own bag-of-words machinery.

◆ Prediction

The tensor and matrix export path is the least mature part of the surface and gained arguments in this release rather than settling, so expect further work there before the token internals change again.

S
susier
ANALYTICS
0.0

Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs

◆ Current state

susieR implements the Sum of Single Effects regression model for variable selection and fine-mapping, widely used in statistical genetics. The recent releases are a tight run of correctness work concentrated in one area: null effect trimming. Version 0.15.55 fixed trimming under the Servin-Stephens residual variance method, 0.15.56 fixed it again for non-uniform prior weights fourteen minutes later, 0.15.57 corrected an ELBO null space term for RSS with X and a matrix symmetry check, and 0.15.58 addressed an alpha0/beta0 issue. Version 0.16.0 migrates the C++ bindings from Rcpp to cpp11 with cpp11armadillo.

◆ Where it's heading

The version-number churn understates how narrow this work is — four consecutive releases touching the same trimming and residual-variance machinery suggests one area where the implementation and the intended behavior had drifted apart. The 0.16.0 binding migration is the only structural change, and it is invisible to users while mattering for build portability and long-term maintenance. Development is clearly active, with automated release tooling and dependency bumps flowing through the same stream.

◆ Prediction

With the binding migration just landed, near-term releases are likely to address fallout from it alongside continued fixes in the same trimming and residual-variance code.

Alternatives to quanteda and susier

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 quanteda or susier.

See all quanteda alternatives → · See all susier alternatives →

Recent activity from quanteda and susier

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

  1. 12d agoquantedaExplicit token recompilation and a denser path out to torch
  2. 3mo agosusierMigrates C++ bindings from Rcpp to cpp11 and cpp11armadillo
  3. 3mo agosusierFixes alpha0/beta0 handling under Servin-Stephens
  4. 4mo agosusierCorrects the null space ELBO term for RSS with X
  5. 5mo agosusierFixes null effect trimming with non-uniform prior weights
  6. 5mo agosusierFixes null effect trimming under Servin-Stephens estimation
  7. 1y agoquantedaCorpus chunking and cheaper token concatenation
  8. 1y agoquantedaFaster concatenation and a dfm_lookup naming fix
  9. 2y agoquantedaMinor test and documentation fixes
  10. 2y agoquantedaPlatform-specific test and installation fixes
  11. 2y agoquantedaCRAN v4.0

Frequently asked questions

What is the difference between quanteda and susier?

Both compete on the same themes — r-package — within Analytics. quanteda 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 quanteda better than susier?

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

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

What are the best alternatives to susier?

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