PurpleAir
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
Comparison · Analytics
ecotraj vs lstar
A side-by-side editorial comparison of ecotraj and lstar — release velocity, themes, recent moves, and the top alternatives to consider.
ecotraj vs lstar: at a glance
What is ecotraj?
Ecological trajectory analysis builds out its cyclical branch, largely through one contributor
ecotraj analyses ecological community trajectories through multivariate space, and since 1.0.0 has carried cyclical ecological trajectory analysis (CETA) alongside the linear methods. Recent releases add convergence plotting, cycle shift arrows, correspondence and reduced major axis functions, and now trajectory averaging — most credited to a single contributor, N. Djeghri. Several older release notes are bare pointers to NEWS rather than descriptions.
What is lstar?
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
lstar stores single-cell data behind one C++ core with Python, R and JS/WASM bindings, and ships a browser viewer that reads the store directly. Zarr v3 is now the default on-disk format across all four surfaces, with zstd compression and sharding that packs many chunks into fewer objects. Viewer stores are compressed per field and resolved at chunk granularity, so a hosted viewer fetches only what it displays. The tag stream carries both lstar and lstar-sc releases.
ecotraj vs lstar: editorial side-by-side
ecotraj
0.0ANALYTICS
Ecological trajectory analysis builds out its cyclical branch, largely through one contributor
◆ Current state
ecotraj analyses ecological community trajectories through multivariate space, and since 1.0.0 has carried cyclical ecological trajectory analysis (CETA) alongside the linear methods. Recent releases add convergence plotting, cycle shift arrows, correspondence and reduced major axis functions, and now trajectory averaging — most credited to a single contributor, N. Djeghri. Several older release notes are bare pointers to NEWS rather than descriptions.
◆ Where it's heading
The centre of gravity has shifted to cycles. The 1.0.0 release introduced CETA and reworked the underlying data structures for it, and every release since extends the cyclical branch or teaches an existing function to handle cycle objects — trajectoryDistances now compares cycles using dates for time comparison, and averageTrajectories covers both trajectories and cycles. A dependency on the MannKendall package was dropped in favour of base cor.test, trimming the install footprint.
◆ Prediction
The pattern of teaching existing linear-trajectory functions to accept cycle objects has repeated across several releases, so further functions gaining cycle support is the most grounded expectation.
lstar
5.0ANALYTICS
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
◆ Current state
lstar stores single-cell data behind one C++ core with Python, R and JS/WASM bindings, and ships a browser viewer that reads the store directly. Zarr v3 is now the default on-disk format across all four surfaces, with zstd compression and sharding that packs many chunks into fewer objects. Viewer stores are compressed per field and resolved at chunk granularity, so a hosted viewer fetches only what it displays. The tag stream carries both lstar and lstar-sc releases.
◆ Where it's heading
The through-line is making a hosted store cheap to read. Sharding addresses the file-per-chunk explosion that makes many-chunk arrays awkward to host; per-field compression with chunk-granular resolution means colouring an embedding by one gene fetches one column rather than an array. The 0.2.x patches are the cost of maintaining four surfaces at once — a WASM heap crash that only browsers exercise, and a count-basis orientation defect where all three surfaces normalized in memory and none owned the on-disk layout.
◆ Prediction
The orientation bug's root cause — no surface owning the on-disk representation while all three normalized in memory — is the kind of gap that usually produces a validation or ownership change rather than another point fix.
Alternatives to ecotraj and lstar
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 ecotraj or lstar.
piecepackr
A board game graphics package runs one of the most disciplined deprecation cycles in R.
e2tree
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
discretefdr
The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.
contentanalysis
A scientific-text analysis package moved from counting citations to classifying argument structure.
relialearnr
The teaching arm of an R reliability suite keeps pace with whatever its analysis siblings ship.
See all ecotraj alternatives → · See all lstar alternatives →
Recent activity from ecotraj and lstar
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21d agolstarViewer count-basis orientation fixed; existing stores need re-prep
- 26d agolstarWASM viewer crash on resizable heaps fixed
- 1mo agolstarlstar 0.2.0 ⚡
- 1mo agolstarMeasure state inferred from content, not slot name
- 2mo agoecotrajTrajectory averaging and cycle-aware distance comparison
- 9mo agoecotrajConvergence plots, RMA functions, and one fewer dependency
- 11mo agoecotrajTrajectory definition and convergence fixes
- 1y agoecotrajECOTRAJ ver. 1.1.0
- 1y agoecotrajECOTRAJ ver. 1.0.0 ⚡
- 2y agoecotrajECOTRAJ ver. 0.1.1
Frequently asked questions
What is the difference between ecotraj and lstar?
They serve adjacent needs but don't currently overlap on shipped themes. lstar is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 ecotraj better than lstar?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lstar is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to ecotraj?
Top ecotraj alternatives in Analytics are ranked by recent ship velocity. Browse the "ecotraj alternatives" section above for the current picks, or visit /alternatives/ecotraj for the full list with editorial commentary on each.
What are the best alternatives to lstar?
Top lstar alternatives in Analytics are ranked by recent ship velocity. Browse the "lstar alternatives" section above for the current picks, or visit /alternatives/lstar for the full list with editorial commentary on each.