r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of cloudml and sdtm.oak — release velocity, themes, recent moves, and the top alternatives to consider.
Six years since the last functional change, and Google renamed the service it wraps in the release before that
cloudml lets R users train keras, tfestimators and tensorflow models on Google's managed machine learning service, tune hyperparameters there, and deploy the results. Its last release with functional content was 0.6.1 in September 2019, which adapted to Google renaming the service from ml-engine to ai-platform. The only entry since is a 2025 documentation update made to satisfy CRAN.
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.
cloudml lets R users train keras, tfestimators and tensorflow models on Google's managed machine learning service, tune hyperparameters there, and deploy the results. Its last release with functional content was 0.6.1 in September 2019, which adapted to Google renaming the service from ml-engine to ai-platform. The only entry since is a 2025 documentation update made to satisfy CRAN.
The visible arc is short and stops abruptly. Releases through 2018 tracked the TensorFlow runtime version and patched packaging problems; 0.6.1 added a customCommands hook so users could run OS-level setup before package installation, and adjusted to the service's new name. Then nothing for six years. A 2025 release containing only documentation changes is the standard signal of a package being kept on CRAN rather than being developed.
There is nothing in this feed to support a prediction of functional work. The most likely next event is another CRAN-driven documentation patch, or archival.
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.
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.
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.
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 cloudml or sdtm.oak.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all cloudml alternatives → · See all sdtm.oak alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. cloudml 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cloudml 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.
Top cloudml alternatives in Analytics are ranked by recent ship velocity. Browse the "cloudml alternatives" section above for the current picks, or visit /alternatives/cloudml for the full list with editorial commentary on each.
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.