MetaboAnalystR
The R engine behind MetaboAnalyst closes the gap from raw spectra to biological interpretation
Comparison · Analytics
cIRT vs enderecobr
A side-by-side editorial comparison of cIRT and enderecobr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
cIRT vs enderecobr: at a glance
What is cIRT?
A choice-based IRT model published once in 2019 and kept compiling ever since
cIRT implements Choice Item Response Theory, jointly modelling which item a respondent picks and how they perform on it — the setting where subjects choose between a harder and an easier question and the choice itself carries information. It comes out of the TMSA Lab, is built on Rcpp and RcppArmadillo, and has had one substantive release since reaching CRAN. Everything after early 2019 is build-system and toolchain upkeep.
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.
cIRT vs enderecobr: editorial side-by-side
cIRT
0.0ANALYTICS
A choice-based IRT model published once in 2019 and kept compiling ever since
◆ Current state
cIRT implements Choice Item Response Theory, jointly modelling which item a respondent picks and how they perform on it — the setting where subjects choose between a harder and an easier question and the choice itself carries information. It comes out of the TMSA Lab, is built on Rcpp and RcppArmadillo, and has had one substantive release since reaching CRAN. Everything after early 2019 is build-system and toolchain upkeep.
◆ Where it's heading
The package's whole functional history fits in a two-day window in January 2019, when the CRAN release and its immediate follow-ups were tagged in one batch, followed a day later by a release enabling C++11 and OpenMP and fixing the choice generation procedure. Since then the releases track other people's deprecations: Armadillo dropping conversions, RcppArmadillo requiring a different Makevars, R raising its floor. The 2025 release is entirely of that kind, down to swapping the README to Quarto.
◆ Prediction
The dependency floors were just raised to current Rcpp and RcppArmadillo, so the next release is most likely the one after Armadillo deprecates something else.
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 cIRT 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 cIRT or enderecobr.
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
dcurves
Decision curve analysis, settled since 2022 and now moving only when its neighbours do
See all cIRT alternatives → · See all enderecobr alternatives →
Recent activity from cIRT and enderecobr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7mo agoenderecobrStandardisation functions rewritten in Rust ⚡
- 10mo agocIRTArmadillo deprecations cleared, build config modernised
- 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
- 4y agocIRTperson() argument fix and dependency floor raise
- 6y agocIRTpkgdown site added, CI moved to GitHub Actions
- 7y agocIRTOpenMP enabled and the choice generation bug fixed
- 7y agocIRTcIRT 1.0.0: Initial Package Released to CRAN
- 7y agocIRTChoice matrix gains hard and easy question ids
Frequently asked questions
What is the difference between cIRT and enderecobr?
Both compete on the same themes — r-package — within Analytics. cIRT 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 cIRT better than enderecobr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cIRT 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 cIRT?
Top cIRT alternatives in Analytics are ranked by recent ship velocity. Browse the "cIRT alternatives" section above for the current picks, or visit /alternatives/cirt 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.