tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
A side-by-side editorial comparison of forrel and pedtools — 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.
pedtools rewrote loop breaking and made a class of pedigrees analyzable for the first time.
pedtools is the foundation of the ped suite, holding the pedigree data structures every other package builds on. Version 2.11.0 revamped the loop breaking algorithm so founders can serve as loop breakers and one individual can break several loops, which makes likelihood calculations possible in pedigrees that previously could not be handled at all. Loop detection also became mandatory and faster, and the surrounding releases have steadily added query and construction helpers.
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().
pedtools is the foundation of the ped suite, holding the pedigree data structures every other package builds on. Version 2.11.0 revamped the loop breaking algorithm so founders can serve as loop breakers and one individual can break several loops, which makes likelihood calculations possible in pedigrees that previously could not be handled at all. Loop detection also became mandatory and faster, and the surrounding releases have steadily added query and construction helpers.
The package has been working toward this for over a year. Version 2.8.0 replaced the igraph-based loop breaker with a custom implementation, 2.8.1 made findLoopBreakers() substantially faster in large pedigrees, and 2.11.0 rewrote the algorithm outright. The new methods ship disabled by default while downstream packages catch up, which is a deliberately staged rollout rather than a flag day. Alongside that, the additive work is small, well-scoped helpers: children2(), addSibling(), isHomozygous(), trim(), nChildren().
Expect the new loop breaking methods to become the default once pedprobr, forrel, and dvir have all shipped support for them, since the only stated reason for the opt-in flag is downstream readiness.
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 pedtools.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
See all forrel alternatives → · See all pedtools alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — forensic genetics — within Analytics. forrel and pedtools 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 pedtools 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 pedtools alternatives in Analytics are ranked by recent ship velocity. Browse the "pedtools alternatives" section above for the current picks, or visit /alternatives/pedtools for the full list with editorial commentary on each.