← Back to home
Comparison · Infra & APIs

missSBM vs simDAG

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

Shared themes:r-package

missSBM vs simDAG: at a glance

FeaturemissSBMsimDAG
SectorInfra & APIsInfra & APIs
Velocity score2.52.5
Sparks · 30d00
Top themesr-package, network-analysis, stochastic-block-model, missing-datar-package, causal-inference, dag-simulation, discrete-event-simulation
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is missSBM?

missSBM returns after four dormant years with a stricter API and a new refinement step.

The package fits stochastic block models to networks with missing data, covering both missing-at-random and informative sampling designs. After a run of releases from 2019 to 2022, the feed goes quiet until this year's 1.1.0, which breaks the control interface, exposes the block split and merge operations as testable instance methods, and adds a node-swap refinement pass that runs after variational convergence.

Read the full missSBM trajectory →

What is simDAG?

simDAG grew a second simulation engine, then spent two releases surviving upstream breakage.

simDAG generates data from directed acyclic graphs, with a library of node types covering Gaussian, binomial, Poisson, negative binomial, zero-inflated, ordered regression, Cox, and Aalen models. The 1.0.0 milestone opened node_cox() to arbitrary baseline hazard functions, which lets continuous time-dependent hazards drive discrete-event simulations. The two most recent releases exist only to keep the package on CRAN through breakage in lme4 and simr.

Read the full simDAG trajectory →

missSBM vs simDAG: editorial side-by-side

M
missSBM
INFRA · APIS
2.5

missSBM returns after four dormant years with a stricter API and a new refinement step.

◆ Current state

The package fits stochastic block models to networks with missing data, covering both missing-at-random and informative sampling designs. After a run of releases from 2019 to 2022, the feed goes quiet until this year's 1.1.0, which breaks the control interface, exposes the block split and merge operations as testable instance methods, and adds a node-swap refinement pass that runs after variational convergence.

◆ Where it's heading

The new release is maintenance-driven in the best sense: it targets the parts of the codebase that were hard to test or easy to misuse. Replacing free-form control lists with a function of named, defaulted arguments turns silent typos into errors, and pulling the exploration logic out of the collection class makes the search algorithm independently testable without changing it. The polish step addresses a known weakness, reaching individually misclassified nodes that split and merge moves cannot fix.

◆ Prediction

Given the gap before this release, the near-term question is whether the cadence resumes at all; the refactoring it contains would support further algorithmic work if it does.

S
simDAG
INFRA · APIS
2.5

simDAG grew a second simulation engine, then spent two releases surviving upstream breakage.

◆ Current state

simDAG generates data from directed acyclic graphs, with a library of node types covering Gaussian, binomial, Poisson, negative binomial, zero-inflated, ordered regression, Cox, and Aalen models. The 1.0.0 milestone opened node_cox() to arbitrary baseline hazard functions, which lets continuous time-dependent hazards drive discrete-event simulations. The two most recent releases exist only to keep the package on CRAN through breakage in lme4 and simr.

◆ Where it's heading

The package has been widening what a simulation can represent rather than deepening any one node. Networks arrived in 0.4.0 so individuals could depend on each other, discrete-event simulation in continuous time arrived in 0.5.0 as an alternative to the discrete-time engine, and 1.0.0 connected the two by letting continuous hazards feed the event-driven path. Alongside that, node types keep accumulating for outcome families the framework could not previously generate.

◆ Prediction

Expect the node library to keep expanding into outcome types the discrete-event engine can now support, though the recent releases suggest upstream dependency churn will keep consuming release slots.

Alternatives to missSBM and simDAG

Other Infra & APIs 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 missSBM or simDAG.

See all missSBM alternatives → · See all simDAG alternatives →

Recent activity from missSBM and simDAG

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

  1. 18d agosimDAGCRAN-retention patch for upstream lme4 breakage
  2. 26d agomissSBMReplaces raw control lists with missSBM_param(), adds polish()
  3. 3mo agosimDAGArbitrary baseline hazards connect node_cox() to discrete-event sims
  4. 4mo agosimDAGTest-only fix for an upstream simr update
  5. 5mo agosimDAGAdds node_polr() for ordinal outcomes and rsurv node support
  6. 7mo agosimDAGAdds continuous-time discrete-event simulation
  7. 10mo agosimDAGAdds link functions to node types and fixes a broken seed default
  8. 3y agomissSBMAdapts to Matrix 1.4-2 and fixes HTML5 documentation
  9. 4y agomissSBMFixes linking against nloptR 2.0.0
  10. 5y agomissSBMRelaxes CRAN test tolerances to avoid random failures
  11. 5y agomissSBMRewrites optimisation in C++ armadillo with sparse matrices
  12. 5y agomissSBMRenames core functions and interfaces with the sbm package

Frequently asked questions

What is the difference between missSBM and simDAG?

Both compete on the same themes — r-package — within Infra & APIs. missSBM and simDAG are shipping at a similar cadence (velocity 2.5 vs 2.5, 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 missSBM better than simDAG?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. missSBM and simDAG are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to missSBM?

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

What are the best alternatives to simDAG?

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