simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of dynwrap and rtrek — release velocity, themes, recent moves, and the top alternatives to consider.
A dormant trajectory-inference wrapper wakes up for maintenance only
dynwrap is the dynverse component that wraps single-cell trajectory inference methods behind a common interface, handling containerised method execution and the trajectory data model. The visible history is dominated by a burst of feature work in 2019 and then near-silence: the only recent release, v1.3.0, is a package modernisation with a minimum-version bump and no user-facing capability. The three entries in the feed span seven years.
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
rtrek bundles Star Trek datasets — book series, timelines, episode transcripts, species and homeworlds, map tile sets — and layers live retrieval on top through memory_alpha() and memory_beta() plus their ma_* and mb_* helpers. Recent releases are almost entirely repairs to that retrieval layer as the source wikis change their page structure.
dynwrap is the dynverse component that wraps single-cell trajectory inference methods behind a common interface, handling containerised method execution and the trajectory data model. The visible history is dominated by a burst of feature work in 2019 and then near-silence: the only recent release, v1.3.0, is a package modernisation with a minimum-version bump and no user-facing capability. The three entries in the feed span seven years.
The direction is custodial rather than developmental. The 2019 releases built out the substance — RNA velocity in the wrapper, velocity-oriented topologies, directed geodesic distances, Singularity 3.0 and sparse matrices throughout — and nothing since has extended it. The 2026 release reads as keeping the package installable against a modern R toolchain, which is what a maintained dependency of a benchmark suite needs rather than what an actively developed tool looks like.
On this evidence, expect further releases to be compatibility maintenance triggered by R or dependency changes; the entries give no indication of resumed feature work.
rtrek bundles Star Trek datasets — book series, timelines, episode transcripts, species and homeworlds, map tile sets — and layers live retrieval on top through memory_alpha() and memory_beta() plus their ma_* and mb_* helpers. Recent releases are almost entirely repairs to that retrieval layer as the source wikis change their page structure.
The package's centre of gravity shifted once, at 0.2.0, from shipping static data to querying Memory Alpha and Memory Beta at runtime. Everything since has been the maintenance bill for that decision: HTML update fixes, parser improvements, portal retrieval bugs. Note that version numbers on this feed do not track time — 0.2.5 is stamped a year before 0.1.0, and three tags were backfilled within four minutes in November 2020 — so neither rank nor version ordering here indicates release sequence.
Expect the next release to fix retrieval against another Memory Alpha layout change, which is what the last four have done. The entries give no indication of new datasets or functions in progress.
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 dynwrap or rtrek.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
See all dynwrap alternatives → · See all rtrek alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dynwrap and rtrek 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. dynwrap and rtrek 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 Analytics products to evaluate alongside.
Top dynwrap alternatives in Analytics are ranked by recent ship velocity. Browse the "dynwrap alternatives" section above for the current picks, or visit /alternatives/dynwrap for the full list with editorial commentary on each.
Top rtrek alternatives in Analytics are ranked by recent ship velocity. Browse the "rtrek alternatives" section above for the current picks, or visit /alternatives/rtrek for the full list with editorial commentary on each.