← Back to home
Comparison · Infra & APIs

robscale vs tealeaves

A side-by-side editorial comparison of robscale and tealeaves — release velocity, themes, recent moves, and the top alternatives to consider.

robscale vs tealeaves: at a glance

Featurerobscaletealeaves
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesrobust-statistics, simd, performance, cranplant-physiology, energy-balance, leaf-temperature, units
Last editorial update2h ago51m ago
WebsiteVisit →Visit →

What is robscale?

A robust-statistics package rewrote its estimators in SIMD C++ and went to CRAN in two weeks.

robscale computes robust scale and location estimators, and its pitch is speed: 21 to 26 times faster than stats::mad, 37 times faster than stats::IQR on small samples, with comparable margins over robustbase for Qn and Sn. The March 2026 releases took it from a GitHub project to a CRAN package carrying eleven estimators, all with confidence intervals.

Read the full robscale trajectory →

What is tealeaves?

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.

Read the full tealeaves trajectory →

robscale vs tealeaves: editorial side-by-side

R
robscale
INFRA · APIS
0.0

A robust-statistics package rewrote its estimators in SIMD C++ and went to CRAN in two weeks.

◆ Current state

robscale computes robust scale and location estimators, and its pitch is speed: 21 to 26 times faster than stats::mad, 37 times faster than stats::IQR on small samples, with comparable margins over robustbase for Qn and Sn. The March 2026 releases took it from a GitHub project to a CRAN package carrying eleven estimators, all with confidence intervals.

◆ Where it's heading

Three releases in a fortnight walk a clear line: expand the public API, submit to CRAN, then tune. The 0.5.4 work is where that tuning shows, and it is unusually specific about hardware, raising sorting-network thresholds after benchmarking and dropping the AVX-512 path entirely in favour of a shorter AVX2-first dispatch chain. The build-fix lists are long, which is what a package fighting compiler and TBB variation across CRAN's platforms looks like.

◆ Prediction

The dispatch hierarchy has been simplified once already; further releases most likely continue narrowing the SIMD surface and hardening the configure step rather than adding estimators. A new estimator would be the surprise.

T
tealeaves
INFRA · APIS
0.0

A leaf-temperature model that finished its job in 2020 and has stayed finished

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to robscale and tealeaves

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 robscale or tealeaves.

See all robscale alternatives → · See all tealeaves alternatives →

Recent activity from robscale and tealeaves

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4mo agorobscaleSIMD median networks land; AVX-512 dispatch is dropped
  2. 4mo agorobscaleCRAN submission ships 11 robust estimators with bootstrap intervals
  3. 5mo agorobscalescale_robust() dispatcher and four new estimators join the public API
  4. 4y agotealeavesCitation file, vignette and README fixes
  5. 6y agotealeavesParameter-crossing bug fixed with tests; coverage added
  6. 6y agotealeavesFix for custom sky temperature function being overwritten
  7. 6y agotealeavesSky temperature as value or function; dplyr 1.0.0 compatibility
  8. 7y agotealeavesUnitless parameter values now accepted and assigned units
  9. 7y agotealeavesFirst release: leaf energy balance with per-surface conductances

Frequently asked questions

What is the difference between robscale and tealeaves?

They serve adjacent needs but don't currently overlap on shipped themes. robscale 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.

Is robscale better than tealeaves?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. robscale 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.

What are the best alternatives to robscale?

Top robscale alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "robscale alternatives" section above for the current picks, or visit /alternatives/robscale for the full list with editorial commentary on each.

What are the best alternatives to tealeaves?

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.