← Back to home
Comparison · Analytics

dfms vs sdtm.oak

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

dfms vs sdtm.oak: at a glance

Featuredfmssdtm.oak
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesnowcasting, state-space-models, econometrics, ropensciclinical-trials, sdtm, pharmaverse, r-package
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is dfms?

Peer-reviewed, feature-complete, and now able to hand its models to other forecasting engines.

dfms estimates dynamic factor models in R, the workhorse for nowcasting economic activity from ragged, mixed-frequency data. The package worked through the Banbura and Modugno (2014) specification in stages — quarterly variables in 0.3.0, AR(1) idiosyncratic errors combined with mixed frequency in 0.4.0 — then declared 1.0.0 feature-complete on completing rOpenSci peer review, adding news decomposition to attribute forecast revisions to specific data releases. Version 1.0.1 adds convert(), which exports fitted models to dlm or KFAS state-space objects.

Read the full dfms trajectory →

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 →

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

D
dfms
ANALYTICS
0.0

Peer-reviewed, feature-complete, and now able to hand its models to other forecasting engines.

◆ Current state

dfms estimates dynamic factor models in R, the workhorse for nowcasting economic activity from ragged, mixed-frequency data. The package worked through the Banbura and Modugno (2014) specification in stages — quarterly variables in 0.3.0, AR(1) idiosyncratic errors combined with mixed frequency in 0.4.0 — then declared 1.0.0 feature-complete on completing rOpenSci peer review, adding news decomposition to attribute forecast revisions to specific data releases. Version 1.0.1 adds convert(), which exports fitted models to dlm or KFAS state-space objects.

◆ Where it's heading

The package has finished the implementation programme it set out in its 2023 vignette and is now working on the edges: interoperability with other state-space packages rather than more estimation methods of its own. The convert() function is the clearest signal — instead of implementing smoothing and prediction intervals natively, it hands the model to packages that already have them. The rOpenSci move also puts it on a review-backed, documented footing that research users can cite.

◆ Prediction

Expect continued interoperability and diagnostic work rather than new estimators, since the maintainer has explicitly scoped the package as complete. Bug fixes against RcppArmadillo releases will likely remain the other recurring driver.

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.

Alternatives to dfms and sdtm.oak

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

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

Recent activity from dfms and sdtm.oak

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

  1. 1mo agodfmsconvert() exports models to dlm and KFAS state-space objects
  2. 6mo agodfms1.0: rOpenSci review passed, news decomposition added
  3. 6mo agodfmsMixed-frequency estimation gains AR(1) idiosyncratic errors
  4. 9mo agodfmsC++ compatibility with RcppArmadillo 15.0.2
  5. 1y agodfmsFixes estimation with a single quarterly variable
  6. 1y agosdtm.oaksdtm.oak v0.2.0 CRAN release
  7. 1y agodfmsAdds mixed-frequency estimation via quarterly.vars
  8. 1y agosdtm.oaksdtm.oak v0.1.1 CRAN release
  9. 1y agosdtm.oaksdtm.oak v0.1.0 CRAN release
  10. 1y agosdtm.oakv0.1.0rc4: [skip vbump] 90 cran comments (#91)
  11. 2y agosdtm.oakv0.1.0rc2: Fix CRAN Comments (#84)
  12. 2y agosdtm.oakv0.1.0: [skip vbump] Bump version for cran release (#77)

Frequently asked questions

What is the difference between dfms and sdtm.oak?

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

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

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

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.