Skip to content

Article on neural nets on orbital for python - #382

Merged
amol- merged 2 commits into
mainfrom
pyorbital-pytorch
Aug 18, 2026
Merged

Article on neural nets on orbital for python#382
amol- merged 2 commits into
mainfrom
pyorbital-pytorch

Conversation

@amol-

@amol- amol- commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Article on the newly released Orbital for Python 0.6.0 with support for PyTorch neural networks.

@netlify

netlify Bot commented Aug 17, 2026

Copy link
Copy Markdown

Deploy Preview for posit-open-source canceled.

Name Link
🔨 Latest commit 1706f81
🔍 Latest deploy log https://app.netlify.com/projects/posit-open-source/deploys/6a845667fd50d00008424f79


Orbital's whole pitch is that a trained model becomes SQL, so a database can run predictions on its own, with no Python process anywhere near it. Until 0.6.0, "trained model" meant scikit-learn: pipelines, trees, linear models, all `.fit()` in Python and then turned into a `SELECT` statement. It never covered what a lot of teams are actually training now: PyTorch models, not scikit-learn pipelines.

Orbital 0.6.0 closes that gap. A `torch.nn.Sequential` network, trained exactly the way you already train it, now compiles to the same kind of SQL a linear regression would.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very good tying this back to linear regression!

Comment thread content/blog/pyorbital-0-6-0/index.qmd Outdated
Comment on lines +55 to +57
Scikit-learn and PyTorch are both real and shipping today, which is enough on its own to call this "multiple frameworks." But the dependency story is already moving that direction: [issue #113](https://github.com/posit-dev/orbital/issues/113) proposes turning scikit-learn itself into an optional dependency, the same way PyTorch already is, so the core stops assuming any particular framework at all.

There are more frameworks already in the works. I won't name them here, only that the architecture was built for exactly this.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this section is getting a little long, instead i think we would get a lot more bang for our buck if we move this to the end of the post as a "hope you like what you see, look forward to more expansions in the future"

Comment thread content/blog/pyorbital-0-6-0/index.qmd Outdated

The fix, `Optimizer.preserve_referenced_outputs()`, runs after every single node in the translation loop, for every translator, not just `MatMul` and `Add`, and checks how many times that node's output is actually referenced downstream. Referenced more than once, it gets materialized as a named column. Referenced once or not at all, it stays inlined, no extra column, no extra noise.

None of this is new machinery either. Tree ensembles already lean on the same trick: `preserve()` materializes per-tree votes, or the whole ensemble's aggregated vote so it isn't re-emitted everywhere it's read, as real SQL columns. `preserve_referenced_outputs()` just applies that same idea automatically, after every step, instead of leaving it to each translator to do it by itself.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same idea is used in a pipeline, instead of inlining everything we create the intermediary values

@amol-

amol- commented Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

@EmilHvitfeldt applied your feedback, let me know if it looks good to you

@github-actions

Copy link
Copy Markdown
Contributor

Blog YAML Checks

content/blog/pyorbital-0-6-0/index.md

  • ⚠️ Can't find people page for Alessandro Molina (expected content/people/alessandro-molina/).
  • ⚠️ date is in the past (2026-08-17). Post will publish immediately on merge.

Summary: 1 files checked, 2 warnings

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@amol-
amol- merged commit f5a5f7b into main Aug 18, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants