← Back to home
Comparison · Analytics

aedseo vs rjdqa

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

Shared themes:r-package

aedseo vs rjdqa: at a glance

Featureaedseorjdqa
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesepidemiology, time-series, surveillance, r-packageofficial-statistics, seasonal-adjustment, quality-assurance, r-package
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is aedseo?

An epidemic-onset detector that now brackets the whole season, not just its start

aedseo is a Statens Serum Institut R package for automated early detection of seasonal epidemic onsets, built around growth-rate estimation over consecutive time intervals. The 1.0.0 line moved it well past its original scope: observations are now modelled as cases or population-adjusted incidence, multiple waves can be estimated in one pass, and disease-specific thresholds are computed by a dedicated function. Version 1.1.0 adds an estimate of when a season has ended after the first onset.

Read the full aedseo trajectory →

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 →

aedseo vs rjdqa: editorial side-by-side

A
aedseo
ANALYTICS
0.0

An epidemic-onset detector that now brackets the whole season, not just its start

◆ Current state

aedseo is a Statens Serum Institut R package for automated early detection of seasonal epidemic onsets, built around growth-rate estimation over consecutive time intervals. The 1.0.0 line moved it well past its original scope: observations are now modelled as cases or population-adjusted incidence, multiple waves can be estimated in one pass, and disease-specific thresholds are computed by a dedicated function. Version 1.1.0 adds an estimate of when a season has ended after the first onset.

◆ Where it's heading

The arc runs from a single-purpose onset detector toward a full seasonal-surveillance toolkit. Each release since 1.0.0 has widened what the package can say about a season rather than improving how it says it: incidence denominators, background population, multi-wave detection, thresholds, and now season end. Fixes in between are narrow and numerical, such as confidence intervals under ATLAS BLAS.

◆ Prediction

The natural next step is symmetry with the onset machinery the package already has: turning the 1.1.0 seasonal offset into a first-class output alongside onset, with its own summary and plotting methods.

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.

Alternatives to aedseo and rjdqa

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

See all aedseo alternatives → · See all rjdqa alternatives →

Recent activity from aedseo and rjdqa

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

  1. 6mo agoaedseocombined_seasonal_output() now estimates when a season ends
  2. 8mo agoaedseoFix growth-rate confidence intervals under ATLAS BLAS
  3. 9mo agoaedseoIncidence, population adjustment and multi-wave detection land in 1.0.0
  4. 9mo agorjdqaForecast observations and conditional trading-days test in dashboards
  5. 1y agorjdqaFix tail() usage on ts objects
  6. 2y agorjdqaFix dependency minimums and outlier ordering
  7. 2y agorjdqasimple_dashboard2() added; deprecated sa_dashboard() removed
  8. 2y agorjdqasimple_dashboard() introduced; sa_dashboard() deprecated
  9. 2y agoaedseoMaintainership transferred to Lasse Engbo Christiansen
  10. 2y agoaedseoepi_calendar() and richer autoplot displays
  11. 2y agoaedseoFirst CRAN release of the aeddo onset detector
  12. 7y agorjdqaFirst CRAN release

Frequently asked questions

What is the difference between aedseo and rjdqa?

Both compete on the same themes — r-package — within Analytics. aedseo and rjdqa 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 aedseo better than rjdqa?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. aedseo and rjdqa 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 aedseo?

Top aedseo alternatives in Analytics are ranked by recent ship velocity. Browse the "aedseo alternatives" section above for the current picks, or visit /alternatives/aedseo-r for the full list with editorial commentary on each.

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.