Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Comparison · Analytics
omock vs tulpa
A side-by-side editorial comparison of omock and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
omock vs tulpa: at a glance
What is omock?
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.
What is tulpa?
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
omock vs tulpa: editorial side-by-side
omock
0.0ANALYTICS
A mock-data generator for OMOP studies that keeps widening what it can fake.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
tulpa
7.5ANALYTICS
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
◆ Current state
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
◆ Where it's heading
Two moves in nine days point at the same destination: the generics conversion made tulpa extensible by downstream packages, and CRAN admission makes it installable by them. The current cadence — several tags a week, some existing only to record a measurement that produced no code change — does not survive CRAN's submission overhead, so the release rhythm has to slow whether or not the project intends it. The correctness work still clusters on the joint nested-Laplace driver, and 0.1.0 extends the same diagnostics habit with .NL_AXIS_SD_REASONS, a closed vocabulary for an outer axis whose grid does not contain its own posterior mode.
◆ Prediction
Expect tulpaObs to follow tulpa onto CRAN, since it is the consumer whose registrations the engine has spent this window unblocking, and expect the version line to move in larger, less frequent steps now that each one carries a submission.
Alternatives to omock and tulpa
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 omock or tulpa.
Lightdash
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
Delta Lake
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio
RStudio ships through release branches, and the notes are commit messages
Recent activity from omock and tulpa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agotulpaFirst CRAN release: engine surface unchanged from 0.0.198 ⚡
- 5d agotulpatulpa_re_aghq() exposes the mode/theta cross-Hessian
- 8d agotulpaDense batched joint path could silently drop a grid cell
- 9d agotulpaCalibration and goodness-of-fit entry points become S3 generics ⚡
- 10d agotulpaCUDA backend had two definitions; link order decided if it ran
- 10d agotulpaHyperparameter bounds now flag when they leave the node range
- 2mo agoomockConcept set subsetting and richer measurement mocks
- 4mo agoomockDelphi dataset added and CDM version bumped
- 6mo agoomockDataset downloads survive the storage move
- 11mo agoomockJOSS submission tag alongside the 0.5.0 release
- 11mo agoomockmockCdmFromDataset gains a source argument
- 1y agoomockmockDatasets introduces bundled reference data
Frequently asked questions
What is the difference between omock and tulpa?
They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 omock better than tulpa?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 omock?
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.
What are the best alternatives to tulpa?
Top tulpa alternatives in Analytics are ranked by recent ship velocity. Browse the "tulpa alternatives" section above for the current picks, or visit /alternatives/tulpa for the full list with editorial commentary on each.