susier
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
Comparison · Analytics
hydroloom vs nflreadr
A side-by-side editorial comparison of hydroloom and nflreadr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
hydroloom vs nflreadr: at a glance
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.
What is nflreadr?
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
nflreadr is the data access layer of the nflverse, wrapping cached downloads of play-by-play, roster, contract, charting and stats releases. Its growth phase peaked with 1.3.0, which added participation data, contracts, weekly rosters, officials and the players endpoint in a single release. Since then the work has been consolidation: 1.5.0 moved to v2 players data and reorganized player stats behind nflfastR's calculate_stats() with a summary_level argument, and 1.5.1 hard-deprecated qs file support after that package was removed from CRAN in January 2026.
hydroloom vs nflreadr: editorial side-by-side
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.
nflreadr
0.0ANALYTICS
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
◆ Current state
nflreadr is the data access layer of the nflverse, wrapping cached downloads of play-by-play, roster, contract, charting and stats releases. Its growth phase peaked with 1.3.0, which added participation data, contracts, weekly rosters, officials and the players endpoint in a single release. Since then the work has been consolidation: 1.5.0 moved to v2 players data and reorganized player stats behind nflfastR's calculate_stats() with a summary_level argument, and 1.5.1 hard-deprecated qs file support after that package was removed from CRAN in January 2026.
◆ Where it's heading
Two external clocks drive this package and neither is under its control. Feature releases land before the NFL season opens — 1.5.0 says so explicitly — and breaking changes are timed to that window. The other clock is CRAN's: losing the qs dependency forced a serialization format out of the package entirely, leaving parquet, rds and csv. The upstream coupling to nflfastR is tightening too, with player and team stats now sourced from its calculation functions rather than computed here.
◆ Prediction
The pattern of a pre-season consolidation release is well established, so the next substantive version is likely timed to the following season's opener rather than to any internal roadmap.
Alternatives to hydroloom and nflreadr
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 nflreadr.
UCell
A rank-based gene signature scorer that has grown by adapting to whatever object format single-cell R uses next
detectseparation
A diagnostic package that generalized past its own name, then learned to say which kind of separation it found
brglm2
A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression
bayestools
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
robma
RoBMA 4.0 tears out its own constructor surface and rebuilds on one class hierarchy
See all hydroloom alternatives → · See all nflreadr alternatives →
Recent activity from hydroloom and nflreadr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agohydroloomhydroloom v1.2.0 ⚡
- 3mo agonflreadrnflreadr 1.5.1
- 5mo agohydroloomTest tolerances relaxed for CRAN Fedora checks
- 5mo agohydroloomNetwork subsetting and divergence-routed accumulation
- 10mo agohydroloomSort and indexing fixes
- 11mo agonflreadrnflreadr 1.5.0
- 1y agohydroloomUpmain and downmain navigation for non-dendritic networks
- 2y agonflreadrnflreadr 1.4.1
- 2y agohydroloomInitial release completing the nhdplusTools migration
- 2y agonflreadrnflreadr 1.4.0
- 3y agonflreadrnflreadr 1.3.2
- 3y agonflreadrnflreadr 1.3.1
Frequently asked questions
What is the difference between hydroloom and nflreadr?
Both compete on the same themes — r-package — within Analytics. hydroloom and nflreadr 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 hydroloom better than nflreadr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. hydroloom and nflreadr 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 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 nflreadr?
Top nflreadr alternatives in Analytics are ranked by recent ship velocity. Browse the "nflreadr alternatives" section above for the current picks, or visit /alternatives/nflreadr for the full list with editorial commentary on each.