Same Message Function Across All Edge Types Issue#52
Open
juhimgupta wants to merge 6 commits intoadalnfrom
Open
Same Message Function Across All Edge Types Issue#52juhimgupta wants to merge 6 commits intoadalnfrom
juhimgupta wants to merge 6 commits intoadalnfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We noticed that in its current implementation, using the same message function across all edge types is leading to poorer performance even on unconditional tasks (i.e. denovo ligand condensed) where only ligand-ligand edge types exist.
The current approach is to either concatenate edge features to scalar features if an edge type has edge features, or concatenate a tensor of 0s to scalar features if an edge type does not have edge features.