-
Notifications
You must be signed in to change notification settings - Fork 283
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
Guidance on initializable iterators w/ numpy arrays #138
Comments
Relates to #68 |
It looks like the Iterator class even completely disappeared from the r2.0 API documentation. |
Using variables is a good idea, thank you! |
@jperl I think it depends on if your data is already in memory (numpy arrays) or not. If the data is already in numpy arrays then I think we could help implement a Dataset to map the numpy arrays into tensors as data continue to feed in. If you have other sources of input (like a file or a stream), we could also help implement a Dataset to take the input directly, not even necessarily to read into numpy array. Maybe you could share some details or some boilerplate code to show what the data input format is? |
The data is paths to images stored on a local filesystem. It is queried from a database, and then in memory as an array of strings. After each training loop we requery the database for the latest paths (and other metadata), and reinitialize the dataset. I believe we can accomplish this similar to the |
I am collecting data during the training process and using Dataset.from_tensor_slices with placeholders and an initializable iterator to refresh the dataset. The dataset uses the tensor slices to then do further preprocessing.
As new data is collected, I reinitialize the iterator's placeholders with the new numpy array data.
Since initializable iterators are deprecated now, how do you recommend I seed the dataset with the dynamics numpy arrays? Should I switch to using a generator?
The text was updated successfully, but these errors were encountered: