spsurvey
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
A side-by-side editorial comparison of forrel and tibblify — 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.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
tibblify converts nested lists and JSON into rectangular tibbles using an explicit specification of the expected structure. Its 0.2.0 rewrite moved the engine to C and reset the API; 0.3.1 then added a path to generate specifications from an OpenAPI document rather than hand-writing them. 0.4.0 in May 2026 is the first release in over two years, and it is a breaking cleanup.
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().
tibblify converts nested lists and JSON into rectangular tibbles using an explicit specification of the expected structure. Its 0.2.0 rewrite moved the engine to C and reset the API; 0.3.1 then added a path to generate specifications from an OpenAPI document rather than hand-writing them. 0.4.0 in May 2026 is the first release in over two years, and it is a breaking cleanup.
The arc runs from 'write a spec by hand' toward 'the spec comes from somewhere else'. Alongside the OpenAPI importer, guess_tspec() gained exported variants so users can override its dispatch, and untibblify() now picks up the tib_spec attribute automatically. 0.4.0's breaking change prefixes all arguments of dot-accepting functions with a period to avoid collisions with column names, softened by a once-per-session deprecation warning, and refactors the entire codebase.
The un-dotted argument forms are explicitly slated for removal, so the next release most likely completes that deprecation. Whether the 0.4.0 refactor introduced corner-case regressions is the open question the release notes themselves raise.
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 tibblify.
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
ieegio's first release lands electrode trajectory burning and a WebGL-free surface plot
See all forrel alternatives → · See all tibblify alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. forrel and tibblify 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 tibblify 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 tibblify alternatives in Analytics are ranked by recent ship velocity. Browse the "tibblify alternatives" section above for the current picks, or visit /alternatives/tibblify for the full list with editorial commentary on each.