merge-ov2

Merge standalone ViT encoder and LLM into a unified LlavaOnevision2 HuggingFace checkpoint.

1.2k|78|Updated Sep 16, 2025
One-click install
npx skills add https://github.com/EvolvingLMMs-Lab/LLaVA-OneVision-2 --skill merge-ov2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-ov2
Source: https://github.com/EvolvingLMMs-Lab/LLaVA-OneVision-2/tree/main/.opencode/skills/merge-ov2
Command: npx skills add https://github.com/EvolvingLMMs-Lab/LLaVA-OneVision-2 --skill merge-ov2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges standalone ViT encoder and LLM into a unified LlavaOnevision2 HuggingFace checkpoint, preserving weights and enabling end-to-end parity checks.

Core Features & Use Cases

  • Remaps and merges visual encoder weights into a single cross-modality checkpoint.
  • Provides end-to-end validation comparing merged weights and inference outputs against originals.
  • Supports optional verification steps and guidance for Megatron-style conversions.

Quick Start

Run the merge_ov2 tool with your ViT encoder, LLM, and processor checkpoints to generate a unified LlavaOnevision2 checkpoint.

Frequently Asked Questions about merge-ov2

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge a standalone ViT encoder and LLM into a unified multimodal checkpoint?

To merge a standalone ViT encoder and LLM, use the merge_ov2 tool to remap and combine weights into a unified LlavaOnevision2 HuggingFace checkpoint. It applies remap and validate tooling to ensure the merged weights and inferences remain consistent with the originals.

What is the best way to validate merged multimodal model weights against original components?

The best way to validate merged multimodal weights is to use end-to-end validation tooling that compares the merged checkpoint's weights and inference outputs directly against the original standalone ViT encoder and LLM components to ensure full parity.

Do I need a GPU-enabled container to merge vision and language models?

Yes, you need a GPU-enabled container to merge vision and language models. The merge process requires a GPU environment and a correct path layout under /workspace/LLaVA-OneVision-2 to successfully produce a validated merged checkpoint.

How to convert standalone encoders for Megatron-style model composition?

To convert standalone encoders for Megatron-style model composition, use the provided guidance and optional verification steps during the merge process. This ensures the standalone ViT encoder and LLM are correctly remapped into the unified checkpoint format.

Why does my merged LlavaOnevision2 checkpoint produce inconsistent inference results?

A merged LlavaOnevision2 checkpoint produces inconsistent inference results if the remap and validate tooling was not applied correctly. Running end-to-end validation comparing outputs against the original ViT and LLM helps identify and resolve weight mismatches.