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
tf.keras.callbacks.Tensorboard: write_images does not visualize Conv2D weights #2240
Comments
@maxstrobel I'm facing same issue. Do you solve it ? |
Hi @menon92, No I did not dive deeper into it. However, the issue seems to be also present in TF2.0. |
cc @caisq FYI re tensor visualization |
@rmothukuru , @nfelt , @caisq , I have the same issue. Tensorboard will not visualize Kernels of Conv2D layers, only biases. |
I have a related issue: On my side, only the first 3 Kernels of the first Conv2D layer are displayed. Is it somewhat related to the signature of the
|
@MZehren: Yes: as you note, we only write the first |
Hi @wchargin , I wonder if in the meantime, you might be able to answer my following question, while we "stat:awaiting tensorflower"... Why is there a label: "type: feature"? Isn't this a bug? Isn't Tensorboard (and it's callback) meant to currently be able visualize the Kernels of Conv2D layers already? |
I moved this issue from tensorflow/tensorflow#28767
System information
Describe the current behavior
When I want to have a look at the weights of Conv2D filters in TensorBoard, only their biases get logged (see attached image). I looked for the corresponding source code and found the following snippet:
https://github.com/tensorflow/tensorflow/blob/6612da89516247503f03ef76e974b51a434fb52e/tensorflow/python/keras/callbacks.py#L951-L983
The problem seems to be that Conv2D weights have a 4d shape [H_kernel, W_kernel, C_in, C_out], which is not intended as convolutional layers case in the above code.
Describe the expected behavior
I would expect that the convolutional weights are visualized. I know this would be a huge amount of images (C_in * C_out), but I think the current behaviour is confusing.
Code to reproduce the issue
Other info / logs
The text was updated successfully, but these errors were encountered: