mice
mice can finally predict, not just estimate, from multiply imputed data.
Comparison · Infra & APIs
massProps vs valr
A side-by-side editorial comparison of massProps and valr — release velocity, themes, recent moves, and the top alternatives to consider.
massProps vs valr: at a glance
What is massProps?
A mass-properties rollup spends a year on documentation and follows its sibling's API
massProps computes mass, centre of mass and inertia tensors — and their uncertainties — over tree-structured assemblies, the calculation systems engineers run on a spacecraft or vehicle breakdown. It sits on top of rollupTree, the same author's generic recursive-computation engine, and its most recent release exists only to adopt accessor functions that sibling added two weeks earlier.
What is valr?
valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.
valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.
massProps vs valr: editorial side-by-side
massProps
0.0INFRA · APIS
A mass-properties rollup spends a year on documentation and follows its sibling's API
◆ Current state
massProps computes mass, centre of mass and inertia tensors — and their uncertainties — over tree-structured assemblies, the calculation systems engineers run on a spacecraft or vehicle breakdown. It sits on top of rollupTree, the same author's generic recursive-computation engine, and its most recent release exists only to adopt accessor functions that sibling added two weeks earlier.
◆ Where it's heading
Every release in the window is documentation, benchmarks, or keeping in step with rollupTree. The inertia tensor and radius-of-gyration uncertainty equations have been reformatted and re-explained three separate times, which suggests the hard part of this package is not the computation but making the covariance treatment legible to the engineers meant to trust it. Development effort clearly sits in the engine underneath, not here.
◆ Prediction
The pattern is unambiguous: rollupTree ships an API change and massProps follows within a fortnight. Whatever the engine does next is what appears here next, and on this evidence it will arrive as a one-line release note.
valr
0.0INFRA · APIS
valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.
◆ Current state
valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.
◆ Where it's heading
Two arcs converge here. One is compatibility: min_overlap arrived with a deprecation warning in 0.9.0 and its default flipped from 0 to 1 in 0.10.0, so book-ended intervals are excluded by default as bedtools does, with the internal calculations in bed_closest() and friends deliberately left counting them. The other is the file-backed path, which grew out of the cpp11bigwig dependency adopted in 0.8.3 for read_bigwig() and re-exported in 0.9.0 — reading a file became querying one. Underneath, the C++ base keeps getting lighter: Rcpp swapped for cpp11, rlang cut to a single function, per-group memory copies removed from three verbs.
◆ Prediction
Only five verbs take a file argument today and bed_closest(), bed_glyph() and the statistical verbs do not, so extending the file-backed path across the rest of the API is the obvious follow-up. The deprecated tibble re-exports and the now-defunct n_fields argument suggest continued removal of the compatibility layer in the next minor release.
Alternatives to massProps and valr
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 massProps or valr.
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 massProps alternatives → · See all valr alternatives →
Recent activity from massProps and valr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agovalrInterval verbs read bigWig and bigBed files directly ⚡
- 6mo agomassPropsSwitched to rollupTree's new row accessors
- 6mo agomassPropsError in the inertia tensor uncertainty documentation
- 7mo agovalrbed_slop() and bed_flank() preserve input row order
- 8mo agovalrmin_overlap introduced; C++ backend moves from Rcpp to cpp11
- 1y agovalrTest updated for ggplot2 3.6.0
- 1y agomassPropsBenchmark results and equation layout cleaned up
- 1y agomassPropsCombine functions given consistent formal parameters
- 1y agomassPropsExamples shrunk to fit CRAN runtime limits
- 1y agovalrread_bigwig() switches to cpp11bigwig; read_gtf() deprecated
- 1y agovalrCRAN Rd link NOTE and maintainer email change
Frequently asked questions
What is the difference between massProps and valr?
They serve adjacent needs but don't currently overlap on shipped themes. massProps and valr 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 massProps better than valr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. massProps and valr 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 massProps?
Top massProps alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "massProps alternatives" section above for the current picks, or visit /alternatives/massprops for the full list with editorial commentary on each.
What are the best alternatives to valr?
Top valr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "valr alternatives" section above for the current picks, or visit /alternatives/valr for the full list with editorial commentary on each.