Llama 3 Compatibility Support - #1409
Conversation
|
Hi @gauravsinghbitmesra-design! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
8156326 to
a76f828
Compare
Production-ready implementation of Llama 3 compatibility: - Configurable RoPE theta (500k context support) - Dual tokenizer support (SentencePiece/Tiktoken) - Flexible ChatFormatter system with Llama 2/3 templates - Comprehensive validation and error handling - Optimized performance and clean mutation-free logic
510e743 to
06b7421
Compare
Llama 3 Compatibility Support
Description
Refactors the model and tokenizer components to support Llama 3 specifications while maintaining backward compatibility with Llama 2.
Key Changes
rope_thetatoModelArgsto support Llama 3's 500k base.tiktokensupport inTokenizerclass to handle Llama 3 models, with automatic fallback to SentencePiece for Llama 2.generation.pyto use aChatFormattersystem, enabling support for Llama 3's special token structure (<|start_header_id|>, etc.).Verification
tests/test_llama3_compat.pyto verify: