gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
Comparison · Analytics
glyenzy vs glyexp
A side-by-side editorial comparison of glyenzy and glyexp — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:glycomics
glyenzy vs glyexp: at a glance
What is glyenzy?
Glycan biosynthesis as a traceable enzyme graph, now including sulfation and gaps it can bridge.
glyenzy infers which enzymes could have produced a glycan and traces biosynthetic routes to it, backed by curated per-enzyme rules for human glycosyltransferases and, since 0.7.0, twelve sulfotransferases. Biosynthesis functions return typed network objects that keep their igraph interface while supporting layered DAG plots with glycan nodes and labelled enzyme edges. Where no concrete enzyme covers a step, bounded virtual transitions bridge the gap and are marked so users can see which edges are inferred rather than enzymatic.
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().
glyenzy vs glyexp: editorial side-by-side
glyenzy
6.3ANALYTICS
Glycan biosynthesis as a traceable enzyme graph, now including sulfation and gaps it can bridge.
◆ Current state
glyenzy infers which enzymes could have produced a glycan and traces biosynthetic routes to it, backed by curated per-enzyme rules for human glycosyltransferases and, since 0.7.0, twelve sulfotransferases. Biosynthesis functions return typed network objects that keep their igraph interface while supporting layered DAG plots with glycan nodes and labelled enzyme edges. Where no concrete enzyme covers a step, bounded virtual transitions bridge the gap and are marked so users can see which edges are inferred rather than enzymatic.
◆ Where it's heading
Two kinds of release alternate here. One is enzyme curation, a steady stream of rule corrections for the FUT, MAN1A and MGAT families and removals where an enzyme turned out to act only on glycolipids, which is the unglamorous accuracy work a rule-based inference engine lives on. The other is turning biosynthesis output into a first-class object: paths became networks, networks became typed with plotting support, and targets became a marked vertex attribute. The package moves in lockstep with its siblings, pinning glyrepr 0.13.0 and glymotif 0.17.0 as those refreshed their data and matching APIs, and the latest release already speaks glydraw 0.8.0's orientation values.
◆ Prediction
The paucimannose N-glycan support dropped in 0.7.0 is the obvious loose end, with users told to stay on 0.6.3, so a reinstated implementation is a plausible next move. Beyond that the virtual-step machinery is new enough that its heuristics, particularly the inferred step limits added in 0.8.1, should keep being tuned.
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 glyenzy 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 glyenzy or glyexp.
ducksemantics
ducksemantics puts an ontology graph and ColBERT retrieval inside DuckDB, callable from R.
dvir
dvir keeps making disaster victim identification a single call instead of a workflow.
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.
See all glyenzy alternatives → · See all glyexp alternatives →
Recent activity from glyenzy and glyexp
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 14d agoglyenzyStep limits inferred from the target glycan; MGAT4 and MGAT5 rules updated
- 17d agoglyenzyBiosynthesis results become typed network objects with layered DAG plots
- 23d agoglyenzySulfotransferases become first-class, and unsupported steps can be bridged ⚡
- 1mo agoglyexpglyexp deprecates its own container for SummarizedExperiment ⚡
- 1mo agoglyexpExperimental GlycomicSE and GlycoproteomicSE containers land
- 1mo agoglyenzyCompatibility with glymotif 0.17.0 and later
- 1mo agoglyenzyEnzyme data refreshed against glyrepr 0.13.0 structure data
- 1mo agoglyexpfrom_se() metadata fixes and dataset refresh
- 1mo agoglyenzyCorrected rules for the MAN1A1, MAN1A2 and MAN1C1 mannosidases
- 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
Frequently asked questions
What is the difference between glyenzy and glyexp?
Both compete on the same themes — glycomics — within Analytics. glyenzy is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is glyenzy better than glyexp?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. glyenzy is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to glyenzy?
Top glyenzy alternatives in Analytics are ranked by recent ship velocity. Browse the "glyenzy alternatives" section above for the current picks, or visit /alternatives/glyenzy 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.