← Back to home
Comparison · Analytics

posterior vs timetk

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

posterior vs timetk: at a glance

Featureposteriortimetk
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesbayesian, rvar, pareto-diagnostics, r-infrastructuretime-series, anomaly-detection, visualization, feature-engineering
Last editorial update59m ago1h ago
WebsiteVisit →Visit →

What is posterior?

posterior keeps deepening two things: the rvar type and Pareto-based diagnostics.

The releases in this window advance on two fronts. The rvar random-variable type gained factor and ordered subtypes (1.4.0), rvar-indexed slicing and `rvar_ifelse()` (1.5.0), base `%*%` matrix multiplication and indexed variable names (1.6.0). Separately, Pareto diagnostics have grown from `pareto_smooth()` options and individual `pareto_khat()`-family functions (1.6.0) through `pit()` for draws and rvars (1.6.1) to exported generalized-Pareto functions and `pareto_pit` (1.7.0). 1.7.1 is a paperwork release for a JOSS submission.

Read the full posterior trajectory →

What is timetk?

timetk swallowed anomalize whole, then went quiet for two years

timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.

Read the full timetk trajectory →

posterior vs timetk: editorial side-by-side

P
posterior
ANALYTICS
0.0

posterior keeps deepening two things: the rvar type and Pareto-based diagnostics.

◆ Current state

The releases in this window advance on two fronts. The rvar random-variable type gained factor and ordered subtypes (1.4.0), rvar-indexed slicing and `rvar_ifelse()` (1.5.0), base `%*%` matrix multiplication and indexed variable names (1.6.0). Separately, Pareto diagnostics have grown from `pareto_smooth()` options and individual `pareto_khat()`-family functions (1.6.0) through `pit()` for draws and rvars (1.6.1) to exported generalized-Pareto functions and `pareto_pit` (1.7.0). 1.7.1 is a paperwork release for a JOSS submission.

◆ Where it's heading

posterior is positioning itself as shared infrastructure rather than an end-user package: 1.7.0 explicitly exports generalized-Pareto machinery 'for use in other packages', and the JOSS paper is a citation vehicle for the same audience. The rvar work points the same way — a random-variable type other Bayesian packages can build on. Cadence is steady but unhurried, roughly one feature release a year.

◆ Prediction

More diagnostic functions are likely to be exported for downstream reuse, following the pattern 1.7.0 established with the generalized-Pareto helpers.

T
timetk
ANALYTICS
0.0

timetk swallowed anomalize whole, then went quiet for two years

◆ Current state

timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.

◆ Where it's heading

The trajectory before the pause was consolidation: fold in adjacent functionality, then make the visualization layer handle many series at once via trelliscopejs, then broaden feature generation with tk_tsfeatures(). The recent release works on the least glamorous layer — internal generics so date parsing and sequence generation behave consistently across Date, POSIXct, hms, yearmon, and yearqtr — which is the kind of foundation work a package does when it has accumulated too many special cases. The long gap and the CI-refresh content suggest maintenance attention rather than a new direction.

◆ Prediction

The stated gap is the unimplemented twitter method for anomalize(), which is the one concrete outstanding item the release notes name; beyond that the recent work points to consolidation rather than expansion.

Alternatives to posterior and timetk

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 posterior or timetk.

See all posterior alternatives → · See all timetk alternatives →

Recent activity from posterior and timetk

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

  1. 2mo agoposteriorposterior 1.7.1 released for JOSS paper
  2. 3mo agoposteriorposterior 1.7.0 exports generalized-Pareto functions
  3. 10mo agoposteriorposterior 1.6.1 adds pit() for draws and rvars
  4. 11mo agotimetktimetk 2.9.1 makes date parsing consistent across time classes
  5. 1y agoposteriorposterior 1.6.0 adds Pareto diagnostics and ESS-based thinning
  6. 2y agotimetktimetk 2.9.0 absorbs the anomalize package
  7. 2y agoposteriorposterior 1.5.0 adds nested-Rhat and rvar indexing
  8. 3y agoposteriorposterior 1.4.0 adds factor and ordered rvar subtypes
  9. 4y agotimetktimetk 2.8.1 exposes trelliscope plotting parameters
  10. 4y agotimetktimetk 2.8.0 adds trelliscopejs support for many-series plots
  11. 4y agotimetktimetk 2.7.0 adds tk_tsfeatures() for grouped feature matrices
  12. 4y agotimetktimetk 2.6.2 adds .week_start and facet direction controls

Frequently asked questions

What is the difference between posterior and timetk?

They serve adjacent needs but don't currently overlap on shipped themes. posterior and timetk 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 posterior better than timetk?

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

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

What are the best alternatives to timetk?

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