reda
A mature recurrent-event toolkit in careful maintenance, shedding weight rather than adding surface.
A side-by-side editorial comparison of forrel and rnpn — 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.
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
rnpn is the R client for the USA National Phenology Network, retrieving observation records, phenometrics and gridded model layers. Version 1.3.0 in March 2025 replaced nearly all of its infrastructure at once — sp and raster dropped, terra made optional, XML swapped for xml2, plyr for dplyr, httr and curl for httr2 — and changed what functions return, with tibbles in place of data.tables and empty tibbles in place of NULL on error. The two releases since have completed the missing-value handling and restored performance lost in the transition.
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().
rnpn is the R client for the USA National Phenology Network, retrieving observation records, phenometrics and gridded model layers. Version 1.3.0 in March 2025 replaced nearly all of its infrastructure at once — sp and raster dropped, terra made optional, XML swapped for xml2, plyr for dplyr, httr and curl for httr2 — and changed what functions return, with tibbles in place of data.tables and empty tibbles in place of NULL on error. The two releases since have completed the missing-value handling and restored performance lost in the transition.
The package is being brought onto the current R stack and made honest about missing data, and those are the same project. Converting the -9999 sentinel to NA started in 1.3.0 for download functions and was extended to all columns in 1.4.1; the string "emptyvalue" got the same treatment. Beyond the migration, the feature additions are modest and specific to the domain, such as custom start and end dates for defining a phenometrics season.
With the dependency migration finished and sentinel handling now applied across all columns, the next releases most likely return to domain features and to fixes surfaced by the server side, which has already prompted work through migrations and backend moves. The removed progress indicator is an acknowledged regression that may come back.
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 rnpn.
A mature recurrent-event toolkit in careful maintenance, shedding weight rather than adding surface.
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
College football's open data client hit v2 — and now reports how many API calls you have left.
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
A spatial-statistics utility package exists to be depended on, and is built accordingly.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. forrel and rnpn 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 rnpn 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 rnpn alternatives in Analytics are ranked by recent ship velocity. Browse the "rnpn alternatives" section above for the current picks, or visit /alternatives/rnpn for the full list with editorial commentary on each.