tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
Comparison · Analytics
dvir vs glyclean
A side-by-side editorial comparison of dvir and glyclean — release velocity, themes, recent moves, and the top alternatives to consider.
dvir vs glyclean: 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 glyclean?
glyclean stopped trusting QC samples to choose its preprocessing strategy.
glyclean handles preprocessing and QC for glycomics and glycoproteomics data: filtering, imputation, normalization, batch correction, and compositional transforms. The defining change in this window is 0.14.0, which abandoned QC coefficient-of-variation heuristics for choosing imputation and normalization methods in favor of rules keyed to sample size. The 0.15.x releases then finished removing the deprecated QC arguments and moved the whole package onto glyexp's SummarizedExperiment containers.
dvir vs glyclean: 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.
glyclean
0.0ANALYTICS
glyclean stopped trusting QC samples to choose its preprocessing strategy.
◆ Current state
glyclean handles preprocessing and QC for glycomics and glycoproteomics data: filtering, imputation, normalization, batch correction, and compositional transforms. The defining change in this window is 0.14.0, which abandoned QC coefficient-of-variation heuristics for choosing imputation and normalization methods in favor of rules keyed to sample size. The 0.15.x releases then finished removing the deprecated QC arguments and moved the whole package onto glyexp's SummarizedExperiment containers.
◆ Where it's heading
Two commitments are visible. First, defaults should be defensible rather than adaptive: the maintainer explicitly judged CV-in-QC-samples not robust and replaced it with sample-size thresholds. Second, the package wants containers, not matrices, and 0.15.0 makes bare matrix inputs an error. Dependency pruning runs alongside both, with imputeLCMD reimplemented away so auto_clean() works out of the box.
◆ Prediction
The compositional data thread is the least finished part of the package, so further CoDA methods or a broader auto_coda() are the likeliest next additions.
Alternatives to dvir and glyclean
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 glyclean.
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 glyclean alternatives →
Recent activity from dvir and glyclean
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoglycleanDocs recommend the new SE containers
- 1mo agoglycleanPreprocessing behaves the same across both containers
- 1mo agoglycleanMatrix inputs rejected; containers now required
- 1mo agodvirCombination sizing and a cutoff for joint analysis
- 3mo agoglycleanauto_clean() works without extra package installs
- 3mo agodvirJoint tables added to solver output
- 3mo agoglycleanImputation strategy now keyed to sample size, not QC
- 3mo agodvirVictim and database accessors, plus solver refinements
- 4mo agoglycleanCoDA transforms aligned with published methods
- 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 glyclean?
They serve adjacent needs but don't currently overlap on shipped themes. dvir and glyclean 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 glyclean?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dvir and glyclean 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 glyclean?
Top glyclean alternatives in Analytics are ranked by recent ship velocity. Browse the "glyclean alternatives" section above for the current picks, or visit /alternatives/glyclean for the full list with editorial commentary on each.