PurpleAir
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
Comparison · Analytics
quanteda vs regfusionr
A side-by-side editorial comparison of quanteda and regfusionr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
quanteda vs regfusionr: at a glance
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.
What is regfusionr?
Registration fusion mapping goes bidirectional, and a vertex-indexing bug that silently returned wrong coordinates is fixed
regfusionr maps coordinates between volumetric brain templates (MNI152, Colin27) and the fsaverage surface. After four dormant years it returned in July 2026 with a release that fixes a coordinate-indexing bug, unblocks a previously disabled function, and completes the template-by-method matrix so all four combinations answer point queries. It also breaks compatibility by switching to the standard FREESURFER_HOME environment variable.
quanteda vs regfusionr: editorial side-by-side
quanteda
2.5ANALYTICS
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.
regfusionr
3.8ANALYTICS
Registration fusion mapping goes bidirectional, and a vertex-indexing bug that silently returned wrong coordinates is fixed
◆ Current state
regfusionr maps coordinates between volumetric brain templates (MNI152, Colin27) and the fsaverage surface. After four dormant years it returned in July 2026 with a release that fixes a coordinate-indexing bug, unblocks a previously disabled function, and completes the template-by-method matrix so all four combinations answer point queries. It also breaks compatibility by switching to the standard FREESURFER_HOME environment variable.
◆ Where it's heading
The package moved from a partial implementation to a complete one in a single release. Before this, vol_coords_to_fsaverage returned coordinates indexed by query position rather than by vertex index — results that looked plausible and were wrong — and fsaverage_to_vol was guarded behind a stop(). Both are now resolved, and the new Colin27 and MNI152 convenience functions make the mapping bidirectional. The sibling package haze shipped a maintenance release 56 minutes later, marking this as a coordinated sweep across the maintainer's neuroimaging stack.
◆ Prediction
With the four template-by-method combinations closed and the coordinate bug fixed, the next release is more likely to be CRAN-adjacent packaging or documentation than new mapping capability.
Alternatives to quanteda and regfusionr
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 regfusionr.
piecepackr
A board game graphics package runs one of the most disciplined deprecation cycles in R.
e2tree
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
discretefdr
The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.
contentanalysis
A scientific-text analysis package moved from counting citations to classifying argument structure.
relialearnr
The teaching arm of an R reliability suite keeps pace with whatever its analysis siblings ship.
See all quanteda alternatives → · See all regfusionr alternatives →
Recent activity from quanteda and regfusionr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoquantedaExplicit token recompilation and a denser path out to torch
- 18d agoregfusionrVersion 0.3.0 -- vol_to_fsaverage, many convenience functions and fixes ⚡
- 1y agoquantedaCorpus chunking and cheaper token concatenation
- 1y agoquantedaFaster concatenation and a dfm_lookup naming fix
- 2y agoquantedaMinor test and documentation fixes
- 2y agoquantedaPlatform-specific test and installation fixes
- 2y agoquantedaCRAN v4.0 ⚡
- 4y agoregfusionrv0.2.0 -- surface to volume data projection
- 4y agoregfusionrv0.1.0: Initial release
Frequently asked questions
What is the difference between quanteda and regfusionr?
Both compete on the same themes — r-package — within Analytics. regfusionr is currently shipping more aggressively (velocity 3.8 vs 2.5), with 1 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 regfusionr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. regfusionr is currently shipping more aggressively (velocity 3.8 vs 2.5), with 1 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 regfusionr?
Top regfusionr alternatives in Analytics are ranked by recent ship velocity. Browse the "regfusionr alternatives" section above for the current picks, or visit /alternatives/regfusionr for the full list with editorial commentary on each.