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

bug in tf.Print summarized formatting #20751

Closed
martin-gorner opened this issue Jul 12, 2018 · 2 comments · Fixed by #20768
Closed

bug in tf.Print summarized formatting #20751

martin-gorner opened this issue Jul 12, 2018 · 2 comments · Fixed by #20768
Assignees

Comments

@martin-gorner
Copy link

System information

  • Have I written custom code (as opposed to using a stock example script provided in TensorFlow): YES
  • OS Platform and Distribution (e.g., Linux Ubuntu 16.04): MacOS
  • TensorFlow installed from (source or binary): binary
  • TensorFlow version (use command below): 1.8
  • Python version: 3.6
  • Bazel version (if compiling from source): N/A
  • GCC/Compiler version (if compiling from source): N/A
  • CUDA/cuDNN version: N/A
  • GPU model and memory: N/A
  • Exact command to reproduce: N/A

If you print a tensor of shape [n, 4] with tf.Print, by default (summarize=3 is the default value), you get:

[[9 21 55]...]

which wrongly looks like your tensor is of shape [n, 3].

The correct output should be:

[[9 21 55...]...]

Here is what you get with tf.Print(summarize=10):

[[9 21 55 30][190 -42 236 4][89 -5]...]

Now the vectors of size 4 are visible although the last one is still wrong (looks like a vector of size 2
)

@yongtang
Copy link
Member

Added a PR #20768 for the fix.

@yongtang yongtang changed the title bug in tf.Pring summarized formatting bug in tf.Print summarized formatting Jul 14, 2018
@tensorflowbutler
Copy link
Member

Nagging Assignee @poxvoculi: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

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 a pull request may close this issue.

4 participants