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

Why the problem of KBAT data leakage is not reflected in your code #5

Closed
xjzhao001 opened this issue Jul 16, 2020 · 3 comments
Closed

Comments

@xjzhao001
Copy link

I want to know whether the result reported in your paper about KBAT is the result after fix. I only saw the content of the evaluation protocol modified in the code, and did not see the modification of the valid_triples_dict you mentioned, thanks.

@svjan5
Copy link
Owner

svjan5 commented Jul 16, 2020

Yes, the results are reported after correcting both the evaluation script and the test leakage problem. Thanks for pointing that out. We might have missed that in the version which we made publicly available.

@xjzhao001
Copy link
Author

Thank you for your reply. Based on the "they shouldn't use valid_triples_dict (all triples in train, dev, and test) in this line, but should only use training data" you mentioned in other issues, can I understand that it is enough to change the "self.valid_triples_dict = {j: i for i, j in enumerate(self.train_triples + self.validation_triples + self.test_triples)}" in the code to "self.valid_triples_dict = {j: i for i, j in enumerate(self.train_triples )}"?

There is another problem. I noticed that you have commented out two lines of code in "main.py". In our experiment, this operation will cause loss to fail to converge. Is it possible that you sort out the omissions of the code or should you really comment it out? If it should be commented out, can you tell me why? Thank you.
#main.py
line198 # loss.backward()
line199 # optimizer.step()

@svjan5
Copy link
Owner

svjan5 commented Jul 17, 2020

Thanks for pointing that out. I have updated the code, please have a look.

@svjan5 svjan5 closed this as completed Jul 21, 2020
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