tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
gigs vs orbital
A side-by-side editorial comparison of gigs and orbital — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
gigs vs orbital: at a glance
What is gigs?
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.
What is orbital?
Turning fitted tidymodels into SQL, one model family at a time — and the boosting engines just landed.
orbital converts a fitted tidymodels workflow into a database expression so prediction runs where the data lives, no R session in the loop. Its value is entirely a function of coverage, and 0.5.0 was the largest coverage release yet: catboost and lightgbm boosted trees, rpart decision trees, earth-backed MARS, glmnet multinomial regression, and both randomForest and ranger random forests, all for numeric, class, and probability predictions. The 0.5.1 follow-up is corrective, fixing SQL that Snowflake and other engines rejected because it cast booleans directly to numeric.
gigs vs orbital: editorial side-by-side
gigs
0.0ANALYTICS
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
◆ Current state
gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.
◆ Where it's heading
The package has moved from vector-in, vector-out conversion helpers to a data.frame-oriented interface with a single classify_growth() entry point that computes whatever outcomes the supplied columns allow. That is a shift from library to tool — the user describes their data rather than picking the right function. The trailing releases suggest the code is settled and the remaining work is packaging and discoverability.
◆ Prediction
With the API rewrite absorbed and hosting moved to rOpenSci, the next substantive release should add growth standards or outcomes rather than reshape the interface again.
orbital
0.0ANALYTICS
Turning fitted tidymodels into SQL, one model family at a time — and the boosting engines just landed.
◆ Current state
orbital converts a fitted tidymodels workflow into a database expression so prediction runs where the data lives, no R session in the loop. Its value is entirely a function of coverage, and 0.5.0 was the largest coverage release yet: catboost and lightgbm boosted trees, rpart decision trees, earth-backed MARS, glmnet multinomial regression, and both randomForest and ranger random forests, all for numeric, class, and probability predictions. The 0.5.1 follow-up is corrective, fixing SQL that Snowflake and other engines rejected because it cast booleans directly to numeric.
◆ Where it's heading
The package has been working outward in rings: recipe preprocessing steps first, then model types, then post-processing via the tailor package in 0.4.0, with show_query() added so users can inspect what actually gets sent. Recent releases show the constraint shifting from R-side translation to SQL dialect compatibility — the bugs now are about what a specific database will accept, not whether a model can be expressed. estimate_orbital_size() in 0.5.1 acknowledges the other practical limit, since generated expressions can grow large enough to matter before you generate them.
◆ Prediction
With the major boosting and ensemble engines covered, expect the next releases to keep chasing dialect-specific SQL correctness across warehouses rather than adding model families.
Alternatives to gigs and orbital
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 gigs or orbital.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all gigs alternatives → · See all orbital alternatives →
Recent activity from gigs and orbital
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoorbitalSnowflake-compatible SQL for dummy and NA steps
- 5mo agoorbitalcatboost, lightgbm, ranger and four more model families translate to SQL ⚡
- 8mo agoorbitalCompatibility with new xgboost versions
- 8mo agoorbitalPost-processing adjustments from tailor become translatable
- 11mo agoorbitalPCA step translation bugs cleared
- 1y agogigsDocs and Zenodo archiving
- 1y agoorbitalClass and probability predictions arrive, with glm and xgboost
- 1y agogigsDocs-only release; nothing changed internally
- 1y agogigsConversion API rewritten around data frames and classify_growth() ⚡
- 2y agogigsDocumentation fixes for autotest compliance
- 2y agogigsINTERGROWTH-21st fetal standards and input validation
- 2y agogigsPatch release with documentation update
Frequently asked questions
What is the difference between gigs and orbital?
Both compete on the same themes — r-package — within Analytics. gigs and orbital 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.
Is gigs better than orbital?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gigs and orbital 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.
What are the best alternatives to gigs?
Top gigs alternatives in Analytics are ranked by recent ship velocity. Browse the "gigs alternatives" section above for the current picks, or visit /alternatives/gigs for the full list with editorial commentary on each.
What are the best alternatives to orbital?
Top orbital alternatives in Analytics are ranked by recent ship velocity. Browse the "orbital alternatives" section above for the current picks, or visit /alternatives/orbital for the full list with editorial commentary on each.