← Back to home
Comparison · Analytics

dvir vs ribd

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

dvir vs ribd: at a glance

Featuredvirribd
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesforensic genetics, victim identification, pipeline, scalabilitystatistical-genetics, pedigree-analysis, relatedness-coefficients, r-packages
Last editorial update38m 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 ribd?

The pedsuite's coefficient engine: broadening what it computes, then making the plots publishable.

ribd computes relatedness coefficients from pedigrees, covering kinship, inbreeding, kappa, condensed and detailed identity coefficients, and two-locus versions of several of these, in autosomal and X-chromosomal form. The IBD triangle is now drawable in base graphics, ggplot2 or plotly, with an optional inset pedigree, and custom relationships can be placed on it. The most recent release is dominated by correctness work, fixing pair ordering and row alignment in coefficient tables and edge cases for pedigree lists, unrelated individuals and self-pairs.

Read the full ribd trajectory →

dvir vs ribd: 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.

R
ribd
ANALYTICS
2.5

The pedsuite's coefficient engine: broadening what it computes, then making the plots publishable.

◆ Current state

ribd computes relatedness coefficients from pedigrees, covering kinship, inbreeding, kappa, condensed and detailed identity coefficients, and two-locus versions of several of these, in autosomal and X-chromosomal form. The IBD triangle is now drawable in base graphics, ggplot2 or plotly, with an optional inset pedigree, and custom relationships can be placed on it. The most recent release is dominated by correctness work, fixing pair ordering and row alignment in coefficient tables and edge cases for pedigree lists, unrelated individuals and self-pairs.

◆ Where it's heading

The arc runs from generality to presentation to precision. Early releases replaced narrow functions with general ones, most visibly when gKinship() absorbed generalisedKinship() and identityCoefs() superseded the separate autosomal and X-chromosomal identity functions in favour of an Xchrom argument. The middle stretch turned the IBD triangle into a proper plotting surface across three graphics systems. The current phase reads as consolidation, with the newest release listing six bug fixes against four features, several of them alignment errors in output tables, which is where a coefficient library most needs to be exactly right.

◆ Prediction

The two new internal functions in the latest release, inbreedingContributions() and ancestralKinship(), are the kind of thing that surfaces publicly a release or two later, so expect them to become exported decomposition tools. The correctness push through pedigree lists and edge cases suggests the near-term focus stays on hardening rather than new coefficient families.

Alternatives to dvir and ribd

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

See all dvir alternatives → · See all ribd alternatives →

Recent activity from dvir and ribd

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

  1. 12d agoribdCustom relationships on the IBD triangle; six alignment and edge-case fixes
  2. 1mo agodvirCombination sizing and a cutoff for joint analysis
  3. 3mo agodvirJoint tables added to solver output
  4. 3mo agodvirVictim and database accessors, plus solver refinements
  5. 1y agoribdkappaIBD() can skip across-component pairs on large pedigrees
  6. 1y agodvirSolver rewritten around generalised likelihood ratios
  7. 2y agoribdIBD triangle plots gain ggplot2 and plotly backends, plus inset pedigrees
  8. 2y agodvirdviSolve() pipeline and manual pairing controls
  9. 2y agodvirMaintainer handover and small reporting additions
  10. 3y agoribdTriangle line clipping, automatic plot margins, citation info
  11. 3y agoribdTwo-locus functions overhauled; twoLocusInbreeding and ELR added
  12. 4y agoribdIdentity coefficients unified behind identityCoefs() and an Xchrom argument

Frequently asked questions

What is the difference between dvir and ribd?

They serve adjacent needs but don't currently overlap on shipped themes. ribd 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 ribd?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ribd 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 ribd?

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