← Back to home
Comparison · Analytics

dvir vs pedtools

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

Shared themes:forensic genetics

dvir vs pedtools: at a glance

Featuredvirpedtools
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesforensic genetics, victim identification, pipeline, scalabilitypedigree analysis, forensic genetics, algorithms, loop breaking
Last editorial update53m ago55m 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 pedtools?

pedtools rewrote loop breaking and made a class of pedigrees analyzable for the first time.

pedtools is the foundation of the ped suite, holding the pedigree data structures every other package builds on. Version 2.11.0 revamped the loop breaking algorithm so founders can serve as loop breakers and one individual can break several loops, which makes likelihood calculations possible in pedigrees that previously could not be handled at all. Loop detection also became mandatory and faster, and the surrounding releases have steadily added query and construction helpers.

Read the full pedtools trajectory →

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

P
pedtools
ANALYTICS
0.0

pedtools rewrote loop breaking and made a class of pedigrees analyzable for the first time.

◆ Current state

pedtools is the foundation of the ped suite, holding the pedigree data structures every other package builds on. Version 2.11.0 revamped the loop breaking algorithm so founders can serve as loop breakers and one individual can break several loops, which makes likelihood calculations possible in pedigrees that previously could not be handled at all. Loop detection also became mandatory and faster, and the surrounding releases have steadily added query and construction helpers.

◆ Where it's heading

The package has been working toward this for over a year. Version 2.8.0 replaced the igraph-based loop breaker with a custom implementation, 2.8.1 made findLoopBreakers() substantially faster in large pedigrees, and 2.11.0 rewrote the algorithm outright. The new methods ship disabled by default while downstream packages catch up, which is a deliberately staged rollout rather than a flag day. Alongside that, the additive work is small, well-scoped helpers: children2(), addSibling(), isHomozygous(), trim(), nChildren().

◆ Prediction

Expect the new loop breaking methods to become the default once pedprobr, forrel, and dvir have all shipped support for them, since the only stated reason for the opt-in flag is downstream readiness.

Alternatives to dvir and pedtools

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

See all dvir alternatives → · See all pedtools alternatives →

Recent activity from dvir and pedtools

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

  1. 1mo agodvirCombination sizing and a cutoff for joint analysis
  2. 1mo agopedtoolsLoop breaking rewrite makes intractable pedigrees analyzable
  3. 3mo agodvirJoint tables added to solver output
  4. 3mo agodvirVictim and database accessors, plus solver refinements
  5. 6mo agopedtoolsGenotype comparison helpers and more flexible subsetting
  6. 9mo agopedtoolsmergePed() handles marker data; genotype removal simplified
  7. 1y agopedtoolssetSNPs() accepts genotypes; proband arrows in plots
  8. 1y agopedtoolstrim() prunes uninformative leaves; loop breaker search sped up
  9. 1y agopedtoolsigraph dependency dropped for a custom loop breaker
  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 pedtools?

Both compete on the same themes — forensic genetics — within Analytics. dvir and pedtools 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 pedtools?

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

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