Repository navigation
feat(merge):add merge py for llava ckpt - #69
Merged
Merged
Conversation
This file contains hidden or 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
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.
What
Adds
src/dataflex/utils/llava_v1d5_ckpt_merge.py, a self-contained CLI for producing LLaVA-1.5 checkpoints that evaluation engines can load.Transformers 5.x exports LLaVA's CLIP vision tower with flat parameter names (vision_tower.embeddings.* / vision_tower.encoder.), while vLLM and Transformers 4.x evaluation stacks expect the classic nested layout
(vision_tower.vision_model.). Loading such a checkpoint fails with:
ValueError: There is no module or parameter named 'vision_tower.embeddings' in LlavaForConditionalGeneration
The new utility wraps
llamafactory-cli exportand then rewrites only the vision-tower key names; every tensor value is copied unchanged, so no numerical change is introduced and the training checkpoint stays untouched.Validated on a real LLaVA-1.5-7B merged checkpoint: the converted output is byte-identical to the previously validated vLLM checkpoint (4/4 shards match sha256, 686 keys, 391 nested vision tensors, ~31s).