tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
Comparison · Analytics
dvir vs glystats
A side-by-side editorial comparison of dvir and glystats — release velocity, themes, recent moves, and the top alternatives to consider.
dvir vs glystats: at a glance
What is dvir?
dvir keeps making disaster victim identification a single call instead of a workflow.
dvir handles disaster victim identification: matching unidentified remains against reference families using pedigree likelihoods. The package has consolidated around dviSolve(), a complete pipeline introduced in 3.2.1 and rewritten in 3.3.0 to use generalised likelihood ratios for families with several missing persons. Recent releases have been about making that pipeline survive large cases, adding dviGridSize() and a maxAssign cutoff to skip joint analysis when the combination count explodes, plus per-step timings.
What is glystats?
glystats keeps deleting analyses it decided belong somewhere else.
glystats provides the statistical tests behind glycoverse: differential analysis, clustering, dimensionality reduction, and until recently enrichment. The last four releases are mostly subtraction. WGCNA and consensus clustering were removed in 0.10.0 as too interactive for a pipeline package, the enrichment functions were deprecated in the same release and deleted in 0.11.0 in favor of glyfun, and 0.11.0 also removed every gly_*_() matrix and vector interface. What remains accepts SummarizedExperiment inputs.
dvir vs glystats: editorial side-by-side
dvir
0.0ANALYTICS
dvir keeps making disaster victim identification a single call instead of a workflow.
◆ Current state
dvir handles disaster victim identification: matching unidentified remains against reference families using pedigree likelihoods. The package has consolidated around dviSolve(), a complete pipeline introduced in 3.2.1 and rewritten in 3.3.0 to use generalised likelihood ratios for families with several missing persons. Recent releases have been about making that pipeline survive large cases, adding dviGridSize() and a maxAssign cutoff to skip joint analysis when the combination count explodes, plus per-step timings.
◆ Where it's heading
The arc is from a toolbox of functions toward one supervised pipeline, with the older jointDVI() now emitting a legacy message. The current constraint is combinatorial: joint analysis over many victims and missing persons blows up, so the work has gone to measuring the blowup and bailing out of it. Parallelism is mid-migration, with the parallel and pbapply implementation removed and a mirai replacement stated as planned but not yet shipped, leaving numCores accepted and ignored with a warning.
◆ Prediction
The mirai-based parallelisation is announced as coming, so expect it next, most likely applied to the joint analysis step that maxAssign currently exists to avoid.
glystats
0.0ANALYTICS
glystats keeps deleting analyses it decided belong somewhere else.
◆ Current state
glystats provides the statistical tests behind glycoverse: differential analysis, clustering, dimensionality reduction, and until recently enrichment. The last four releases are mostly subtraction. WGCNA and consensus clustering were removed in 0.10.0 as too interactive for a pipeline package, the enrichment functions were deprecated in the same release and deleted in 0.11.0 in favor of glyfun, and 0.11.0 also removed every gly_*_() matrix and vector interface. What remains accepts SummarizedExperiment inputs.
◆ Where it's heading
The package is narrowing on purpose. The through-line across removals is a refusal to support two calling conventions or two homes for the same analysis: containers only, no bare matrices; one enrichment implementation, in glyfun. The additive work in the window went to statistical rigor rather than surface area, with effect sizes added to the four main tests, sign bugs fixed, and the log2 pseudo-count reduced.
◆ Prediction
With the interface pruning finished, the next releases are more likely to deepen the tests that remain than to add new analysis families.
Alternatives to dvir and glystats
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 dvir or glystats.
spsurvey
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
rpymat
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
See all dvir alternatives → · See all glystats alternatives →
Recent activity from dvir and glystats
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoglystatsDocs recommend the new SE containers
- 1mo agoglystatsTests recognize both container types consistently
- 1mo agoglystatsMatrix interfaces and enrichment functions removed
- 1mo agodvirCombination sizing and a cutoff for joint analysis
- 2mo agoglystatsSmaller log2 pseudo-count across DEA and clustering
- 3mo agodvirJoint tables added to solver output
- 3mo agoglystatsWGCNA and clustering dropped, enrichment deprecated
- 3mo agodvirVictim and database accessors, plus solver refinements
- 4mo agoglystatsEffect sizes added and test statistic signs fixed
- 1y agodvirSolver rewritten around generalised likelihood ratios
- 2y agodvirdviSolve() pipeline and manual pairing controls
- 2y agodvirMaintainer handover and small reporting additions
Frequently asked questions
What is the difference between dvir and glystats?
They serve adjacent needs but don't currently overlap on shipped themes. dvir and glystats 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 dvir better than glystats?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dvir and glystats 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 dvir?
Top dvir alternatives in Analytics are ranked by recent ship velocity. Browse the "dvir alternatives" section above for the current picks, or visit /alternatives/dvir for the full list with editorial commentary on each.
What are the best alternatives to glystats?
Top glystats alternatives in Analytics are ranked by recent ship velocity. Browse the "glystats alternatives" section above for the current picks, or visit /alternatives/glystats for the full list with editorial commentary on each.