tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of geodist and omock — release velocity, themes, recent moves, and the top alternatives to consider.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
A mock-data generator for OMOP studies that keeps widening what it can fake.
omock builds synthetic OMOP Common Data Model tables so packages in the darwin-eu and OHDSI ecosystem can be tested without touching patient data. The 0.7.0 release adds concept set subsetting with its own vignette, unit and value support in mockMeasurement, observation date validation and cohort attrition initialization, while deprecating mockConcepts. Releases arrive as PR digests rather than written notes.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
Development has been about making the speed-accuracy trade visible rather than hiding it. The 0.0.6 release added messages telling users to pick a different measure once the default cheap approximation is applied beyond 100km, where its error stops being negligible. Around that, the work is input handling — tibble support, better lon/lat column matching, vector inputs — and hardening the C code. It is a package that treats being small and correct as the feature.
Expect continued low-frequency maintenance: compiler warnings and geodesic source updates account for three of the last six releases, and the function surface has grown by only two entries in five years.
omock builds synthetic OMOP Common Data Model tables so packages in the darwin-eu and OHDSI ecosystem can be tested without touching patient data. The 0.7.0 release adds concept set subsetting with its own vignette, unit and value support in mockMeasurement, observation date validation and cohort attrition initialization, while deprecating mockConcepts. Releases arrive as PR digests rather than written notes.
The package has been moving from generating tables to shipping and managing reference datasets — mockDatasets arrived in 0.4.0, mockCdmFromDataset gained a source argument in 0.5.0, and 0.6.1 added download retry handling plus an internal GiBleed dataset after the hosted files moved. The recent work is filling in CDM fidelity: type concepts, measurement units, attrition, and guards for degenerate cases like an empty person table.
Expect coverage to keep extending table by table toward the parts of the CDM that omock still cannot mock, with mockConcepts removed outright once the concept set subsetting path settles.
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 geodist or omock.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
A single-purpose ggplot2 inset tool, refining the same three arguments.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools stopped guarding its own object model and started accepting everyone else's.
The glue package that makes R carry units and uncertainty through the same calculation.
See all geodist alternatives → · See all omock alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. geodist and omock 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. geodist and omock 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 geodist alternatives in Analytics are ranked by recent ship velocity. Browse the "geodist alternatives" section above for the current picks, or visit /alternatives/geodist-r for the full list with editorial commentary on each.
Top omock alternatives in Analytics are ranked by recent ship velocity. Browse the "omock alternatives" section above for the current picks, or visit /alternatives/omock-r for the full list with editorial commentary on each.