gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
A side-by-side editorial comparison of glyenzy and glyfun — release velocity, themes, recent moves, and the top alternatives to consider.
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.
glyfun is three releases old and has spent all of them chasing glyexp's container change.
glyfun is the newest glycoverse package, carved out to hold the enrichment analysis functions that glystats deprecated. Its entire visible history is the 0.1.x series, and all three releases are container plumbing: detected_universe() learning to accept GlycoproteomicSE, then the vignette and documentation following. There is no independent feature work in the record yet.
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.
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.
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.
glyfun is the newest glycoverse package, carved out to hold the enrichment analysis functions that glystats deprecated. Its entire visible history is the 0.1.x series, and all three releases are container plumbing: detected_universe() learning to accept GlycoproteomicSE, then the vignette and documentation following. There is no independent feature work in the record yet.
This is a package being born into a migration rather than one navigating it. Because glystats removed its gly_enrich_*() functions outright and glysmith already routes enrichment through glyfun, the functional surface is inherited rather than designed here. The near-term arc is catching up to the rest of the stack; the interesting question is what glyfun adds once it is no longer just the relocation target.
Expect the first release with genuinely new enrichment capability rather than migration plumbing, most likely broadening the gene-set sources glystats never covered.
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 glyfun.
gps2gtfs spent a release making its docs stop describing functions it does not have.
ducksemantics puts an ontology graph and ColBERT retrieval inside DuckDB, callable from R.
dvir keeps making disaster victim identification a single call instead of a workflow.
pedbuildr reconstructs pedigrees from DNA, and it just got much faster at the search.
forrel is getting faster at the simulations forensic kinship work actually spends its time on.
pedFamilias exists to read one legacy file format, and it has that job nearly finished.
See all glyenzy alternatives → · See all glyfun alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
Top glyfun alternatives in Analytics are ranked by recent ship velocity. Browse the "glyfun alternatives" section above for the current picks, or visit /alternatives/glyfun for the full list with editorial commentary on each.