HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
A side-by-side editorial comparison of ltertools and simDAG — release velocity, themes, recent moves, and the top alternatives to consider.
A column-key toolkit for stitching decades of ecological field data into one table.
ltertools serves the Long Term Ecological Research network, where the same measurement carries a different column name at every site and in every era. Its core is a column key: begin_key drafts one, harmonize applies it, and the 2.0.0 release added check_key to validate a key and standardize to apply one to a single dataset. Harmonization of files above 5 MB now runs in roughly half the time.
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.
ltertools serves the Long Term Ecological Research network, where the same measurement carries a different column name at every site and in every era. Its core is a column key: begin_key drafts one, harmonize applies it, and the 2.0.0 release added check_key to validate a key and standardize to apply one to a single dataset. Harmonization of files above 5 MB now runs in roughly half the time.
Development has moved from breadth to depth. The first year added assorted utilities — temperature conversion, solar day length, a site timeline — while the last two releases have concentrated on the key workflow itself: incremental key expansion, validation, per-dataset application, and speed. A dependency archival forced the removal of the JSON helper, trimming the package back toward that core.
The key workflow now has draft, expand, check and apply steps, so the remaining gap is diagnostics on the harmonized output; the entries show no other thread in progress.
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.
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.
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.
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 ltertools or simDAG.
France's national flood statistics, ported out of Fortran and into R.
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Fast design-based estimators for experiments, coasting on CRAN patches.
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
IP address vectors for R that hit 1.0 and then went quiet.
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
See all ltertools alternatives → · See all simDAG alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top ltertools alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ltertools alternatives" section above for the current picks, or visit /alternatives/ltertools for the full list with editorial commentary on each.
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.