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

Explanation Accuracy Much Lower Than Table in Paper for syn2/syn4/syn5 #1

Closed
HuichenLi opened this issue Jan 25, 2022 · 1 comment
Closed

Comments

@HuichenLi
Copy link

Dear authors,
Thank you for sharing the code. I am trying to run your code to reproduce the results reported in your paper. I downloaded the project, unzip it, and then run
python3 script_eval_gt.py --dataset synX
with X equals 1, 2, 4, and 5, without changing anything in the project. With the dataset syn1, I got node accuracy 0.99, which matches the number in Table 1. However, I got node accuracy 0.62/0.61/0.51 for syn2/syn4/syn5, which are much lower than the 0.93/0.97/0.93 in Table 1 for these three cases.
Did I misinterpret anything? Are there something special about syn2/syn4/syn5 datasets that I should modify before I can get the same results as Table 1? Thank you! Your response/help is greatly appreciated.

@AlexDuvalinho
Copy link
Owner

AlexDuvalinho commented Jan 28, 2022 via email

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

2 participants