Skip to content

Conversation

@FHof
Copy link

@FHof FHof commented May 14, 2020

The trainer was always in the waiting state, so for testing I have added some print debugging and made the ConsoleStats output less invasive (https://pastebin.com/TAiCVhGD).
With these changes, when running train.py, I could see that self.model.predict throws an error: https://pastebin.com/raw/w9cLY8LM

To fix the trainer crash, I have applied the suggestion from tensorflow/tensorflow#28287 (comment).

I'm not familiar with tensorflow, so I don't know if I've fixed the problem correctly;
now the trainer is no longer stuck in the waiting state.

related issue: #3

I have applied the suggestion from tensorflow/tensorflow#28287 (comment)
I'm not familiar with tensorflow, so I don't know if I've fixed the problem correctly.
Now the trainer is no longer stuck in the waiting state.
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

Successfully merging this pull request may close these issues.

1 participant