cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
A side-by-side editorial comparison of dcurves and popbayes — release velocity, themes, recent moves, and the top alternatives to consider.
Decision curve analysis, settled since 2022 and now moving only when its neighbours do
dcurves implements decision curve analysis — evaluating a prediction model or diagnostic test by net benefit across the range of thresholds a clinician might plausibly use, rather than by a single discrimination statistic. Its API stabilised in 2022 around dca() and test_consequences(). The two releases since exist because gtsummary and CRAN documentation rules changed, not because the method did.
A wildlife population-trend package in low-maintenance mode.
popbayes fits Bayesian trends to animal population count series that mix ground counts, aerial counts and expert estimates. The visible history is short and slow: three releases across four years, with the most recent, 1.3, swapping usethis for cli in error messages and tidying the website. The substantive work in the window is 1.1, which reorganised how format_data() handles a dataset.
dcurves implements decision curve analysis — evaluating a prediction model or diagnostic test by net benefit across the range of thresholds a clinician might plausibly use, rather than by a single discrimination statistic. Its API stabilised in 2022 around dca() and test_consequences(). The two releases since exist because gtsummary and CRAN documentation rules changed, not because the method did.
The package reached its intended scope quickly and then stopped. Its 2022 releases did the substantive work: adding threshold-level diagnostic accuracy, tightening argument validation, and taking one breaking change to make net-interventions-avoided plots show the treat-all and treat-none reference lines by default. Since then it has moved only as a dependent of the wider tidy-modelling documentation ecosystem it plugs into.
Nothing in these entries points to method or API work; expect the next release to be another compatibility or CRAN documentation patch.
popbayes fits Bayesian trends to animal population count series that mix ground counts, aerial counts and expert estimates. The visible history is short and slow: three releases across four years, with the most recent, 1.3, swapping usethis for cli in error messages and tidying the website. The substantive work in the window is 1.1, which reorganised how format_data() handles a dataset.
Development has settled into maintenance carried largely by outside contributors, with the current release consisting of a dependency swap and message fixes from two different contributors. The one release with real design work, 1.1, moved format_data() from operating on a whole dataset to operating per count series, letting different series of the same species carry different conversion assumptions. Nothing since has changed the modelling surface.
The entries do not support a confident prediction beyond further contributor-driven maintenance; there is no visible signal of new modelling work.
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 dcurves or popbayes.
A choice-based IRT model published once in 2019 and kept compiling ever since
The R engine behind MetaboAnalyst closes the gap from raw spectra to biological interpretation
Rebuilding SAS's formatting layer in R, one format specification at a time
Standardised coefficients for models where standardising everything is wrong — but the feed only links out
Stream-network spatial models learning to run on data that no longer fits in memory
Bioconductor's installer, frozen at 1.30.x and tuned almost entirely through environment variables
See all dcurves alternatives → · See all popbayes alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. dcurves and popbayes 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dcurves and popbayes 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.
Top dcurves alternatives in Analytics are ranked by recent ship velocity. Browse the "dcurves alternatives" section above for the current picks, or visit /alternatives/dcurves for the full list with editorial commentary on each.
Top popbayes alternatives in Analytics are ranked by recent ship velocity. Browse the "popbayes alternatives" section above for the current picks, or visit /alternatives/popbayes for the full list with editorial commentary on each.