datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
Comparison · Analytics
lightr vs sdtm.oak
A side-by-side editorial comparison of lightr and sdtm.oak — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
lightr vs sdtm.oak: at a glance
What is lightr?
Reorganised its parsers by vendor, then opened the parser slot to users.
lightr reads spectrometry files from the proprietary formats that instrument vendors ship, and its recent releases have been about the structure of that parser collection rather than adding one more format. Version 2.0.0 renamed every low-level parser from lr_parse_<extension>() to lr_parse_<brand>_<extension>(), a breaking change made specifically so two vendors can share a file extension without colliding, and restored binary parsing for Avantes AvaSoft 8.4 using vendor-supplied format documentation. Version 2.1.0 follows through by exposing a parser argument on the high-level functions.
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.
lightr vs sdtm.oak: editorial side-by-side
lightr
0.0ANALYTICS
Reorganised its parsers by vendor, then opened the parser slot to users.
◆ Current state
lightr reads spectrometry files from the proprietary formats that instrument vendors ship, and its recent releases have been about the structure of that parser collection rather than adding one more format. Version 2.0.0 renamed every low-level parser from lr_parse_<extension>() to lr_parse_<brand>_<extension>(), a breaking change made specifically so two vendors can share a file extension without colliding, and restored binary parsing for Avantes AvaSoft 8.4 using vendor-supplied format documentation. Version 2.1.0 follows through by exposing a parser argument on the high-level functions.
◆ Where it's heading
The package is moving from a fixed set of formats it knows about to a dispatch system users can extend. The brand-qualified naming and the parser argument are two halves of the same design: name parsers unambiguously, then let callers select or supply one. Alongside that runs steady attention to metadata fidelity — measurement timestamps, checksum verification against tampering, and timezone handling that survived upstream tzdata removing legacy codes.
◆ Prediction
Expect additional vendor parsers to arrive under the new brand-qualified scheme, and the custom-parser path to absorb formats the maintainers do not want to support directly. The entries do not name specific instruments planned next.
sdtm.oak
0.0ANALYTICS
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 lightr 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 lightr or sdtm.oak.
maplegend
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
lang
R help pages translated on demand by whichever LLM you point it at.
mapsf
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
fabletools
The tidyverts forecasting core rebuilt model combination on full residual covariance.
See all lightr alternatives → · See all sdtm.oak alternatives →
Recent activity from lightr and sdtm.oak
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agolightrHigh-level functions accept a custom parser argument
- 1mo agolightrParsers renamed by vendor; Avantes binary support restored ⚡
- 1y agolightrChecksum verification and measurement timestamps in metadata
- 1y agosdtm.oaksdtm.oak v0.2.0 CRAN release ⚡
- 1y agolightrReworks timezone handling after tzdata dropped legacy codes
- 1y agosdtm.oaksdtm.oak v0.1.1 CRAN release
- 1y agosdtm.oaksdtm.oak v0.1.0 CRAN release
- 1y agosdtm.oakv0.1.0rc4: [skip vbump] 90 cran comments (#91)
- 2y agosdtm.oakv0.1.0rc2: Fix CRAN Comments (#84)
- 2y agosdtm.oakv0.1.0: [skip vbump] Bump version for cran release (#77)
- 2y agolightrAdds lintr and stabilises floating-point tests
- 4y agolightrParser errors surface as warnings instead of being silenced
Frequently asked questions
What is the difference between lightr and sdtm.oak?
Both compete on the same themes — r-package — within Analytics. lightr 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 lightr better than sdtm.oak?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lightr 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 lightr?
Top lightr alternatives in Analytics are ranked by recent ship velocity. Browse the "lightr alternatives" section above for the current picks, or visit /alternatives/lightr 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.