Zoho Creator
Three months on, Zoho is still selling the HDS certification rather than shipping past it.
Comparison · Infra & APIs
exametrika vs GeoThinneR
A side-by-side editorial comparison of exametrika and GeoThinneR — release velocity, themes, recent moves, and the top alternatives to consider.
exametrika vs GeoThinneR: at a glance
What is exametrika?
exametrika breaks its own numbers to fix them, and ships the fit statistic nominal data lacked.
exametrika is an R psychometrics package covering IRT, latent class and rank analysis, and biclustering. Version 2.0.0 is a deliberate break: an EM convergence defect inherited from the reference implementation stopped estimation after as little as one cycle while reporting convergence, so every EM-based model in the package now returns different estimates than it did before. The package no longer reproduces the numbers printed in Shojima (2022), and the maintainer says so directly rather than burying it. The deprecation removals promised since 1.15.0 ride along in the same release, and the package title changed to Test Data Engineering.
What is GeoThinneR?
Spatial thinning grows a result object, and the API breaks to make room for it
GeoThinneR removes spatially redundant occurrence records before species distribution modelling. Version 2.0.0 restructured it around a GeoThinned S3 class with print, summary, plot and trial-accessor methods, replacing the bare logical vectors earlier versions returned, and reorganised the methods into three named strategies — distance, grid and precision — with the search algorithm as a separate argument. The two releases since have added a priority system for choosing which of several tied points to drop.
exametrika vs GeoThinneR: editorial side-by-side
exametrika
3.8INFRA · APIS
exametrika breaks its own numbers to fix them, and ships the fit statistic nominal data lacked.
◆ Current state
exametrika is an R psychometrics package covering IRT, latent class and rank analysis, and biclustering. Version 2.0.0 is a deliberate break: an EM convergence defect inherited from the reference implementation stopped estimation after as little as one cycle while reporting convergence, so every EM-based model in the package now returns different estimates than it did before. The package no longer reproduces the numbers printed in Shojima (2022), and the maintainer says so directly rather than burying it. The deprecation removals promised since 1.15.0 ride along in the same release, and the package title changed to Test Data Engineering.
◆ Where it's heading
The consolidation arc that ran through 1.14.0 and 1.15.0 has closed, but not the way the audit trail suggested it would. Rather than pausing new modelling work through the cleanup, 2.0.0 pairs the breaking removals with real capability: M2() and add_M2() bring a limited-information fit statistic with a full margin-based index set, order-restricted estimation becomes the default for Ranklustering on the strength of a higher likelihood, and LCA() picks up nominal and rated data. The correctness fixes share one shape - defects that got worse as data got larger, where a 700-respondent dataset silently merged fields and a 40-item test returned no assignments at all. A two-tier test suite now keeps 3,507 tests in CI while CRAN sees a 17-second subset.
◆ Prediction
With the deprecation backlog cleared and the EM core rewritten, the next releases have room to build on M2() - most plausibly extending the margin-based indices to the models that do not yet report them. Whether the R Journal submission that shaped 1.13.1 and 1.14.0 has landed is not visible in these entries.
GeoThinneR
0.0INFRA · APIS
Spatial thinning grows a result object, and the API breaks to make room for it
◆ Current state
GeoThinneR removes spatially redundant occurrence records before species distribution modelling. Version 2.0.0 restructured it around a GeoThinned S3 class with print, summary, plot and trial-accessor methods, replacing the bare logical vectors earlier versions returned, and reorganised the methods into three named strategies — distance, grid and precision — with the search algorithm as a separate argument. The two releases since have added a priority system for choosing which of several tied points to drop.
◆ Where it's heading
The package is moving from a function that returns an answer to a tool that returns something you can interrogate. Multiple thinning trials are first-class — you can ask for the largest, fetch a specific one, summarise one — and the recent work is about making the choice among tied candidates controllable rather than random. Dependency discipline runs alongside: the R-tree method was dropped when its package was not on CRAN, and spatial coverage degrades to NA rather than failing when s2 is missing.
◆ Prediction
The priority mechanism now covers all three strategies and the last release was an overflow fix in the local kd-tree path at large sizes, so scale is where the pressure is. More work on the distance methods at large N is the likelier next step than another strategy.
Alternatives to exametrika and GeoThinneR
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 exametrika or GeoThinneR.
Retool
Retool now debugs the apps its agent builds, and versions them across instances.
nuggets
A pattern-mining package that keeps making its own search cheaper rather than wider.
Traefik
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
NGINX
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
ESPHome
ESPHome closes the 2026.8 cycle, but the release body is a bare link to the real notes.
See all exametrika alternatives → · See all GeoThinneR alternatives →
Recent activity from exametrika and GeoThinneR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoexametrikaEM convergence fix changes every estimate; deprecated names removed ⚡
- 1mo agoexametrikaFull-codebase audit fixes silent result corruption, unifies arguments
- 2mo agoexametrikaPlot methods finally forward the graphical parameters they documented
- 3mo agoexametrikaCRAN resubmission: slow tests skipped to fit the check budget
- 3mo agoexametrikaGraphical Lasso and Chatterjee's xi extend the package into network estimation ⚡
- 3mo agoexametrikaFrozen research baseline, never released to CRAN
- 5mo agoGeoThinneRInteger overflow in local kd-tree grid assignment
- 8mo agoGeoThinneRPriority-based tie-breaking across all thinning methods
- 1y agoGeoThinneRGeoThinned result objects and a reorganised method surface ⚡
- 1y agoGeoThinneRR-tree thinning removed with its off-CRAN dependency
Frequently asked questions
What is the difference between exametrika and GeoThinneR?
They serve adjacent needs but don't currently overlap on shipped themes. exametrika is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is exametrika better than GeoThinneR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. exametrika is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to exametrika?
Top exametrika alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "exametrika alternatives" section above for the current picks, or visit /alternatives/exametrika for the full list with editorial commentary on each.
What are the best alternatives to GeoThinneR?
Top GeoThinneR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GeoThinneR alternatives" section above for the current picks, or visit /alternatives/geothinner for the full list with editorial commentary on each.