gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
A side-by-side editorial comparison of forrel and pedbuildr — release velocity, themes, recent moves, and the top alternatives to consider.
forrel is getting faster at the simulations forensic kinship work actually spends its time on.
forrel handles forensic pedigree analysis: kinship likelihood ratios, profile simulation, relationship checking, and missing person calculations. Version 1.9.0 synced with pedtools 2.11.0's loop handling, which the release notes credit with enabling complex pedigrees that were previously intractable, and moved profileSim() to mirai for parallelism. It also added fEstimate() for inbreeding coefficients and parentChildLikelihood() as a fast path for the simplest case.
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.
forrel handles forensic pedigree analysis: kinship likelihood ratios, profile simulation, relationship checking, and missing person calculations. Version 1.9.0 synced with pedtools 2.11.0's loop handling, which the release notes credit with enabling complex pedigrees that were previously intractable, and moved profileSim() to mirai for parallelism. It also added fEstimate() for inbreeding coefficients and parentChildLikelihood() as a fast path for the simplest case.
Two long threads run through the window. One is making the common operations cheap: faster simulations through reorganized likelihood calculations, a dedicated parent-child path, dropped map attribute preservation, log-likelihoods to avoid underflow in kinshipLR(). The other is making relationship checking presentable, with checkPairwise() growing ggplot2 and plotly output, verbal relationship descriptions, and bootstrap p-values. Reference data is maintained alongside both, with the FORCE SNP panel completed and an X-chromosomal counterpart added.
With profileSim() on mirai and the loop handling synced, the next likely step is extending mirai parallelism to the other simulation-heavy functions such as exclusionPower() and the bootstrap in checkPairwise().
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 forrel 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.
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.
pedprobr is the likelihood engine, and it keeps finding ways to compute what it previously could not.
See all forrel alternatives → · See all pedbuildr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — forensic genetics, parallel computing, performance — within Analytics. forrel 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. forrel 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 forrel alternatives in Analytics are ranked by recent ship velocity. Browse the "forrel alternatives" section above for the current picks, or visit /alternatives/forrel 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.