-
Notifications
You must be signed in to change notification settings - Fork 67
[Docs] Clarify get-events API usage #320
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
Conversation
Don't merge yet, was going to make some comments |
docs/guides/fine_tuning.md
Outdated
as well as any errors that may have occurred. If you encounter any errors with your fine-tune, | ||
the events are a good place to start debugging. For example, if you see `Unable to read training or validation dataset`, | ||
you may need to make your files accessible to LLM Engine. If you see `Invalid value received for lora parameter 'lora_alpha'!`, | ||
you should check that your hyperparameters are valid. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be good to add a reminder link to the canonical definition of valid hyperparameters?
The status of your fine-tune will give a high-level overview of the fine-tune's progress. | ||
The events of your fine-tune will give more detail, such as the training loss and validation loss at each epoch, | ||
as well as any errors that may have occurred. If you encounter any errors with your fine-tune, | ||
the events are a good place to start debugging. For example, if you see `Unable to read training or validation dataset`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have a separate error for malformed files, e.g. files that don't have prompt,response
headers?
Would it make sense to put these in a table?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed offline: prompt,response
header validation would happen earlier, at FineTune.create
time.
Also update docs to reflect that mistral-7b is available