tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
Comparison · Analytics
errors vs vellum
A side-by-side editorial comparison of errors and vellum — release velocity, themes, recent moves, and the top alternatives to consider.
errors vs vellum: at a glance
What is errors?
errors keeps making uncertainty print the way each scientific field expects.
errors attaches uncertainty to numeric vectors and propagates it automatically through arithmetic, as part of the r-quantities family alongside units. The propagation core is settled; recent releases concentrate on presentation and integration — PDG rounding rules in 0.4.2, decimal support in parenthesis notation in 0.4.3, and ggplot2 deprecation tracking in 0.4.1 and 0.4.4.
What is vellum?
vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
errors vs vellum: editorial side-by-side
errors
0.0ANALYTICS
errors keeps making uncertainty print the way each scientific field expects.
◆ Current state
errors attaches uncertainty to numeric vectors and propagates it automatically through arithmetic, as part of the r-quantities family alongside units. The propagation core is settled; recent releases concentrate on presentation and integration — PDG rounding rules in 0.4.2, decimal support in parenthesis notation in 0.4.3, and ggplot2 deprecation tracking in 0.4.1 and 0.4.4.
◆ Where it's heading
Two threads run through this history. One is formatting convergence: uncertainty has field-specific conventions, and the package has been absorbing them one contributed pull request at a time rather than imposing a single style. The other is keeping the errors class first-class everywhere R users work — vctrs methods for dplyr 1.0, a geom_errors() layer for ggplot2, missing-value and duplicate handling. Both are integration work, which is what a type-extension package mostly is.
◆ Prediction
Expect further formatting conventions to arrive as contributions, following PDG rounding and the decimals option, plus continued upkeep against ggplot2 aesthetic deprecations that have forced two of the last four releases.
vellum
5.0ANALYTICS
vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.
◆ Current state
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
◆ Where it's heading
The pivotal detail is stated outright in 0.6.3 — the first bug in the series found by using the engine from vellumplot rather than testing it in isolation. Every release since names the downstream as the source: the contrast rule's false positives, the lint rules that fired on all five sample plots, the keyed roundrect batch. A rendering engine with a real grammar built on top of it is now getting the integration coverage that unit tests structurally cannot provide, and the fixes are converging on one theme: the measurement path and the draw path must not drift.
◆ Prediction
Expect the release rate to fall as the vellumplot integration surface is exhausted, with remaining work concentrated in the lint rule set now that it is meant to gate builds rather than just inform.
Alternatives to errors and vellum
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 errors or vellum.
tern.mmrm
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
ggmagnify
A single-purpose ggplot2 inset tool, refining the same three arguments.
symengine
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools
gtfstools stopped guarding its own object model and started accepting everyone else's.
quantities
The glue package that makes R carry units and uncertainty through the same calculation.
See all errors alternatives → · See all vellum alternatives →
Recent activity from errors and vellum
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11d agovellumLinter grows to 20 rules and stops firing on every plot
- 13d agovellumAnimated SVGs no longer blink once and vanish or play in reverse
- 14d agovellumPick table now reports device pixels instead of two coordinate systems
- 15d agovellumContrast rule stops flagging every plot; gridlines become PDF artifacts
- 15d agovellumgrobwidth and grobheight now measure wrapped text, not the unwrapped line
- 15d agovellumKeyed roundrect becomes a real batch after downstream integration exposes it
- 1y agoerrorserrors 0.4.4 replaces deprecated geom_errorbarh()
- 1y agoerrorserrors 0.4.3 supports decimals in parenthesis notation
- 2y agoerrorserrors 0.4.2 adds PDG rounding rules
- 2y agoerrorserrors 0.4.1 handles missing values, fixes na.rm
- 3y agoerrorserrors 0.4.0 adds geom_errors() for automatic errorbars
- 5y agoerrorserrors 0.3.6
Frequently asked questions
What is the difference between errors and vellum?
They serve adjacent needs but don't currently overlap on shipped themes. vellum is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is errors better than vellum?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vellum is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to errors?
Top errors alternatives in Analytics are ranked by recent ship velocity. Browse the "errors alternatives" section above for the current picks, or visit /alternatives/errors-r for the full list with editorial commentary on each.
What are the best alternatives to vellum?
Top vellum alternatives in Analytics are ranked by recent ship velocity. Browse the "vellum alternatives" section above for the current picks, or visit /alternatives/vellum-r for the full list with editorial commentary on each.