cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
Comparison · Analytics
common vs tulpaRatio
A side-by-side editorial comparison of common and tulpaRatio — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
common vs tulpaRatio: at a glance
What is common?
A base-R utility belt that grows one small function at a time, on no particular schedule
common collects small helpers that base R leaves out — data frame labelling and sorting, infix operators for pasting and equality, UTF-8 superscript and subscript lookups, file and directory search, attribute copying between data frames. It has no dependencies to speak of and deliberately removed the one it had. In practice it is the shared substrate for its author's wider package family, and its source.all() function is maintained specifically to cooperate with the logr logging package.
What is tulpaRatio?
A Bayesian ratio-modelling package that threw out its Stan dependency and wrote its own sampler
ratiod models ratios, rates and proportions hierarchically, with the stated position that a ratio is a derived quantity and inference should run on the latent numerator and denominator processes rather than their quotient. The 1.0.0 release shipped a native HMC/NUTS backend, removing the Stan dependency that packages in this space normally take as given. Everything since has been sampler optimisation, benchmarked against the Stan implementations it replaced.
common vs tulpaRatio: editorial side-by-side
common
0.0ANALYTICS
A base-R utility belt that grows one small function at a time, on no particular schedule
◆ Current state
common collects small helpers that base R leaves out — data frame labelling and sorting, infix operators for pasting and equality, UTF-8 superscript and subscript lookups, file and directory search, attribute copying between data frames. It has no dependencies to speak of and deliberately removed the one it had. In practice it is the shared substrate for its author's wider package family, and its source.all() function is maintained specifically to cooperate with the logr logging package.
◆ Where it's heading
The pattern is accretion rather than direction: each release adds a couple of utilities and fixes whatever the last batch broke, with gaps of a year or more between them. Function additions cluster around whatever the author's other packages needed at the time — file search, attribute preservation, group-boundary detection, script sourcing. The 2025 release continues exactly this, extending the infix comparison operators from equality alone to the full set of relational tests.
◆ Prediction
Expect more of the same shape — a handful of small helpers whenever a sibling package needs them — with no sign in these entries of a broader API push.
tulpaRatio
0.0ANALYTICS
A Bayesian ratio-modelling package that threw out its Stan dependency and wrote its own sampler
◆ Current state
ratiod models ratios, rates and proportions hierarchically, with the stated position that a ratio is a derived quantity and inference should run on the latent numerator and denominator processes rather than their quotient. The 1.0.0 release shipped a native HMC/NUTS backend, removing the Stan dependency that packages in this space normally take as given. Everything since has been sampler optimisation, benchmarked against the Stan implementations it replaced.
◆ Where it's heading
The feed reads as one architectural bet followed by the work to justify it. After the native backend landed, the releases are a steady march of gradient and adaptation work — hand-coded gradients for more model families, L-BFGS mass matrix adaptation, an O2 build — each measured as a speed multiple against Stan. Coverage is tracked openly as a fraction (48 of 60 hand-coded configs), and unresolved problems are named rather than buried, including a deferred GP spatial bug.
◆ Prediction
The hand-coded gradient coverage count is the visible backlog, so the next releases most likely close the remaining configs and resolve the GP spatial issue that the benchmark release explicitly deferred.
Alternatives to common and tulpaRatio
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 common or tulpaRatio.
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 common alternatives → · See all tulpaRatio alternatives →
Recent activity from common and tulpaRatio
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agotulpaRatioHand-coded gradients reach binomial zero-inflated and hurdle models
- 6mo agotulpaRatioGaussian process sampling reaches roughly 4x Stan
- 7mo agotulpaRatioL-BFGS mass matrix adaptation for MSGP models
- 7mo agotulpaRatioBenchmarks published for 35 of 40 model configurations
- 7mo agotulpaRatioFirst stable release ships a native HMC/NUTS backend, no Stan required ⚡
- 8mo agocommonFull set of relational infix operators added
- 2y agocommonsource.all() fixed to cooperate with logr
- 2y agocommonsource.all() added for sourcing a directory of scripts
- 2y agocommonchanged() fixed for single-value input
- 2y agocommonchanged() identifies grouping boundaries
- 3y agocommonthis.path() dependency removed
Frequently asked questions
What is the difference between common and tulpaRatio?
Both compete on the same themes — r-package — within Analytics. common and tulpaRatio 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 common better than tulpaRatio?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. common and tulpaRatio 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 common?
Top common alternatives in Analytics are ranked by recent ship velocity. Browse the "common alternatives" section above for the current picks, or visit /alternatives/common for the full list with editorial commentary on each.
What are the best alternatives to tulpaRatio?
Top tulpaRatio alternatives in Analytics are ranked by recent ship velocity. Browse the "tulpaRatio alternatives" section above for the current picks, or visit /alternatives/tulparatio for the full list with editorial commentary on each.