You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After creating a dataset pipeline with a batch and mapAsync operation. Passing it to model.fitDataset, causes the mapAsync to run over the whole dataset and then once again for each batch.
I've made a repo to reproduce that I'll link below but here is some of the output I get.
Hi @tafsiri ,
Apology for the late response.
Kindly Let me know if your issue is resolved in latest version of npm 4.4.0. If it is not resolved yet, kindly share the reproducible code. Your provided code link is broken. Thanks!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you.
TensorFlow.js version
"@tensorflow/tfjs": "1.0.0",
Browser version
Node 11.11
Describe the problem or feature request
batch
andmapAsync
operation. Passing it to model.fitDataset, causes themapAsync
to run over the whole dataset and then once again for each batch.I've made a repo to reproduce that I'll link below but here is some of the output I get.
The code looks like this https://github.com/tafsiri/use-text-classifier/blob/fitdataset/training/train.js#L63
The initial behaviour of going through all the batches happens at the start of each epoch.
2). When using mapAsync without batch it seems to not always wait for the function to finish? I'll link to sample code below but in this case I get
The counter seems to increment multiple times before some of the tensor operations complete.
The code looks like this https://github.com/tafsiri/use-text-classifier/blob/fitdataset/training/train.js#L23
Code to reproduce the bug / link to feature request
To reproduce 1). Clone this repo https://github.com/tafsiri/use-text-classifier/tree/fitdataset switch the fitDataset branch, go into the training folder and run
node train.js
To reproduce 2). Do the same as above but comment out lines 124-130 in train.js and uncomment lines 133-140.
The text was updated successfully, but these errors were encountered: