Bad performance when fine-tuning Vicuna on Arabic data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.5k
- Forks
- 4.8k
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
Given that Vicuna actually responds to Arabic prompts in Arabic (although lacking), I still judged it to be suitable enough for fine-tuning on Arabic data (more specifically, instructional data and closed-book QA data). However, after fine-tuning the 7b variant, the performance is really bad as it's not even able to construct a sentence that's fully correct when prompted.
I expected a mediocre performance after seeing that the loss was in the range of 4-6, but what could be the reason behind this? Note that I modified the Llama tokenizer so that it supports Arabic vocabulary by integrating an Arabic sentencepiece model.
Any help is most appreciated! thanks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is named. Start by reproducing fine-tuning of the Vicuna 7B variant on the described Arabic instructional and closed-book QA data, then inspect the modified Llama tokenizer and reported loss range; done requires identifying and documenting the cause of the poor Arabic output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100