lstar
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
Comparison · Analytics
collinear vs hydroloom
A side-by-side editorial comparison of collinear and hydroloom — release velocity, themes, recent moves, and the top alternatives to consider.
collinear vs hydroloom: at a glance
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.
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.
collinear vs hydroloom: editorial side-by-side
collinear
0.0ANALYTICS
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.
hydroloom
0.0ANALYTICS
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.
Alternatives to collinear and hydroloom
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 hydroloom.
quanteda
Text analysis in R keeps optimising its token internals — and builds a path out to torch
moderndive
The ModernDive teaching package learns to render inside the browser that runs its own textbook
glmbayes
A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain
chromConverter
The chromatography file-format translator keeps absorbing vendor formats one release at a time
slope
A year after gutting itself for a C++ rewrite, SLOPE is back to polishing the interface
See all collinear alternatives → · See all hydroloom alternatives →
Recent activity from collinear and hydroloom
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agohydroloomhydroloom v1.2.0 ⚡
- 3mo agocollinearNamespace, NA and sf fixes; example data moves to spatialData
- 5mo agohydroloomTest tolerances relaxed for CRAN Fedora checks
- 5mo agohydroloomNetwork subsetting and divergence-routed accumulation
- 8mo agocollinearAdaptive thresholds, multi-response support and a new output class ⚡
- 10mo agohydroloomSort and indexing fixes
- 1y agocollinearCategorical responses, f_auto() defaults and future-based parallelism ⚡
- 1y agohydroloomUpmain and downmain navigation for non-dendritic networks
- 2y agohydroloomInitial release completing the nhdplusTools migration
Frequently asked questions
What is the difference between collinear and hydroloom?
They serve adjacent needs but don't currently overlap on shipped themes. collinear and hydroloom 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 collinear better than hydroloom?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. collinear and hydroloom 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 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 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.