← Back to home
Comparison · Analytics

sdtm.oak vs tidymodels

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

sdtm.oak vs tidymodels: at a glance

Featuresdtm.oaktidymodels
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-trials, sdtm, pharmaverse, r-packagetidymodels, meta-package, dependency-management, namespace-conflicts
Last editorial update3h ago46m ago
WebsiteVisit →Visit →

What is sdtm.oak?

Two releases in, the open-source SDTM toolkit now covers the domains it originally excluded.

sdtm.oak builds SDTM datasets — the tabulation standard clinical trial submissions are filed in — from raw collected data. The 0.1.0 release shipped the mapping algorithm functions and derived-variable helpers but explicitly excluded DM, trial design domains, and several others. Version 0.2.0 closes the largest of those gaps, adding DM domain support via calc_min_max_date() and oak_calc_ref_dates(), plus generate_sdtm_supp() for supplemental qualifier domains.

Read the full sdtm.oak trajectory →

What is tidymodels?

The meta-package ships almost nothing, which is exactly what a version-pinning shim should do

The tidymodels package is a loader and version pin for the modeling framework's core set rather than a place where features live. Its entire changelog consists of updated dependency versions, adjustments to how tidymodels_prefer() resolves name conflicts against other packages, and the occasional addition of a package to the core set — workflowsets in 0.1.3, tailor in 1.4.0. The most recent releases moved the package's own code from the magrittr pipe to R's base pipe and patched a bug where some attached packages were omitted.

Read the full tidymodels trajectory →

sdtm.oak vs tidymodels: editorial side-by-side

S
sdtm.oak
ANALYTICS
0.0

Two releases in, the open-source SDTM toolkit now covers the domains it originally excluded.

◆ Current state

sdtm.oak builds SDTM datasets — the tabulation standard clinical trial submissions are filed in — from raw collected data. The 0.1.0 release shipped the mapping algorithm functions and derived-variable helpers but explicitly excluded DM, trial design domains, and several others. Version 0.2.0 closes the largest of those gaps, adding DM domain support via calc_min_max_date() and oak_calc_ref_dates(), plus generate_sdtm_supp() for supplemental qualifier domains.

◆ Where it's heading

This is the pharmaverse pattern of building submission tooling in the open, one domain class at a time, with the release history running through GitHub release-candidate tags before each CRAN submission. The direction is clear from the domain checklist: start with the mechanically simple Findings and Events domains, then work toward the ones with cross-dataset dependencies. DM and SUPP were the two that most often forced teams back to bespoke code.

◆ Prediction

The remaining exclusions from the 0.1.0 scope — trial design domains, SV, SE, RELREC and the EPOCH variable — are the obvious next targets, with EPOCH likely first since it depends on the reference dates 0.2.0 just added. Expect the same rhythm of release candidates ahead of each CRAN submission.

T
tidymodels
ANALYTICS
0.0

The meta-package ships almost nothing, which is exactly what a version-pinning shim should do

◆ Current state

The tidymodels package is a loader and version pin for the modeling framework's core set rather than a place where features live. Its entire changelog consists of updated dependency versions, adjustments to how tidymodels_prefer() resolves name conflicts against other packages, and the occasional addition of a package to the core set — workflowsets in 0.1.3, tailor in 1.4.0. The most recent releases moved the package's own code from the magrittr pipe to R's base pipe and patched a bug where some attached packages were omitted.

◆ Where it's heading

Release cadence tracks the ecosystem rather than any roadmap of its own: a version bump when member packages release, a tidymodels_prefer() rule when a new conflict appears — DALEX::explains() over dplyr::explains(), recipes::update() over other update() methods. Additions to the core set are the only structurally interesting events, and there have been two in seven releases. Everything else is plumbing that exists so a single library() call attaches a consistent set of versions.

◆ Prediction

The next release will most likely be another version-set update, with any new core package the only thing worth noting. Feature news for this framework will keep arriving in the member packages, not here.

Alternatives to sdtm.oak and tidymodels

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 sdtm.oak or tidymodels.

See all sdtm.oak alternatives → · See all tidymodels alternatives →

Recent activity from sdtm.oak and tidymodels

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

  1. 11mo agotidymodelsFix for packages omitted from attachment
  2. 11mo agotidymodelstailor joins the core set; base pipe replaces magrittr
  3. 1y agosdtm.oaksdtm.oak v0.2.0 CRAN release
  4. 1y agotidymodelsConflict preferences added for DALEX and recipes
  5. 1y agosdtm.oaksdtm.oak v0.1.1 CRAN release
  6. 1y agosdtm.oaksdtm.oak v0.1.0 CRAN release
  7. 1y agosdtm.oakv0.1.0rc4: [skip vbump] 90 cran comments (#91)
  8. 2y agosdtm.oakv0.1.0rc2: Fix CRAN Comments (#84)
  9. 2y agosdtm.oakv0.1.0: [skip vbump] Bump version for cran release (#77)
  10. 3y agotidymodelsConflict preferences and pinned versions refreshed
  11. 4y agotidymodelsVersion refresh and testthat 3e migration
  12. 4y agotidymodelsRotating startup messages and an analysis template

Frequently asked questions

What is the difference between sdtm.oak and tidymodels?

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

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

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

What are the best alternatives to tidymodels?

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