← Back to home
Comparison · Infra & APIs

cvms vs simDAG

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

Shared themes:r-package

cvms vs simDAG: at a glance

FeaturecvmssimDAG
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themescross-validation, r-package, model-evaluation, visualizationr-package, causal-inference, dag-simulation, discrete-event-simulation
Last editorial update59m ago2h ago
WebsiteVisit →Visit →

What is cvms?

A cross-validation package whose real development has moved to its plotting function

cvms runs repeated cross-validation over model formulas and reports comparable metrics. The 2.0.0 release was a breaking correctness fix: every function accepting fold_cols mismatched training and testing data when fold indices were non-sequential, did not start at 1, or were strings, because the iteration index was compared against the raw fold value rather than its factor level index. 2.0.1 restored coefficient extraction for nnet::multinom and mixed models by supplying an environment containing the training data, and followed lme4's move of findbars() into the reformulas package.

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

cvms vs simDAG: editorial side-by-side

C
cvms
INFRA · APIS
0.0

A cross-validation package whose real development has moved to its plotting function

◆ Current state

cvms runs repeated cross-validation over model formulas and reports comparable metrics. The 2.0.0 release was a breaking correctness fix: every function accepting fold_cols mismatched training and testing data when fold indices were non-sequential, did not start at 1, or were strings, because the iteration index was compared against the raw fold value rather than its factor level index. 2.0.1 restored coefficient extraction for nnet::multinom and mixed models by supplying an environment containing the training data, and followed lme4's move of findbars() into the reformulas package.

◆ Where it's heading

Two threads run in parallel and only one is about cross-validation. The plotting function plot_confusion_matrix() has absorbed most feature work since 1.5.0 - custom gradient palettes, intensity limits, per-tile settings, dynamic font colors keyed to value thresholds, and arguments that accept functions rather than constants - to the point where a companion web application exists for using it without code. The cross-validation core, by contrast, sees maintenance: upstream compatibility fixes for pROC, ggnewscale and ggplot2, and the fold-matching correction that finally forced a major version.

◆ Prediction

Expect continued option growth in the confusion matrix plotting surface, since that is where nearly every release since 1.5.0 has spent its changes, with core cross-validation changes arriving only as upstream packages force them.

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

See all cvms alternatives → · See all simDAG alternatives →

Recent activity from cvms and simDAG

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

  1. 18d agosimDAGCRAN-retention patch for upstream lme4 breakage
  2. 2mo agocvmsCoefficient extraction restored for multinom and mixed models
  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. 9mo agocvmsBreaking fix for mismatched folds with non-sequential fold IDs
  8. 10mo agosimDAGAdds link functions to node types and fixes a broken seed default
  9. 11mo agocvmsTest compatibility with pROC 1.19 and a deprecation warning fix
  10. 1y agocvmsConfusion matrix fonts and colors can now be computed from the values
  11. 1y agocvmsTile intensity by row or column percentages
  12. 1y agocvmsMultinom coefficient extraction fix after a parameters update

Frequently asked questions

What is the difference between cvms 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 cvms 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 cvms?

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