-
Notifications
You must be signed in to change notification settings - Fork 531
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
Infer step size for Embeddings #1647
Conversation
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.
Small comments
I really like this idea. I do have a couple soft suggestions:
Anyway, the current approach is fine too, but wanted to share just in case. |
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.
This looks mostly good to me!
A few requests for integration tests:
- Confirm expected behavior when training data has no hard negatives.
- Confirm when using hard negatives = 1.
- Confirm when using hard negatives = 3 (or some number besides 1).
Maybe you've already done this? In which case I will switch to approve after you address my minor comments.
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.
Theres two cases:
We can remove setting step_size and autoinfer without needing the pos_step_size. We will need to look at the first batch to determine how many hard negatives. If there are hard negatives, we will use that - 1 as the step size. Otherwise, we will defer to batch negatives, setting step_size = 2
Testing:
embedding-ft-no-pos-zXOtvz (off of this branch, removed pos_step_size keyword):
embedding-ft-pos-kl2fPy (off foundry main pos_step_size = 2):
embedding-ft-pos-neg-gMJSGx (off foundry main pos_step_size = 21)
embedding-ft-no-pos-neg-3GoEms (off of this branch, removed pos_step_size keyword):