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

Consider switching to keras as engine #751

Open
NickleDave opened this issue May 5, 2024 · 0 comments
Open

Consider switching to keras as engine #751

NickleDave opened this issue May 5, 2024 · 0 comments

Comments

@NickleDave
Copy link
Collaborator

Keras 3.0 is out and allows tensorflow/torch/jax as backends.

This would let us

  • vendor more models instead of re-implement them (user would need to install appropriate backend as needed): e.g., DAS, DAN, etc
  • not have to deal with pain points of lightning that I am now running into
  • be able to use jax for ops that are still not painful/not possible in torch/tensorflow

I am sure there are similar pain points to using keras with multiple back-ends but it is a simple API that would make it easier for users to implement their own models without having to grok the abstraction I came up with. I would need to test it in a branch and see what breaks

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

1 participant