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

TensorFlow 2.0 plans #4

Closed
nredell opened this issue Nov 18, 2019 · 2 comments
Closed

TensorFlow 2.0 plans #4

nredell opened this issue Nov 18, 2019 · 2 comments

Comments

@nredell
Copy link

nredell commented Nov 18, 2019

Hi. The tensorsem paper that you put out was an interesting read. Do you have any plans to port this package over to TensorFlow 2.0?

On a related note, do you have a roadmap or plan of what functionality you'd like to add next?

I'm curious because this seems like it'd be a worthwhile project to contribute to.

@vankesteren
Copy link
Owner

vankesteren commented Nov 20, 2019

Hi Nick,

thank you for the interest! Yes, I am currently looking at several features to move towards in the future. Tensorflow 2.0 is definitely high up on the to-do list, and more generally optimizing the tensorflow backend (e.g., looking at whether using GPU compute can speed up everything, seeing if any other optimizations can be made in this file). Unfortunately right now I'm a bit busy with other projects and I'm not so very up-to-date on the whole tf1 - tf2 upgrade. I'm also not opposed to the idea of implementing the entire package in a different framework than tensorflow (torch, mxnet, or any other computation graph + autodiff + adam optimizer software) because I am not too sure about the whole R -> python -> tensorflow tower of cards -- but this requires quite some research.

If you know how to translate the current state of this package into tensorflow 2.0 I'd be very happy to receive a pull request!

One thing on the feature roadmap is casewise / stochastic gradient descent optimization. There is a (kind of old) branch called batch_processing which implements this, but it's pretty slow and it uses some intransparent data wrangling for the tfdatasets package.
Another thing I want to think about is how to let the user add their own tensors (penalties, alternative losses) to the computation graph without pre-programming them first as in these lines. Some kind of function pass-through in the tf_sem() function would be nice.

Ideally, there would be a CRAN release at some point too.

@nredell
Copy link
Author

nredell commented Feb 6, 2020

Bad follow-up on my part. Thanks for updating to version 2.0+. Looking forward to giving this a spin.

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

2 participants