gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
A side-by-side editorial comparison of dvir and pedbuildr — release velocity, themes, recent moves, and the top alternatives to consider.
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.
pedbuildr reconstructs pedigrees from DNA, and it just got much faster at the search.
pedbuildr infers pedigree structure from marker data by scoring candidate pedigrees against likelihoods. Version 0.4.0 moved reconstruct() to mirai for parallel likelihood computation, deprecated the old numCores argument, and picked up the improved loop breaking from pedtools and pedprobr, which lets many complex looped pedigrees succeed where they previously failed. buildPeds() also got significantly faster in its default configuration where mating between lineally related individuals is disallowed.
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.
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.
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.
pedbuildr infers pedigree structure from marker data by scoring candidate pedigrees against likelihoods. Version 0.4.0 moved reconstruct() to mirai for parallel likelihood computation, deprecated the old numCores argument, and picked up the improved loop breaking from pedtools and pedprobr, which lets many complex looped pedigrees succeed where they previously failed. buildPeds() also got significantly faster in its default configuration where mating between lineally related individuals is disallowed.
The package is bounded by two costs: how many candidate pedigrees it enumerates and how expensive each likelihood is. The recent release attacks both, parallelizing the likelihoods and speeding up enumeration in the common case. The earlier 0.3.0 release worked on the other end, adding inbreeding limits and a proper result class so the output of a large search is manageable. Releases are infrequent, roughly three years apart in this window.
Expect the candidate generation side to receive the same attention the likelihood side just did, since search space size is the remaining bound on what pedbuildr can reconstruct.
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 pedbuildr.
gps2gtfs spent a release making its docs stop describing functions it does not have.
ducksemantics puts an ontology graph and ColBERT retrieval inside DuckDB, callable from R.
forrel is getting faster at the simulations forensic kinship work actually spends its time on.
pedFamilias exists to read one legacy file format, and it has that job nearly finished.
pedmut turns awkward mutation models into ones the likelihood engine can actually handle.
pedprobr is the likelihood engine, and it keeps finding ways to compute what it previously could not.
See all dvir alternatives → · See all pedbuildr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — forensic genetics, parallel computing — within Analytics. dvir and pedbuildr 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dvir and pedbuildr 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.
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.
Top pedbuildr alternatives in Analytics are ranked by recent ship velocity. Browse the "pedbuildr alternatives" section above for the current picks, or visit /alternatives/pedbuildr for the full list with editorial commentary on each.