gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
Comparison · Analytics
dvir vs glydet
A side-by-side editorial comparison of dvir and glydet — release velocity, themes, recent moves, and the top alternatives to consider.
dvir vs glydet: 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 glydet?
glydet is rebuilding its glycan trait vocabulary on top of someone else's container.
glydet derives glycan-derived traits from glycomics and glycoproteomics data. The 0.12.x line spent its releases absorbing glyexp's container migration: derive_traits(), quantify_motifs(), and add_meta_properties() now accept GlycomicSE and GlycoproteomicSE natively, with the legacy experiment() path kept only for backward-compatible return types. The substantive feature work sits one release back in 0.11.0, which added sialic acid linkage traits and three published trait sets.
dvir vs glydet: 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.
glydet
0.0ANALYTICS
glydet is rebuilding its glycan trait vocabulary on top of someone else's container.
◆ Current state
glydet derives glycan-derived traits from glycomics and glycoproteomics data. The 0.12.x line spent its releases absorbing glyexp's container migration: derive_traits(), quantify_motifs(), and add_meta_properties() now accept GlycomicSE and GlycoproteomicSE natively, with the legacy experiment() path kept only for backward-compatible return types. The substantive feature work sits one release back in 0.11.0, which added sialic acid linkage traits and three published trait sets.
◆ Where it's heading
Two threads run in parallel here. One is infrastructure: track glyexp's Stage II migration, drop the underscore matrix interfaces, and converge on a single trait column in var_info. The other is content: keep adding named trait sets from the literature (Clerc 2018, Li 2025, Fu 2026) so users cite a set rather than hand-roll definitions. The LLM-backed explain_trait() and make_trait() helpers are becoming provider-agnostic rather than deeper.
◆ Prediction
The trait catalogue is the growth area, so expect more published trait sets added as named functions, and the deprecated basic_traits() and all_traits() aliases to be removed once the container migration settles.
Alternatives to dvir and glydet
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 glydet.
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.
Recent activity from dvir and glydet
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoglydetDocs and vignettes move to SummarizedExperiment inputs
- 1mo agoglydetTrait functions behave consistently across both containers
- 1mo agoglydetContainer migration lands alongside batch trait creation
- 1mo agoglydetglymotif 0.17 compatibility and clearer trait wording
- 1mo agodvirCombination sizing and a cutoff for joint analysis
- 3mo agodvirJoint tables added to solver output
- 3mo agoglydetSialic acid linkage traits and three published trait sets
- 3mo agodvirVictim and database accessors, plus solver refinements
- 4mo agoglydetVariable name standardization and vignette fixes
- 1y agodvirSolver rewritten around generalised likelihood ratios
- 2y agodvirdviSolve() pipeline and manual pairing controls
- 2y agodvirMaintainer handover and small reporting additions
Frequently asked questions
What is the difference between dvir and glydet?
They serve adjacent needs but don't currently overlap on shipped themes. dvir and glydet 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 glydet?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dvir and glydet 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 glydet?
Top glydet alternatives in Analytics are ranked by recent ship velocity. Browse the "glydet alternatives" section above for the current picks, or visit /alternatives/glydet for the full list with editorial commentary on each.