fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
Comparison · Analytics
nflreadr vs regfusionr
A side-by-side editorial comparison of nflreadr and regfusionr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
nflreadr vs regfusionr: at a glance
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.
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.
nflreadr vs regfusionr: editorial side-by-side
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.
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 nflreadr 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 nflreadr or regfusionr.
gcube
gcube's recent releases are all packaging metadata, not simulation code
cubist
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats
ggstats keeps widening what a coefficient or Likert plot can be
ecodive
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
simStateSpace
State-space data simulation for R, filled in one function at a time
See all nflreadr alternatives → · See all regfusionr alternatives →
Recent activity from nflreadr and regfusionr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18d agoregfusionrVersion 0.3.0 -- vol_to_fsaverage, many convenience functions and fixes ⚡
- 3mo agonflreadrnflreadr 1.5.1
- 11mo agonflreadrnflreadr 1.5.0
- 2y agonflreadrnflreadr 1.4.1
- 2y agonflreadrnflreadr 1.4.0
- 3y agonflreadrnflreadr 1.3.2
- 3y agonflreadrnflreadr 1.3.1
- 4y agoregfusionrv0.2.0 -- surface to volume data projection
- 4y agoregfusionrv0.1.0: Initial release
Frequently asked questions
What is the difference between nflreadr 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 nflreadr 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 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.
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.