← Back to home
Comparison · Infra & APIs

contagionchannels vs simDAG

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

Shared themes:r-package

contagionchannels vs simDAG: at a glance

FeaturecontagionchannelssimDAG
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themeseconometrics, contagion-analysis, cran-submission, r-packager-package, causal-inference, dag-simulation, discrete-event-simulation
Last editorial update1h ago1d ago
WebsiteVisit →Visit →

What is contagionchannels?

Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.

contagionchannels reached CRAN on 2026-05-08 with a methodology preprint behind it and a cross-quantilogram lineage visible in its citations. What the release feed does not contain is any description of what the package computes: all three entries document the submission process — a licence field reduced from GPL-3 plus file to plain GPL-3, an arXiv reference rewritten in canonical DOI form, and a base-graphics fallback adjusted on a reviewer's request.

Read the full contagionchannels 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 →

contagionchannels vs simDAG: editorial side-by-side

C
contagionchannels
INFRA · APIS
0.0

Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.

◆ Current state

contagionchannels reached CRAN on 2026-05-08 with a methodology preprint behind it and a cross-quantilogram lineage visible in its citations. What the release feed does not contain is any description of what the package computes: all three entries document the submission process — a licence field reduced from GPL-3 plus file to plain GPL-3, an arXiv reference rewritten in canonical DOI form, and a base-graphics fallback adjusted on a reviewer's request.

◆ Where it's heading

There is no product trajectory to read here yet, only a submission one, and it is unusually well documented — each entry names the reviewer or check that prompted it and quotes the feedback verbatim. That transparency is the one signal available: the maintainer treats review rounds as releases worth publishing rather than squashing. Any judgement about direction will have to wait for a release that changes the package rather than its metadata.

◆ Prediction

With CRAN acceptance secured, the next release should be the first to carry actual methodological content; until one appears, there is not enough in these entries to say where the package is heading.

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 contagionchannels 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 contagionchannels or simDAG.

See all contagionchannels alternatives → · See all simDAG alternatives →

Recent activity from contagionchannels and simDAG

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

  1. 19d agosimDAGCRAN-retention patch for upstream lme4 breakage
  2. 3mo agosimDAGArbitrary baseline hazards connect node_cox() to discrete-event sims
  3. 3mo agocontagionchannelsv0.1.3 — first CRAN release
  4. 3mo agocontagionchannelsv0.1.2: switch arXiv reference in DESCRIPTION to canonical DOI form
  5. 3mo agocontagionchannelsv0.1.1: address CRAN reviewer feedback (License) + add arXiv reference
  6. 4mo agosimDAGTest-only fix for an upstream simr update
  7. 5mo agosimDAGAdds node_polr() for ordinal outcomes and rsurv node support
  8. 7mo agosimDAGAdds continuous-time discrete-event simulation
  9. 10mo agosimDAGAdds link functions to node types and fixes a broken seed default

Frequently asked questions

What is the difference between contagionchannels and simDAG?

Both compete on the same themes — r-package — within Infra & APIs. simDAG is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 contagionchannels better than simDAG?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. simDAG is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to contagionchannels?

Top contagionchannels alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "contagionchannels alternatives" section above for the current picks, or visit /alternatives/contagionchannels 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.