Llava 1.6 Instruction Finetuning
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- ai, machine-learning
Research direction
The issue names no files, tests, or entry points; it asks for guidance on BlockAP quantization, projector training, and end-to-end fine-tuning for Llava 1.6. Review the repository's relevant training and quantization entry points, then document the intended stages, parameters, and code references so each question has a confirmed answer.
Written by the indexing model from the issue text.
Description
Hi @ChenMnZ,
I am seeking clarification and guidance on the process of quantizing the Llava 1.6 model using the Efficient QAT repository. Specifically, I would like to confirm the steps involved and understand the details regarding what components are finetuned at each stage of the process.
Queries
- Applying BlockAP on LLM : Is the initial step to apply BlockAP quantization on the LLM? If so, are there any specific datasets, considerations or configurations required during this step?
- Freezing LLM and Vision Transformer (ViT), and Training the Projector: After obtaining the BlockAP-quantized LLM, the next step appears to involve freezing both the LLM and ViT while training the projector. Could you provide details on where to perform the projector training ? Any relevant scripts or functions would be helpful for implementing this step effectively.
- End-to-End Fine-Tuning of LLM and Projector: During the end-to-end fine-tuning stage, do we:
a. Finetune only the scales for the LLM?
b. Finetune the weights for the projector?
Are there any additional parameters or components involved in this finetuning process that I might be missing?
Could you please provide clarity on the above queries and confirm if the outlined process aligns with the intended approach for quantizing Llava 1.6? Additionally, I would appreciate any guidance on specific code references or best practices for implementing the training and fine-tuning stages.
Looking forward to your insights! Thank you in advance for your support.
- Dominant language
- Python
- Stars
- 351
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
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.
More from OpenGVLab/EfficientQAT
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
OpenGVLab/EfficientQAT#31 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
OpenGVLab/EfficientQAT#34 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
OpenGVLab/EfficientQAT#33 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
OpenGVLab/EfficientQAT#32 ·
-
About Dataset Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
OpenGVLab/EfficientQAT#30 ·
All issues in OpenGVLab/EfficientQAT
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1780 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·