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

Should we move to pytorch? #29

Open
mathomp4 opened this issue Feb 11, 2025 · 2 comments
Open

Should we move to pytorch? #29

mathomp4 opened this issue Feb 11, 2025 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@mathomp4
Copy link
Member

As seen in #28, tensorflow is not yet Python 3.13 ready.

That said, a lot of the internet seems to like PyTorch more than Tensorflow. So, should we move GEOSpyD to use it?

I call on @katherbreen, @dbarahon, @amdasilva, and @JulesKouatchou as people more knowledgeable than I to see.

It would be nice for us to support a Python 3.13 GEOSpyD stack

@mathomp4 mathomp4 added the question Further information is requested label Feb 11, 2025
@mathomp4 mathomp4 self-assigned this Feb 11, 2025
@JulesKouatchou
Copy link

I am in favor of adding PyTorch (if possible) to GEOSpyD. I recently wrote introductory materials on PyTorch:

https://github.com/astg606/astg_pymaterials/tree/main/pytorch

The examples in the three notebooks are for CPUs only. I will soon make small modification to make them work on both CPUs and GPUs.

PyTorch appears to be more popular than TensorFlow. People like its ability to change the computational graph at run time. It is good to have both options available.

@mathomp4
Copy link
Member Author

@JulesKouatchou Okay. I can look at maybe adding it and then not installing Tensorflow if Python 3.13 (for now)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants