← Back to home
Comparison · Analytics

dvir vs glymotif

A side-by-side editorial comparison of dvir and glymotif — release velocity, themes, recent moves, and the top alternatives to consider.

dvir vs glymotif: at a glance

Featuredvirglymotif
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesforensic genetics, victim identification, pipeline, scalabilityglycomics, motif-matching, graph-algorithms, performance
Last editorial update22m ago1h ago
WebsiteVisit →Visit →

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.

Read the full dvir trajectory →

What is glymotif?

A glycan motif matcher trading convenience wrappers for speed, strictness and explicit specs.

glymotif detects and counts structural motifs in glycans, over a built-in motif database or user-supplied structures, with fuzzy modification matching and alignment control. Database motifs are now requested through a db_motifs_spec object carrying their own matching parameters rather than as a name vector with loose arguments, and db_motif_info() exposes the built-in set as an inspectable tibble. A lenient mode lets lower-information glycans match more specific motifs while concrete mismatches still fail, and low-level entry points work directly on igraph objects for other package authors.

Read the full glymotif trajectory →

dvir vs glymotif: editorial side-by-side

D
dvir
ANALYTICS
0.0

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.

G
glymotif
ANALYTICS
2.5

A glycan motif matcher trading convenience wrappers for speed, strictness and explicit specs.

◆ Current state

glymotif detects and counts structural motifs in glycans, over a built-in motif database or user-supplied structures, with fuzzy modification matching and alignment control. Database motifs are now requested through a db_motifs_spec object carrying their own matching parameters rather than as a name vector with loose arguments, and db_motif_info() exposes the built-in set as an inspectable tibble. A lenient mode lets lower-information glycans match more specific motifs while concrete mismatches still fail, and low-level entry points work directly on igraph objects for other package authors.

◆ Where it's heading

Performance has been a recurring line item across at least four releases, culminating in optimised graph searches and candidate filtering aimed at batch analyses, which points at the real workload being whole experiments rather than single glycans. The API has moved the other way from convenience toward explicitness: the add_motifs_lgl() and add_motifs_int() wrappers are deprecated in favour of composing with dplyr or glyexp verbs, optional arguments must now be named, and loose matching parameters were folded into the spec object. Documentation is being steered toward the cohort's newer container types, so this package is following a coordinated migration rather than setting its own course.

◆ Prediction

With the deprecated annotation wrappers on their way out and documentation already pointing at the replacement verbs, their removal is the likely next breaking change. The lenient matching mode is new enough that its boundary against concrete mismatches will probably need tuning as users apply it to real, partially resolved data.

Alternatives to dvir and glymotif

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 glymotif.

See all dvir alternatives → · See all glymotif alternatives →

Recent activity from dvir and glymotif

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 29d agoglymotifOptimised graph search cuts batch matching time; missing N-glycan core now warns
  2. 1mo agoglymotifDocs point at the new container types and replacement verbs
  3. 1mo agoglymotifExamples run against both legacy and current containers
  4. 1mo agoglymotifLenient matching for lower-information glycans; annotation wrappers deprecated
  5. 1mo agodvirCombination sizing and a cutoff for joint analysis
  6. 1mo agoglymotifEmpty glycans handled in motif matching
  7. 1mo agoglymotifDatabase motifs become a spec object carrying their own parameters
  8. 3mo agodvirJoint tables added to solver output
  9. 3mo agodvirVictim and database accessors, plus solver refinements
  10. 1y agodvirSolver rewritten around generalised likelihood ratios
  11. 2y agodvirdviSolve() pipeline and manual pairing controls
  12. 2y agodvirMaintainer handover and small reporting additions

Frequently asked questions

What is the difference between dvir and glymotif?

They serve adjacent needs but don't currently overlap on shipped themes. glymotif is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is dvir better than glymotif?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. glymotif is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 glymotif?

Top glymotif alternatives in Analytics are ranked by recent ship velocity. Browse the "glymotif alternatives" section above for the current picks, or visit /alternatives/glymotif for the full list with editorial commentary on each.