gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
A side-by-side editorial comparison of dvir and ibdsim2 — 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.
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.
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.
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.
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.
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.
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.
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.
pedbuildr reconstructs pedigrees from DNA, and it just got much faster at the search.
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.
See all dvir alternatives → · See all ibdsim2 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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 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.