cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
Comparison · Analytics
DHARMa vs enderecobr
A side-by-side editorial comparison of DHARMa and enderecobr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
DHARMa vs enderecobr: 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 enderecobr?
Brazilian address standardisation moves its core to Rust, betting on throughput over pure R
enderecobr standardises Brazilian address fields — street types, neighbourhoods, states, postcodes, house numbers — into consistent forms so records from different registries can be compared. It comes out of the ipeaGIT ecosystem and its API is a family of padronizar_* functions plus one padronizar_enderecos() that runs them together. The 0.5.0 release rewrote those standardisation functions in Rust with a documented speedup.
DHARMa vs enderecobr: 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.
enderecobr
0.0ANALYTICS
Brazilian address standardisation moves its core to Rust, betting on throughput over pure R
◆ Current state
enderecobr standardises Brazilian address fields — street types, neighbourhoods, states, postcodes, house numbers — into consistent forms so records from different registries can be compared. It comes out of the ipeaGIT ecosystem and its API is a family of padronizar_* functions plus one padronizar_enderecos() that runs them together. The 0.5.0 release rewrote those standardisation functions in Rust with a documented speedup.
◆ Where it's heading
Two years of releases were about control and correctness: new formato arguments letting callers choose state names or abbreviations, integers or characters for house numbers, and a run of fixes for numbers mangled by thousands separators. That work settled the semantics. With the behaviour pinned down, the Rust rewrite becomes the natural next move, and the release pairs it with new matching rules for the two messiest fields, neighbourhoods and street names.
◆ Prediction
The rewrite covers the standardisation functions specifically, so the remaining pure-R paths around them are the likely next targets, alongside continued rule additions for street and neighbourhood variants.
Alternatives to DHARMa and enderecobr
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 enderecobr.
MetaboAnalystR
The R engine behind MetaboAnalyst closes the gap from raw spectra to biological interpretation
fmtr
Rebuilding SAS's formatting layer in R, one format specification at a time
betaselectr
Standardised coefficients for models where standardising everything is wrong — but the feed only links out
SSN2
Stream-network spatial models learning to run on data that no longer fits in memory
BiocManager
Bioconductor's installer, frozen at 1.30.x and tuned almost entirely through environment variables
See all DHARMa alternatives → · See all enderecobr alternatives →
Recent activity from DHARMa and enderecobr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agoDHARMaConditional simulation becomes the GLMM default, changing residuals ⚡
- 7mo agoenderecobrStandardisation functions rewritten in Rust ⚡
- 1y agoenderecobrNamespaced calls no longer error on internal warnings
- 1y agoenderecobrHouse numbers gain output format control, thousands-separator bug fixed
- 1y agoenderecobrStates can be standardised to full names or abbreviations
- 1y agoenderecobrAuthor added to package metadata
- 1y agoenderecobrStreet-type functions added and output columns given a naming convention
- 1y agoDHARMaDHARMa 0.4.7
- 3y agoDHARMaDHARMa 0.4.6
- 4y agoDHARMaDHARMa 0.4.5
- 4y agoDHARMaDHARMa 0.4.4
- 5y agoDHARMaDHARMa 0.4.3
Frequently asked questions
What is the difference between DHARMa and enderecobr?
Both compete on the same themes — r-package — within Analytics. DHARMa and enderecobr 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 enderecobr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DHARMa and enderecobr 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 enderecobr?
Top enderecobr alternatives in Analytics are ranked by recent ship velocity. Browse the "enderecobr alternatives" section above for the current picks, or visit /alternatives/enderecobr for the full list with editorial commentary on each.