← Back to home
Comparison · Analytics

rjdqa vs vellum

A side-by-side editorial comparison of rjdqa and vellum — release velocity, themes, recent moves, and the top alternatives to consider.

rjdqa vs vellum: at a glance

Featurerjdqavellum
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesofficial-statistics, seasonal-adjustment, quality-assurance, r-packager-graphics, rendering-engine, linting, accessibility
Last editorial update57m ago4h ago
WebsiteVisit →Visit →

What is rjdqa?

rjdqa keeps refining one screen: the seasonal adjustment quality dashboard

rjdqa builds quality assessment dashboards for seasonal adjustment models produced by JDemetra+, aimed at official statisticians reviewing adjusted series. Essentially all development goes into two functions, simple_dashboard() and its denser variant simple_dashboard2(). Version 0.1.6 adds parameters to append observations to the forecast and to control whether the residual trading-days test is printed, defaulting to monthly series only, plus outlier table layout work and user-defined calendar regressor support in sc_dashboard().

Read the full rjdqa trajectory →

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.

Read the full vellum trajectory →

rjdqa vs vellum: editorial side-by-side

R
rjdqa
ANALYTICS
0.0

rjdqa keeps refining one screen: the seasonal adjustment quality dashboard

◆ Current state

rjdqa builds quality assessment dashboards for seasonal adjustment models produced by JDemetra+, aimed at official statisticians reviewing adjusted series. Essentially all development goes into two functions, simple_dashboard() and its denser variant simple_dashboard2(). Version 0.1.6 adds parameters to append observations to the forecast and to control whether the residual trading-days test is printed, defaulting to monthly series only, plus outlier table layout work and user-defined calendar regressor support in sc_dashboard().

◆ Where it's heading

The package has converged on a single deliverable and is tuning it against reviewer practice. Each release adds a parameter that lets the analyst include or exclude one element of the dashboard, or adjusts how densely information is packed into the fixed space of the layout. The td_effect default — print the test only for monthly series — is characteristic: the knowledge about when a diagnostic is meaningful is being encoded into the tool rather than left to the reader.

◆ Prediction

The pattern of adding one toggle per diagnostic per release points at the same thing again, most likely another test given a conditional default, rather than a new dashboard function alongside the two that exist.

V
vellum
ANALYTICS
5.0

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 rjdqa 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 rjdqa or vellum.

See all rjdqa alternatives → · See all vellum alternatives →

Recent activity from rjdqa and vellum

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 11d agovellumLinter grows to 20 rules and stops firing on every plot
  2. 13d agovellumAnimated SVGs no longer blink once and vanish or play in reverse
  3. 14d agovellumPick table now reports device pixels instead of two coordinate systems
  4. 15d agovellumContrast rule stops flagging every plot; gridlines become PDF artifacts
  5. 15d agovellumgrobwidth and grobheight now measure wrapped text, not the unwrapped line
  6. 15d agovellumKeyed roundrect becomes a real batch after downstream integration exposes it
  7. 9mo agorjdqaForecast observations and conditional trading-days test in dashboards
  8. 1y agorjdqaFix tail() usage on ts objects
  9. 2y agorjdqaFix dependency minimums and outlier ordering
  10. 2y agorjdqasimple_dashboard2() added; deprecated sa_dashboard() removed
  11. 2y agorjdqasimple_dashboard() introduced; sa_dashboard() deprecated
  12. 7y agorjdqaFirst CRAN release

Frequently asked questions

What is the difference between rjdqa 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 rjdqa 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 rjdqa?

Top rjdqa alternatives in Analytics are ranked by recent ship velocity. Browse the "rjdqa alternatives" section above for the current picks, or visit /alternatives/rjdqa-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.