nflreadr
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
Comparison · Analytics
lstar vs mmconvert
A side-by-side editorial comparison of lstar and mmconvert — release velocity, themes, recent moves, and the top alternatives to consider.
lstar vs mmconvert: 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 mmconvert?
A single-purpose mouse map interpolator that solved its problem in 2023 and has coasted since
mmconvert does one thing: interpolate between GRCm39 physical positions and the revised Cox genetic map for mouse MUGA array markers. The substantive work all landed in a burst across 2021-2023 — the initial function, the GRCm39 annotation dataset, cross2_to_grcm39(), the recomputed Cox maps and their smoothed replacement. Everything since is upkeep: a warning-message fix in 0.12, and 0.14 is a test adjustment to silence a CRAN Note with no code change at all.
lstar vs mmconvert: 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.
mmconvert
0.0ANALYTICS
A single-purpose mouse map interpolator that solved its problem in 2023 and has coasted since
◆ Current state
mmconvert does one thing: interpolate between GRCm39 physical positions and the revised Cox genetic map for mouse MUGA array markers. The substantive work all landed in a burst across 2021-2023 — the initial function, the GRCm39 annotation dataset, cross2_to_grcm39(), the recomputed Cox maps and their smoothed replacement. Everything since is upkeep: a warning-message fix in 0.12, and 0.14 is a test adjustment to silence a CRAN Note with no code change at all.
◆ Where it's heading
The package has reached the natural end state of a reference-data converter — the reference data stopped moving, so the package stopped moving. Releases now arrive roughly annually and exist to keep CRAN checks green. The 0.14 release shipped the same day as sibling qtl2convert 0.36, confirming these are batch maintenance passes across the maintainer's packages rather than independent development.
◆ Prediction
Without a new mouse genome build or a revised Cox map, the next release is likely another CRAN-check accommodation rather than new functionality.
Alternatives to lstar and mmconvert
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 mmconvert.
susier
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
UCell
A rank-based gene signature scorer that has grown by adapting to whatever object format single-cell R uses next
detectseparation
A diagnostic package that generalized past its own name, then learned to say which kind of separation it found
brglm2
A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression
bayestools
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
See all lstar alternatives → · See all mmconvert alternatives →
Recent activity from lstar and mmconvert
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 agommconvertTest adjustment to clear a CRAN Note
- 1mo agolstarlstar 0.2.0 ⚡
- 1mo agolstarMeasure state inferred from content, not slot name
- 1y agommconvertFixes a malformed warning message in mmconvert()
- 3y agommconvertOmits X chromosome positions for sex-averaged and male maps
- 3y agommconvertCRAN release adds chromosome lengths and smoothed Cox maps
- 3y agommconvertRecomputed Cox genetic maps and combined-array support
- 4y agommconvertRepoints data sources from master to main branches
Frequently asked questions
What is the difference between lstar and mmconvert?
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 mmconvert?
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 mmconvert?
Top mmconvert alternatives in Analytics are ranked by recent ship velocity. Browse the "mmconvert alternatives" section above for the current picks, or visit /alternatives/mmconvert for the full list with editorial commentary on each.