-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Confirmation] Optimal Hyperparameters and Reproducibility #21
Comments
Hi, thanks for your question: When running downstream tasks, please keep the parameters consistent with Table 6 in the paper. I need to explain that the |
Hi, thank you for the prompt reply. It's very helpful! Meanwhile, I carefully check the
|
Hello: |
Thanks. I can roughly reproduce the results using the latest scripts (except contact, which is still running). |
Hi @zxlzr , I got the following result for OntoProtein on contact, which seems to be too. The paper reports 0.40 for l2. I'm not sure if I miss sth, can you help double-check it?
|
Hi, can you please provide more detailed information? For example, your hyperparameters and the sequence length between amino acids. |
Hi there, |
|
Thanks. I'm reporting the one for |
Hi, may I ask if there are any follow-ups? |
I don't know precisely what the error cause is, but we can provide a model of the contact task fine-tuned according to our hyperparameters. And this model was also retrained by us, so there may be 2~4 points of fluctuation, but the difference will not be much. |
Sounds good! That would be very helpful! |
You can download the checkpoint here |
@cheng-siyuan
Not sure if I miss sth. |
Yes, this checkpoint is obtained later when we have updated the hyperparameters, so that the effect will be 3 to 4 points higher than our result at the beginning. The result in the paper is not the best result yet, and I apologize for the trouble to your experiment. |
No problem at all, and you have already been very helpful in replying to the messages :) So just to double-check, you mean that in Table 1 of your paper, it should be updated to |
Yes, we recommend that you use the results of this checkpoint as a reference. |
Sounds good! Appreciate your help and being responsible for your work! |
You're welcome:) |
Hi there,
Thanks for providing the nice codebase. I'm trying to reproduce the results for downstream tasks, and I have the following questions.
gradient_accumulation_steps
andeval_step
. Can you help clarify this?Any help is appreciated.
The text was updated successfully, but these errors were encountered: