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

Why is it suddenly 'killed' run train.py? #111

Open
INJNainggolan opened this issue Jul 22, 2019 · 1 comment
Open

Why is it suddenly 'killed' run train.py? #111

INJNainggolan opened this issue Jul 22, 2019 · 1 comment

Comments

@INJNainggolan
Copy link

step 246 total loss = 0.767, sub4 = 1.042, sub24 = 0.553, sub124 = 0.238, val_loss: 0.706 (1.229 sec/step)
step 247 total loss = 0.775, sub4 = 0.978, sub24 = 0.558, sub124 = 0.254, val_loss: 0.917 (0.760 sec/step)
step 248 total loss = 0.996, sub4 = 1.198, sub24 = 0.775, sub124 = 0.353, val_loss: 1.151 (0.849 sec/step)
step 249 total loss = 0.765, sub4 = 0.959, sub24 = 0.647, sub124 = 0.211, val_loss: 0.858 (1.241 sec/step)
2019-07-22 02:07:55.482708: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:97] Filling up shuffle buffer (this may take a while): 59 of 500
2019-07-22 02:08:04.897199: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:97] Filling up shuffle buffer (this may take a while): 131 of 500
2019-07-22 02:08:14.928381: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:97] Filling up shuffle buffer (this may take a while): 213 of 500
Killed

Why is it suddenly 'killed' during run train.py?

@ZhenpengChenCode
Copy link

Hello, I encountered the same problem, did you solve it?

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