rasterpic
rasterpic became an S3 generic and picked up stars support; the rest is upkeep
Comparison · Analytics
dvir vs glyread
A side-by-side editorial comparison of dvir and glyread — release velocity, themes, recent moves, and the top alternatives to consider.
dvir vs glyread: 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 glyread?
glyread now hands every importer's output straight to Bioconductor.
glyread is the import layer, converting output from pGlyco3, Byonic, GlycanFinder, GlyHunter, and pGlycoQuant into glycoverse objects. Version 0.12.0 changed what those objects are: every read_*() function now returns GlycomicSE or GlycoproteomicSE, and 0.12.1 raised the glyexp floor to 0.16.0 to match. Earlier releases in the window went to format handling, particularly multi-glycosite glycopeptides and linkage-specific derivatization presets.
dvir vs glyread: 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.
glyread
0.0ANALYTICS
glyread now hands every importer's output straight to Bioconductor.
◆ Current state
glyread is the import layer, converting output from pGlyco3, Byonic, GlycanFinder, GlyHunter, and pGlycoQuant into glycoverse objects. Version 0.12.0 changed what those objects are: every read_*() function now returns GlycomicSE or GlycoproteomicSE, and 0.12.1 raised the glyexp floor to 0.16.0 to match. Earlier releases in the window went to format handling, particularly multi-glycosite glycopeptides and linkage-specific derivatization presets.
◆ Where it's heading
As the stack's entry point, glyread absorbs container decisions first and hardest: because it constructs the objects everything downstream consumes, it had no compatibility path and simply switched return types. The other visible thread is coverage of upstream software, adding importers and presets as new search engines and protocols appear. Those two threads rarely interact.
◆ Prediction
Expect the next releases to return to importer coverage, adding formats or presets, now that the container question is settled at the source.
Alternatives to dvir and glyread
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 glyread.
igoR
igoR reached 1.0.0 with no user-visible change, then spent three releases on AI-assisted cleanup
parglm
Under a new maintainer, parglm traded raw speed work for glm parity and memory safety
epinowcast
epinowcast added Gaussian processes to its formula interface and made the sampler twice as fast
duckspatial
duckspatial rebuilt itself around a lazy DuckDB class, then spent four releases filling in the geometry surface
timbr
Three years dormant, timbr returns with dplyr verbs that finally respect tree structure
See all dvir alternatives → · See all glyread alternatives →
Recent activity from dvir and glyread
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoglyreadMinimum glyexp version raised to 0.16.0
- 1mo agoglyreadAll read_*() functions return SummarizedExperiment objects
- 1mo agodvirCombination sizing and a cutoff for joint analysis
- 3mo agodvirJoint tables added to solver output
- 3mo agoglyreadMulti-glycosite glycopeptides get an expand-or-drop option
- 3mo agodvirVictim and database accessors, plus solver refinements
- 3mo agoglyreadread_glyhunter() gains a derivatization preset
- 4mo agoglyreadglyread 0.9.2
- 6mo agoglyreadDependency strategy update
- 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 glyread?
They serve adjacent needs but don't currently overlap on shipped themes. dvir and glyread 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 glyread?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dvir and glyread 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 glyread?
Top glyread alternatives in Analytics are ranked by recent ship velocity. Browse the "glyread alternatives" section above for the current picks, or visit /alternatives/glyread for the full list with editorial commentary on each.