compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
Comparison · Analytics
DHARMa vs kwb.geosalz
A side-by-side editorial comparison of DHARMa and kwb.geosalz — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
DHARMa vs kwb.geosalz: at a glance
What is DHARMa?
DHARMa changed how GLMM residuals are simulated, so the same code now returns different numbers.
DHARMa generates scaled quantile residuals for fitted GLMMs and runs the dispersion, uniformity, and autocorrelation tests built on them. Version 0.5.0 changed the default simulation for hierarchical models from the model's own default, mostly unconditional, to conditional simulation, and states plainly that residuals will differ from those computed by older versions. The same release added brms to the supported model set and reworked how predictors are passed to plotting and testing functions.
What is kwb.geosalz?
A research-project workflow package where the interesting work is in the plumbing.
kwb.geosalz documents the data workflows for GeoSalz, a groundwater salinisation project run by Kompetenzzentrum Wasser Berlin, packaging retrieval, checking and plotting steps as reproducible R code. The current release replaces an SFTP dependency with curl and reports listing files on the SFTP server running 50 to 100 times faster. Earlier releases added data-availability workflows against Berlin's open water portal and functions for well-field abstraction figures.
DHARMa vs kwb.geosalz: editorial side-by-side
DHARMa
0.0ANALYTICS
DHARMa changed how GLMM residuals are simulated, so the same code now returns different numbers.
◆ Current state
DHARMa generates scaled quantile residuals for fitted GLMMs and runs the dispersion, uniformity, and autocorrelation tests built on them. Version 0.5.0 changed the default simulation for hierarchical models from the model's own default, mostly unconditional, to conditional simulation, and states plainly that residuals will differ from those computed by older versions. The same release added brms to the supported model set and reworked how predictors are passed to plotting and testing functions.
◆ Where it's heading
The package has spent several releases widening which model backends it can diagnose, from glmmTMB through mgcv, phylolm and now brms, while methodological work has gone into handling correlated residuals via the rotation argument. Version 0.5.0 shifts from adding coverage to changing defaults for statistical power. The formula interface arriving across plotResiduals, testCategorical, testQuantiles and the autocorrelation tests suggests the API is being unified rather than extended function by function.
◆ Prediction
The next releases will likely broaden brms support past the simple-model restriction and continue converting remaining functions to the formula interface.
kwb.geosalz
0.0ANALYTICS
A research-project workflow package where the interesting work is in the plumbing.
◆ Current state
kwb.geosalz documents the data workflows for GeoSalz, a groundwater salinisation project run by Kompetenzzentrum Wasser Berlin, packaging retrieval, checking and plotting steps as reproducible R code. The current release replaces an SFTP dependency with curl and reports listing files on the SFTP server running 50 to 100 times faster. Earlier releases added data-availability workflows against Berlin's open water portal and functions for well-field abstraction figures.
◆ Where it's heading
Releases track the project's own data-collection reality rather than a software roadmap: new data source appears, a workflow is added; a transfer library becomes a liability, it is swapped out. The measurement-chain pipeline is the recurring subject, appearing in plotting fixes at 0.7.1 and the transport rewrite at 0.7.2. Cadence is roughly annual and the changelog is written for project members, which makes external readability secondary by design.
◆ Prediction
Expect the next release to follow the measurement-chain data as it accumulates, most likely more plotting or availability-checking work rather than new infrastructure.
Alternatives to DHARMa and kwb.geosalz
Other Analytics 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 DHARMa or kwb.geosalz.
nabla
nabla dropped its C++ engine to chase exact derivatives at any order.
snowflakeauth
Eight months from first release to keyring caching and workload identity.
cyclocomp
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
revdbayes
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
lazyeval
A package retired in 2017 just got rewritten against R's public C API.
See all DHARMa alternatives → · See all kwb.geosalz alternatives →
Recent activity from DHARMa and kwb.geosalz
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agoDHARMaConditional simulation becomes the GLMM default, changing residuals ⚡
- 5mo agokwb.geosalzSFTP transfers moved to curl, file listing 50-100x faster
- 1y agokwb.geosalzConductivity outliers filtered from measurement chain plots
- 1y agoDHARMaDHARMa 0.4.7
- 2y agokwb.geosalzRelease rolling up vignette cleanup and well operation work
- 3y agoDHARMaDHARMa 0.4.6
- 4y agokwb.geosalzWasserportal Berlin workflow and CRS conversion added
- 4y agokwb.geosalzAnnual well-field abstraction figures retrievable
- 4y agoDHARMaDHARMa 0.4.5
- 4y agoDHARMaDHARMa 0.4.4
- 5y agoDHARMaDHARMa 0.4.3
- 7y agokwb.geosalzInitial release scaffolded from the in-house package template
Frequently asked questions
What is the difference between DHARMa and kwb.geosalz?
Both compete on the same themes — r-package — within Analytics. DHARMa and kwb.geosalz are shipping at a similar cadence (velocity 0.0 vs 0.0, 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 DHARMa better than kwb.geosalz?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DHARMa and kwb.geosalz are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to DHARMa?
Top DHARMa alternatives in Analytics are ranked by recent ship velocity. Browse the "DHARMa alternatives" section above for the current picks, or visit /alternatives/dharma for the full list with editorial commentary on each.
What are the best alternatives to kwb.geosalz?
Top kwb.geosalz alternatives in Analytics are ranked by recent ship velocity. Browse the "kwb.geosalz alternatives" section above for the current picks, or visit /alternatives/kwb-geosalz for the full list with editorial commentary on each.