Translate preference pairs #10
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
RishabhMaheshwary
requested review from
ljvmiranda921,
sanggusti and
ShayekhBinIslam
ljvmiranda921
approved these changes
Jul 19, 2024
|
Will merge this now! Let's just update the |
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.
Major Changes:
facebook/nllb-200-3.3Bintranslate_preference_pairs_nllb.py. At the moment, it supports only English as the source langauge and works on any huggingface preference dataset havingprompt,chosenandrejectedkeys.run_nllb.shscript has the 22 langauges listed with the codes used byfacebook/nllb-200-3.3B. The script parallelizes the translation of langauges across the number of availble GPUs.