RenShiPDev/LFM2.5-1.2B-Thinking-LeetCode-QLoRA
049
LFM2.5-1.2B-Thinking + LeetCode (QLoRA)
Early-stage reasoning fine-tune (500 steps). A LoRA adapter for `LiquidAI/LFM2.5-1.2B-Thinking`, trained on `greengerong/leetcode` to study whether algorithmic/code data transfers into better logical reasoning on a small (1.2B) model.
This is not a production model and not a "better everywhere" upgrade. It is a transparent research checkpoint with a clear trade-off: improved reasoning (ARC, MMLU) at the cost of some world-knowledge recall (CommonsenseQA, OpenBookQA).
๐งช Training Details
Training dynamics
- Train loss: 2.09 โ 0.80; final eval loss 0.83.
- ~15.95M input tokens seen over 500 steps.
Note. batch_size = 1 (with ร4 accumulation) is a low-resource setting that introduces gradient noise; the results below reflect that. This checkpoint is an early exploration, not a fully converged model.๐ Benchmark Results (LoRA vs. base model)
Interpretation
- Positive transfer. Large gains on ARC-Easy (+11.87 pp) and MMLU (+5.45 pp) suggest the model internalized stronger reasoning patterns from the code data โ reasoning generalized beyond code.
- Trade-off / catastrophic forgetting. Drops on CommonsenseQA (-6.96 pp) and OpenBookQA (-3.20 pp) are a classic symptom of a small model overwriting world knowledge with algorithmic patterns.
๐จ Benchmark Transparency (data-leakage warning)
The training dataset greengerong/leetcode contains coding problems. Benchmarks such as HumanEval or MBPP may contain problems that are similar or identical to those in the training set.
Therefore the +1.83% on HumanEval should be read as task adaptation, not as a fair zero-shot generalization score against models that never saw this data. For an honest assessment, evaluate this adapter on completely unseen, custom tests.
โ ๏ธ Limitations
- Not for fact/knowledge retrieval. The adapter is measurably worse than the base model on open-book and commonsense tasks.
- Not a general code assistant. Only a modest HumanEval gain; the base model is not code-specialized.
- Early checkpoint. 500 steps is a small budget; results are exploratory.
- Data-leakage caveat applies to any code benchmark (see above).
