mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of baseq and emuR — release velocity, themes, recent moves, and the top alternatives to consider.
A basic DNA and RNA sequence toolkit that went quiet for three years, then jumped to 2.0.
baseq provides elementary sequence processing for biological data in R: cleaning DNA and RNA strings, counting bases and patterns, GC content, translation and reverse complement, and readers and writers for FASTA and FASTQ. The 0.1.x releases all landed in a two-week window in 2023, several of them backfilled within seconds of each other and in an order that does not match their version numbers. A 2.0 tag then appeared in March 2026 after three years of silence, with release notes naming only a development pull request and a CI workflow.
The R half of the EMU speech database system, fixing what was quietly broken.
emuR is the R interface to the EMU Speech Database Management System — loading annotated speech corpora, running hierarchical queries over annotation levels, extracting signal track data, and serving corpora to the EMU-webApp for browser-based annotation. It is at 2.6.0 on a slow cadence of roughly one release a year. Recent work has centred on the CRUD operations for annotation items and on widening what serve() can hand the web application.
baseq provides elementary sequence processing for biological data in R: cleaning DNA and RNA strings, counting bases and patterns, GC content, translation and reverse complement, and readers and writers for FASTA and FASTQ. The 0.1.x releases all landed in a two-week window in 2023, several of them backfilled within seconds of each other and in an order that does not match their version numbers. A 2.0 tag then appeared in March 2026 after three years of silence, with release notes naming only a development pull request and a CI workflow.
The visible history is a package assembled quickly and then left alone. Across the 0.1.x tags the notes are a printed inventory of exported functions rather than a changelog, with consecutive versions restating the same list unchanged, so the actual increments have to be inferred by diffing those inventories: file-level cleaning and GC content arrived at 0.1.3, and the FASTA and FASTQ readers, writers and converters at 0.1.1. What the 2.0 release contains is not stated anywhere in the feed, which makes the most significant-looking tag here also the least legible.
Nothing in these entries supports a confident prediction. The reappearance of activity after three years and the addition of a CI workflow suggest maintenance has resumed, but until a release describes its own contents there is no basis for saying in what direction.
emuR is the R interface to the EMU Speech Database Management System — loading annotated speech corpora, running hierarchical queries over annotation levels, extracting signal track data, and serving corpora to the EMU-webApp for browser-based annotation. It is at 2.6.0 on a slow cadence of roughly one release a year. Recent work has centred on the CRUD operations for annotation items and on widening what serve() can hand the web application.
The releases read as a package being brought up to the standard its own API implied. delete_itemsInLevel() shipped in 2.1.1 as a first version, was described in 2.5.0 as heavily flawed and now usable, and the create/update/delete family is still called ongoing work. Alongside that, the query engine was rewritten onto CTEs and the signal-processing layer is being opened past the bundled wrassp, starting with Matlab. Speed work recurs — SQLite transactions, prepared statements, on-the-fly caching — consistent with corpora outgrowing the original design.
Two threads are explicitly unfinished: the CRUD documentation and behaviour, described as ongoing, and the add_signalVia family, described as a draft starting with Matlab. Expect the next release to advance one of them rather than open new ground.
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 baseq or emuR.
mice can finally predict, not just estimate, from multiply imputed data.
A market-microstructure toolkit that keeps adding estimators as the papers land.
A vowel-analysis package trimming dependencies after an email address got it archived.
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots keeps rebuilding its own foundations rather than layering around them.
A GENCODE annotation toolkit spent its first year getting out of CRAN's way.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. baseq and emuR 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. baseq and emuR 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.
Top baseq alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "baseq alternatives" section above for the current picks, or visit /alternatives/baseq for the full list with editorial commentary on each.
Top emuR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "emuR alternatives" section above for the current picks, or visit /alternatives/emur for the full list with editorial commentary on each.