quanteda
Text analysis in R keeps optimising its token internals — and builds a path out to torch
Comparison · Analytics
lstar vs scTypeEval
A side-by-side editorial comparison of lstar and scTypeEval — release velocity, themes, recent moves, and the top alternatives to consider.
lstar vs scTypeEval: at a glance
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.
What is scTypeEval?
scTypeEval judges single-cell annotations without needing a ground truth to judge them against.
scTypeEval evaluates the consistency of single-cell cell type annotations without a ground-truth reference, using pseudobulk distances, Wasserstein distances and reciprocal classification as alternative dissimilarity strategies. It cleared Bioconductor's submission process on its first cycle, moving from a 0.99.30 pre-release in April 2026 to version 1.0.0 in the Bioconductor 3.23 release a month later. It accepts matrix, Seurat and SingleCellExperiment inputs.
lstar vs scTypeEval: editorial side-by-side
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.
scTypeEval
0.0ANALYTICS
scTypeEval judges single-cell annotations without needing a ground truth to judge them against.
◆ Current state
scTypeEval evaluates the consistency of single-cell cell type annotations without a ground-truth reference, using pseudobulk distances, Wasserstein distances and reciprocal classification as alternative dissimilarity strategies. It cleared Bioconductor's submission process on its first cycle, moving from a 0.99.30 pre-release in April 2026 to version 1.0.0 in the Bioconductor 3.23 release a month later. It accepts matrix, Seurat and SingleCellExperiment inputs.
◆ Where it's heading
The visible history is short and shaped entirely by the Bioconductor pipeline — the 0.99.x series is that project's submission convention, and 1.0.0 is what acceptance looks like rather than a maturity claim by the authors. What the pre-release notes emphasise is breadth of input format and of dissimilarity strategy rather than a single recommended method, which suggests the package is positioned as a comparison harness rather than a scoring tool. Nothing in these two entries indicates work beyond getting accepted.
◆ Prediction
With only a submission cycle in the record, there is not enough here to predict a direction; the next release will most likely be whatever the Bioconductor 3.24 cycle requires, and the first post-acceptance release is what will show whether development continues.
Alternatives to lstar and scTypeEval
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 lstar or scTypeEval.
moderndive
The ModernDive teaching package learns to render inside the browser that runs its own textbook
glmbayes
A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain
hydroloom
USGS puts a type system over its river network toolkit so errors surface at dispatch
chromConverter
The chromatography file-format translator keeps absorbing vendor formats one release at a time
slope
A year after gutting itself for a C++ rewrite, SLOPE is back to polishing the interface
See all lstar alternatives → · See all scTypeEval alternatives →
Recent activity from lstar and scTypeEval
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
- 3mo agoscTypeEvalAccepted into the Bioconductor 3.23 release
- 4mo agoscTypeEvalBioconductor pre-release: ground-truth-agnostic annotation evaluation
Frequently asked questions
What is the difference between lstar and scTypeEval?
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 lstar better than scTypeEval?
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 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.
What are the best alternatives to scTypeEval?
Top scTypeEval alternatives in Analytics are ranked by recent ship velocity. Browse the "scTypeEval alternatives" section above for the current picks, or visit /alternatives/sctypeeval for the full list with editorial commentary on each.