Update README.md
Browse files
README.md
CHANGED
|
@@ -1,199 +1,107 @@
|
|
| 1 |
---
|
| 2 |
library_name: transformers
|
| 3 |
-
|
|
|
|
|
|
|
|
|
|
| 4 |
---
|
| 5 |
|
| 6 |
# Model Card for Model ID
|
| 7 |
|
| 8 |
-
|
| 9 |
-
|
| 10 |
-
|
| 11 |
-
|
| 12 |
-
|
| 13 |
-
|
| 14 |
-
|
| 15 |
-
|
| 16 |
-
|
| 17 |
-
|
| 18 |
-
|
| 19 |
-
|
| 20 |
-
-
|
| 21 |
-
-
|
| 22 |
-
-
|
| 23 |
-
|
| 24 |
-
|
| 25 |
-
|
| 26 |
-
|
| 27 |
-
|
| 28 |
-
### Model Sources [optional]
|
| 29 |
-
|
| 30 |
-
<!-- Provide the basic links for the model. -->
|
| 31 |
-
|
| 32 |
-
- **Repository:** [More Information Needed]
|
| 33 |
-
- **Paper [optional]:** [More Information Needed]
|
| 34 |
-
- **Demo [optional]:** [More Information Needed]
|
| 35 |
-
|
| 36 |
-
## Uses
|
| 37 |
-
|
| 38 |
-
<!-- Address questions around how the model is intended to be used, including the foreseeable users of the model and those affected by the model. -->
|
| 39 |
-
|
| 40 |
-
### Direct Use
|
| 41 |
-
|
| 42 |
-
<!-- This section is for the model use without fine-tuning or plugging into a larger ecosystem/app. -->
|
| 43 |
-
|
| 44 |
-
[More Information Needed]
|
| 45 |
-
|
| 46 |
-
### Downstream Use [optional]
|
| 47 |
-
|
| 48 |
-
<!-- This section is for the model use when fine-tuned for a task, or when plugged into a larger ecosystem/app -->
|
| 49 |
-
|
| 50 |
-
[More Information Needed]
|
| 51 |
-
|
| 52 |
-
### Out-of-Scope Use
|
| 53 |
-
|
| 54 |
-
<!-- This section addresses misuse, malicious use, and uses that the model will not work well for. -->
|
| 55 |
-
|
| 56 |
-
[More Information Needed]
|
| 57 |
-
|
| 58 |
-
## Bias, Risks, and Limitations
|
| 59 |
-
|
| 60 |
-
<!-- This section is meant to convey both technical and sociotechnical limitations. -->
|
| 61 |
-
|
| 62 |
-
[More Information Needed]
|
| 63 |
-
|
| 64 |
-
### Recommendations
|
| 65 |
-
|
| 66 |
-
<!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
|
| 67 |
-
|
| 68 |
-
Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations.
|
| 69 |
-
|
| 70 |
-
## How to Get Started with the Model
|
| 71 |
-
|
| 72 |
-
Use the code below to get started with the model.
|
| 73 |
-
|
| 74 |
-
[More Information Needed]
|
| 75 |
-
|
| 76 |
-
## Training Details
|
| 77 |
-
|
| 78 |
-
### Training Data
|
| 79 |
-
|
| 80 |
-
<!-- This should link to a Dataset Card, perhaps with a short stub of information on what the training data is all about as well as documentation related to data pre-processing or additional filtering. -->
|
| 81 |
-
|
| 82 |
-
[More Information Needed]
|
| 83 |
-
|
| 84 |
-
### Training Procedure
|
| 85 |
-
|
| 86 |
-
<!-- This relates heavily to the Technical Specifications. Content here should link to that section when it is relevant to the training procedure. -->
|
| 87 |
-
|
| 88 |
-
#### Preprocessing [optional]
|
| 89 |
-
|
| 90 |
-
[More Information Needed]
|
| 91 |
-
|
| 92 |
-
|
| 93 |
-
#### Training Hyperparameters
|
| 94 |
-
|
| 95 |
-
- **Training regime:** [More Information Needed] <!--fp32, fp16 mixed precision, bf16 mixed precision, bf16 non-mixed precision, fp16 non-mixed precision, fp8 mixed precision -->
|
| 96 |
-
|
| 97 |
-
#### Speeds, Sizes, Times [optional]
|
| 98 |
-
|
| 99 |
-
<!-- This section provides information about throughput, start/end time, checkpoint size if relevant, etc. -->
|
| 100 |
-
|
| 101 |
-
[More Information Needed]
|
| 102 |
-
|
| 103 |
-
## Evaluation
|
| 104 |
-
|
| 105 |
-
<!-- This section describes the evaluation protocols and provides the results. -->
|
| 106 |
-
|
| 107 |
-
### Testing Data, Factors & Metrics
|
| 108 |
-
|
| 109 |
-
#### Testing Data
|
| 110 |
-
|
| 111 |
-
<!-- This should link to a Dataset Card if possible. -->
|
| 112 |
-
|
| 113 |
-
[More Information Needed]
|
| 114 |
-
|
| 115 |
-
#### Factors
|
| 116 |
-
|
| 117 |
-
<!-- These are the things the evaluation is disaggregating by, e.g., subpopulations or domains. -->
|
| 118 |
-
|
| 119 |
-
[More Information Needed]
|
| 120 |
-
|
| 121 |
-
#### Metrics
|
| 122 |
-
|
| 123 |
-
<!-- These are the evaluation metrics being used, ideally with a description of why. -->
|
| 124 |
-
|
| 125 |
-
[More Information Needed]
|
| 126 |
-
|
| 127 |
-
### Results
|
| 128 |
-
|
| 129 |
-
[More Information Needed]
|
| 130 |
-
|
| 131 |
-
#### Summary
|
| 132 |
-
|
| 133 |
-
|
| 134 |
-
|
| 135 |
-
## Model Examination [optional]
|
| 136 |
-
|
| 137 |
-
<!-- Relevant interpretability work for the model goes here -->
|
| 138 |
-
|
| 139 |
-
[More Information Needed]
|
| 140 |
-
|
| 141 |
-
## Environmental Impact
|
| 142 |
-
|
| 143 |
-
<!-- Total emissions (in grams of CO2eq) and additional considerations, such as electricity usage, go here. Edit the suggested text below accordingly -->
|
| 144 |
-
|
| 145 |
-
Carbon emissions can be estimated using the [Machine Learning Impact calculator](https://mlco2.github.io/impact#compute) presented in [Lacoste et al. (2019)](https://arxiv.org/abs/1910.09700).
|
| 146 |
-
|
| 147 |
-
- **Hardware Type:** [More Information Needed]
|
| 148 |
-
- **Hours used:** [More Information Needed]
|
| 149 |
-
- **Cloud Provider:** [More Information Needed]
|
| 150 |
-
- **Compute Region:** [More Information Needed]
|
| 151 |
-
- **Carbon Emitted:** [More Information Needed]
|
| 152 |
-
|
| 153 |
-
## Technical Specifications [optional]
|
| 154 |
|
| 155 |
-
#
|
| 156 |
|
| 157 |
-
|
|
|
|
| 158 |
|
| 159 |
-
|
| 160 |
|
| 161 |
-
|
| 162 |
|
| 163 |
-
###
|
|
|
|
| 164 |
|
| 165 |
-
|
|
|
|
|
|
|
|
|
|
| 166 |
|
| 167 |
-
###
|
|
|
|
|
|
|
|
|
|
|
|
|
| 168 |
|
| 169 |
-
|
| 170 |
|
| 171 |
-
|
| 172 |
|
| 173 |
-
|
|
|
|
|
|
|
|
|
|
| 174 |
|
| 175 |
-
|
|
|
|
|
|
|
|
|
|
| 176 |
|
| 177 |
-
|
| 178 |
|
| 179 |
-
|
|
|
|
|
|
|
|
|
|
| 180 |
|
| 181 |
-
|
| 182 |
|
| 183 |
-
|
|
|
|
|
|
|
| 184 |
|
| 185 |
-
|
| 186 |
|
| 187 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 188 |
|
| 189 |
-
#
|
|
|
|
|
|
|
| 190 |
|
| 191 |
-
|
|
|
|
|
|
|
|
|
|
| 192 |
|
| 193 |
-
|
|
|
|
| 194 |
|
| 195 |
-
|
| 196 |
|
| 197 |
-
|
| 198 |
|
| 199 |
-
|
|
|
|
| 1 |
---
|
| 2 |
library_name: transformers
|
| 3 |
+
license: apache-2.0
|
| 4 |
+
language:
|
| 5 |
+
- en
|
| 6 |
+
- es
|
| 7 |
---
|
| 8 |
|
| 9 |
# Model Card for Model ID
|
| 10 |
|
| 11 |
+
---
|
| 12 |
+
language:
|
| 13 |
+
- en
|
| 14 |
+
- es
|
| 15 |
+
license: apache-2.0
|
| 16 |
+
tags:
|
| 17 |
+
- moe
|
| 18 |
+
- gpt-oss
|
| 19 |
+
- model-compression
|
| 20 |
+
- pruning
|
| 21 |
+
- mixture-of-experts
|
| 22 |
+
- optimization
|
| 23 |
+
- math
|
| 24 |
+
- code
|
| 25 |
+
- logic
|
| 26 |
+
model_name: Scal-lite-60b-code-math
|
| 27 |
+
base_model: openai/gpt-oss-120b
|
| 28 |
+
inference: true
|
| 29 |
+
pipeline_tag: text-generation
|
| 30 |
+
---
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 31 |
|
| 32 |
+
# Scal-lite-60b-code-math
|
| 33 |
|
| 34 |
+
## Model Summary
|
| 35 |
+
**Scal-lite-60b-code-math** is a highly efficient, structurally pruned version of the `gpt-oss-120b` Mixture of Experts (MoE) model. Through **Activation-Guided Structural Pruning**, the model was reduced from 128 to 64 experts, resulting in a 60-billion total parameter architecture (~5.1B active parameters per token).
|
| 36 |
|
| 37 |
+
Unlike standard magnitude-based pruning, this model preserves critical specialized knowledge in low-frequency domains, such as **Spanish language proficiency**, **advanced LaTeX mathematics**, and **strict JSON/Python code generation**.
|
| 38 |
|
| 39 |
+
## Technical Methodology: "The Surgery"
|
| 40 |
|
| 41 |
+
### 1. Activation-Guided Sparsity
|
| 42 |
+
Conventional magnitude pruning (L2 norm) often fails in MoE models because specialized skills (like non-English languages or specific code syntaxes) are often mapped to experts with smaller weight magnitudes.
|
| 43 |
|
| 44 |
+
To prevent "functional lobotomy," we implemented **Activation-Guided Pruning**:
|
| 45 |
+
- **Forward Hooks:** Monitored `mlp.router` activity during stress tests.
|
| 46 |
+
- **Utility Ranking:** Identified hyper-specialized experts (e.g., Expert #13) essential for Spanish logic and strict syntax.
|
| 47 |
+
- **Amputation:** Removed the 64 statistically least-used experts per layer based on real-world utility rather than static weight size.
|
| 48 |
|
| 49 |
+
### 2. Targeted Router Healing
|
| 50 |
+
Post-pruning, the original routing network suffers from "Router Trauma" or probability misalignment. To fix this, we applied a lightweight **Targeted Router Healing** process:
|
| 51 |
+
- **Frozen Experts:** Core knowledge weights remained untouched.
|
| 52 |
+
- **Trainable Router:** Fine-tuned only the gating network for 3,000 steps using the `MetaMathQA` dataset.
|
| 53 |
+
- **Result:** Successfully recalibrated the model's internal navigation to access its latent reasoning capabilities.
|
| 54 |
|
| 55 |
+
## Benchmarks & Evaluation
|
| 56 |
|
| 57 |
+
The optimization process not only halved the VRAM requirements but also restored benchmark performance to state-of-the-art levels for its size class.
|
| 58 |
|
| 59 |
+
| Benchmark | Scal-lite-60b (Pre-Healing) | Scal-lite-60b (Post-Healing) |
|
| 60 |
+
|-----------|-----------------------------|------------------------------|
|
| 61 |
+
| **GSM8K (Math)** | 17.59% | **72.48%** |
|
| 62 |
+
| **Hellaswag (Common Sense)** | 34.23% | **47.35%** |
|
| 63 |
|
| 64 |
+
### Real-World Validation: The Kaggle Challenge
|
| 65 |
+
Tested on a private set of 50 complex algorithmic programming problems:
|
| 66 |
+
- **Original Hypernova (Baseline):** 9/50 solved.
|
| 67 |
+
- **Scal-lite-60b-code-math:** **36/50 solved** (when equipped with Python execution tool-use).
|
| 68 |
|
| 69 |
+
## Hardware Requirements & Deployment
|
| 70 |
|
| 71 |
+
This model is designed to bridge the gap between massive MoEs and accessible hardware.
|
| 72 |
+
- **Precision (BF16):** ~120 GB VRAM (Recommended: 2x A100 80GB or 4x L40S).
|
| 73 |
+
- **Quantization (MXFP4):** ~60-65 GB VRAM (Compatible with NVIDIA Blackwell/Hopper architectures).
|
| 74 |
+
- **Efficiency:** Significant performance-per-watt gains over the original 120B version.
|
| 75 |
|
| 76 |
+
## Usage (Transformers)
|
| 77 |
|
| 78 |
+
```python
|
| 79 |
+
from transformers import AutoModelForCausalLM, AutoTokenizer
|
| 80 |
+
import torch
|
| 81 |
|
| 82 |
+
model_id = "your-username/Scal-lite-60b-code-math"
|
| 83 |
|
| 84 |
+
tokenizer = AutoTokenizer.from_pretrained(model_id)
|
| 85 |
+
model = AutoModelForCausalLM.from_pretrained(
|
| 86 |
+
model_id,
|
| 87 |
+
torch_dtype=torch.bfloat16,
|
| 88 |
+
device_map="auto"
|
| 89 |
+
)
|
| 90 |
|
| 91 |
+
# Example: Reasoning in Spanish
|
| 92 |
+
prompt = "Resuelve el siguiente problema: Si una red MoE tiene 128 expertos y podamos el 50%, ¿cuántos expertos quedan y cómo afecta esto a la VRAM?"
|
| 93 |
+
inputs = tokenizer(prompt, return_tensors="pt").to("cuda")
|
| 94 |
|
| 95 |
+
output = model.generate(**inputs, max_new_tokens=256)
|
| 96 |
+
print(tokenizer.decode(output[0], skip_special_tokens=True))
|
| 97 |
+
Limitations
|
| 98 |
+
While Activation-Guided Pruning significantly preserves bilingual skills, some edge-case linguistic nuances may show degradation compared to the 120B original. Users are encouraged to apply context-specific system prompts for best results in non-English languages.
|
| 99 |
|
| 100 |
+
Citation & References
|
| 101 |
+
If you use this model or its pruning methodology, please cite:
|
| 102 |
|
| 103 |
+
Structural Pruning and Optimization in Mixture of Experts (MoE) Models: An Applied Analysis to GPT-OSS-120B.
|
| 104 |
|
| 105 |
+
OpenAI (2025). gpt-oss: Open-Weight Models for Advanced Reasoning.
|
| 106 |
|
| 107 |
+
ICLR Proceedings. "Mixture Compressor for Mixture-of-Experts LLMs Gains More."
|