nflreadr
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
Comparison · Analytics
discretefdr vs invasimapr
A side-by-side editorial comparison of discretefdr and invasimapr — release velocity, themes, recent moves, and the top alternatives to consider.
discretefdr vs invasimapr: at a glance
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.
What is invasimapr?
invasimapr halved its install size and became citable; the science stayed put.
invasimapr estimates species invasiveness and site invasibility from trait, environmental and resident-community data, exposing a traits → competition → invasion-fitness pipeline behind seven high-level wrappers. Its three releases are all packaging and standards work: a first citable archive in June 2026, then a maturity release bringing it in line with the B-Cubed software development guide. The one behavioral addition in that release is an opt-in standardise_inputs argument on compute_invasion_fitness(), off by default.
discretefdr vs invasimapr: editorial side-by-side
discretefdr
0.0ANALYTICS
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.
invasimapr
0.0ANALYTICS
invasimapr halved its install size and became citable; the science stayed put.
◆ Current state
invasimapr estimates species invasiveness and site invasibility from trait, environmental and resident-community data, exposing a traits → competition → invasion-fitness pipeline behind seven high-level wrappers. Its three releases are all packaging and standards work: a first citable archive in June 2026, then a maturity release bringing it in line with the B-Cubed software development guide. The one behavioral addition in that release is an opt-in standardise_inputs argument on compute_invasion_fitness(), off by default.
◆ Where it's heading
The pressure is toward being installable and auditable rather than more capable — install slimmed from roughly 100 MB to 56 MB, R CMD check warnings and notes resolved, sp moved to Suggests, a Darwin Core-aligned data dictionary added, and a Zenodo concept DOI with CITATION.cff, codemeta.json and .zenodo.json. The package moves in lockstep with its B-Cubed sibling dissmapr, tagged within minutes of each other at both 0.1.0 and 0.2.1, which points at project-level standards deadlines rather than independent release decisions. Trait dispersion metrics and scenario exploration remain on the roadmap.
◆ Prediction
Standards compliance is now complete and the roadmap names functional trait dispersion metrics and scenario exploration tools, so the next release is the first that can plausibly be about invasion ecology rather than packaging.
Alternatives to discretefdr and invasimapr
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 invasimapr.
susier
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
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
See all discretefdr alternatives → · See all invasimapr alternatives →
Recent activity from discretefdr and invasimapr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoinvasimaprVersion bump; notes identical to 0.2.0
- 1mo agoinvasimaprB-Cubed standards alignment; install slimmed to 56 MB
- 1mo agoinvasimaprinvasimapr v0.1.0: First citable release
- 3mo agodiscretefdrDeprecated internal calls replaced
- 1y agodiscretefdrDiscrete Benjamini-Yekutieli procedure added
- 1y agodiscretefdrDatasets split out and step-up procedures sped up
Frequently asked questions
What is the difference between discretefdr and invasimapr?
They serve adjacent needs but don't currently overlap on shipped themes. discretefdr and invasimapr 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 invasimapr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. discretefdr and invasimapr 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 invasimapr?
Top invasimapr alternatives in Analytics are ranked by recent ship velocity. Browse the "invasimapr alternatives" section above for the current picks, or visit /alternatives/invasimapr for the full list with editorial commentary on each.