Tensorboard debugger graph disappears, only queue left, why?
I am trying to use the tensorboard debugger to debug my application. I see how the graph gets slowly build, but when the training starts I only see the queue nodes on the CPU and the rest of the graph and the whole GPU section is not visible anymore. It is easiest to explain with a few pictures.
Before I run the first session.run(var.assign(data)) to initialize data:
Then I step trough the initialization of the vars:
and at the end when I start the training with sess.run(training_op):
Why do I only see the FIFO queue in the end and not the whole graph?
It looks like the GPU is getting cut out from the debugging process, but I'm not sure why, because for sure it is getting used, because I have written custom ops, where when I print I get output, but this is a cumbersome way to debug.
I can't post a MVC because the codebase is huge and convoluted, but the principle is:
- FIFO queues
q = tf.FIFOQueue(queue_size, [tf.float32, tf.float32, tf.int32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32])
- graph build up
def make_var(self, name, shape, initializer=None, regularizer=None, trainable=True):
return tf.get_variable(name, shape, initializer=initializer, regularizer=regularizer, trainable=trainable)
- variables initialization
session.run(var.assign(data))
- 2nd thread started to feed the queues
t = threading.Thread(target=load_and_enqueue, args=(sess, self.net, data_layer, coord_train, iters_train))
- training loop
- point 5 and 6 are both shown here:
formatting dummy text
for epoch in range(epochs):
coord_train.run = True
coord_val.run = True
t = threading.Thread(target=load_and_enqueue, args=(sess, self.net, data_layer, coord_train, iters_train))
t.start()
t_val = threading.Thread(target=load_and_enqueue_val, args=(sess, self.net, data_layer, coord_val, iters_val))
print("Epoch: %d / %d" % (epoch, epochs))
for iter_train in range(iters_train):
timer.tic()
loss_summary, loss_cls_summary, loss_vertex_summary, loss_pose_summary, loss_regu_summary, loss_value, loss_cls_value, loss_vertex_value, loss_pose_value, loss_regu_value, lr, _
= sess.run([loss_op, loss_cls_op, loss_vertex_op, loss_pose_op, loss_regu_op, loss, loss_cls, loss_vertex, loss_pose, loss_regu, learning_rate, train_op])
Let me know if I can provide more information and what kind would be useful to debug this problem.
python debugging tensorflow
asked Jan 3 at 10:14
HakaishinHakaishin
4991624
add a comment |
I am trying to use the tensorboard debugger to debug my application. I see how the graph gets slowly build, but when the training starts I only see the queue nodes on the CPU and the rest of the graph and the whole GPU section is not visible anymore. It is easiest to explain with a few pictures.
Before I run the first session.run(var.assign(data)) to initialize data:
Then I step trough the initialization of the vars:
and at the end when I start the training with sess.run(training_op):
Why do I only see the FIFO queue in the end and not the whole graph?
It looks like the GPU is getting cut out from the debugging process, but I'm not sure why, because for sure it is getting used, because I have written custom ops, where when I print I get output, but this is a cumbersome way to debug.
I can't post a MVC because the codebase is huge and convoluted, but the principle is:
- FIFO queues
q = tf.FIFOQueue(queue_size, [tf.float32, tf.float32, tf.int32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32])
- graph build up
def make_var(self, name, shape, initializer=None, regularizer=None, trainable=True):
return tf.get_variable(name, shape, initializer=initializer, regularizer=regularizer, trainable=trainable)
- variables initialization
session.run(var.assign(data))
- 2nd thread started to feed the queues
t = threading.Thread(target=load_and_enqueue, args=(sess, self.net, data_layer, coord_train, iters_train))
- training loop
- point 5 and 6 are both shown here:
formatting dummy text
for epoch in range(epochs):
coord_train.run = True
coord_val.run = True
t = threading.Thread(target=load_and_enqueue, args=(sess, self.net, data_layer, coord_train, iters_train))
t.start()
t_val = threading.Thread(target=load_and_enqueue_val, args=(sess, self.net, data_layer, coord_val, iters_val))
print("Epoch: %d / %d" % (epoch, epochs))
for iter_train in range(iters_train):
timer.tic()
loss_summary, loss_cls_summary, loss_vertex_summary, loss_pose_summary, loss_regu_summary, loss_value, loss_cls_value, loss_vertex_value, loss_pose_value, loss_regu_value, lr, _
= sess.run([loss_op, loss_cls_op, loss_vertex_op, loss_pose_op, loss_regu_op, loss, loss_cls, loss_vertex, loss_pose, loss_regu, learning_rate, train_op])
Let me know if I can provide more information and what kind would be useful to debug this problem.
python debugging tensorflow
asked Jan 3 at 10:14
HakaishinHakaishin
4991624
add a comment |
I am trying to use the tensorboard debugger to debug my application. I see how the graph gets slowly build, but when the training starts I only see the queue nodes on the CPU and the rest of the graph and the whole GPU section is not visible anymore. It is easiest to explain with a few pictures.
Before I run the first session.run(var.assign(data)) to initialize data:
Then I step trough the initialization of the vars:
and at the end when I start the training with sess.run(training_op):
Why do I only see the FIFO queue in the end and not the whole graph?
It looks like the GPU is getting cut out from the debugging process, but I'm not sure why, because for sure it is getting used, because I have written custom ops, where when I print I get output, but this is a cumbersome way to debug.
I can't post a MVC because the codebase is huge and convoluted, but the principle is:
- FIFO queues
q = tf.FIFOQueue(queue_size, [tf.float32, tf.float32, tf.int32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32])
- graph build up
def make_var(self, name, shape, initializer=None, regularizer=None, trainable=True):
return tf.get_variable(name, shape, initializer=initializer, regularizer=regularizer, trainable=trainable)
- variables initialization
session.run(var.assign(data))
- 2nd thread started to feed the queues
t = threading.Thread(target=load_and_enqueue, args=(sess, self.net, data_layer, coord_train, iters_train))
- training loop
- point 5 and 6 are both shown here:
formatting dummy text
for epoch in range(epochs):
coord_train.run = True
coord_val.run = True
t = threading.Thread(target=load_and_enqueue, args=(sess, self.net, data_layer, coord_train, iters_train))
t.start()
t_val = threading.Thread(target=load_and_enqueue_val, args=(sess, self.net, data_layer, coord_val, iters_val))
print("Epoch: %d / %d" % (epoch, epochs))
for iter_train in range(iters_train):
timer.tic()
loss_summary, loss_cls_summary, loss_vertex_summary, loss_pose_summary, loss_regu_summary, loss_value, loss_cls_value, loss_vertex_value, loss_pose_value, loss_regu_value, lr, _
= sess.run([loss_op, loss_cls_op, loss_vertex_op, loss_pose_op, loss_regu_op, loss, loss_cls, loss_vertex, loss_pose, loss_regu, learning_rate, train_op])
Let me know if I can provide more information and what kind would be useful to debug this problem.
python debugging tensorflow
asked Jan 3 at 10:14
HakaishinHakaishin
4991624
I am trying to use the tensorboard debugger to debug my application. I see how the graph gets slowly build, but when the training starts I only see the queue nodes on the CPU and the rest of the graph and the whole GPU section is not visible anymore. It is easiest to explain with a few pictures.
Before I run the first session.run(var.assign(data)) to initialize data:
Then I step trough the initialization of the vars:
and at the end when I start the training with sess.run(training_op):
Why do I only see the FIFO queue in the end and not the whole graph?
It looks like the GPU is getting cut out from the debugging process, but I'm not sure why, because for sure it is getting used, because I have written custom ops, where when I print I get output, but this is a cumbersome way to debug.
I can't post a MVC because the codebase is huge and convoluted, but the principle is:
- FIFO queues
q = tf.FIFOQueue(queue_size, [tf.float32, tf.float32, tf.int32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32, tf.float32])
- graph build up
def make_var(self, name, shape, initializer=None, regularizer=None, trainable=True):
return tf.get_variable(name, shape, initializer=initializer, regularizer=regularizer, trainable=trainable)
- variables initialization
session.run(var.assign(data))
- 2nd thread started to feed the queues
t = threading.Thread(target=load_and_enqueue, args=(sess, self.net, data_layer, coord_train, iters_train))
- training loop
- point 5 and 6 are both shown here:
formatting dummy text
for epoch in range(epochs):
coord_train.run = True
coord_val.run = True
t = threading.Thread(target=load_and_enqueue, args=(sess, self.net, data_layer, coord_train, iters_train))
t.start()
t_val = threading.Thread(target=load_and_enqueue_val, args=(sess, self.net, data_layer, coord_val, iters_val))
print("Epoch: %d / %d" % (epoch, epochs))
for iter_train in range(iters_train):
timer.tic()
loss_summary, loss_cls_summary, loss_vertex_summary, loss_pose_summary, loss_regu_summary, loss_value, loss_cls_value, loss_vertex_value, loss_pose_value, loss_regu_value, lr, _
= sess.run([loss_op, loss_cls_op, loss_vertex_op, loss_pose_op, loss_regu_op, loss, loss_cls, loss_vertex, loss_pose, loss_regu, learning_rate, train_op])
Let me know if I can provide more information and what kind would be useful to debug this problem.
python debugging tensorflow
python debugging tensorflow
asked Jan 3 at 10:14
HakaishinHakaishin
4991624
asked Jan 3 at 10:14
HakaishinHakaishin
4991624
asked Jan 3 at 10:14
HakaishinHakaishin
4991624
asked Jan 3 at 10:14
HakaishinHakaishin
4991624
asked Jan 3 at 10:14
HakaishinHakaishin
4991624
4991624
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54020198%2ftensorboard-debugger-graph-disappears-only-queue-left-why%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54020198%2ftensorboard-debugger-graph-disappears-only-queue-left-why%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
