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

Use of graph pooling for node classification #57

Open
torjusn opened this issue Apr 21, 2021 · 0 comments
Open

Use of graph pooling for node classification #57

torjusn opened this issue Apr 21, 2021 · 0 comments

Comments

@torjusn
Copy link

torjusn commented Apr 21, 2021

The usage file and another paper I found mentions the possibility of using the architecture for node classification. I wondered how the signal classification example differs from node classification with multi-feature nodes V=(number of nodes, node features) and A = (number of nodes, number of nodes), specifically:

  1. For node classification I'd assume we need the final layer to output: (Batch size=1, Number of classes, Nodes) to get a prediction per class just set the last fully connected layer=number of classes, but how can we get a prediction for each node when the node pooling decreases number of nodes so the final layers number of nodes is V/(pool_size_1*pool_size_2).
  2. The Notebook example expands input since features=1, so first pass to gconv is N, M, F=1, i.e. graph signals in a batch, number of nodes, and features=1. For this case would rank still be=2 since data only has number of nodes in batch and features, and should it be expanded? It doesn't seem like there should be any M if not dealing with graph signals.

Thank you for the great article!

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

No branches or pull requests

1 participant