-
Notifications
You must be signed in to change notification settings - Fork 157
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
Is it possible to learn more than 2 edge-types in unsupervised manner? #26
Comments
The number of edges is a parameter that can be set to any number of edge types (of course not all numbers might work well). When we said "known" we didn't mean supervised manner, but that the number of edge types is known in advance as it is a simulation created by us. |
Thank you for the reply! Now, I'm trying to reproduce the results, and generate a dataset of simulation that has 3 edge-types (weak spring, strong spring, no-interaction) When I trained NRI with 2 edge-types dataset (that I generate myself), It reaches to about 99% accuracy. |
Thank you for your questions. I have not reproduced the results of this paper and I'm not very clear about the non-interaction edge type. Since there is no interaction between the non-interaction edge type should we directly ignore the non-interaction edge type in the decoder? E.g. If we use z_{ij}=[0,1] to denote interaction and z_{ij}=[1,0] to denote non-interaction, in the decoder should we write the edge embedding as: h^t_{ij} = z_{ij,0}fe([x^t_i, x^t_j]) ? |
I think in the paper they mean there are still 2 edge types(interaction or non-interaction) in the labels, but add an 3rd unknown(non-exist) edge in the encoder. |
Hello, thank you for your great work and nice code.
I saw the supplementary material, and it said that NRI can learn "known" 3 edge types (no-interaction, weak spring, strong spring).
In this sentence, dose "known" mean that NRI can learn the relations only in supervised manner, not in unsupervised manner?
In the source code, is it right that relation-supervised training is not implemented?
Again, thank you for your great work!
The text was updated successfully, but these errors were encountered: