gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
Comparison · Analytics
dvir vs glysmith
A side-by-side editorial comparison of dvir and glysmith — release velocity, themes, recent moves, and the top alternatives to consider.
dvir vs glysmith: 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 glysmith?
glysmith turns an LLM interview into a reproducible glycomics analysis pipeline.
glysmith is the orchestration layer of glycoverse: inquire_blueprint() interviews the user, and forge_analysis() runs the resulting step blueprint end to end. The recent 0.12.x releases wired that pipeline onto glyexp's new SummarizedExperiment containers, and 0.12.0 pulled QC sample handling out of step_preprocess() entirely. The larger feature release was 0.11.0, which added structure inference and three more enrichment steps to the step catalogue.
dvir vs glysmith: 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.
glysmith
0.0ANALYTICS
glysmith turns an LLM interview into a reproducible glycomics analysis pipeline.
◆ Current state
glysmith is the orchestration layer of glycoverse: inquire_blueprint() interviews the user, and forge_analysis() runs the resulting step blueprint end to end. The recent 0.12.x releases wired that pipeline onto glyexp's new SummarizedExperiment containers, and 0.12.0 pulled QC sample handling out of step_preprocess() entirely. The larger feature release was 0.11.0, which added structure inference and three more enrichment steps to the step catalogue.
◆ Where it's heading
The package is growing along two axes: more steps in the catalogue, and less ceremony around getting to them. QC handling and preprocessing arguments keep being removed rather than added, while the AI layer widens to more providers instead of getting more elaborate. glysmith is also the package that absorbs the rest of the stack's reorganizations, routing enrichment to glyfun after glystats deprecated it and pulling structure inference from glyanno.
◆ Prediction
Expect the step catalogue to keep tracking sibling packages, with new steps appearing shortly after the packages behind them ship the underlying capability.
Alternatives to dvir and glysmith
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 glysmith.
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 glysmith alternatives →
Recent activity from dvir and glysmith
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoglysmithBlueprint functions accept the new SE containers
- 1mo agoglysmithforge_analysis() runs natively on SummarizedExperiment
- 1mo agodvirCombination sizing and a cutoff for joint analysis
- 2mo agoglysmithQC sample handling removed from preprocessing
- 3mo agodvirJoint tables added to solver output
- 3mo agoglysmithStructure inference and three new enrichment steps
- 3mo agodvirVictim and database accessors, plus solver refinements
- 5mo agoglysmithstep_preprocess() matches its documented QC behavior
- 5mo agoglysmithMotif quantification splits into dynamic and branch steps
- 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 glysmith?
They serve adjacent needs but don't currently overlap on shipped themes. dvir and glysmith 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 glysmith?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dvir and glysmith 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 glysmith?
Top glysmith alternatives in Analytics are ranked by recent ship velocity. Browse the "glysmith alternatives" section above for the current picks, or visit /alternatives/glysmith for the full list with editorial commentary on each.