← Back to home
Comparison · Analytics

discretefdr vs glmbayes

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

Shared themes:r-package

discretefdr vs glmbayes: at a glance

Featurediscretefdrglmbayes
SectorAnalyticsAnalytics
Velocity score0.06.3
Sparks · 30d01
Top themesmultiple-testing, false-discovery-rate, discrete-statistics, r-packagebayesian-statistics, generalized-linear-models, opencl, r-package
Last editorial update44m ago1h 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 glmbayes?

A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain

glmbayes fits Bayesian generalized linear models with optional OpenCL acceleration. The last four months moved it from a package with its own vocabulary to one that answers the insight and bayestestR generics the rest of the R Bayesian ecosystem is built on, while pushing the OpenCL kernels out into a separate nmathopencl dependency that carries CRAN Windows binaries. It returned to CRAN in August after an archival over a configure policy issue.

Read the full glmbayes trajectory →

discretefdr vs glmbayes: 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.

G
glmbayes
ANALYTICS
6.3

A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain

◆ Current state

glmbayes fits Bayesian generalized linear models with optional OpenCL acceleration. The last four months moved it from a package with its own vocabulary to one that answers the insight and bayestestR generics the rest of the R Bayesian ecosystem is built on, while pushing the OpenCL kernels out into a separate nmathopencl dependency that carries CRAN Windows binaries. It returned to CRAN in August after an archival over a configure policy issue.

◆ Where it's heading

The arc is about removing reasons not to use it. GPU support was previously blocked on Windows because the OpenCL kernels were vendored; splitting them into a CRAN package with binaries fixed that. The ecosystem work does the same thing for tooling — a glmb fit now responds to get_parameters, get_priors, simulate_prior and check_prior, so it drops into workflows built around easystats rather than requiring its own. The CRAN archival and the configure fixes that followed show how much of the effort goes into distribution rather than modelling.

◆ Prediction

get_priors() returning the full prior specification rather than a marginal table is the kind of detail that invites further bayestestR integration, and the diagnostic surface is the least built-out part of what has shipped so far.

Alternatives to discretefdr and glmbayes

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

See all discretefdr alternatives → · See all glmbayes alternatives →

Recent activity from discretefdr and glmbayes

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

  1. 10d agoglmbayesBack on CRAN after a configure policy fix
  2. 22d agoglmbayesOpenCL split out to nmathopencl; insight and bayestestR integration
  3. 1mo agoglmbayesMulti-response models and conjugate GLM priors
  4. 3mo agoglmbayesOpenCL kernels restructured and a binomial GPU bug fixed
  5. 3mo agodiscretefdrDeprecated internal calls replaced
  6. 3mo agoglmbayesVersion bump for CRAN resubmission
  7. 1y agoglmbayesCRAN-ready beta with the core S3 interface
  8. 1y agodiscretefdrDiscrete Benjamini-Yekutieli procedure added
  9. 1y agodiscretefdrDatasets split out and step-up procedures sped up

Frequently asked questions

What is the difference between discretefdr and glmbayes?

Both compete on the same themes — r-package — within Analytics. glmbayes is currently shipping more aggressively (velocity 6.3 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 discretefdr better than glmbayes?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. glmbayes is currently shipping more aggressively (velocity 6.3 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 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 glmbayes?

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