gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
Comparison · Analytics
dvir vs glyanno
A side-by-side editorial comparison of dvir and glyanno — release velocity, themes, recent moves, and the top alternatives to consider.
dvir vs glyanno: 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 glyanno?
Glycan annotation stops depending on the database having seen the structure before.
glyanno resolves mass spectrometry observations into glycan compositions and structures, converting between m/z, composition and structure, filling in missing detail on partial structures, and mapping results to GlyTouCan accessions. The newest release adds de novo reconstruction of topological N-glycans, falling back to the topological database only when reconstruction is not possible. Batch performance was reworked at the same time, with vector inputs reusing prepared databases and direct lookups instead of repeating setup per element.
dvir vs glyanno: 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.
glyanno
3.8ANALYTICS
Glycan annotation stops depending on the database having seen the structure before.
◆ Current state
glyanno resolves mass spectrometry observations into glycan compositions and structures, converting between m/z, composition and structure, filling in missing detail on partial structures, and mapping results to GlyTouCan accessions. The newest release adds de novo reconstruction of topological N-glycans, falling back to the topological database only when reconstruction is not possible. Batch performance was reworked at the same time, with vector inputs reusing prepared databases and direct lookups instead of repeating setup per element.
◆ Where it's heading
The consistent theme is making ambiguous results honest and predictable. return_best moved from returning a shortened tibble to a vector aligned with the input, with NA for unmatched glycans; matching concrete compositions against a generic database now errors instead of silently returning nothing; zero-length database arguments are rejected. Alongside that, functions belonging elsewhere have been pushed down into glyrepr rather than duplicated, which is the same boundary discipline visible across this cohort. Version churn is largely driven by upstream: two of the last six entries exist to absorb breaking changes in glyrepr.
◆ Prediction
De novo reconstruction currently covers topological N-glycans only, so extending it to other structure levels or to O-glycans is the natural next step. The performance work suggests batch annotation of full experiments is now the primary use being optimised for.
Alternatives to dvir and glyanno
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 glyanno.
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 glyanno alternatives →
Recent activity from dvir and glyanno
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 24d agoglyannoDe novo reconstruction of topological N-glycans, with database fallback ⚡
- 1mo agodvirCombination sizing and a cutoff for joint analysis
- 3mo agodvirJoint tables added to solver output
- 3mo agoglyannoGlyTouCan accession mapping and anomeric position filling
- 3mo agoglyannoFixes an enhance_struc() break from glyrepr 0.11.0
- 3mo agodvirVictim and database accessors, plus solver refinements
- 4mo agoglyannoExplicit empty return from com_to_struc()
- 4mo agoglyannoreturn_best output aligns with input length; silent empty matches now error
- 5mo agoglyannoto_level parameter removed from enhance_struc()
- 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 glyanno?
They serve adjacent needs but don't currently overlap on shipped themes. glyanno is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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.
Is dvir better than glyanno?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. glyanno is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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.
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 glyanno?
Top glyanno alternatives in Analytics are ranked by recent ship velocity. Browse the "glyanno alternatives" section above for the current picks, or visit /alternatives/glyanno for the full list with editorial commentary on each.