[Bug Fix] Fix RGAT when inputs of rgat.forward have shape (0, x) #562
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
October 13, 2023 22:52
added 2 commits
October 16, 2023 09:38
classicsong
added
bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
When inputs of RGAT.RelationalAttLayer have some node types with input shape (0, x). The module will crash.
Description of changes:
Fix the bug. More details please see tests/unit-tests/test_nn_model.py: test_rgat_with_zero_input
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.