← Back to home
Comparison · Analytics

collinear vs regfusionr

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

collinear vs regfusionr: at a glance

Featurecollinearregfusionr
SectorAnalyticsAnalytics
Velocity score0.03.8
Sparks · 30d01
Top themesmulticollinearity, variable selection, vif, breaking changesneuroimaging, coordinate-mapping, freesurfer, r-package
Last editorial update1h ago33m ago
WebsiteVisit →Visit →

What is collinear?

collinear has broken its API twice to stop making the user pick thresholds.

collinear removes multicollinearity from predictor sets through pairwise correlation and VIF filtering, with a preference order deciding which variable survives each conflict. Two major versions in thirteen months each rewrote the interface: 2.0.0 extended every function to any combination of categorical and numeric responses and predictors, and 3.0.0 moved to multiple responses, restructured the output into classed objects, and made both filtering thresholds adaptive by default. Version 3.0.1 is the first release since that is purely repair.

Read the full collinear trajectory →

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.

Read the full regfusionr trajectory →

collinear vs regfusionr: editorial side-by-side

C
collinear
ANALYTICS
0.0

collinear has broken its API twice to stop making the user pick thresholds.

◆ Current state

collinear removes multicollinearity from predictor sets through pairwise correlation and VIF filtering, with a preference order deciding which variable survives each conflict. Two major versions in thirteen months each rewrote the interface: 2.0.0 extended every function to any combination of categorical and numeric responses and predictors, and 3.0.0 moved to multiple responses, restructured the output into classed objects, and made both filtering thresholds adaptive by default. Version 3.0.1 is the first release since that is purely repair.

◆ Where it's heading

The through-line is removing decisions the user was never well placed to make. Preference-order functions were renamed twice — first onto a metric-and-model scheme in 2.0.0, then onto a response-type scheme in 3.0.0 — and f_auto() picks one when none is given; target encoding went from automatic to opt-in; max_cor and max_vif now default to NULL and trigger a data-driven threshold derived from the 75th percentile of pairwise correlations through a sigmoid and a fitted correlation-to-VIF mapping. Each change is defensible and each one broke callers, which is the cost of this approach.

◆ Prediction

3.0.1 moved the example datasets out into a separate spatialData package and fixed four crashes rather than adding anything, so the next release is most likely more consolidation on the 3.0 surface than a fourth interface.

R
regfusionr
ANALYTICS
3.8

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 collinear 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 collinear or regfusionr.

See all collinear alternatives → · See all regfusionr alternatives →

Recent activity from collinear and regfusionr

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

  1. 18d agoregfusionrVersion 0.3.0 -- vol_to_fsaverage, many convenience functions and fixes
  2. 3mo agocollinearNamespace, NA and sf fixes; example data moves to spatialData
  3. 8mo agocollinearAdaptive thresholds, multi-response support and a new output class
  4. 1y agocollinearCategorical responses, f_auto() defaults and future-based parallelism
  5. 4y agoregfusionrv0.2.0 -- surface to volume data projection
  6. 4y agoregfusionrv0.1.0: Initial release

Frequently asked questions

What is the difference between collinear and regfusionr?

They serve adjacent needs but don't currently overlap on shipped themes. regfusionr is currently shipping more aggressively (velocity 3.8 vs 0.0), 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 collinear 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 0.0), 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 collinear?

Top collinear alternatives in Analytics are ranked by recent ship velocity. Browse the "collinear alternatives" section above for the current picks, or visit /alternatives/collinear 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.