incident.io
Nexus does the diagnosis; the agent is now reaching into the status page too.
A side-by-side editorial comparison of polyRAD and tealeaves — release velocity, themes, recent moves, and the top alternatives to consider.
Polyploid genotype calling went quiet for three years, then returned with a bug-fix tag.
polyRAD calls genotypes from RAD sequencing data in polyploid and diploid populations using Bayesian estimation. Its capability surface has been settled since 2.0 in late 2022, which added support for ploidy that varies among individuals. The March 2026 release is a CRAN bug-fix sync after a three-and-a-half-year gap, with the substance deferred to NEWS.
A leaf-temperature model that finished its job in 2020 and has stayed finished
tealeaves solves for leaf temperature from an energy balance, using explicit units to keep parameters consistent and modelling lower and upper leaf surfaces separately so sensible and latent heat loss are computed for each. The package reached its current form in 2020 across versions 1.0.2 to 1.0.5, which added direct or functional sky temperature, dplyr 1.0.0 compatibility, and fixes to a parameter-crossing bug that the new sky temperature function had introduced. The only release since, v1.0.6 in July 2022, corrects a name in the citation file, stops parallel evaluation in a vignette and fixes README links.
polyRAD calls genotypes from RAD sequencing data in polyploid and diploid populations using Bayesian estimation. Its capability surface has been settled since 2.0 in late 2022, which added support for ploidy that varies among individuals. The March 2026 release is a CRAN bug-fix sync after a three-and-a-half-year gap, with the substance deferred to NEWS.
The releases between 1.0 and 2.0 followed a consistent pattern: add export paths to other tools in the polyploid genetics stack, add simulation controls, fix what CRAN checks caught. That expansion stopped at 2.0, and 2.0.1 does not resume it. The package reads as complete and maintained rather than under development.
Continued low-frequency patch releases keeping the package on CRAN as R and its dependencies move. The release notes give no sign of a 2.1 feature line.
tealeaves solves for leaf temperature from an energy balance, using explicit units to keep parameters consistent and modelling lower and upper leaf surfaces separately so sensible and latent heat loss are computed for each. The package reached its current form in 2020 across versions 1.0.2 to 1.0.5, which added direct or functional sky temperature, dplyr 1.0.0 compatibility, and fixes to a parameter-crossing bug that the new sky temperature function had introduced. The only release since, v1.0.6 in July 2022, corrects a name in the citation file, stops parallel evaluation in a vignette and fixes README links.
This is finished scientific software. The arc runs from a 1.0.0 that already described the full model, through a usability decision in 1.0.1 to accept unitless values and assign units rather than demand them, to a 2020 cluster of compatibility and correctness work around publication. Nothing since has touched the model, and the 2022 release is pure paperwork. Its most instructive entry remains 1.0.5, where a new feature silently produced incorrect parameter crossing and the fix arrived with tests to pin the behaviour.
Expect nothing unless a dependency or CRAN check forces a release; on this record any such release will be documentation and packaging rather than a change to the energy balance.
Other Infra & APIs 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 polyRAD or tealeaves.
Nexus does the diagnosis; the agent is now reaching into the status page too.
Warp turned its quarter of software-factory essays into infrastructure you can buy.
Okta's developer blog is a Cross App Access campaign, now diluted by advocacy-team storytelling.
A credential platform assembled two or three pull requests at a time, never a headline
Search without knowing the field — SigNoz keeps lowering the cost of not knowing your schema
A NOAA Fisheries colour palette that ships when the branding guide changes
See all polyRAD alternatives → · See all tealeaves alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. polyRAD and tealeaves 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. polyRAD and tealeaves 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 Infra & APIs products to evaluate alongside.
Top polyRAD alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "polyRAD alternatives" section above for the current picks, or visit /alternatives/polyrad for the full list with editorial commentary on each.
Top tealeaves alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "tealeaves alternatives" section above for the current picks, or visit /alternatives/tealeaves for the full list with editorial commentary on each.