gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
A side-by-side editorial comparison of glydraw and glyparse — release velocity, themes, recent moves, and the top alternatives to consider.
SNFG glycan cartoons stopped being pictures and became ggplot2 geoms, guides and axis labels.
glydraw renders glycan structures as SNFG-standard cartoons, standalone or exported in bulk, and since 0.7.0 as native ggplot2 components: geom_glycan() for observations, geom_node_glycan() for ggraph networks, guide_glycan() for legends, and scale_x_glycan() and scale_y_glycan() for discrete axes. Appearance is configured through a single reusable style object rather than scattered arguments, a consolidation that 0.8.0 made breaking. The colour handling now expects a complete SNFG palette rather than sparse per-monosaccharide overrides.
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.
glydraw renders glycan structures as SNFG-standard cartoons, standalone or exported in bulk, and since 0.7.0 as native ggplot2 components: geom_glycan() for observations, geom_node_glycan() for ggraph networks, guide_glycan() for legends, and scale_x_glycan() and scale_y_glycan() for discrete axes. Appearance is configured through a single reusable style object rather than scattered arguments, a consolidation that 0.8.0 made breaking. The colour handling now expects a complete SNFG palette rather than sparse per-monosaccharide overrides.
The first half of this record is geometry correctness, fixing branch spacing, overlapping linkage annotations, core fucose collisions, triangle alignment and nested side-chain layout, because a cartoon that draws the wrong topology is worse than no cartoon. Once the drawing was trustworthy the package moved outward into ggplot2 and then inward again to consolidate its own API, dropping the glyexp dependency, removing positional argument support, and folding rendering options into style_glydraw(). Each of the last several releases has been explicitly breaking, which is a maintainer using a pre-1.0 window deliberately.
With the style object established and the ggplot2 surface in place, the remaining explicit arguments, show_linkage and orient, are the visible inconsistency and may follow the others into the style. Sibling packages adopt each change within days, as glyenzy did with the new orientation values, so expect the next breaking change to propagate the same way.
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.
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.
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.
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 glydraw or glyparse.
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 glydraw alternatives → · See all glyparse alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — glycomics — within Analytics. glydraw 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. glydraw 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 glydraw alternatives in Analytics are ranked by recent ship velocity. Browse the "glydraw alternatives" section above for the current picks, or visit /alternatives/glydraw for the full list with editorial commentary on each.
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.