cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
Comparison · Analytics
BORG vs enderecobr
A side-by-side editorial comparison of BORG and enderecobr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
BORG vs enderecobr: at a glance
What is BORG?
A cross-validation guard that refuses to run random CV on dependent data unless you insist
BORG detects spatial, temporal and clustered dependence in a modelling dataset and generates a cross-validation scheme that respects it — spatial blocks, temporal blocks, group folds — rather than letting random splits leak information between train and test. Its distinguishing choice is enforcement: when it finds dependence, random CV is blocked outright and needs an explicit allow_random=TRUE to proceed. The package also wraps the standard rsample and caret entry points so the guard applies inside existing workflows.
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.
BORG vs enderecobr: editorial side-by-side
BORG
0.0ANALYTICS
A cross-validation guard that refuses to run random CV on dependent data unless you insist
◆ Current state
BORG detects spatial, temporal and clustered dependence in a modelling dataset and generates a cross-validation scheme that respects it — spatial blocks, temporal blocks, group folds — rather than letting random splits leak information between train and test. Its distinguishing choice is enforcement: when it finds dependence, random CV is blocked outright and needs an explicit allow_random=TRUE to proceed. The package also wraps the standard rsample and caret entry points so the guard applies inside existing workflows.
◆ Where it's heading
The entire visible history is a single day, and the sequence within it is coherent rather than churn: enforcement first, then the evidence layer, then framework integration, then idiomatic R polish. The evidence work matters to the pitch — borg_compare_cv() runs random against blocked CV so users see the inflation on their own data instead of taking the warning on faith, and the methods-text and certificate exports are aimed squarely at getting this into published papers. By the final release the interface has been rebuilt on standard S3 plot and summary methods.
◆ Prediction
The wrappers so far cover rsample and caret; tidymodels and mlr3 are the obvious remaining entry points if the guard is to reach the workflows it hasn't yet intercepted.
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 BORG 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 BORG 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 BORG alternatives → · See all enderecobr alternatives →
Recent activity from BORG and enderecobr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7mo agoenderecobrStandardisation functions rewritten in Rust ⚡
- 7mo agoBORGInterface rebuilt on standard S3 plot and summary methods
- 7mo agoBORGGuarded wrappers for rsample and caret splitting functions
- 7mo agoBORGEmpirical inflation comparison and publication-ready reporting
- 7mo agoBORGRandom CV blocked by default when dependence is detected ⚡
- 7mo agoBORGVersion bump to 0.1.1
- 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
Frequently asked questions
What is the difference between BORG and enderecobr?
Both compete on the same themes — r-package — within Analytics. BORG 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 BORG better than enderecobr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BORG 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 BORG?
Top BORG alternatives in Analytics are ranked by recent ship velocity. Browse the "BORG alternatives" section above for the current picks, or visit /alternatives/borg 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.