gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
Comparison · Analytics
glyenzy vs glyparse
A side-by-side editorial comparison of glyenzy and glyparse — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:glycomics
glyenzy vs glyparse: 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 glyparse?
glyparse is quietly becoming the universal reader for glycan text notation.
glyparse converts the various text encodings of glycan structures into glyrepr objects. Version 0.7.0 was the widest release in the window, adding parsers for GlyCAM IUPAC, IUPAC-compact, KCF, and LINUCS and teaching auto_parse() to route them, alongside a long list of GlycoCT and WURCS edge cases. The rest of the window is error-handling and performance work: an on_failure switch, a 10-30x speedup on large inputs, and NA and name preservation.
glyenzy vs glyparse: 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.
glyparse
0.0ANALYTICS
glyparse is quietly becoming the universal reader for glycan text notation.
◆ Current state
glyparse converts the various text encodings of glycan structures into glyrepr objects. Version 0.7.0 was the widest release in the window, adding parsers for GlyCAM IUPAC, IUPAC-compact, KCF, and LINUCS and teaching auto_parse() to route them, alongside a long list of GlycoCT and WURCS edge cases. The rest of the window is error-handling and performance work: an on_failure switch, a 10-30x speedup on large inputs, and NA and name preservation.
◆ Where it's heading
Two things are being built at once. Coverage keeps widening, both in the number of notations supported and in how much malformed or ambiguous real-world input each parser tolerates: alditol residues, unknown ring positions, ambiguous sialic acid descriptors, uppercase residue IDs. Meanwhile the package is hardening for batch use, with progress bars, vectorized speed, and a choice between erroring and returning NA on unparsable strings.
◆ Prediction
With the major notations now covered, expect further releases to go to robustness on messy inputs and to keeping pace with glyrepr's structure representation rather than adding formats.
Alternatives to glyenzy and glyparse
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 glyparse.
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 glyparse alternatives →
Recent activity from glyenzy and glyparse
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 agoglyparseParser output uses glyrepr's public constructor
- 1mo agoglyenzyCompatibility with glymotif 0.17.0 and later
- 1mo agoglyenzyEnzyme data refreshed against glyrepr 0.13.0 structure data
- 1mo agoglyparseFour new notations parsed and auto-detected
- 1mo agoglyparseWURCS and GlycoCT edge cases handled
- 1mo agoglyenzyCorrected rules for the MAN1A1, MAN1A2 and MAN1C1 mannosidases
- 3mo agoglyparseon_failure lets parsers return NA instead of erroring
- 5mo agoglyparseIUPAC parser accepts plain-text equivalents
- 5mo agoglyparseParsers get 10-30x faster on large inputs
Frequently asked questions
What is the difference between glyenzy and glyparse?
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 glyparse?
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 glyparse?
Top glyparse alternatives in Analytics are ranked by recent ship velocity. Browse the "glyparse alternatives" section above for the current picks, or visit /alternatives/glyparse for the full list with editorial commentary on each.