Skip to content

Remove the hatched background from functions #601

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

Merged
merged 1 commit into from
Oct 1, 2017

Conversation

chihuahua
Copy link
Member

@chihuahua chihuahua commented Oct 1, 2017

Previously, the graph explorer had made functions stand out via giving
them a hatched background. However, functions are intended to seamlessly
integrate into the graph, so we remove the hatch. @wchargin brought up some
compelling points:

  • The nodes are extremely hard to read. To quote from pgfmanual (3.0.1a,
    95): Do not use background patterns, like a crosshatch or diagonal
    lines, instead of colors. They distract. Background patterns in
    information graphics are evil.
  • We already have a "Usages of the Function" section within the info
    card that shows up when either a function template or one of its calls
    is selected. This suffices to identify the node as being associated with
    a function.
  • We already have triangles within function nodes that uniquely identify
    function input and output ops.

Test Plan: Start TensorBoard pointed at the attached events file. Note that
function nodes now lack hatched backgrounds.

u7rawcexlsc

events.out.tfevents.1506397086.functions.txt

Previously, the graph explorer had made functions stand out via giving
them a hatched background. However, functions are intended to seamlessly
integrate into the graph, so remove the hatch. @wchargin brought up some
good points.

* The nodes are extremely hard to read. To quote from pgfmanual (3.0.1a,
95): Do not use background patterns, like a crosshatch or diagonal
lines, instead of colors. They distract. Background patterns in
information graphics are _evil_.
* We already have a "Usages of the Function" section within the info
card that shows up when either a function template or one of its calls
is selected. This suffices to identify the node as being associated with
a function.
* We already have triangles within function nodes that uniquely identify
function input and output ops.
Copy link
Contributor

@wchargin wchargin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fantastic. Thanks!

@chihuahua chihuahua merged commit 6d598fc into master Oct 1, 2017
@chihuahua chihuahua deleted the chihuahua-remove-stripes branch October 1, 2017 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants