gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
A side-by-side editorial comparison of glyfun and pedbuildr — release velocity, themes, recent moves, and the top alternatives to consider.
glyfun is three releases old and has spent all of them chasing glyexp's container change.
glyfun is the newest glycoverse package, carved out to hold the enrichment analysis functions that glystats deprecated. Its entire visible history is the 0.1.x series, and all three releases are container plumbing: detected_universe() learning to accept GlycoproteomicSE, then the vignette and documentation following. There is no independent feature work in the record yet.
pedbuildr reconstructs pedigrees from DNA, and it just got much faster at the search.
pedbuildr infers pedigree structure from marker data by scoring candidate pedigrees against likelihoods. Version 0.4.0 moved reconstruct() to mirai for parallel likelihood computation, deprecated the old numCores argument, and picked up the improved loop breaking from pedtools and pedprobr, which lets many complex looped pedigrees succeed where they previously failed. buildPeds() also got significantly faster in its default configuration where mating between lineally related individuals is disallowed.
glyfun is the newest glycoverse package, carved out to hold the enrichment analysis functions that glystats deprecated. Its entire visible history is the 0.1.x series, and all three releases are container plumbing: detected_universe() learning to accept GlycoproteomicSE, then the vignette and documentation following. There is no independent feature work in the record yet.
This is a package being born into a migration rather than one navigating it. Because glystats removed its gly_enrich_*() functions outright and glysmith already routes enrichment through glyfun, the functional surface is inherited rather than designed here. The near-term arc is catching up to the rest of the stack; the interesting question is what glyfun adds once it is no longer just the relocation target.
Expect the first release with genuinely new enrichment capability rather than migration plumbing, most likely broadening the gene-set sources glystats never covered.
pedbuildr infers pedigree structure from marker data by scoring candidate pedigrees against likelihoods. Version 0.4.0 moved reconstruct() to mirai for parallel likelihood computation, deprecated the old numCores argument, and picked up the improved loop breaking from pedtools and pedprobr, which lets many complex looped pedigrees succeed where they previously failed. buildPeds() also got significantly faster in its default configuration where mating between lineally related individuals is disallowed.
The package is bounded by two costs: how many candidate pedigrees it enumerates and how expensive each likelihood is. The recent release attacks both, parallelizing the likelihoods and speeding up enumeration in the common case. The earlier 0.3.0 release worked on the other end, adding inbreeding limits and a proper result class so the output of a large search is manageable. Releases are infrequent, roughly three years apart in this window.
Expect the candidate generation side to receive the same attention the likelihood side just did, since search space size is the remaining bound on what pedbuildr can reconstruct.
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 glyfun or pedbuildr.
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.
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.
pedmut turns awkward mutation models into ones the likelihood engine can actually handle.
See all glyfun alternatives → · See all pedbuildr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r packages — within Analytics. glyfun and pedbuildr are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. glyfun and pedbuildr are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top glyfun alternatives in Analytics are ranked by recent ship velocity. Browse the "glyfun alternatives" section above for the current picks, or visit /alternatives/glyfun for the full list with editorial commentary on each.
Top pedbuildr alternatives in Analytics are ranked by recent ship velocity. Browse the "pedbuildr alternatives" section above for the current picks, or visit /alternatives/pedbuildr for the full list with editorial commentary on each.