Mohamed (@mohammad2012191) header
Mohamed (@mohammad2012191) profile picture

وماذا عليك لو ذهبوا هُم بالدنيا، وأنتَ ذهبت بالقرآن؟ | AI Researcher @ KAUST - Kaggle Competitions Master (Highest Rank: 236th in the World)

Joined October 2013
Photo by Mohamed (@mohammad2012191)Photo by Mohamed (@mohammad2012191)Photo by Mohamed (@mohammad2012191)Photo by Mohamed (@mohammad2012191)Photo by Mohamed (@mohammad2012191)Photo by Mohamed (@mohammad2012191)Photo by Mohamed (@mohammad2012191)Photo by Mohamed (@mohammad2012191)Photo by Mohamed (@mohammad2012191)Photo by Mohamed (@mohammad2012191)
Jev is used to pick one option. Let’s see how far we can squeeze it.
2
1
20
1,363
Mohamed retweeted
Hi all, I have a new result I'm excited to share. It turns out that *all existing implementations* of softmax and cross-entropy (that's JAX, PyTorch, textbooks, etc) have a subtle bug --- two bugs, actually. A simple rewrite fixes both, and eliminates "slingshots" when grokking:
135
793
152
6,553
821,920
1/9 Current optimizers are static during training. What if the optimizer could think and react while the network trains? We let an agent watch the training dynamics and rewrite the optimizer's source code as training goes: a reactive optimizer. In every language and image setting we tried that has no tuned recipe, it matches or beats the best recipe one can one-shot, and it guards against loss spikes and overfitting by itself. In the near future, optimization decisions may belong to agents, not humans. 📝 xingjianbai.com/reactive-opt… 💻 Try it on your task: github.com/xingjian-bai/opal 🧵
75
199
66
1,537
213,374
قبل سنة تقريباً نشرت AI Specialization Roadmap عن أساسيات الـAI، واليوم أنشر الجزء الثاني: المهارات اللي تساعدك تنتقل من الأساسيات للـindustry. أتمنى تنال إعجابكم :) mohammad2012191.github.io/AI…
4
23
268
11,799
1/ During OLMo3-32B pre-training, accuracy on an arithmetic diagnostic hits 81% at 2.17T tokens, collapses to 0% at 2.19T, and jumps back to 81.7% at 2.21T. All while validation loss decreases smoothly. The phenomenon: mode-hopping. 🧵
6
34
5
231
16,049
Let's make KV cache great again :) What if you could run your LLM on almost arbitrarily long text without caring about the KV cache, and still match a full read? ⬇️ New preprint: Periscope: Extending Frozen Language Models Beyond Their Context Window 🔴 tl;dr: a new training-free inference method that relies on short local and strided reads to approximate the global context. A frozen model served at a window of W tokens can now read texts of W²/c tokens (e.g., a 27B model reads 4.5M tokens on one 80GB GPU) with the KV cache size of only a few chunks, at accuracy comparable to reading everything. (image: results on LongBench v2)
1
9
1
39
2,890
🔵What this means: memory for a long read is set by the model's weights, not by the text. A model that fits your GPU can read texts that GPU could never cache in one pass. 🔵That could unlock serving small models at far longer context on cards that today stop at the window.
1
1
164
When a benchmark saturates, we write a harder one: MMLU → MMLU-Pro, MMMU → MMMU-Pro. What if the harder benchmark was already sitting inside the old one? 🤔 🔴New preprint: Your Benchmark Is Not Saturated: Reviving Multiple-Choice Evaluation with Answer Pooling ➡️tl;dr: We introduce Answer Pooling, a label-free way to make multiple-choice benchmarks harder with zero human intervention. Take questions that share a context, pool all their options into one list, and ask the model to match every question to its answer.
2
21
1,134
Hmm, but Mohamed, maybe pooling is just an unfamiliar format? 🤔 No 🎯 Same prompt, same pool size, but every wrong option swapped for an unrelated answer: ➡️ QuALITY: MCQ 76% → this control 84% → real pool 60% ➡️The format costs nothing. The drop comes from the newly-added plausible wrong options. 🔵 A saturated benchmark still holds a harder task in the labels it already ships.
1
190