← Back to home
Comparison · Analytics

discretefdr vs nflreadr

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

Shared themes:r-package

discretefdr vs nflreadr: at a glance

Featurediscretefdrnflreadr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmultiple-testing, false-discovery-rate, discrete-statistics, r-packager-package, sports-analytics, data-access, deprecation
Last editorial update1h ago51m ago
WebsiteVisit →Visit →

What is discretefdr?

The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.

DiscreteFDR implements false discovery rate procedures adapted for discrete test statistics, where the standard continuous-case corrections are conservative. It now covers a discrete Benjamini-Yekutieli procedure alongside the Benjamini-Hochberg variants it started with, including adaptive versions. Its datasets and test-result classes have been moved out into companion packages, so it increasingly does one job and defers the rest.

Read the full discretefdr trajectory →

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 →

discretefdr vs nflreadr: editorial side-by-side

D
discretefdr
ANALYTICS
0.0

The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.

◆ Current state

DiscreteFDR implements false discovery rate procedures adapted for discrete test statistics, where the standard continuous-case corrections are conservative. It now covers a discrete Benjamini-Yekutieli procedure alongside the Benjamini-Hochberg variants it started with, including adaptive versions. Its datasets and test-result classes have been moved out into companion packages, so it increasingly does one job and defers the rest.

◆ Where it's heading

The direction is decomposition into a suite. The amnesia dataset went to DiscreteDatasets, summary output now interoperates with the DiscreteTestResults class from DiscreteTests, and match.pvals() stopped being exported — each release trims something that belongs elsewhere. What remains gets methodological additions at a slow, deliberate cadence, with performance work on the step-up procedures that dominate cost when the number of tests is large. Recent activity is maintenance: replacing deprecated calls the package still made of its own siblings. This is a mature statistical package whose release notes are short because the methods underneath them are settled.

◆ Prediction

Expect further alignment with the companion packages rather than new procedures, since the last substantive release was already about interoperating with DiscreteTests classes and the most recent one about clearing deprecations.

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.

Alternatives to discretefdr 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 discretefdr or nflreadr.

See all discretefdr alternatives → · See all nflreadr alternatives →

Recent activity from discretefdr and nflreadr

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

  1. 3mo agodiscretefdrDeprecated internal calls replaced
  2. 3mo agonflreadrnflreadr 1.5.1
  3. 11mo agonflreadrnflreadr 1.5.0
  4. 1y agodiscretefdrDiscrete Benjamini-Yekutieli procedure added
  5. 1y agodiscretefdrDatasets split out and step-up procedures sped up
  6. 2y agonflreadrnflreadr 1.4.1
  7. 2y agonflreadrnflreadr 1.4.0
  8. 3y agonflreadrnflreadr 1.3.2
  9. 3y agonflreadrnflreadr 1.3.1

Frequently asked questions

What is the difference between discretefdr and nflreadr?

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

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

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