Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Aesara as a backend #213

Open
rlouf opened this issue Feb 4, 2023 · 4 comments
Open

Add Aesara as a backend #213

rlouf opened this issue Feb 4, 2023 · 4 comments

Comments

@rlouf
Copy link

rlouf commented Feb 4, 2023

I am a core member of Aesara, a fork of the now deprecated Theano. Since there is a Theano backend, do you think it would make sense to have an Aesara backend as well?

@dgasmith
Copy link
Owner

@rlouf Absolutely, always happy to review PRs!

@jcmgray
Copy link
Collaborator

jcmgray commented Feb 13, 2023

Yes it would certiainly be nice to have, I'll just note the requirements are pretty simple:

  • ability to dynamically define high dimensional tensors.
  • tensordot implementation
  • (optional) einsum implementation -- without this only some contractions can be performed

@jcmgray
Copy link
Collaborator

jcmgray commented Feb 17, 2023

Possibly relevant question @rlouf, what is the best way to get the shape of a TensorType as a plain tuple of int? They don't have an infer_shape method. Is t.shape.eval() the way to go?

@rlouf
Copy link
Author

rlouf commented Feb 17, 2023

You can try t.type.shape if the shape is known before evaluating the graph. The reason you don't get a tuple of int immediately is that in most cases the shape is not known before evaluating the graph with the inputs; t.type.shape will give you a tuple with int when the dimension is known and None otherwise.

@rlouf rlouf mentioned this issue Mar 10, 2023
1 task
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

No branches or pull requests

3 participants