Giter Club home page Giter Club logo

ivy's Introduction


Website
Website
Docs
Docs
Demos
Demos
Design
Design
FAQ
FAQ


Convert Machine Learning Code Between Frameworks

Ivy enables you to:

  • Convert ML models, tools and libraries between frameworks while maintaining complete functionality using ivy.transpile
  • Create optimized graph-based models and functions in any native framework (PyTorch, TensorFlow, etc..) with ivy.trace_graph

Installing ivy

The easiest way to set up Ivy is to install it using pip:

pip install ivy
Docker Image

You can pull the Docker image for Ivy from:

docker pull ivyllc/ivy:latest
From Source

You can also install Ivy from source if you want to take advantage of the latest changes, but we can't ensure everything will work as expected ๐Ÿ˜…

git clone https://github.com/ivy-llc/ivy.git
cd ivy
pip install --user -e .

If you want to set up testing and various frameworks it's probably best to check out the Setting Up page, where OS-specific and IDE-specific instructions and video tutorials to do so are available!


Supported Frameworks

These are the frameworks that ivy.transpile currently supports conversions from and to. We're working hard on adding support for more frameworks, let us know on Discord if there are source/target frameworks that would be useful for you!

Framework Source Target
PyTorch โœ… ๐Ÿšง
TensorFlow ๐Ÿšง โœ…
JAX ๐Ÿšง ๐Ÿšง
NumPy ๐Ÿšง ๐Ÿšง

Getting started

Ivy's transpiler allows you convert code between different ML frameworks. Have a look at our Quickstart notebook to get a brief idea of the features!

Beyond that, based on the frameworks you want to convert code between, there are a few more examples further down this page ๐Ÿ‘‡ which contain a number of models and libraries transpiled between PyTorch, JAX, TensorFlow and NumPy.


Using ivy

Here's some examples, to help you get started using Ivy! The examples page also features a wide range of demos and tutorials showcasing some more use cases for Ivy.

Transpiling any code from one framework to another
import ivy
import torch
import tensorflow as tf

def torch_fn(x):
    a = torch.mul(x, x)
    b = torch.mean(x)
    return x * a + b

tf_fn = ivy.transpile(torch_fn, source="torch", target="tensorflow")

tf_x = tf.convert_to_tensor([1., 2., 3.])
ret = tf_fn(tf_x)
Tracing a computational graph of any code
import ivy
import torch

def torch_fn(x):
    a = torch.mul(x, x)
    b = torch.mean(x)
    return x * a + b

torch_x = torch.tensor([1., 2., 3.])
graph = ivy.trace_graph(jax_fn, to="torch", args=(torch_x,))
ret = graph(torch_x)

How ivy works?

Let's take a look at how Ivy works as a transpiler in more detail to get an idea of why and where to use it.

When is Ivy's transpiler useful?

If you want to use building blocks published in other frameworks (neural networks, layers, array computing libraries, training pipelines...), you want to integrate code developed in various frameworks, or maybe straight up migrate code from one framework to another or even between versions of the same framework, the transpiler is definitely the tool for the job! You can use the converted code just as if it was code originally developed in that framework, applying framework-specific optimizations or tools, instantly exposing your project to all of the unique perks of a different framework.


Ivy's transpiler allows you to use code from any other framework (or from any other version of the same framework!) in your own code, by just adding one line of code.

This way, Ivy makes all ML-related projects available for you, independently of the framework you want to use to research, develop, or deploy systems. Feel free to head over to the docs for the full API reference, but the functions you'd most likely want to use are:

# Converts framework-specific code to a target framework of choice. See usage in the documentation
ivy.transpile()

# Traces an efficient fully-functional graph from a function, removing all wrapping and redundant code. See usage in the documentation
ivy.trace_graph()

ivy.transpile will eagerly transpile if a class or function is provided

import ivy
import torch
import tensorflow as tf

def torch_fn(x):
    x = torch.abs(x)
    return torch.sum(x)

x1 = torch.tensor([1., 2.])
x1 = tf.convert_to_tensor([1., 2.])

# Transpilation happens eagerly
tf_fn = ivy.transpile(test_fn, source="torch", target="tensorflow")

# tf_fn is now tensorflow code and runs efficiently
ret = tf_fn(x1)

ivy.transpile will lazily transpile if a module (library) is provided

import kornia

x2 = torch.rand(5, 3, 4, 4)

# Module is provided -> transpilation happens lazily
tf_kornia = ivy.transpile(kornia, source="torch", target="tensorflow")

# The transpilation is initialized here, and this function is converted to tensorflwo
ret = tf_kornia.color.rgb_to_grayscale(x2)

# Transpilation has already occurred, the tensorflow function runs efficiently
ret = tf_kornia.color.rgb_to_grayscale(x2)

ivy.trace_graph can be used eagerly or lazily

If you pass the necessary arguments for function tracing, the graph tracing step will happen instantly (eagerly). Otherwise, the graph tracing will happen only when the returned function is first invoked.

import ivy
import jax
ivy.set_backend("jax")

# Simple JAX function to transpile
def test_fn(x):
    return jax.numpy.sum(x)

x1 = ivy.array([1., 2.])
# Arguments are available -> tracing happens eagerly
eager_graph = ivy.trace_graph(test_fn, to="jax", args=(x1,))

# eager_graph now runs efficiently
ret = eager_graph(x1)
# Arguments are not available -> tracing happens lazily
lazy_graph = ivy.trace_graph(test_fn, to="jax")

# The traced graph is initialized, tracing will happen here
ret = lazy_graph(x1)

# Tracing has already happend, traced graph runs efficiently
ret = lazy_graph(x1)

If you want to learn more, you can find more information in the Ivy as a transpiler section of the docs!


Documentation

You can find Ivy's documentation on the Docs page, which includes:

  • Motivation: This contextualizes the problem Ivy is trying to solve by going over
  • Related Work: Which paints a picture of the role Ivy plays in the ML stack, comparing it to other existing solutions in terms of functionalities and abstraction level.
  • Design: A user-focused guide about the design decision behind the architecture and the main building blocks of Ivy.
  • Deep Dive: Which delves deeper into the implementation details of Ivy and is oriented towards potential contributors to the code base.

Contributing

We believe that everyone can contribute and make a difference. Whether it's writing code, fixing bugs, or simply sharing feedback, your contributions are definitely welcome and appreciated ๐Ÿ™Œ

Check out all of our Open Tasks, and find out more info in our Contributing guide in the docs! Or to immediately dive into a useful task, look for any failing tests on our Test Dashboard!


Community



Join our growing community on a mission to make conversions between frameworks simple and accessible to all! Whether you are a seasoned developer or just starting out, you'll find a place here! Join the Ivy community on our Discord ๐Ÿ‘พ server, which is the perfect place to ask questions, share ideas, and get help from both fellow developers and the Ivy Team directly.

See you there!


Citation

If you use Ivy for your work, please don't forget to give proper credit by including the accompanying paper ๐Ÿ“„ in your references. It's a small way to show appreciation and help to continue to support this and other open source projects ๐Ÿ™Œ

@article{lenton2021ivy,
  title={Ivy: Templated deep learning for inter-framework portability},
  author={Lenton, Daniel and Pardo, Fabio and Falck, Fabian and James, Stephen and Clark, Ronald},
  journal={arXiv preprint arXiv:2102.02886},
  year={2021}
}

ivy's People

Contributors

1doomdie1 avatar aarsh2001 avatar ahmedo42 avatar annatz avatar catb1t avatar daniel4078 avatar djl11 avatar fnhirwa avatar fspyridakos avatar hello-fri-end avatar hmahmood24 avatar ishticode avatar ivy-branch avatar jerrygcding avatar jiahanxie353 avatar juliagsy avatar kareemmax avatar mahmoudashraf97 avatar mattbarrett98 avatar nripeshn avatar rashulchutani avatar ricksanchezstoic avatar saeedashrraf avatar sai-suraj-27 avatar sam-armstrong avatar sherry30 avatar simonetgordon avatar vaatsalya123 avatar vedpatwardhan avatar zaeemansari70 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ivy's Issues

Add Pooling functions to PyTorch Frontend

Add Pooling functions to PyTorch frontend:

_

Please keep in mind that the proper way to link an issue to this list is to comment "- [ ] #issue_number" while the issue's title only includes the name of the function you've chosen.

_

The main file paths where these functions are likely to be added are:

  • ivy/functional/frontends/torch/nn/functional/pooling\_functions.py
  • ivy\_tests/test\_ivy/test\_frontends/test\_torch/test\_pooling\_functions.py

Add Loss functions to PyTorch Frontend

Add Loss functions to PyTorch frontend:

_

Please keep in mind that the proper way to link an issue to this list is to comment "- [ ] #issue_number" while the issue's title only includes the name of the function you've chosen.

_

The main file paths where these functions are likely to be added are:

  • ivy/functional/frontends/torch/loss\_functions.py
  • ivy\_tests/test\_ivy/test\_frontends/test\_torch/test\_loss\_functions.py
  • ivy/functional/frontends/torch/nn/functional/loss\_functions.py

ivy.torch.use not exist

I have worked around ivy for some time and found the idea of integrating multiple frameworks very intersting and useful. I have noticed the following error on my machine. The following code does not work properly:

import ivy
import torch
import numpy as np

with ivy.numpy.use:
    x = np.array([0.])
    y = ivy.cos(x) 

with ivy.torch.use:
    x = torch.tensor([0.])
    y = ivy.cos(x) 

The above code emits the error: module 'ivy' has no attribute 'numpy'. This error is only resolved when I set the framework to numpy. Moreover, it seems that if I set the framework to torch, there is still no variable named use in ivy.torch. I have looked at the implementation and found this problem a bit weird, since the use variable seems to be declared in each module.

Thank you for viewing this request.

Add Layer Functions to Ivy Frontend

Add Layer Functions to Ivy frontend:

Linear

  • linear

Dropout

  • dropout

Attention

  • scaled_dot_product_attention
  • multi_head_attention

Convolutions

  • conv1d
  • conv1d_transpose
  • conv2d
  • conv2d_transpose
  • depthwise_conv2d
  • conv3d
  • conv3d_transpose

LSTM

  • lstm_update

Add Pointwise ops to PyTorch Frontend

Add Pointwise ops to PyTorch frontend:

_

Please keep in mind that the proper way to link an issue to this list is to comment "- [ ] #issue_number" while the issue's title only includes the name of the function you've chosen.

_

The main file paths where these functions are likely to be added are:

  • ivy/functional/frontends/torch/pointwise\_ops.py
  • ivy\_tests/test\_ivy/test\_frontends/test\_torch/test\_pointwise\_ops.py
  • ivy/functional/frontends/torch/\_\_init\_\_.py
  • ivy/functional/frontends/torch/non\_linear\_activation\_functions.py
  • ivy\_tests/test\_ivy/test\_frontends/test\_torch/test\_non\_linear\_activation\_functions.py
  • ivy\_tests/test\_ivy/test\_stateful/test\_activations.py

Add Multi-Device Functions + Classes to Ivy Frontend

Add Multi-Device Functions + Classes to Ivy frontend:

Multi-Device

  • MultiDev
  • MultiDevItem
  • MultiDevIter
  • MultiDevNest

Device Distribution

  • DevDistItem
  • DevDistIter
  • DevDistNest
  • dev_dist_array
  • dev_dist
  • dev_dist_iter
  • dev_dist_nest

Device Cloning

  • DevClonedItem
  • DevClonedIter
  • DevClonedNest
  • dev_clone_array
  • dev_clone
  • dev_clone_iter
  • dev_clone_nest

Device Unification

  • dev_unify_array
  • dev_unify
  • dev_unify_iter
  • dev_unify_nest

Device Mappers

  • DevMapper
  • DevMapperMultiProc

Device Manager

  • DevManager

Profiler

  • Profiler

Add General Functions to Ivy Frontend

Add General Functions to Ivy frontend:

  • get_referrers_recursive
  • array
  • is_array
  • copy_array
  • array_equal
  • arrays_equal
  • equal
  • to_numpy
  • to_scalar
  • to_list
  • shape
  • get_num_dims
  • minimum
  • maximum
  • clip
  • clip_vector_norm
  • clip_matrix_norm
  • round
  • floormod
  • floor
  • ceil
  • abs
  • argmax
  • argmin
  • argsort
  • cast
  • arange
  • linspace
  • logspace
  • concatenate
  • flip
  • stack
  • unstack
  • split
  • repeat
  • tile
  • constant_pad
  • zero_pad
  • fourier_encode
  • swapaxes
  • transpose
  • expand_dims
  • where
  • indices_where
  • isnan
  • value_is_nan
  • has_nans
  • reshape
  • broadcast_to
  • squeeze
  • zeros
  • zeros_like
  • ones
  • ones_like
  • one_hot
  • cross
  • matmul
  • cumsum
  • cumprod
  • identity
  • meshgrid
  • scatter_flat
  • scatter_nd
  • gather
  • gather_nd
  • linear_resample
  • exists
  • default
  • try_else_none
  • arg_names
  • match_kwargs
  • dtype
  • dtype_to_str
  • dtype_str
  • cache_fn
  • current_framework_str
  • einops_rearrange
  • einops_reduce
  • einops_repeat
  • get_min_denominator
  • set_min_denominator
  • stable_divide
  • get_min_base
  • set_min_base
  • stable_pow
  • multiprocessing
  • set_queue_timeout
  • queue_timeout
  • tmp_dir
  • set_tmp_dir
  • get_all_arrays_in_memory
  • num_arrays_in_memory
  • print_all_arrays_in_memory
  • container_types

Add Miscellaneous Operations to PyTorch Frontend

Add miscellaneous operations to PyTorch frontend:

_

Please keep in mind that the proper way to link an issue to this list is to comment "- [ ] #issue_number" while the issue's title only includes the name of the function you've chosen.

_

The main file paths where these functions are likely to be added are:

  • ivy/functional/frontends/torch/miscellaneous\_ops.py
  • ivy\_tests/test\_ivy/test\_frontends/test\_torch/test\_miscellaneous\_ops.py

Add Indexing, Slicing, Joining, Mutating Ops to PyTorch Frontend

Add indexing, slicing, joining, mutating ops to PyTorch frontend:

_

Please keep in mind that the proper way to link an issue to this list is to comment "- [ ] #issue_number" while the issue's title only includes the name of the function you've chosen.

_

The main file paths where these functions are likely to be added are:

  • ivy/functional/frontends/torch/indexing\_slicing\_joining\_mutating\_ops.py
  • ivy\_tests/test\_ivy/test\_frontends/test\_torch/test\_indexing\_slicing\_joining\_mutating\_ops.py
  • ivy/array/experimental/manipulation.py
  • ivy/container/experimental/manipulation.py
  • ivy/functional/backends/jax/experimental/manipulation.py
  • ivy/functional/backends/numpy/experimental/manipulation.py
  • ivy/functional/backends/tensorflow/experimental/manipulation.py
  • ivy/functional/backends/torch/experimental/manipulation.py
  • ivy/functional/ivy/experimental/manipulation.py

Add Ivy Container Instance Methods

Add Ivy Container Instance Methods:

  • update_config
  • inplace_update
  • set_framework
  • all_true
  • all_false
  • reduce_sum
  • reduce_prod
  • reduce_mean
  • reduce_var
  • reduce_std
  • reduce_min
  • reduce_max
  • minimum
  • maximum
  • clip
  • clip_vector_norm
  • einsum
  • vector_norm
  • matrix_norm
  • flip
  • shuffle
  • slice_via_key
  • as_ones
  • as_zeros
  • as_bools
  • as_random_uniform
  • to_native
  • to_ivy
  • expand_dims
  • dev_clone
  • dev_dist
  • to_multi_dev
  • unstack
  • split
  • gather
  • gather_nd
  • repeat
  • swapaxes
  • reshape
  • einops_rearrange
  • einops_reduce
  • einops_repeat
  • to_dev
  • stop_gradients
  • as_variables
  • as_arrays
  • num_arrays
  • size_ordered_arrays
  • to_numpy
  • from_numpy
  • arrays_as_lists
  • to_disk_as_hdf5
  • to_disk_as_pickled
  • to_jsonable
  • to_disk_as_json
  • to_list
  • to_raw
  • to_dict
  • to_iterator
  • to_iterator_values
  • to_iterator_keys
  • to_flat_list
  • from_flat_list
  • has_key
  • has_key_chain
  • find_sub_container
  • contains_sub_container
  • assert_contains_sub_container
  • find_sub_structure
  • contains_sub_structure
  • assert_contains_sub_structure
  • has_nans
  • at_keys
  • at_key_chain
  • at_key_chains
  • all_key_chains
  • key_chains_containing
  • set_at_keys
  • set_at_key_chain
  • overwrite_at_key_chain
  • set_at_key_chains
  • overwrite_at_key_chains
  • prune_keys
  • prune_key_chain
  • prune_key_chains
  • format_key_chains
  • sort_by_key
  • prune_empty
  • prune_key_from_key_chains
  • prune_keys_from_key_chains
  • restructure_key_chains
  • restructure
  • flatten_key_chains
  • copy
  • deep_copy
  • map
  • map_conts
  • dtype
  • with_entries_as_lists
  • reshape_like
  • create_if_absent
  • if_exists
  • try_kc
  • cutoff_at_depth
  • cutoff_at_height
  • slice_keys
  • with_print_limit
  • remove_print_limit
  • with_key_length_limit
  • remove_key_length_limit
  • with_print_indent
  • with_print_line_spacing
  • with_default_key_color
  • with_ivy_backend
  • set_ivy_backend
  • show
  • show_sub_container

Add Creation Ops to PyTorch Frontend

Add creation ops to PyTorch frontend:

_

Please keep in mind that the proper way to link an issue to this list is to comment "- [ ] #issue_number" while the issue's title only includes the name of the function you've chosen.

_

The main file paths where these functions are likely to be added are:

  • ivy/functional/frontends/torch/creation\_ops.py
  • ivy\_tests/test\_ivy/test\_frontends/test\_torch/test\_creation\_ops.py

Add BLAS and LAPACK Operations to PyTorch Frontend

Add BLAS and LAPACK Operations to PyTorch frontend:

_

Please keep in mind that the proper way to link an issue to this list is to comment "- [ ] #issue_number" while the issue's title only includes the name of the function you've chosen.

_

Note: If the function to be implemented has identical behavior to another PyTorch function, you should simply keep an alias in the blas\_and\_lapack\_ops.py file rather than creating a duplicate implementation.
For example:
torch.det is defined as an alias of torch.linalg.det in the official docs, and so it is defined as shown below
https://github.com/unifyai/ivy/blob/7c28666a4ff161117e7b9e4104f08be3bd7cad26/ivy/functional/frontends/torch/blas\_and\_lapack\_ops.py#L93

The main file paths where these functions are likely to be added are:

  • ivy/functional/frontends/torch/blas\_and\_lapack\_ops.py
  • ivy\_tests/test\_ivy/test\_frontends/test\_torch/test\_blas\_and\_lapack\_ops.py

Add Vision functions to PyTorch Frontend

Add Vision functions to PyTorch frontend:

_

Please keep in mind that the proper way to link an issue to this list is to comment "- [ ] #issue_number" while the issue's title only includes the name of the function you've chosen.

_

The main file paths where these functions are likely to be added are:

  • ivy/functional/frontends/torch/vision\_functions.py
  • ivy\_tests/test\_ivy/test\_frontends/test\_torch/test\_vision\_functions.py
  • ivy/functional/frontends/torch/nn/functional/vision\_functions.py

Add Gradient Functions + Classes to Ivy Frontend

Add Gradient Functions + Classes to Ivy frontend:

  • GradientTracking

Gradient Mode

  • with_grads
  • set_with_grads
  • unset_with_grads

Variables

  • variable
  • is_variable
  • variable_data
  • inplace_update
  • inplace_decrement
  • inplace_increment
  • stop_gradient

AutoGrad

  • execute_with_gradients

Optimizer Steps

  • adam_step

Optimizer Updates

  • optimizer_update
  • gradient_descent_update
  • lars_update
  • adam_update
  • lamb_update

Add Pooling Layers

Would be better to be able to add pooling in the layers, like MaxPool2D.

Add Nest Functions to Ivy Frontend

Add Nest Functions to Ivy frontend:

  • index_nest
  • set_nest_at_index
  • map_nest_at_index
  • multi_index_nest
  • set_nest_at_indices
  • map_nest_at_indices
  • nested_indices_where
  • all_nested_indices
  • map
  • nested_map
  • copy_nest

Add Ivy Container Built-in Methods

Add Ivy Container Built-in Methods:

  • repr
  • dir
  • getattr
  • setattr
  • getitem
  • setitem
  • contains
  • pos
  • neg
  • pow
  • rpow
  • add
  • radd
  • sub
  • rsub
  • mul
  • rmul
  • truediv
  • rtruediv
  • floordiv
  • rfloordiv
  • abs
  • lt
  • le
  • eq
  • ne
  • gt
  • ge
  • and
  • rand
  • or
  • ror
  • invert
  • xor
  • rxor
  • getstate
  • setstate

Add Reduction ops to PyTorch Frontend

Add Reduction ops to PyTorch frontend:

_

Please keep in mind that the proper way to link an issue to this list is to comment "- [ ] #issue_number" while the issue's title only includes the name of the function you've chosen.

_

The main file paths where these functions are likely to be added are:

  • ivy/functional/frontends/torch/reduction\_ops.py
  • ivy\_tests/test\_ivy/test\_frontends/test\_torch/test\_reduction\_ops.py

Add Dropout functions to PyTorch Frontend

Add Dropout functions to PyTorch frontend:

_

Please keep in mind that the proper way to link an issue to this list is to comment "- [ ] #issue_number" while the issue's title only includes the name of the function you've chosen.

_

The main file paths where these functions are likely to be added are:

  • ivy/functional/frontends/torch/nn/functional/dropout\_functions.py
  • ivy\_tests/test\_ivy/test\_frontends/test\_torch/test\_dropout\_functions.py

Add Functions to core API

Add new Ivy functions:

general

  • is_floating_point
  • is_nonzero
  • set_default_dtype
  • get_default_dtype
  • numel
  • full
  • full_like

random

  • bernoulli
  • poisson
  • randperm

math

  • copysign
  • deg2rad
  • rad2deg

"Quick Start" issue

Avoid other changes when changing frameworks except ivy.set_framework(). In the example, Quick Start, if I want to run it in tensorflow, except changing 'torch' to 'tensorflow' for ivy.set_framework(), I have to change the shape of x_in from [3] to [1, 3].

Add Device Functions to Ivy Frontend

Add Device Functions to Ivy frontend:

Device Queries

Array Printing:

  • get_all_arrays_on_dev
  • num_arrays_on_dev
  • print_all_arrays_on_dev

Retireval:

  • dev
  • dev_str

Conversion:

  • dev_to_str
  • str_to_dev

Memory:

  • clear_mem_on_dev
  • total_mem_on_dev
  • used_mem_on_dev
  • percent_used_mem_on_dev

Utilization:

  • dev_util

Availability:

  • gpu_is_available
  • num_cpu_cores
  • num_gpus
  • tpu_is_available

Default Device

  • default_device
  • set_default_device
  • unset_default_device

Device Allocation

  • to_dev

Function Splitting

  • split_factor
  • set_split_factor
  • split_func_call

Add Ivy Container Static Methods

Add Ivy Container Static Methods:

  • list_join
  • list_stack
  • unify
  • concat
  • stack
  • combine
  • diff
  • structural_diff
  • multi_map
  • common_key_chains
  • identical
  • assert_identical
  • identical_structure
  • assert_identical_structure
  • identical_configs
  • identical_array_shapes
  • from_disk_as_hdf5
  • from_disk_as_pickled
  • from_disk_as_json
  • h5_file_size
  • shuffle_h5_file
  • reduce
  • flatten_key_chain
  • trim_key

Add Non-linear activation functions to PyTorch Frontend

Add Non-linear activation functions to PyTorch frontend:

_

Please keep in mind that the proper way to link an issue to this list is to comment "- [ ] #issue_number" while the issue's title only includes the name of the function you've chosen.

_

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.