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

How to reuse best checkpoint and turned hparams.yaml to predict results #39

Open
YonDraco opened this issue Apr 8, 2024 · 3 comments
Open

Comments

@YonDraco
Copy link

YonDraco commented Apr 8, 2024

I used best checkpoint after turning then used get_lag_llama_predictions function to predict from best checkpoint . However, the predicted result is much lower than when I turned and trained that checkpoint.

@YonDraco YonDraco closed this as completed Apr 8, 2024
@YonDraco YonDraco reopened this Apr 8, 2024
@ashok-arjun
Copy link
Contributor

Sorry, I don't understand. Can you elaborate? Which checkpoint did you use?

@YonDraco
Copy link
Author

YonDraco commented Apr 9, 2024

@ashok-arjun I saved the best checkpoint epoch=36-step=1850.ckpt after turning and used the get_lag_llama_predictions function as in colab demo 2 to make predictions from this checkpoint. However, when loading this checkpoint to make predictions, the results are worse than when turning. So I think I will have to load both checkpoint and hparams.yml but I don't know how to handle them

@ashok-arjun
Copy link
Contributor

ashok-arjun commented Apr 9, 2024

Sorry, I don't understand what "turning" is. Do you mean finetuning or training?

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