mice
mice can finally predict, not just estimate, from multiply imputed data.
Comparison · Infra & APIs
LightLogR vs surveytidy
A side-by-side editorial comparison of LightLogR and surveytidy — release velocity, themes, recent moves, and the top alternatives to consider.
LightLogR vs surveytidy: at a glance
What is LightLogR?
Wearable light-exposure data gets circular time and versioned device formats
LightLogR ingests recordings from wearable light loggers and optical radiation dosimeters, and its release notes are lopsided: four of the six most recent tags are one-line merge stubs while 0.10.0 carries several thousand words. That release is where the package sits — dataset-wide summary tables, a version argument on the importers, and time of day handled as a circular quantity.
What is surveytidy?
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
LightLogR vs surveytidy: editorial side-by-side
LightLogR
0.0INFRA · APIS
Wearable light-exposure data gets circular time and versioned device formats
◆ Current state
LightLogR ingests recordings from wearable light loggers and optical radiation dosimeters, and its release notes are lopsided: four of the six most recent tags are one-line merge stubs while 0.10.0 carries several thousand words. That release is where the package sits — dataset-wide summary tables, a version argument on the importers, and time of day handled as a circular quantity.
◆ Where it's heading
The arc runs from reading files off N devices toward modelling the awkward shapes of chronobiology data. Circular conversion lets bedtimes crossing midnight average correctly; remove_partial_data() can demand a minimum duration rather than a fraction of a known total; add_states() takes Interval objects so sleep-scoring output flows straight in. The device side hardens in parallel — supported_versions() exists because a VEET firmware release changed the file format mid-life.
◆ Prediction
The version switch currently covers VEET and a German-locale Actiwatch Spectrum; more device-format generations behind that same argument are the obvious continuation as manufacturers revise exports. The named milestones (Civil Dawn, then Sunrise) suggest the next substantive release will be another themed one rather than a steady drip.
surveytidy
0.0INFRA · APIS
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
◆ Current state
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
◆ Where it's heading
The package is being built in two layers that arrive in order: vector-level transformations first, structural dispatch second. The make_* family in 0.4.0 handles the recoding that survey work actually consists of — labelled to factor, multi-level to dichotomous, scale reversal, valence flipping — with value labels propagating automatically. Collection support then applies data-masking, tidyselect, grouping, slicing and collapsing verbs per survey, with joins explicitly refused and a typed message reporting which surveys were skipped. Metadata fidelity is the recurring bug source: labels surviving across(), stale labels left behind by recoding, the transformation log keeping up with what the verbs did.
◆ Prediction
Joins are the one verb family that errors on collections, with users directed to join before constructing the collection, so that restriction is the clearest outstanding gap. The re-export of surveycore's collection constructors suggests the package is positioning itself as the single import users need, which points toward more re-exports as surveycore's stable API settles.
Alternatives to LightLogR and surveytidy
Other Infra & APIs 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 LightLogR or surveytidy.
PINstimation
A market-microstructure toolkit that keeps adding estimators as the papers land.
nzilbb.vowels
A vowel-analysis package trimming dependencies after an email address got it archived.
emuR
The R half of the EMU speech database system, fixing what was quietly broken.
BAS
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all LightLogR alternatives → · See all surveytidy alternatives →
Recent activity from LightLogR and surveytidy
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosurveytidymutate() syncs metadata for across() recodes
- 3mo agosurveytidydplyr and tidyr verbs dispatch across survey collections
- 3mo agoLightLogRLYS imports accept any timestamp-prefixed column
- 5mo agosurveytidyFive label-aware recoding functions for use inside mutate()
- 8mo agoLightLogRCircular time, dataset-wide summaries, versioned device formats ⚡
- 1y agoLightLogRv0.9.2 Sunrise
- 1y agoLightLogRSunrise: cluster detection, metric summaries, new plots
- 1y agoLightLogRv0.5.3 Civil Dawn
- 1y agoLightLogRCitations updated on a merged dev branch
Frequently asked questions
What is the difference between LightLogR and surveytidy?
They serve adjacent needs but don't currently overlap on shipped themes. LightLogR and surveytidy 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 LightLogR better than surveytidy?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. LightLogR and surveytidy 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to LightLogR?
Top LightLogR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "LightLogR alternatives" section above for the current picks, or visit /alternatives/lightlogr for the full list with editorial commentary on each.
What are the best alternatives to surveytidy?
Top surveytidy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveytidy alternatives" section above for the current picks, or visit /alternatives/surveytidy for the full list with editorial commentary on each.