gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
Comparison · Analytics
dvir vs glyvis
A side-by-side editorial comparison of dvir and glyvis — release velocity, themes, recent moves, and the top alternatives to consider.
dvir vs glyvis: 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 glyvis?
glyvis keeps losing plot functions as the packages behind them get reorganized.
glyvis is the plotting layer for glycoverse results. Its recent releases are dominated by two forces it does not control: glyexp's container migration, which it absorbed in 0.7.0 by accepting SummarizedExperiment inputs, and glystats' function removals, which cost it first the WGCNA and consensus-clustering autoplot methods and then the entire enrichment plotting surface. Its own additions in the window are narrow, mostly label handling and NA robustness.
dvir vs glyvis: 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.
glyvis
0.0ANALYTICS
glyvis keeps losing plot functions as the packages behind them get reorganized.
◆ Current state
glyvis is the plotting layer for glycoverse results. Its recent releases are dominated by two forces it does not control: glyexp's container migration, which it absorbed in 0.7.0 by accepting SummarizedExperiment inputs, and glystats' function removals, which cost it first the WGCNA and consensus-clustering autoplot methods and then the entire enrichment plotting surface. Its own additions in the window are narrow, mostly label handling and NA robustness.
◆ Where it's heading
The package is being pruned from upstream rather than expanded from within. Every breaking change in the last four releases is a removal triggered by a sibling package dropping the function that produced the object being plotted. With enrichment now living in glyfun, the plotting for it has to be rebuilt somewhere, and glyvis is the obvious home.
◆ Prediction
Expect enrichment plotting to return once glyfun's result objects stabilize, since the visualizations were removed for want of an upstream producer rather than because users stopped needing them.
Alternatives to dvir and glyvis
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 glyvis.
ducksemantics
ducksemantics puts an ontology graph and ColBERT retrieval inside DuckDB, callable from R.
pedbuildr
pedbuildr reconstructs pedigrees from DNA, and it just got much faster at the search.
forrel
forrel is getting faster at the simulations forensic kinship work actually spends its time on.
pedFamilias
pedFamilias exists to read one legacy file format, and it has that job nearly finished.
pedmut
pedmut turns awkward mutation models into ones the likelihood engine can actually handle.
Recent activity from dvir and glyvis
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoglyvisDocs recommend the new SE containers
- 1mo agoglyvisplot_logo() detects glycoproteomics across both containers
- 1mo agoglyvisPlots accept SummarizedExperiment; enrichment plots removed
- 1mo agodvirCombination sizing and a cutoff for joint analysis
- 3mo agodvirJoint tables added to solver output
- 3mo agoglyvisStale WGCNA and clustering autoplot methods removed
- 3mo agodvirVictim and database accessors, plus solver refinements
- 6mo agoglyvisDependencies move to the r-universe repository
- 7mo agoglyvisplot_logo() fetches UniProt sequences automatically
- 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 glyvis?
They serve adjacent needs but don't currently overlap on shipped themes. dvir and glyvis 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 glyvis?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dvir and glyvis 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 glyvis?
Top glyvis alternatives in Analytics are ranked by recent ship velocity. Browse the "glyvis alternatives" section above for the current picks, or visit /alternatives/glyvis for the full list with editorial commentary on each.