← Back to home
Comparison · Analytics

hydroloom vs regfusionr

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

Shared themes:r-package

hydroloom vs regfusionr: at a glance

Featurehydroloomregfusionr
SectorAnalyticsAnalytics
Velocity score0.03.8
Sparks · 30d01
Top themeshydrology, network-analysis, geospatial, r-packageneuroimaging, coordinate-mapping, freesurfer, r-package
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is hydroloom?

USGS puts a type system over its river network toolkit so errors surface at dispatch

hydroloom builds and navigates hydrologic flow networks, carrying functionality migrated out of nhdplusTools. Version 1.2.0 introduces an S3 class hierarchy — hy_topo, hy_leveled, hy_node, hy_flownetwork — assigned automatically by hy() and by producer functions, letting the package validate input at dispatch time and emit guided errors. Outlet detection is now defined explicitly: a row is an outlet when its toid is not in id, with reserved values, NA and implicit absence all accepted.

Read the full hydroloom 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 →

hydroloom vs regfusionr: editorial side-by-side

H
hydroloom
ANALYTICS
0.0

USGS puts a type system over its river network toolkit so errors surface at dispatch

◆ Current state

hydroloom builds and navigates hydrologic flow networks, carrying functionality migrated out of nhdplusTools. Version 1.2.0 introduces an S3 class hierarchy — hy_topo, hy_leveled, hy_node, hy_flownetwork — assigned automatically by hy() and by producer functions, letting the package validate input at dispatch time and emit guided errors. Outlet detection is now defined explicitly: a row is an outlet when its toid is not in id, with reserved values, NA and implicit absence all accepted.

◆ Where it's heading

The package spent its first releases porting and broadening — non-dendritic network support, divergence routing, subsetting that follows diversions out of a basin — and has now turned to making that surface safe to use. The class hierarchy is the structural expression of that turn: instead of every function re-checking whether a data frame has the columns it needs, the type carries the guarantee. The explicit outlet rule resolves a category of failure where valid networks errored on NA or orphan toid values.

◆ Prediction

The release notes flag that subclass attributes are stripped by standard dplyr operations, which is the kind of rough edge that usually generates follow-up work — expect attribute preservation or restoration helpers next.

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

See all hydroloom alternatives → · See all regfusionr alternatives →

Recent activity from hydroloom 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. 2mo agohydroloomhydroloom v1.2.0
  3. 5mo agohydroloomTest tolerances relaxed for CRAN Fedora checks
  4. 5mo agohydroloomNetwork subsetting and divergence-routed accumulation
  5. 10mo agohydroloomSort and indexing fixes
  6. 1y agohydroloomUpmain and downmain navigation for non-dendritic networks
  7. 2y agohydroloomInitial release completing the nhdplusTools migration
  8. 4y agoregfusionrv0.2.0 -- surface to volume data projection
  9. 4y agoregfusionrv0.1.0: Initial release

Frequently asked questions

What is the difference between hydroloom and regfusionr?

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

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