tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
Comparison · Analytics
dvir vs glycoverse
A side-by-side editorial comparison of dvir and glycoverse — release velocity, themes, recent moves, and the top alternatives to consider.
dvir vs glycoverse: 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 glycoverse?
glycoverse is a meta-package whose whole job is keeping a dozen siblings installable.
glycoverse installs and version-checks the rest of the stack via glycoverse_update(), glycoverse_deps(), and glycoverse_sitrep(). Its releases track membership and distribution rather than capability: glyfun was reclassified as non-core in 0.3.1, the case studies were moved out to a standalone tutorials site in 0.3.2, and 0.2.5 switched installation from GitHub releases to r-universe. No analysis code lives here.
dvir vs glycoverse: 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.
glycoverse
0.0ANALYTICS
glycoverse is a meta-package whose whole job is keeping a dozen siblings installable.
◆ Current state
glycoverse installs and version-checks the rest of the stack via glycoverse_update(), glycoverse_deps(), and glycoverse_sitrep(). Its releases track membership and distribution rather than capability: glyfun was reclassified as non-core in 0.3.1, the case studies were moved out to a standalone tutorials site in 0.3.2, and 0.2.5 switched installation from GitHub releases to r-universe. No analysis code lives here.
◆ Where it's heading
The package is thinning as the ecosystem grows. Documentation moved off to its own site, packages keep shifting between core and non-core, and installation was handed to pak and r-universe rather than bespoke logic. Meanwhile the substantive work in this window happened in the siblings, notably the container migration that reshaped ten of them without requiring a glycoverse release at all.
◆ Prediction
Expect the next release to be another membership or version-pinning adjustment, most likely acknowledging the newer packages that joined during the container migration.
Alternatives to dvir and glycoverse
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 glycoverse.
spsurvey
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
rpymat
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
See all dvir alternatives → · See all glycoverse alternatives →
Recent activity from dvir and glycoverse
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoglycoverseCase studies move to a standalone tutorials site
- 1mo agodvirCombination sizing and a cutoff for joint analysis
- 2mo agoglycoverseglyfun reclassified as a non-core package
- 3mo agodvirJoint tables added to solver output
- 3mo agodvirVictim and database accessors, plus solver refinements
- 4mo agoglycoverseglycoverse_update() gains dev-version control
- 6mo agoglycoverseInstallation moves from GitHub releases to r-universe
- 6mo agoglycoverseNon-core packages no longer skipped on update
- 7mo agoglycoverseSwitch to the CRAN version of glyparse
- 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 glycoverse?
They serve adjacent needs but don't currently overlap on shipped themes. dvir and glycoverse 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 glycoverse?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dvir and glycoverse 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 glycoverse?
Top glycoverse alternatives in Analytics are ranked by recent ship velocity. Browse the "glycoverse alternatives" section above for the current picks, or visit /alternatives/glycoverse for the full list with editorial commentary on each.