-
Notifications
You must be signed in to change notification settings - Fork 19.5k
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
Functional Preprocessing and Augmentation API #6655
Comments
Is there anything like the tf preprocessing for theano? Otherwise, I guess it's a deal-breaker for theano users. |
@Dref360 I don't know, perhaps plain python APIs could be run on the theano side? They already have the sequential api you mentioned so adaptation may not be too hard, where would a feature request for theano be submitted? |
Edit: A new example proposal + details is in #6891 (comment). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 30 days if no further activity occurs, but feel free to re-open a closed issue if needed. |
If you're using the TensorFlow backend, you can just use input tensors by following the mnist_tfrecord.py example, and before passing your tensors to the Input layer apply TensorFlow preprocessing ops such as tf.random_crop. Since there is a way to accomplish this, I'm closing the issue. |
Edit: A new example proposal + details is in #6891 (comment).
Discussion about a dense prediction API such as image segmentation in #6538 brought up the possibility of a functional preprocessing API, which could move preprocessing steps into the Keras backend APIs and generalize preprocessing to more network designs. Dropout provides a precedent for such augmentation layers.
If the layers could be designed much like dropout, and I would expect them to be configured so that the augmentation operations could be applied identically to one or more image inputs as well as one or more image label data, useful for dense prediction tasks.
This could have the advantages of being easy to use, easily applied consistently for arbitrary data inputs, and make it possible to use the TF backend image augmentation APIs thus improving performance.
What would be the pros/cons and barriers to a Functional Preprocessing API?
Example usage, label augmentation optional for dense prediction tasks:
The text was updated successfully, but these errors were encountered: