incident.io
Nexus does the diagnosis; the agent is now reaching into the status page too.
A side-by-side editorial comparison of ggInterval and tealeaves — release velocity, themes, recent moves, and the top alternatives to consider.
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
ggInterval visualizes symbolic interval-valued data — observations recorded as ranges rather than points — with a family of plot functions in the ggplot2 idiom. The plot catalogue grew most recently with interval correlation heatmaps and interval line plots compatible with time-series input. The three releases before that were corrections: seven plot functions renamed for consistency, examples switched from dontrun to donttest at CRAN's request, and a vignette rewritten to demonstrate every function in one place.
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.
ggInterval visualizes symbolic interval-valued data — observations recorded as ranges rather than points — with a family of plot functions in the ggplot2 idiom. The plot catalogue grew most recently with interval correlation heatmaps and interval line plots compatible with time-series input. The three releases before that were corrections: seven plot functions renamed for consistency, examples switched from dontrun to donttest at CRAN's request, and a vignette rewritten to demonstrate every function in one place.
The package is consolidating an interface that had drifted. Renaming seven functions in a single release is the clearest signal — the naming was inconsistent enough to be worth breaking, and the vignette rewrite that followed suggests discoverability was the underlying complaint. Underneath that, the additions are steady and narrow: each release brings interval-aware versions of plot types that already exist for point data, which is the whole premise of the package.
The pattern of porting one more standard plot type into interval-aware form each release is the most likely continuation; the tsplot compatibility in the latest version hints that time-series interval data is the direction attracting attention.
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 ggInterval 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 ggInterval 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. ggInterval 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. ggInterval 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 ggInterval alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ggInterval alternatives" section above for the current picks, or visit /alternatives/gginterval 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.