Downloads · 30 days
10
8% of all-time downloads
AmanPriyanshu/gpt-oss-11.4b-specialized-math-pruned-moe-only-16-experts
gpt-oss-11.4b-specialized-math-pruned-moe-only-16-experts is a text generation model from AmanPriyanshu. Use it when you need the model to write or continue text. The card lists the license as apache-2.0.
Project: https://amanpriyanshu.github.io/GPT-OSS-MoE-ExpertFingerprinting/
Downloads · 30 days
10
8% of all-time downloads
All-time downloads
132
Public
Parameters
11.4B
22.7 GB on disk
Likes
1
Public
Click a slice to open those files.
.safetensors22.7 GB · 100%
From the Hugging Face model README
Project: https://amanpriyanshu.github.io/GPT-OSS-MoE-ExpertFingerprinting/
<div align="center">This is a pruned variant of OpenAI's GPT-OSS-20B model, reduced to 16 experts per layer based on activation patterns from the AmanPriyanshu/GPT-OSS-20B MoE Expert Activations dataset. We analyzed router decisions across evaluation benchmarks to identify and retain experts most relevant for math tasks.
⚠️ Experimental Model: This is an experimental pruned model that may not work well - check the examples below to see if the outputs meet your needs before use.
This pruning approach reduces the model size while attempting to preserve performance on the target domain.
| Metric | Value |
|---|---|
| Base Model | openai/gpt-oss-20b |
| Architecture | Mixture-of-Experts Transformer |
| Total Parameters | ~11.4B (pruned from 21B) |
| Original Experts per Layer | 32 |
| Pruned Experts per Layer | 16 |
| Layers | 24 |
| Top-k Routing | 4 |
| Context Length | 128K tokens |
| Attention Heads | 64 (Query), 8 (Key-Value) |
| Residual Dimension | 2880 |
| Attention Pattern | Alternating dense & sliding window (128 tokens) |
| Positional Encoding | RoPE (Rotary Position Embedding) |
| Normalization | RMSNorm |
| Precision | BF16 |
| License | Apache 2.0 |
| Specialization | Math |
Mixture-of-Experts models contain multiple specialized sub-networks (experts) per layer. During inference, only a subset of experts are activated for each token. Expert pruning involves:
Note: Performance may vary depending on how well the pruned experts match your specific use case.
This mathematics-focused model utilizes experts that exhibited strong performance on mathematical reasoning tasks from MMLU mathematics subjects and quantitative sections. These experts excel at mathematical computation, proof strategies, and logical reasoning.
The expert selection process utilized our comprehensive analysis of router activation patterns across multiple evaluation benchmarks:
By identifying experts that consistently activated for math tasks, we created this specialized model that maintains domain expertise while significantly reducing computational requirements from 32 to 16 experts per layer.
This model is based on analysis from the GPT-OSS-20B MoE Expert Activations dataset available at: 🔗 https://huggingface.co/datasets/AmanPriyanshu/GPT-OSS-20B-MoE-expert-activations
The dataset contains router activation patterns from OpenAI's GPT-OSS-20B model across diverse evaluation benchmarks, enabling the creation of these domain-optimized models through systematic expert pruning.
Our approach involves:
This is a direct pruning approach - no additional training was performed. The model inherits all capabilities from the original GPT-OSS-20B with focused expert selection.
from transformers import AutoModelForCausalLM, AutoTokenizer
import torch
# Load the specialized model on CPU
model = AutoModelForCausalLM.from_pretrained(
"AmanPriyanshu/gpt-oss-11.4b-specialized-math-pruned-moe-only-16-experts",
torch_dtype=torch.bfloat16,
device_map="cpu",
trust_remote_code=True
)
tokenizer = AutoTokenizer.from_pretrained("AmanPriyanshu/gpt-oss-11.4b-specialized-math-pruned-moe-only-16-experts")
# Generate with the model
messages = [
{"role": "user", "content": "Solve this equation: 2x + 5 = 17. Show your work step by step."}
]
inputs = tokenizer.apply_chat_template(
messages,
add_generation_prompt=True,
return_tensors="pt",
return_dict=True,
reasoning_effort="medium"
)
# Ensure inputs are on the same device as model
inputs = {k: v.to(model.device) for k, v in inputs.items()}
outputs = model.generate(
**inputs,
max_new_tokens=512,
do_sample=True,
temperature=0.1,
top_p=0.9,
pad_token_id=tokenizer.eos_token_id,
eos_token_id=tokenizer.eos_token_id
)
# Decode only the generated part
input_length = inputs['input_ids'].shape[1]
response_tokens = outputs[0][input_length:]
response = tokenizer.decode(response_tokens, skip_special_tokens=True)
print(response)
from transformers import AutoModelForCausalLM, AutoTokenizer
import torch
# Check MPS availability and load model
device = "mps" if torch.backends.mps.is_available() else "cpu"
model = AutoModelForCausalLM.from_pretrained(
"AmanPriyanshu/gpt-oss-11.4b-specialized-math-pruned-moe-only-16-experts",
torch_dtype=torch.float16, # Better MPS compatibility
device_map=device,
trust_remote_code=True,
low_cpu_mem_usage=True
)
tokenizer = AutoTokenizer.from_pretrained("AmanPriyanshu/gpt-oss-11.4b-specialized-math-pruned-moe-only-16-experts")
# Generate with the model
messages = [
{"role": "user", "content": "Solve this equation: 2x + 5 = 17. Show your work step by step."}
]
inputs = tokenizer.apply_chat_template(
messages,
add_generation_prompt=True,
return_tensors="pt",
return_dict=True,
reasoning_effort="medium"
)
# Move inputs to model device
inputs = {k: v.to(model.device) if isinstance(v, torch.Tensor) else v for k, v in inputs.items()}
# Use torch.no_grad for MPS stability
with torch.no_grad():
outputs = model.generate(
**inputs,
max_new_tokens=512,
do_sample=True,
temperature=0.1,
top_p=0.9,
pad_token_id=tokenizer.eos_token_id,
eos_token_id=tokenizer.eos_token_id,
use_cache=True
)
# Decode only the generated part
input_length = inputs['input_ids'].shape[1]
response_tokens = outputs[0][input_length:]
response = tokenizer.decode(response_tokens, skip_special_tokens=True)
print(response)
For CUDA GPU inference, the models work with minimal modifications from the CPU example above. Simply change:
device_map="auto" # Will automatically use GPU if available
torch_dtype=torch.bfloat16 # or torch.float16
The following examples demonstrate the model's performance on math tasks:
Question: Solve this equation: 2x + 5 = 17. Show your work step by step.
Response:
<|channel|>analysis<|message|>We need to solve 2x+5=17. Show step-by-step.<|end|><|start|>assistant<|channel|>final<|message|>**Equation to solve**
\[
2x + 5 = 17
\]
---
### Step 1: Isolate the variable term
Subtract 5 from both sides to get the variable term alone on the left.
\[
2x + 5 - 5 = 17 - 5
\]
\[
2x = 12
\]
---
### Step 2: Solve for \(x\)
Divide both sides by 2 (the coefficient of \(x\)).
\[
\frac{2x}{2} = \frac{12}{2}
\]
\[
x = 6
\]
---
### Result
\[
\boxed{x = 6}
\]
**Check**:
Plug \(x = 6\) back into the original equation:
\[
2(6) + 5 = 12 + 5 = 17
\]
It satisfies the equation, so the solution is correct.<|return|>
Question: What is the Pythagorean theorem and how is it used?
Response:
<|channel|>analysis<|message|>Need explain theorem, formula, usage.<|end|><|start|>assistant<|channel|>final<|message|>## The Pythagorean Theorem
### 1. Statement of the Theorem
In a right‑angled triangle (a triangle with one 90° angle), the relationship between the lengths of the two legs (the sides that form the right angle) and the hypotenuse (the side opposite the right angle) is:
\[
\boxed{a^{2} + b^{2} = c^{2}}
\]
- **\(a\)** and **\(b\)** are the lengths of the two shorter sides (the legs).
- **\(c\)** is the length of the longest side (the hypotenuse).
This equation says that the sum of the squares of the legs equals the square of the hypotenuse.
---
### 2. Why It’s Called “Pythagorean”
The theorem is named after the ancient Greek mathematician **Pythagoras of Alexandria** (c. 570–495 BC), who first proved the relationship in the *Book of the Elements* (circa 300 BC). It is one of the most fundamental results in Euclidean geometry.
---
## How the Theorem Is Used
| Application | What You Do | Example |
|-------------|-------------|---------|
| **Finding a side of a triangle** | Rearsolve the equation for the missing side | In a right triangle with legs 3 m and 4 m, find the hypotenuse: \(c = \sqrt{3^{2}+4^{2}} = 5\) m. |
| **Checking if a triangle is right‑angled** | Verify if \(a^{2}+b^{2}=c^{2}\) holds | For sides 6, 8, 10: \(6^{2}+8^{2}=36+64=100=10^{2}\) → right triangle. |
| **Geometry & Engineering** | Compute distances, angles, or design shapes (e.g., building a bridge, laying a road, or designing a 3‑D shape). | In civil engineering, the Pythagorean theorem helps calculate the length of a side of a rectangular bridge segment. |
| **Physics & Kinematics** | Relate velocity, acceleration, and time in right‑angled motion (e.g., projectile motion). | For a projectile moving horizontally 5 m and vertically 12 m, the
Question: Calculate the area of a circle with radius 7 meters.
Response:
<|channel|>analysis<|message|>Need area = π r^2 = π*49 = 49π ≈ 153.938.<|end|><|start|>assistant<|channel|>final<|message|>The area \(A\) of a circle is given by
\[
A = \pi r^{2}
\]
where \(r\) is the radius.
For a radius of \(7\) m:
\[
A = \pi (7\,\text{m})^{2}
= \pi \times 49\,\text{m}^{2}
= 49\pi \,\text{m}^{2}
\]
Numerically (using \(\pi \approx 3.14159\)):
\[
A \approx 49 \times 3.14159 \,\text{m}^{2}
\approx 153.94 \,\text{m}^{2}
\]
So the area of the circle is **\(49\pi\) square meters**, or about **\(154\) m²**.<|return|>
If you use this model in your research, please cite:
@misc{priyanshu2025gptoss,
title={{GPT-OSS MoE Expert Fingerprinting: Analyzing Expert Activation Patterns in Mixture of Experts Models}},
author={Priyanshu, Aman and Vijay, Supriti},
year={2025},
howpublished={\url{https://amanpriyanshu.github.io/GPT-OSS-MoE-ExpertFingerprinting/}},
note={Interactive analysis tool for expert activation patterns in MoE architectures}
}