soilDBdata
soilDBdata exists so soilDB's tests can run without a NASIS connection.
A side-by-side editorial comparison of minimaxapprox and nert — release velocity, themes, recent moves, and the top alternatives to consider.
minimaxapprox found its Remez exchange had been silently returning the wrong minimax.
minimaxapprox computes minimax polynomial and rational approximations to functions via the Remez exchange algorithm. Version 0.6.0 is a correctness release of unusual depth: the exchange was redesigned after two structural defects were found that let it converge to a reference-local fixed point that is not the global minimax, with no warning. The worked example in the notes has atan on [0,3] at degree 3 reporting an expected error 1.8 times smaller than the returned approximation's true maximum error.
nert put fourteen TERN datasets behind one dispatcher and called it stable.
nert is an R client for the TERN data API, reaching its first stable release in May 2026 after a year of milestone-tagged development. Version 1.0.0 exposes eleven functions covering fourteen datasets — SMIPS, ASC, AET, eight SLGA soil attributes, Soil Beta Diversity, Canopy Height and Land Surface Phenology — through a single read_tern(dataset_id, ...) dispatcher plus collect_tern_data() for batch extraction across locations and date ranges. Coverage sits at 83% overall with every reader at 100%.
minimaxapprox computes minimax polynomial and rational approximations to functions via the Remez exchange algorithm. Version 0.6.0 is a correctness release of unusual depth: the exchange was redesigned after two structural defects were found that let it converge to a reference-local fixed point that is not the global minimax, with no warning. The worked example in the notes has atan on [0,3] at degree 3 reporting an expected error 1.8 times smaller than the returned approximation's true maximum error.
The redesign changes what drives the algorithm: roots are now located across the whole interval from an oversampled grid rather than only between consecutive reference points, each sign region takes its search direction from the error's own sign instead of a mechanically alternated schedule, and endpoints are always retained as exchange candidates. Around that sit a cluster of fixes with the same signature — a stagnation check tested in only one direction, a missing abs() in a coefficient test, ztol applied on the monomial scale when Chebyshev was requested — each one a silent wrong answer rather than a crash. Conditioning on ranges far from [-1,1] was also addressed, at the cost of a breaking change.
Nearly every fix here came from auditing places where the package trusted its own structure instead of measuring the error curve, so the next release most likely continues that audit into the rational-approximation path rather than adding features.
nert is an R client for the TERN data API, reaching its first stable release in May 2026 after a year of milestone-tagged development. Version 1.0.0 exposes eleven functions covering fourteen datasets — SMIPS, ASC, AET, eight SLGA soil attributes, Soil Beta Diversity, Canopy Height and Land Surface Phenology — through a single read_tern(dataset_id, ...) dispatcher plus collect_tern_data() for batch extraction across locations and date ranges. Coverage sits at 83% overall with every reader at 100%.
The release history is unusual in that most of its tags are not releases: Milestone 1, 2 and 4 were pushed within eight minutes of each other in July 2025 purely as grant reporting and audit markers, with no user-facing content. What the 1.0.0 notes emphasise instead is test discipline — 310 deterministic offline tests, snapshot pins on every TERN bucket path and filename template, and mocked COG reads so R CMD check never touches the network. That is a client built on the assumption that the remote API's URL structure will change underneath it.
The notes describe pre-CRAN review polish and itemise remaining check NOTEs in cran-comments.md, so the next move is most likely a CRAN submission rather than additional dataset coverage.
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 minimaxapprox or nert.
soilDBdata exists so soilDB's tests can run without a NASIS connection.
collinear has broken its API twice to stop making the user pick thresholds.
scTypeEval judges single-cell annotations without needing a ground truth to judge them against.
medrobust made its partial-identification bounds usable by giving them confidence intervals.
probmed went from one probabilistic effect size to a family of them in sixteen days.
fluxnet keeps swapping its own plumbing — first a Python downloader, now a DuckDB backend.
See all minimaxapprox alternatives → · See all nert alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r package — within Analytics. minimaxapprox and nert 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. minimaxapprox and nert 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 minimaxapprox alternatives in Analytics are ranked by recent ship velocity. Browse the "minimaxapprox alternatives" section above for the current picks, or visit /alternatives/minimaxapprox for the full list with editorial commentary on each.
Top nert alternatives in Analytics are ranked by recent ship velocity. Browse the "nert alternatives" section above for the current picks, or visit /alternatives/nert for the full list with editorial commentary on each.