tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
A side-by-side editorial comparison of dvir and glydb — 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.
glydb is pulling GlyGen's structure database onto the user's own disk.
glydb bundles glycan structure reference data and provides lookup helpers for compositions, structures, and species. The 0.6.0 release grew the bundled dataset to 19,436 GlyGen structures including non-intact glycans, and changed glytoucan_to_struc() to search that local data before falling back to the online GlyGen API. Version 0.4.0 added a confidence attribute that glyanno uses to rank candidate matches.
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.
glydb bundles glycan structure reference data and provides lookup helpers for compositions, structures, and species. The 0.6.0 release grew the bundled dataset to 19,436 GlyGen structures including non-intact glycans, and changed glytoucan_to_struc() to search that local data before falling back to the online GlyGen API. Version 0.4.0 added a confidence attribute that glyanno uses to rank candidate matches.
The arc is from thin wrapper toward self-contained reference: the bundled data keeps growing, online lookups are demoted to fallbacks, and classification vocabularies are being adopted from GlyGen rather than invented locally. The other constant is chasing glyrepr, whose structure representation has changed enough times that regenerating the bundled indexes is a recurring release note.
Expect the bundled dataset to track further GlyGen and GlyTouCan releases, with the online API path continuing to narrow to accessions the local data does not cover.
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 glydb.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dvir and glydb 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 glydb 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 glydb alternatives in Analytics are ranked by recent ship velocity. Browse the "glydb alternatives" section above for the current picks, or visit /alternatives/glydb for the full list with editorial commentary on each.