179 questions
No questions match those filters.
You've implemented a new architecture from a paper. It...
This is one of the questions in the full AI/ML interview bank. Pro unlocks all 1789 questions; Premium includes the same bank plus the highest daily Practice limit.
See plansThe reflex when a loss curve is flat is to start tuning — lower the learning rate, swap AdamW for SGD, double-check normalization — and that reflex treats a correctness problem as a performance problem. Traditional software fails loudly: a bug throws an exception, the program crashes, you get a stack trace pointing roughly at the cause. ML systems fail silently. A dataloader that’s accidentally shuffling labels, a detached tensor that quietly stops gradient flow, or a shape mismatch that broadcasts instead of raising an error will all let training run to completion without a single warning — the model simply never learns anything, and the loss curve is flat because nothing is actually being optimized.
Tuning hyperparameters on top of that is wasted effort in either direction: if the bug is real, no learning rate fixes it; if the model is somehow fine and the real issue is elsewhere, you’ve spent your debugging budget on the wrong layer.
The single-batch overfit test isolates correctness from everything else. Take one small batch — thirty-two examples is plenty — and strip out every regularizer: dropout to zero, weight decay to zero, augmentation off. Train on that one batch, repeatedly, for as many steps as it takes. An architecture that’s wired correctly should be capable of memorizing thirty-two examples; loss should collapse to essentially zero and training accuracy should hit 100%. If it can’t “cheat” its way to memorizing a handful of inputs, there’s a logic bug somewhere in the forward pass, the loss computation, or the gradient flow — and finding that bug is the actual next step, not a hyperparameter sweep.