← Back to home
Comparison · Analytics

nflreadr vs tglkmeans

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

Shared themes:r-package

nflreadr vs tglkmeans: at a glance

Featurenflreadrtglkmeans
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-package, sports-analytics, data-access, deprecationr-package, clustering, missing-data, correctness
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

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.

Read the full nflreadr trajectory →

What is tglkmeans?

A k-means implementation that just told users their Spearman clustering on missing data was wrong

tglkmeans is a multi-core k-means implementation with seeding, aimed at single-cell and other large matrix workloads. Version 0.4.0 flipped the id_column default and moved to R's random number generator, 0.5.x added count-matrix downsampling and fixed id handling, and 0.6.3 in May 2026 is a correctness release: Spearman distance was ranking missing values as the largest value instead of dropping them, and predict_tgl_kmeans() with Euclidean distance did not reproduce the training metric when a cluster center had a missing dimension.

Read the full tglkmeans trajectory →

nflreadr vs tglkmeans: editorial side-by-side

N
nflreadr
ANALYTICS
0.0

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.

T
tglkmeans
ANALYTICS
0.0

A k-means implementation that just told users their Spearman clustering on missing data was wrong

◆ Current state

tglkmeans is a multi-core k-means implementation with seeding, aimed at single-cell and other large matrix workloads. Version 0.4.0 flipped the id_column default and moved to R's random number generator, 0.5.x added count-matrix downsampling and fixed id handling, and 0.6.3 in May 2026 is a correctness release: Spearman distance was ranking missing values as the largest value instead of dropping them, and predict_tgl_kmeans() with Euclidean distance did not reproduce the training metric when a cluster center had a missing dimension.

◆ Where it's heading

The package handles missing data across three distance metrics, and 0.6.3 shows those paths had drifted apart — Spearman behaved unlike Euclidean and Pearson, and prediction behaved unlike training. Both fixes change results on affected data, and the release notes are careful to bound exactly where: Spearman on data with NAs changes, complete data does not. Performance work runs alongside, with the dense per-thread vote matrix removed from the reassignment step.

◆ Prediction

With the metric paths now aligned on missing-value handling, further work is more likely to target the parallel reassignment internals than the distance semantics.

Alternatives to nflreadr and tglkmeans

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 tglkmeans.

See all nflreadr alternatives → · See all tglkmeans alternatives →

Recent activity from nflreadr and tglkmeans

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

  1. 2mo agotglkmeansSpearman metric no longer ranks missing values as the largest
  2. 3mo agonflreadrnflreadr 1.5.1
  3. 11mo agonflreadrnflreadr 1.5.0
  4. 2y agonflreadrnflreadr 1.4.1
  5. 2y agotglkmeansFixes corrupted cluster ids and dropped dimnames
  6. 2y agotglkmeansAdds downsample_matrix() for count matrices
  7. 2y agotglkmeansBreaking: id_column defaults to FALSE, switches to R's RNG
  8. 2y agonflreadrnflreadr 1.4.0
  9. 3y agonflreadrnflreadr 1.3.2
  10. 3y agonflreadrnflreadr 1.3.1

Frequently asked questions

What is the difference between nflreadr and tglkmeans?

Both compete on the same themes — r-package — within Analytics. nflreadr and tglkmeans 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 nflreadr better than tglkmeans?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nflreadr and tglkmeans 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 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 tglkmeans?

Top tglkmeans alternatives in Analytics are ranked by recent ship velocity. Browse the "tglkmeans alternatives" section above for the current picks, or visit /alternatives/tglkmeans for the full list with editorial commentary on each.