-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[Documentation] make documentation of GATConv
and GATv2Conv
more explicit and accurate
#8201
[Documentation] make documentation of GATConv
and GATv2Conv
more explicit and accurate
#8201
Conversation
Codecov Report
@@ Coverage Diff @@
## master #8201 +/- ##
==========================================
- Coverage 87.40% 87.39% -0.02%
==========================================
Files 473 473
Lines 28613 28613
==========================================
- Hits 25010 25006 -4
- Misses 3603 3607 +4
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
GATconv
and GATv2conv
more explicit and accurate
GATconv
and GATv2conv
more explicit and accurateGATConv
and GATv2Conv
more explicit and accurate
ok great, should we make the two failing checks pass? I had a look at the changelog, but the PR doesn't seem to contain something worth mentioning there. The test for previous pytorch version seems not to be failing because of this PR. How can the stuff be merged in the end? |
hey guys, I wanted to ask again, who can push the merge button (once this is updated with master) and if we need to make the changelog happy. |
@rusty1s would take care of it :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, this is indeed much clearer :)
It was a pleasure. I always like to share such improvements. Documentation is always a difficuilt point, because the author of the code is often hugely biased and has a large knowledge advantage, which makes it pretty hard for him to write the docs. |
What?
I explicitly named the different
\Theta
s used in the different layers by an index s and t (like it is already done in the docs when talking about input sizes). I did the same for a in the GATconv layer. Finally removed the unclear||
operator and just wrote out the few additions.Why?
To solve the issues discussed in #8200
Testing?
No tests needed, as only documentation was changed.