trackeR
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
Comparison · Infra & APIs
GeoThinneR vs modsem
A side-by-side editorial comparison of GeoThinneR and modsem — release velocity, themes, recent moves, and the top alternatives to consider.
GeoThinneR vs modsem: at a glance
| Feature | GeoThinneR | modsem |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | spatial-thinning, species-distribution, occurrence-data, breaking-changes | structural-equation-modeling, latent-interactions, lms-estimator, mplus-interop |
| Last editorial update | 1h ago | 2h ago |
| Website | Visit → | Visit → |
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.
What is modsem?
modsem is grinding latent interaction models toward Mplus parity, one estimator at a time.
modsem fits interaction and quadratic effects between latent variables in R, offering both product-indicator approaches (modsem_pi) and distribution-analytic ones (modsem_da, covering LMS and QML). Releases land roughly monthly and are dense pull-request lists. The recent line is dominated by the LMS approach: gradient refactors, parallel E-steps, composite construct support, and careful handling of residual covariances between latent variables.
GeoThinneR vs modsem: editorial side-by-side
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.
modsem
0.0INFRA · APIS
modsem is grinding latent interaction models toward Mplus parity, one estimator at a time.
◆ Current state
modsem fits interaction and quadratic effects between latent variables in R, offering both product-indicator approaches (modsem_pi) and distribution-analytic ones (modsem_da, covering LMS and QML). Releases land roughly monthly and are dense pull-request lists. The recent line is dominated by the LMS approach: gradient refactors, parallel E-steps, composite construct support, and careful handling of residual covariances between latent variables.
◆ Where it's heading
Two things are being closed at once. The modelling gap — composites and formative constructs, categorical estimators, residual covariances in every direction, multigroup and clustered designs — brings modsem toward what commercial Mplus users expect, and the package's Mplus bridge is maintained alongside it, now with unique file IDs and a cleanup argument. The performance gap is the other: memoised H0, parallel E-step, optimized gradients and Hessians for both LMS and QML, all aimed at the distribution-analytic estimators that are expensive by construction. Convention borrowing from lavaan continues in message formatting and standard-error defaults.
◆ Prediction
The 1.0.20 and 1.0.21 releases both spent effort on residual covariances between endogenous and exogenous latent variables across estimation, prediction and standardization, and that thread has not obviously closed. The arrival of a second contributor moving MplusAutomation to Suggests suggests dependency trimming continues.
Alternatives to GeoThinneR and modsem
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 GeoThinneR or modsem.
states
State-panel tooling holding steady since its 2020 data and ergonomics release.
multimark
Five years of compiler and CRAN fixes on a capture-recapture package.
metagroup
A first release that turns meta-analytic heterogeneity into interpretable subgroups.
vcmeta
A meta-analysis toolkit still renaming its own API as it adds effect sizes.
JointFPM
Recurrent-event modelling settles, with mean_no() promoted to stable.
See all GeoThinneR alternatives → · See all modsem alternatives →
Recent activity from GeoThinneR and modsem
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agomodsemUnique Mplus file IDs, cleanup argument, LMS gradient refactor
- 2mo agomodsemComposite constructs for LMS, plus MC-LMS-CAT and MC-QML-CAT
- 3mo agomodsemPrint spacing and a partial-match fix in getSortedEtas()
- 4mo agomodsemCategorical argument for Mplus; partial support for the <~ operator
- 5mo agoGeoThinneRInteger overflow in local kd-tree grid assignment
- 5mo agomodsemConsistent three-way interaction estimates with rcs=TRUE
- 6mo agomodsemSecondary pruning and a forward-difference Hessian mode
- 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 GeoThinneR and modsem?
They serve adjacent needs but don't currently overlap on shipped themes. GeoThinneR and modsem 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 GeoThinneR better than modsem?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. GeoThinneR and modsem 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 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.
What are the best alternatives to modsem?
Top modsem alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "modsem alternatives" section above for the current picks, or visit /alternatives/modsem for the full list with editorial commentary on each.