Replies: 1 comment 2 replies
-
What do you mean by the number of features is different? As long as they are consistent on the table-level, you should be absolutely fine. This is a perfect use-case for PyG, and we have tried to write many resources on it: |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm currently working on transitioning from using regression models with table data to exploring Graph Neural Networks (GNNs).
This is my first time working with graph networks, and I would greatly appreciate any advice or insights you can provide.
For example, suppose we have the following four tables.
There are more columns and rows in the data, but I simplified it to illustrate.
I want to use the relationships between these to create graph data and perform a task to predict the target for new data.
The new data will be a combination of the items listed in the above tables.
First, I would like advice on what kind of graph data and tasks should be set.
Currently, I'm considering the following two:
As shown in the table, the number of features is different, so that's a point of concern that should be noted.
I know the model's performance depends on the data's quality or the architecture itself, but I would appreciate it if we could discuss which approach is more effective in such cases.
Beta Was this translation helpful? Give feedback.
All reactions