-
Notifications
You must be signed in to change notification settings - Fork 568
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
Optimizer and trainer states for OLMo-7B (Feb. 2024) #796
Comments
Hey @rahuln, those files were deleted by mistake. I'm in the process of restoring them. I will update you once they are back. |
I just wanted to follow up on this, are those training checkpoints now available? |
Hey @rahuln, I have started the process, it might take 3-4 days to upload. If you need any particular checkpoint, I can fast-forward that and provide you the link. |
Awesome, thank you! I'd mainly like to use earlier checkpoints (the first 5 or so), so if those are available sooner and you're able to share the links I'd really appreciate it. |
Hey @rahuln, first 5 checkpoints are restored. Check out the same links. |
Great, thanks so much! Would you happen to have the links for all of the early checkpoints? The links in the CSV file for the original version of OLMo (this file) only start at step 5000. |
Hey @rahuln, yes we do have them, I will upload them by the end of this week. |
❓ The question
I'd like to be able to do continued pretraining with the intermediate checkpoints of the original OLMo-7B model (from February 2024), including initializing from the intermediate optimizer and trainer states. I found an older version of the README that includes instructions on how to access these intermediate checkpoints as well as a list of paths pointing to those files, but they don't seem to work with the OLMo training code (i.e., files like
model.pt
/model.safetensors
andoptim.pt
/optim.safetensors
can't be found at those links). Is there somewhere I can go to find links to the original OLMo checkpoints with optimizer and trainer state files?The text was updated successfully, but these errors were encountered: