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

Citeseer data set accuracy #14

Closed
xuhaiyun42 opened this issue Nov 24, 2018 · 2 comments
Closed

Citeseer data set accuracy #14

xuhaiyun42 opened this issue Nov 24, 2018 · 2 comments

Comments

@xuhaiyun42
Copy link

Hello!I used the GAT network to run the citeseer database, but the accuracy could not reach 72.5, only 70.3. How did you set the parameters to run so high?

@PetarV-
Copy link
Owner

PetarV- commented Nov 24, 2018

Hello,

Thanks for your issue!

Regarding the Citeseer setup, we have found that early stopping just on the accuracy (rather than loss and accuracy) yielded better results.

Here is a relevant code segment:

if val_acc_avg/vl_step >= vacc_mx:
    if val_acc_avg/vl_step >= vacc_mx:
        vacc_early_model = val_acc_avg/vl_step
        vlss_early_model = val_loss_avg/vl_step
        saver.save(sess, checkpt_file)
    vacc_mx = np.max((val_acc_avg/vl_step, vacc_mx))
    vlss_mn = np.min((val_loss_avg/vl_step, vlss_mn))
    curr_step = 0

Hope that helps! Note that the standard deviation on Citeseer is large (0.7) so it might take multiple runs to achieve a satisfactory accuracy. For example, I had five runs in a row with 73.1%, 74.2%, 71.9%, 73.1%, 70.9% under this configuration.

Thanks,
Petar

@PetarV- PetarV- closed this as completed Nov 24, 2018
@xuhaiyun42
Copy link
Author

Thank you very much for the reply.

Thanks,
Xu Haiyun

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