Fix Google Colab notebook 2024-05 #1662
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Without explicitly installing mlflow the `accelerate launch` command fails.
winglian
approved these changes
May 28, 2024
djsaunde
pushed a commit
that referenced
this pull request
Dec 17, 2024
* include mlflow installation in the colab notebook Without explicitly installing mlflow the `accelerate launch` command fails. * update the colab noteboko to use the latest tinyllama config
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A couple of fixes to make the Google Colab notebook run (tried on an L4 GPU):
mlflowinstallation in the setupexamples/Description
The
accelerate launchcommand fails without installingmlflow, so I included!pip install mlflow=="2.13.0"with the other deps at the top.The current config YAML included in the notebook results in
_amp_foreach_non_finite_check_and_unscale_cuda" not implemented for 'BFloat16'. This doesn't happen when we instead use the current QLORA config for tinyllama. Possibly just updating tobf16: autowould be enough? But I didn't test that and using the entire new config seems better.Motivation and Context
I tried to get started in Colab and couldn't because of these issues.
How has this been tested?
Ran in Colab using an L4 GPU.
Types of changes
Social Handles (Optional)