← Back to home
Comparison · Analytics

detectseparation vs susier

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

Shared themes:r-package

detectseparation vs susier: at a glance

Featuredetectseparationsusier
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-package, regression, diagnostics, separationr-package, statistical-genetics, fine-mapping, cpp-bindings
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is detectseparation?

A diagnostic package that generalized past its own name, then learned to say which kind of separation it found

detectseparation identifies separation and infinite estimates in binomial-response GLMs — the condition where maximum likelihood estimates diverge and standard software reports large coefficients with enormous standard errors instead of an error. Version 0.3 was the structural turn: detect_infinite_estimates() became the general method covering log, logit, probit and cauchit links, with detect_separation() demoted to a wrapper around it. Version 0.4 in April 2026 adds the ability to distinguish complete from quasi-complete separation via separation_type.

Read the full detectseparation trajectory →

What is susier?

Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs

susieR implements the Sum of Single Effects regression model for variable selection and fine-mapping, widely used in statistical genetics. The recent releases are a tight run of correctness work concentrated in one area: null effect trimming. Version 0.15.55 fixed trimming under the Servin-Stephens residual variance method, 0.15.56 fixed it again for non-uniform prior weights fourteen minutes later, 0.15.57 corrected an ELBO null space term for RSS with X and a matrix symmetry check, and 0.15.58 addressed an alpha0/beta0 issue. Version 0.16.0 migrates the C++ bindings from Rcpp to cpp11 with cpp11armadillo.

Read the full susier trajectory →

detectseparation vs susier: editorial side-by-side

D0.0

A diagnostic package that generalized past its own name, then learned to say which kind of separation it found

◆ Current state

detectseparation identifies separation and infinite estimates in binomial-response GLMs — the condition where maximum likelihood estimates diverge and standard software reports large coefficients with enormous standard errors instead of an error. Version 0.3 was the structural turn: detect_infinite_estimates() became the general method covering log, logit, probit and cauchit links, with detect_separation() demoted to a wrapper around it. Version 0.4 in April 2026 adds the ability to distinguish complete from quasi-complete separation via separation_type.

◆ Where it's heading

The package has been generalizing steadily — first past its own framing, since separation is one case of infinite estimates rather than the whole problem, and now toward finer classification of what it detects. The distinction 0.4 adds is practically useful because complete and quasi-complete separation call for different responses. Release intervals are long, roughly two to four years, which fits a diagnostic tool whose underlying theory is settled.

◆ Prediction

With link coverage broad and separation now classified by type, further work is more likely to refine reporting than to extend detection to new model families.

S
susier
ANALYTICS
0.0

Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs

◆ Current state

susieR implements the Sum of Single Effects regression model for variable selection and fine-mapping, widely used in statistical genetics. The recent releases are a tight run of correctness work concentrated in one area: null effect trimming. Version 0.15.55 fixed trimming under the Servin-Stephens residual variance method, 0.15.56 fixed it again for non-uniform prior weights fourteen minutes later, 0.15.57 corrected an ELBO null space term for RSS with X and a matrix symmetry check, and 0.15.58 addressed an alpha0/beta0 issue. Version 0.16.0 migrates the C++ bindings from Rcpp to cpp11 with cpp11armadillo.

◆ Where it's heading

The version-number churn understates how narrow this work is — four consecutive releases touching the same trimming and residual-variance machinery suggests one area where the implementation and the intended behavior had drifted apart. The 0.16.0 binding migration is the only structural change, and it is invisible to users while mattering for build portability and long-term maintenance. Development is clearly active, with automated release tooling and dependency bumps flowing through the same stream.

◆ Prediction

With the binding migration just landed, near-term releases are likely to address fallout from it alongside continued fixes in the same trimming and residual-variance code.

Alternatives to detectseparation and susier

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 detectseparation or susier.

See all detectseparation alternatives → · See all susier alternatives →

Recent activity from detectseparation and susier

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

  1. 3mo agodetectseparationdetectseparation v0.4
  2. 3mo agosusierMigrates C++ bindings from Rcpp to cpp11 and cpp11armadillo
  3. 3mo agosusierFixes alpha0/beta0 handling under Servin-Stephens
  4. 4mo agosusierCorrects the null space ELBO term for RSS with X
  5. 5mo agosusierFixes null effect trimming with non-uniform prior weights
  6. 5mo agosusierFixes null effect trimming under Servin-Stephens estimation
  7. 3y agodetectseparationdetectseparation v0.3
  8. 5y agodetectseparationdetectseparation v0.2

Frequently asked questions

What is the difference between detectseparation and susier?

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

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

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

What are the best alternatives to susier?

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