gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
Comparison · Analytics
dvir vs glyexp
A side-by-side editorial comparison of dvir and glyexp — release velocity, themes, recent moves, and the top alternatives to consider.
dvir vs glyexp: 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 glyexp?
glyexp is retiring its own data container and handing the job to Bioconductor.
glyexp is the container layer under the glycoverse stack, and it just changed what that container is. Versions 0.15.0 and 0.16.0 introduced GlycomicSE and GlycoproteomicSE as SummarizedExperiment subclasses, taught the dplyr-style verbs to operate on them, and then deprecated the legacy experiment() constructor and its accessors. Earlier releases in the window were narrower: as_pseudo_glycome(), a magrittr-free rewrite, and an offline standardize_variable().
dvir vs glyexp: 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.
glyexp
0.0ANALYTICS
glyexp is retiring its own data container and handing the job to Bioconductor.
◆ Current state
glyexp is the container layer under the glycoverse stack, and it just changed what that container is. Versions 0.15.0 and 0.16.0 introduced GlycomicSE and GlycoproteomicSE as SummarizedExperiment subclasses, taught the dplyr-style verbs to operate on them, and then deprecated the legacy experiment() constructor and its accessors. Earlier releases in the window were narrower: as_pseudo_glycome(), a magrittr-free rewrite, and an offline standardize_variable().
◆ Where it's heading
The package is moving from a bespoke object model to the Bioconductor one, and doing it in explicitly numbered stages tracked in a single issue (glyexp#15). Stage I added the subclasses as experimental; Stage II deprecated the old container and pushed the migration through ten sibling packages within days. The tidy manipulation verbs are being kept as the compatibility bridge, which suggests the dplyr surface is what the maintainer considers glyexp's actual contribution once the container is someone else's.
◆ Prediction
Expect a Stage III release that removes the deprecated experiment() constructor and accessors outright, leaving GlycomicSE and GlycoproteomicSE as the only supported containers.
Alternatives to dvir and glyexp
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 glyexp.
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.
Recent activity from dvir and glyexp
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoglyexpglyexp deprecates its own container for SummarizedExperiment ⚡
- 1mo agoglyexpExperimental GlycomicSE and GlycoproteomicSE containers land
- 1mo agoglyexpfrom_se() metadata fixes and dataset refresh
- 1mo agodvirCombination sizing and a cutoff for joint analysis
- 3mo agodvirJoint tables added to solver output
- 3mo agodvirVictim and database accessors, plus solver refinements
- 4mo agoglyexpfilter_obs() and filter_var() drop unused factor levels
- 4mo agoglyexpas_pseudo_glycome() converts glycoproteomics to glycomics
- 5mo agoglyexpstandardize_variable() drops its UniProt network dependency
- 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 glyexp?
They serve adjacent needs but don't currently overlap on shipped themes. dvir and glyexp 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 glyexp?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dvir and glyexp 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 glyexp?
Top glyexp alternatives in Analytics are ranked by recent ship velocity. Browse the "glyexp alternatives" section above for the current picks, or visit /alternatives/glyexp for the full list with editorial commentary on each.