You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifically, I used the k_hop_subgraph function to find the one-hop neighbors of a target node. My target nodes are defined as torch.arange(gia_test.y.shape[0], gia_test.x.shape[0]), where gia_test.x represents the original dataset with some newly added nodes. Naturally, these new nodes introduce additional connections; however, I did not assign them any labels. My goal is to identify the original nodes to which these new nodes are connected.
To achieve this, I executed the following code. However, I was surprised to find that the resulting edge_index contained some extra nodes that I did not expect. I am unsure why this occurs—could this behavior be considered normal?
🐛 Describe the bug
Specifically, I used the
k_hop_subgraph
function to find the one-hop neighbors of a target node. My target nodes are defined astorch.arange(gia_test.y.shape[0], gia_test.x.shape[0])
, wheregia_test.x
represents the original dataset with some newly added nodes. Naturally, these new nodes introduce additional connections; however, I did not assign them any labels. My goal is to identify the original nodes to which these new nodes are connected.To achieve this, I executed the following code. However, I was surprised to find that the resulting
edge_index
contained some extra nodes that I did not expect. I am unsure why this occurs—could this behavior be considered normal?Versions
The text was updated successfully, but these errors were encountered: