Downloads · 30 days
95
10% of all-time downloads
OpenMOSE/Qwen3.5-REAP-97B-A10B
Qwen3.5-REAP-97B-A10B is a machine learning model from OpenMOSE. Use it for the machine learning task on the model card, and read the license before you ship it in a product. The card lists the license as apache-2.0.
Vision–Language MoE model created by applying Router-weighted Expert Activation Pruning (REAP) to Qwen3.5-122B-A10B.
Downloads · 30 days
95
10% of all-time downloads
All-time downloads
952
Public
Parameters
97.2B
194 GB on disk
Likes
16
Public
Click a slice to open those files.
.safetensors194 GB · 100%
From the Hugging Face model README
Vision–Language MoE model created by applying Router-weighted Expert Activation Pruning (REAP) to Qwen3.5-122B-A10B.
This is an unofficial community variant of Qwen3.5, not affiliated with or endorsed by Alibaba or Cerebras Systems.
REAP (Router-weighted Expert Activation Pruning) is a pruning method for MoE models that uses:
to identify under-used or redundant experts and prune them while preserving model quality as much as possible.
For this model:
In short: same REAP algorithm, adapted to Qwen3.5's hybrid linear/full attention MoE architecture, leaving VL functionality available.
The REAP pruning statistics were computed using:
Calibration dataset: https://huggingface.co/datasets/OpenMOSE/reap-calib-mix
This dataset is mostly synthetic, generated by Qwen3-235B-Instruct on mixed prompts designed to cover:
The calibration set is not used for additional fine-tuning; it is used solely to measure router/expert activations to decide which experts to prune.
Qwen3.5-122B-A10B is one of the most frontier-capable open-source models runnable at 96 GB, but it still exceeds what a typical 48 GB GPU setup can handle. By pruning ~22% of experts:
The model shrinks from ~122B total parameters to about 97B total parameters.
Sparse MoE activation keeps around 10B parameters active per token ("A10B"), same effective compute profile as the base model.
In practice, this makes the model feasible to deploy on a 48 GB GPU with modest CPU offload:
The overarching goal is to bring the closest OSS approximation to a frontier model into local deployment, making Qwen3.5-122B-A10B accessible without requiring multi-GPU nodes.
Key architectural properties inherited from the base model and preserved after pruning:
| Property | Value |
|---|---|
| Hidden size | 3072 |
| Num layers | 48 |
| Attention type | Hybrid (3× linear + 1× full, repeating) |
| Full attention interval | every 4th layer |
| Num attention heads | 32 |
| Num KV heads | 2 |
| Head dim | 256 |
| MoE experts total | 200 (pruned from 256) |
| Experts per token | 8 |
| MoE intermediate size | 1024 |
| Max context length | 262,144 tokens |
| Vocab size | 248,320 |
The hybrid attention design (linear attention layers interleaved with full attention every 4 layers) is a distinctive feature of the Qwen3.5 family and is retained fully after pruning.
Primary intended uses
Research on:
Experimental deployment for:
Suitable tasks (examples)
Out-of-scope / high-risk uses
This model should not be used without additional safeguards for:
This model inherits all the limitations of Qwen3.5-122B-A10B plus those introduced by pruning:
Hallucinations: The model can generate plausible but incorrect facts.
Bias & toxicity: Biases from the original training data and synthetic calibration data remain and may be amplified.
Distribution shift from pruning:
Multimodal edge cases:
Hybrid attention sensitivity:
Users should perform their own evaluation before relying on the model in any sensitive context.
Note: Requires
transformers >= 4.57.0.dev0for Qwen3.5 MoE support (Qwen3_5MoeForConditionalGeneration).
import torch
from transformers import AutoProcessor
from transformers.models.qwen3_5_moe import Qwen3_5MoeForConditionalGeneration
model_id = "OpenMOSE/Qwen3.5-REAP-97B-A10B"
# default: Load the model on the available device(s)
model = Qwen3_5MoeForConditionalGeneration.from_pretrained(
model_id, dtype="auto", device_map="auto"#, use_cache = False
)
processor = AutoProcessor.from_pretrained(model_id)
messages = [
{
"role": "user",
"content": [
{
"type": "image",
"image": "https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/pipeline-cat-chonk.jpeg",
},
{"type": "text", "text": "Describe the image."},
],
}
]
# Preparation for inference
inputs = processor.apply_chat_template(
messages,
tokenize=True,
add_generation_prompt=True,
return_dict=True,
return_tensors="pt"
)
print(inputs)
# Inference: Generation of the output
generated_ids = model.generate(**inputs, max_new_tokens=256,do_sample=True,temperature=0.7, # ← 1.0より小さいほど保守的
top_p=0.9) # or top_k=50 など)
generated_ids_trimmed = [
out_ids[len(in_ids) :] for in_ids, out_ids in zip(inputs.input_ids, generated_ids)
]
output_text = processor.batch_decode(
generated_ids_trimmed, skip_special_tokens=True, clean_up_tokenization_spaces=False
)
print(output_text[0])
For text-only usage, omit the images= argument.
For 48 GB GPU + CPU offload configurations, GGUF quantized versions (e.g., Q4_K_M) are recommended. Example offload configuration:
./llama-cli -m qwen3.5-reap-97b-a10b.Q4_K_M.gguf \
--n-gpu-layers 38 \ # tune based on your VRAM
--ctx-size 8192
This release focuses on making the REAP-pruned model available for the community.
Quantitative benchmarks (e.g., MMLU, GSM8K, MMBench) are still work in progress.
Early qualitative checks show:
Community contributions with detailed benchmarks are very welcome.
Base model: Qwen/Qwen3.5-122B-A10B
Pruning method: REAP (Router-weighted Expert Activation Pruning)
Experts: 256 → 200 (22% pruned)
Calibration data: OpenMOSE/reap-calib-mix (mostly generated by Qwen3-235B-Instruct)
Post-processing:
Future versions may include post-pruning fine-tuning or knowledge distillation from the full 122B model to recover further performance.
Let's grow this model together as a community.
You are encouraged to:
Run benchmarks and publish results
Contribute scripts for:
Report issues or findings about failure modes, biases, or surprising behaviors
This architecture research and implementation was made possible with computing power and technical support from Recursal AI. We sincerely thank them for enabling this work.
2025 OpenMOSE