endless-frontier/BigBang-v1 - qwen 3.5 finetunes

Reddit r/LocalLLaMA Models

Summary

A skeptical take on the BigBang-v1 finetune of Qwen 3.5, noting suspicious benchmark claims and potential test contamination despite Bartowski's GGUF conversion.

table bench https://huggingface.co/bartowski/endless-frontier_BigBang-v1-GGUF I'm downloading this model only because Bartowski converted it to .gguf, so it might be interesting. Doubts : The headline number is basically meaningless. "Performance between DeepSeek Flash (old one) and Pro" okay, on what? Did they average the benchmarks? Weight them? Pick and choose? Because if you actually look at the per-benchmark scores, this thing ranges from decent (50 on HLE) to straight up bad (15.7 on BioMystery-HD). Saying "aggregate performance" without showing the math is just... marketing. Like when a startup says "we're 10x faster" and it turns out they benchmarked one very specific edge case. A 35B model hanging with 284B–1.6T models? Suspicious as hell. Not impossible, but the first thing that jumps to mind is benchmark contamination. And here's the kicker, their whole training setup uses critics calibrated on "held-out real research tasks." So the question becomes: how do we know the eval benchmarks weren't basically in the training distribution? The paper kind of hand-waves this. If you're gonna claim a tiny model beats much bigger ones, you need to actually prove you're not just overfitting to the test set. Let's est it
Original Article

Similar Articles

endless-frontier/BigBang-v1

Hugging Face Models Trending

BigBang is a general-purpose LLM built from Qwen 3.6 35B-A3B via adversarial self-evolving synthetic data training, achieving frontier-level results on scientific research, coding, and reasoning benchmarks despite modest data scale.

Comparing Qwen3.8-27B fine-tunes and baselining vs. frontier

Reddit r/LocalLLaMA

A benchmarking write-up comparing multiple Qwen3.8-27B fine-tunes against frontier models like Opus 5.5 and Astra on a 469-question domain-specific eval, finding that a Q4_K_M quantization (Signal-3.8-27B-Terse-Coder) outperformed larger fine-tunes locally while remaining ~28x slower than frontier. The author also released the decoupled eval tool 'tuieval' on GitHub for reproducible, hardware-grounded comparisons.