gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
Comparison · Analytics
glyparse vs KLINK
A side-by-side editorial comparison of glyparse and KLINK — release velocity, themes, recent moves, and the top alternatives to consider.
glyparse vs KLINK: at a glance
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.
What is KLINK?
Forensic kinship testing with linked STR markers, now peer-reviewed and taking data from anywhere.
KLINK is a Shiny application and R package for kinship testing that accounts for linkage between STR markers, rather than treating all markers as independent. The built-in genetic map covers 50 common STR markers, pairs them dynamically after data loads, and lets the user set the maximum distance at which a pair counts as linked. Custom marker maps can now arrive as Excel files including KLINK's own download files, and a paper describing the tool was published in FSI:Genetics in 2026.
glyparse vs KLINK: editorial side-by-side
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.
KLINK
2.5ANALYTICS
Forensic kinship testing with linked STR markers, now peer-reviewed and taking data from anywhere.
◆ Current state
KLINK is a Shiny application and R package for kinship testing that accounts for linkage between STR markers, rather than treating all markers as independent. The built-in genetic map covers 50 common STR markers, pairs them dynamically after data loads, and lets the user set the maximum distance at which a pair counts as linked. Custom marker maps can now arrive as Excel files including KLINK's own download files, and a paper describing the tool was published in FSI:Genetics in 2026.
◆ Where it's heading
The direction is from fixed panel toward general instrument. Hard-coded linkage pairs gave way to dynamic pairing, the built-in map grew from 18 to 50 markers, the map itself was then moved out to the norSTR package, and the app now accepts custom maps in several file formats and decimal conventions. Method capability tracks the upstream pedsuite rather than KLINK itself: special lumping in pedprobr and pedmut is what allowed complex mutation models in common pedigrees, and the newest release pins pedtools 2.11.0 and pedprobr 1.1.0 for faster likelihoods and better handling of looped pedigrees. Much of the remaining work is unglamorous casework ergonomics, replacing stray Norwegian text in Excel output, controlling table heights, fixing karyogram colours.
◆ Prediction
With the map externalised and custom maps loading from multiple formats, the likeliest next step is broader marker-panel coverage through norSTR rather than changes in KLINK itself. Method gains should continue to arrive as pedprobr and pedmut version bumps.
Alternatives to glyparse and KLINK
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 KLINK.
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 glyparse alternatives → · See all KLINK alternatives →
Recent activity from glyparse and KLINK
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoKLINKExcel marker maps, more robust map loading, and a published paper
- 1mo agoglyparseParser output uses glyrepr's public constructor
- 1mo agoglyparseFour new notations parsed and auto-detected
- 1mo agoglyparseWURCS and GlycoCT edge cases handled
- 3mo agoglyparseon_failure lets parsers return NA instead of erroring
- 3mo agoKLINKIn-app help pages, a mutation-model setting, and clearer controls
- 5mo agoglyparseIUPAC parser accepts plain-text equivalents
- 5mo agoglyparseParsers get 10-30x faster on large inputs
- 1y agoKLINKComplex mutation models become usable via upstream special lumping
- 1y agoKLINKDownload fix for XML initials containing hyphens
- 1y agoKLINKUnlinked report picks the higher-PIC marker from each pair
- 2y agoKLINKMarkers pair dynamically against a 50-marker map, replacing hard-coded pairs ⚡
Frequently asked questions
What is the difference between glyparse and KLINK?
They serve adjacent needs but don't currently overlap on shipped themes. KLINK 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.
Is glyparse better than KLINK?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. KLINK 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.
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.
What are the best alternatives to KLINK?
Top KLINK alternatives in Analytics are ranked by recent ship velocity. Browse the "KLINK alternatives" section above for the current picks, or visit /alternatives/klink for the full list with editorial commentary on each.