gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
A side-by-side editorial comparison of dvir and glyfun — 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.
glyfun is three releases old and has spent all of them chasing glyexp's container change.
glyfun is the newest glycoverse package, carved out to hold the enrichment analysis functions that glystats deprecated. Its entire visible history is the 0.1.x series, and all three releases are container plumbing: detected_universe() learning to accept GlycoproteomicSE, then the vignette and documentation following. There is no independent feature work in the record yet.
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.
glyfun is the newest glycoverse package, carved out to hold the enrichment analysis functions that glystats deprecated. Its entire visible history is the 0.1.x series, and all three releases are container plumbing: detected_universe() learning to accept GlycoproteomicSE, then the vignette and documentation following. There is no independent feature work in the record yet.
This is a package being born into a migration rather than one navigating it. Because glystats removed its gly_enrich_*() functions outright and glysmith already routes enrichment through glyfun, the functional surface is inherited rather than designed here. The near-term arc is catching up to the rest of the stack; the interesting question is what glyfun adds once it is no longer just the relocation target.
Expect the first release with genuinely new enrichment capability rather than migration plumbing, most likely broadening the gene-set sources glystats never covered.
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 glyfun.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dvir and glyfun 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 glyfun 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 glyfun alternatives in Analytics are ranked by recent ship velocity. Browse the "glyfun alternatives" section above for the current picks, or visit /alternatives/glyfun for the full list with editorial commentary on each.