← Back to home
Comparison · Analytics

dvir vs ibdsim2

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

dvir vs ibdsim2: at a glance

Featuredviribdsim2
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesforensic genetics, victim identification, pipeline, scalabilitystatistical-genetics, pedigree-analysis, simulation, 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 ibdsim2?

A pedigree IBD simulator that absorbed its own web app and now optimises for dense marker panels.

ibdsim2 simulates identity-by-descent sharing along chromosomes for arbitrary pedigrees, in both autosomal and X-chromosomal form, with downstream tools for segment statistics, pattern finding and distribution plots. Since 2.1.0 the Shiny front end lives inside the package and launches via launchApp() rather than sitting in a separate repository. The latest release is performance work, with profileSimIBD() substantially sped up for dense marker panels and ibdsim() skipping recombination in pedigree branches that cannot affect the result.

Read the full ibdsim2 trajectory →

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

I
ibdsim2
ANALYTICS
2.5

A pedigree IBD simulator that absorbed its own web app and now optimises for dense marker panels.

◆ Current state

ibdsim2 simulates identity-by-descent sharing along chromosomes for arbitrary pedigrees, in both autosomal and X-chromosomal form, with downstream tools for segment statistics, pattern finding and distribution plots. Since 2.1.0 the Shiny front end lives inside the package and launches via launchApp() rather than sitting in a separate repository. The latest release is performance work, with profileSimIBD() substantially sped up for dense marker panels and ibdsim() skipping recombination in pedigree branches that cannot affect the result.

◆ Where it's heading

Two long-running threads. One is the app as a first-class part of the package, which has been getting input validation, dependency checks and plotting fixes release after release, treating a research GUI as software to be maintained rather than a demo. The other is numerical care: the built-in recombination map was rebuilt in 2.3.0 with better chromosome endpoints and a thinning algorithm that cut it from about 38,000 points to 14,000 without losing accuracy, and IBD segment merging has been made consistent across the realised-coefficient functions. The maintainer flags repeatedly that seeded results may differ across versions, which is the right disclosure for a simulator used in published analyses.

◆ Prediction

The recent work points at further speed on dense panels and continued hardening of app input handling, both of which have appeared in each of the last several releases. Nothing here signals a new modelling capability on the way.

Alternatives to dvir and ibdsim2

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

See all dvir alternatives → · See all ibdsim2 alternatives →

Recent activity from dvir and ibdsim2

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

  1. 11d agoibdsim2profileSimIBD() sped up for dense marker panels; segment merging fixed
  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. 8mo agoibdsim2Segment-distribution merge argument, and function-valued parameters
  6. 1y agoibdsim2Built-in decode19 recombination map rebuilt, cutting 38k points to 14k
  7. 1y agoibdsim2Consistent IBD segment merging across the realised-coefficient functions
  8. 1y agodvirSolver rewritten around generalised likelihood ratios
  9. 1y agoibdsim2Built-in pedigree labels revised; extra inbred examples added
  10. 1y agoibdsim2The Shiny front end moves into the package and gains X-chromosomal simulation
  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 ibdsim2?

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

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

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