gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
A side-by-side editorial comparison of glyparse and ribd — release velocity, themes, recent moves, and the top alternatives to consider.
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.
The pedsuite's coefficient engine: broadening what it computes, then making the plots publishable.
ribd computes relatedness coefficients from pedigrees, covering kinship, inbreeding, kappa, condensed and detailed identity coefficients, and two-locus versions of several of these, in autosomal and X-chromosomal form. The IBD triangle is now drawable in base graphics, ggplot2 or plotly, with an optional inset pedigree, and custom relationships can be placed on it. The most recent release is dominated by correctness work, fixing pair ordering and row alignment in coefficient tables and edge cases for pedigree lists, unrelated individuals and self-pairs.
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.
ribd computes relatedness coefficients from pedigrees, covering kinship, inbreeding, kappa, condensed and detailed identity coefficients, and two-locus versions of several of these, in autosomal and X-chromosomal form. The IBD triangle is now drawable in base graphics, ggplot2 or plotly, with an optional inset pedigree, and custom relationships can be placed on it. The most recent release is dominated by correctness work, fixing pair ordering and row alignment in coefficient tables and edge cases for pedigree lists, unrelated individuals and self-pairs.
The arc runs from generality to presentation to precision. Early releases replaced narrow functions with general ones, most visibly when gKinship() absorbed generalisedKinship() and identityCoefs() superseded the separate autosomal and X-chromosomal identity functions in favour of an Xchrom argument. The middle stretch turned the IBD triangle into a proper plotting surface across three graphics systems. The current phase reads as consolidation, with the newest release listing six bug fixes against four features, several of them alignment errors in output tables, which is where a coefficient library most needs to be exactly right.
The two new internal functions in the latest release, inbreedingContributions() and ancestralKinship(), are the kind of thing that surfaces publicly a release or two later, so expect them to become exported decomposition tools. The correctness push through pedigree lists and edge cases suggests the near-term focus stays on hardening rather than new coefficient families.
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 glyparse or ribd.
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 glyparse alternatives → · See all ribd alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ribd is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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. ribd is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 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.
Top ribd alternatives in Analytics are ranked by recent ship velocity. Browse the "ribd alternatives" section above for the current picks, or visit /alternatives/ribd for the full list with editorial commentary on each.