glyfun
glyfun is three releases old and has spent all of them chasing glyexp's container change.
A side-by-side editorial comparison of glymotif and vellumwidget — release velocity, themes, recent moves, and the top alternatives to consider.
A glycan motif matcher trading convenience wrappers for speed, strictness and explicit specs.
glymotif detects and counts structural motifs in glycans, over a built-in motif database or user-supplied structures, with fuzzy modification matching and alignment control. Database motifs are now requested through a db_motifs_spec object carrying their own matching parameters rather than as a name vector with loose arguments, and db_motif_info() exposes the built-in set as an inspectable tibble. A lenient mode lets lower-information glycans match more specific motifs while concrete mismatches still fail, and low-level entry points work directly on igraph objects for other package authors.
vellumwidget is dissolving its own API: interaction now lives in the plot spec, not the widget call.
vellumwidget compiles a vellum scene or a vellumplot plot into a self-contained client-side htmlwidget with hover, select, brush, lasso, pan/zoom and export, and no server round-trip. The two-way Shiny story is complete: interactions surface as reactive inputs keyed by output id, and vellumwidget_proxy() drives an already-rendered widget from the server without re-rendering it. The last two releases are fidelity work rather than new surface, calibrating hit-testing from the rendered positions of marks and rendering the raster base image at 2x for HiDPI screens.
glymotif detects and counts structural motifs in glycans, over a built-in motif database or user-supplied structures, with fuzzy modification matching and alignment control. Database motifs are now requested through a db_motifs_spec object carrying their own matching parameters rather than as a name vector with loose arguments, and db_motif_info() exposes the built-in set as an inspectable tibble. A lenient mode lets lower-information glycans match more specific motifs while concrete mismatches still fail, and low-level entry points work directly on igraph objects for other package authors.
Performance has been a recurring line item across at least four releases, culminating in optimised graph searches and candidate filtering aimed at batch analyses, which points at the real workload being whole experiments rather than single glycans. The API has moved the other way from convenience toward explicitness: the add_motifs_lgl() and add_motifs_int() wrappers are deprecated in favour of composing with dplyr or glyexp verbs, optional arguments must now be named, and loose matching parameters were folded into the spec object. Documentation is being steered toward the cohort's newer container types, so this package is following a coordinated migration rather than setting its own course.
With the deprecated annotation wrappers on their way out and documentation already pointing at the replacement verbs, their removal is the likely next breaking change. The lenient matching mode is new enough that its boundary against concrete mismatches will probably need tuning as users apply it to real, partially resolved data.
vellumwidget compiles a vellum scene or a vellumplot plot into a self-contained client-side htmlwidget with hover, select, brush, lasso, pan/zoom and export, and no server round-trip. The two-way Shiny story is complete: interactions surface as reactive inputs keyed by output id, and vellumwidget_proxy() drives an already-rendered widget from the server without re-rendering it. The last two releases are fidelity work rather than new surface, calibrating hit-testing from the rendered positions of marks and rendering the raster base image at 2x for HiDPI screens.
The direction is declarative. 0.7.0 removed the interaction-intent arguments from as_widget() outright, dropping the signature from roughly 36 arguments to 24 and moving highlight, filter and cross-filter into vellumplot's spec via select_point(), condition() and filter_by(). Each release since has enacted more of that compiled spec on the frozen scene, from conditional encodings to single-view filters to cross-view cross-filtering, leaving the widget as an interpreter of the plot rather than a configuration surface of its own. The bug fixes track the same theme the engine's do: measured geometry and rendered geometry must not drift.
The notes name the remaining hold-outs explicitly, saying hover_mode, crosshair, legend_click, select_mode and the tooltip-appearance arguments remain only until their spec equivalents land, so the next releases most likely move those into vellumplot and shrink as_widget() further. The scale binds flagged as following the filter work are the other stated next step.
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 glymotif or vellumwidget.
glyfun is three releases old and has spent all of them chasing glyexp's container change.
glydet is rebuilding its glycan trait vocabulary on top of someone else's container.
glyexp is retiring its own data container and handing the job to Bioconductor.
The type system the rest of the glycan stack is built on, being hardened one breaking change at a time.
Glycan annotation stops depending on the database having seen the structure before.
SNFG glycan cartoons stopped being pictures and became ggplot2 geoms, guides and axis labels.
See all glymotif alternatives → · See all vellumwidget alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. vellumwidget is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. vellumwidget is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 glymotif alternatives in Analytics are ranked by recent ship velocity. Browse the "glymotif alternatives" section above for the current picks, or visit /alternatives/glymotif for the full list with editorial commentary on each.
Top vellumwidget alternatives in Analytics are ranked by recent ship velocity. Browse the "vellumwidget alternatives" section above for the current picks, or visit /alternatives/vellumwidget for the full list with editorial commentary on each.