At Ivy, we’re on a mission to unify all ML frameworks 💥 + automate code conversions 🔄
pip install ivy-core 🚀, join our growing community 😊, and lets-unify.ai! 🦾
In this post, we introduce Ivy, a new ML framework that currently supports JAX, TensorFlow, PyTorch, MXNet, and Numpy. We’re very excited for you to try it out!
Next on our roadmap is to support automatic code conversions between any frameworks 🔄, and add instant multi-framework support for all open-source libraries with only a few lines of code changed! Read on to learn more 😊
The post is split into a number of sub-pages explaining different aspects of why we created Ivy, how to use it, what we’ve got planned on our roadmap, and how to contribute! Click on the sub-headings to check out these pages!
We use 🚧 to indicate that the feature being discussed is in development. We use ✅ to indicate that it is already implemented!
Background
(a) ML Explosion
A huge number of ML tools have exploded onto the scene!
(b) Why Unify?
Why should we try to unify them?
(c) Standardization
We’re collaborating with The Consortium for Python Data API Standards
Design
Ivy can fulfill two distinct purposes:
- enable automatic code conversions between frameworks 🚧
- serve as a new ML framework with multi-framework support ✅
The Ivy codebase can then be split into three categories, and can be further split into 8 distinct submodules, each of which fall into one of these three categories as follows:
(a) Building Blocks
back-end functional APIs ✅
Ivy functional API ✅
Framework Handler ✅
Ivy Compiler 🚧
(b) Ivy as a Transpiler
front-end functional APIs 🚧
(c) Ivy as a Framework
Ivy stateful API ✅
Ivy Container ✅
Ivy Array 🚧
Extensions
(a) Applied Libraries ✅
Ivy libraries in mechanics, vision, robotics, memory and other areas
(b) Builder [post coming soon!] ✅
ivy.Trainer, ivy.Dataset, ivy.Dataloader and other helpful classes and functions for creating training workflows in only a few lines of code
Roadmap
We strongly welcome and encourage contributions from the community as we take on this important journey towards ML framework unification. These posts will explain exactly how you can get involved 🙂
(a) Standardize [post coming soon!] 🚧
Align Ivy with the Consortium for Python Data API Standards
(b) Front-Ends [post coming soon!] 🚧
Create framework-specific front-ends for each supported ML framework
(c) Code Conversions [post coming soon!] 🚧
Verify code conversions work for each back-end and front-end combo
(d) Ecosystem [post coming soon!] 🚧
Add multi-framework support to popular repos with a few lines changed
Contributing
Join our community as a code contributor, and help accelerate our journey to unify all ML frameworks! Find out more in our Contributing guide!
Article originally posted here. Reposted with permission.
