gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
Comparison · Analytics
dvir vs pedprobr
A side-by-side editorial comparison of dvir and pedprobr — release velocity, themes, recent moves, and the top alternatives to consider.
dvir vs pedprobr: 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 pedprobr?
pedprobr is the likelihood engine, and it keeps finding ways to compute what it previously could not.
pedprobr computes pedigree likelihoods for the ped suite. Version 1.1.0 updated its loop handling to match pedtools 2.11.0, including founder and repeated loop breakers, and improved the peeling algorithm with single-child shortcuts and lower memory use. Version 1.0.0 was the other expansion: special lumping lets markers with mutation models that are un-lumpable in the Kemeny-Snell sense be lumped anyway in certain cases, with alleleLimit as a fallback for the rest.
dvir vs pedprobr: 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.
pedprobr
0.0ANALYTICS
pedprobr is the likelihood engine, and it keeps finding ways to compute what it previously could not.
◆ Current state
pedprobr computes pedigree likelihoods for the ped suite. Version 1.1.0 updated its loop handling to match pedtools 2.11.0, including founder and repeated loop breakers, and improved the peeling algorithm with single-child shortcuts and lower memory use. Version 1.0.0 was the other expansion: special lumping lets markers with mutation models that are un-lumpable in the Kemeny-Snell sense be lumped anyway in certain cases, with alleleLimit as a fallback for the rest.
◆ Where it's heading
Every significant release here removes a class of computation that used to be infeasible, either by making a marker lumpable or by making a loop breakable. The rest is steady peeling-algorithm optimization, which has been reducing memory footprint release after release since 0.9.2. The newly added .diagnostics option suggests the peeling internals are now complex enough that the maintainer needs to inspect them.
◆ Prediction
Since special lumping is documented as covering only some cases so far, expect further lumping situations to be implemented as pedmut adds them.
Alternatives to dvir and pedprobr
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 pedprobr.
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.
See all dvir alternatives → · See all pedprobr alternatives →
Recent activity from dvir and pedprobr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agodvirCombination sizing and a cutoff for joint analysis
- 1mo agopedprobrLoop handling updated for pedtools' new loop breakers
- 3mo agodvirJoint tables added to solver output
- 3mo agodvirVictim and database accessors, plus solver refinements
- 1y agopedprobrCRAN example rounding fix
- 1y agopedprobrSpecial lumping for previously un-lumpable mutation models
- 1y agopedprobrGenotype distributions gain sparse and table output
- 1y agodvirSolver rewritten around generalised likelihood ratios
- 2y agopedprobrPeeling order bug fix
- 2y agopedprobrPartial genotype fix for singletons
- 2y agodvirdviSolve() pipeline and manual pairing controls
- 2y agodvirMaintainer handover and small reporting additions
Frequently asked questions
What is the difference between dvir and pedprobr?
They serve adjacent needs but don't currently overlap on shipped themes. dvir and pedprobr 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 pedprobr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dvir and pedprobr 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 pedprobr?
Top pedprobr alternatives in Analytics are ranked by recent ship velocity. Browse the "pedprobr alternatives" section above for the current picks, or visit /alternatives/pedprobr for the full list with editorial commentary on each.