exametrika
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
Comparison · Infra & APIs
nuggets vs simDAG
A side-by-side editorial comparison of nuggets and simDAG — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
nuggets vs simDAG: at a glance
What is nuggets?
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
nuggets searches for association rules, contrasts and other conditional patterns in the GUHA tradition, with a C++ core behind dig() and an interactive explore() app for reading results. Since the 2.0 rewrite of that core, every release has widened the same three surfaces: more pattern families to mine, more of explore() to inspect them in, and steady performance work underneath. The most recent tag optimises dig() on sparse crisp data with a sparse bit chain and adds clustering characteristics to explore() for association rules.
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.
nuggets vs simDAG: editorial side-by-side
nuggets
2.5INFRA · APIS
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
◆ Current state
nuggets searches for association rules, contrasts and other conditional patterns in the GUHA tradition, with a C++ core behind dig() and an interactive explore() app for reading results. Since the 2.0 rewrite of that core, every release has widened the same three surfaces: more pattern families to mine, more of explore() to inspect them in, and steady performance work underneath. The most recent tag optimises dig() on sparse crisp data with a sparse bit chain and adds clustering characteristics to explore() for association rules.
◆ Where it's heading
Two forces are shaping the package. One is coverage: baseline, complement and paired-baseline contrasts, correlations, tautologies, ancestors and clustering have all been added as first-class dig_ or explore_ surfaces, so the same search engine now answers a widening set of questions. The other is weight — Shiny packages moved from Imports to Suggests, BH and RcppThread dropped, XSIMD updated, parse_condition() rewritten in C++ — which keeps a package with an interactive app from forcing that app's dependencies on every user. Deprecations are handled through lifecycle rather than removed abruptly.
◆ Prediction
Expect the sparse-data optimisation to extend from crisp to fuzzy data, and explore() to keep gaining tabs as each new pattern family lands, on the roughly six-week cadence the 2.2 line has held.
simDAG
2.5INFRA · APIS
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 nuggets 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 nuggets or simDAG.
projoint
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
lifecontingencies
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
EDAForge
EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.
See all nuggets alternatives → · See all simDAG alternatives →
Recent activity from nuggets and simDAG
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 19d agosimDAGCRAN-retention patch for upstream lme4 breakage
- 27d agonuggetsSparse bit chain speeds dig(); explore() gains clustering
- 2mo agonuggetspartition() gains .subsets; geom_diamond() layout improved
- 3mo agosimDAGArbitrary baseline hazards connect node_cox() to discrete-event sims
- 4mo agosimDAGTest-only fix for an upstream simr update
- 5mo agonuggetsexplore() covers contrasts and correlations; dig_ancestors() added
- 5mo agosimDAGAdds node_polr() for ordinal outcomes and rsurv node support
- 6mo agonuggetsCritical explore() bug fixed; is_logicalish() added
- 6mo agonuggetsShiny deps moved to Suggests; BH and RcppThread dropped
- 7mo agosimDAGAdds continuous-time discrete-event simulation ⚡
- 8mo agonuggetscluster_associations() and add_interest() arrive; C++ condition parser
- 10mo agosimDAGAdds link functions to node types and fixes a broken seed default
Frequently asked questions
What is the difference between nuggets and simDAG?
Both compete on the same themes — r-package — within Infra & APIs. nuggets 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 nuggets better than simDAG?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nuggets 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 nuggets?
Top nuggets alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "nuggets alternatives" section above for the current picks, or visit /alternatives/nuggets 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.