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 pedprobr and tibblify — release velocity, themes, recent moves, and the top alternatives to consider.
pedprobr is the likelihood engine, and it keeps finding ways to compute what it previously could not.
pedprobr computes pedigree likelihoods for the ped suite. Version 1.1.0 updated its loop handling to match pedtools 2.11.0, including founder and repeated loop breakers, and improved the peeling algorithm with single-child shortcuts and lower memory use. Version 1.0.0 was the other expansion: special lumping lets markers with mutation models that are un-lumpable in the Kemeny-Snell sense be lumped anyway in certain cases, with alleleLimit as a fallback for the rest.
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.
pedprobr computes pedigree likelihoods for the ped suite. Version 1.1.0 updated its loop handling to match pedtools 2.11.0, including founder and repeated loop breakers, and improved the peeling algorithm with single-child shortcuts and lower memory use. Version 1.0.0 was the other expansion: special lumping lets markers with mutation models that are un-lumpable in the Kemeny-Snell sense be lumped anyway in certain cases, with alleleLimit as a fallback for the rest.
Every significant release here removes a class of computation that used to be infeasible, either by making a marker lumpable or by making a loop breakable. The rest is steady peeling-algorithm optimization, which has been reducing memory footprint release after release since 0.9.2. The newly added .diagnostics option suggests the peeling internals are now complex enough that the maintainer needs to inspect them.
Since special lumping is documented as covering only some cases so far, expect further lumping situations to be implemented as pedmut adds them.
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 pedprobr 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 pedprobr 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. pedprobr 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. pedprobr 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 pedprobr alternatives in Analytics are ranked by recent ship velocity. Browse the "pedprobr alternatives" section above for the current picks, or visit /alternatives/pedprobr 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.