tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
A side-by-side editorial comparison of dvir and reproducible — release velocity, themes, recent moves, and the top alternatives to consider.
dvir keeps making disaster victim identification a single call instead of a workflow.
dvir handles disaster victim identification: matching unidentified remains against reference families using pedigree likelihoods. The package has consolidated around dviSolve(), a complete pipeline introduced in 3.2.1 and rewritten in 3.3.0 to use generalised likelihood ratios for families with several missing persons. Recent releases have been about making that pipeline survive large cases, adding dviGridSize() and a maxAssign cutoff to skip joint analysis when the combination count explodes, plus per-step timings.
reproducible added a windowed read path so remote GeoTiffs never fully download
reproducible provides caching and input-preparation tooling for R workflows, with prepInputs() as the central entry point for fetching, cropping and post-processing spatial data. Only two releases are on record here, both from May 2026 and two days apart: a feature release followed immediately by a CRAN-triggered patch.
dvir handles disaster victim identification: matching unidentified remains against reference families using pedigree likelihoods. The package has consolidated around dviSolve(), a complete pipeline introduced in 3.2.1 and rewritten in 3.3.0 to use generalised likelihood ratios for families with several missing persons. Recent releases have been about making that pipeline survive large cases, adding dviGridSize() and a maxAssign cutoff to skip joint analysis when the combination count explodes, plus per-step timings.
The arc is from a toolbox of functions toward one supervised pipeline, with the older jointDVI() now emitting a legacy message. The current constraint is combinatorial: joint analysis over many victims and missing persons blows up, so the work has gone to measuring the blowup and bailing out of it. Parallelism is mid-migration, with the parallel and pbapply implementation removed and a mirai replacement stated as planned but not yet shipped, leaving numCores accepted and ignored with a warning.
The mirai-based parallelisation is announced as coming, so expect it next, most likely applied to the joint analysis step that maxAssign currently exists to avoid.
reproducible provides caching and input-preparation tooling for R workflows, with prepInputs() as the central entry point for fetching, cropping and post-processing spatial data. Only two releases are on record here, both from May 2026 and two days apart: a feature release followed immediately by a CRAN-triggered patch.
3.1.0 adds prepInputsCOG, a fast path inside prepInputs for remote tiled GeoTiffs including Cloud Optimized GeoTiffs. When the URL is HTTP(S) and any of to, cropTo or maskTo is supplied, only the spatial window of interest is fetched through GDAL's /vsicurl/, and the resulting windowed SpatRaster continues through the normal post-processing pipeline. The same release renames the inputPaths options to the destinationPathShared family with backwards-compatible aliases and a deprecation message, and lets alsoExtract accept regex patterns.
The COG path being opt-out via options(reproducible.useCOG = FALSE) suggests confidence in it as a default, so wider application across the prepInputs family is the plausible next step. Two entries is a thin base for predicting cadence.
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 dvir or reproducible.
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
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 dvir alternatives → · See all reproducible alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dvir and reproducible 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. dvir and reproducible 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 dvir alternatives in Analytics are ranked by recent ship velocity. Browse the "dvir alternatives" section above for the current picks, or visit /alternatives/dvir for the full list with editorial commentary on each.
Top reproducible alternatives in Analytics are ranked by recent ship velocity. Browse the "reproducible alternatives" section above for the current picks, or visit /alternatives/reproducible for the full list with editorial commentary on each.