Reading and reproducing ML papers
6.5.1· AI-ML › Research Frontiers & Practice
Structured Three-Pass Reading Method
Pass 1: 10-Minute Survey (Decision Pass)
Goal: Decide karo ki yeh paper tumhara time worth hai ya nahi.
Kya padhna hai (order mein):
- Title + Abstract → Main claim
- Introduction (pehle 2 paragraphs) → Problem aur motivation
- Section headings → Solution ki structure
- Conclusion → Unhone kya achieve kiya
- Figures & captions → Visual story
- References → Context (koi key citations pehchante ho?)
Output: In questions ka jawab do:
- Yeh kis category mein aata hai? (New architecture / Training technique / Theoretical result / Dataset / Application)
- Yeh kaun si problem solve karta hai?
- Kya claimed improvement mere kaam se relevant hai?
- Kya assumptions reasonable hain?
Pass 2: 1-Hour Deep Dive (Understanding Pass)
Goal: Reproduce kiye bina main contributions ko samjho.
Kaise padhna hai:
- Sequentially padho lekin proofs skip karo (abhi ke liye)
- Margins mein Annotate karo: "Yeh choice kyun?", "Agar hum X change kar dein toh?"
- Har figure/table ke liye:
- Caption padhne se pehle likho ki yeh kya claim karta hai
- Check karo ki tumhari interpretation match karti hai ya nahi
- Core innovation identify karo: Ek naya idea kya hai?
- Experimental setup details note karo: Dataset, baselines, hyperparameters
Key questions jinke jawab dhundho:
- Mathematical formulation: Inputs, outputs, loss function kya hain?
- Algorithmic innovation: Prior work se kya naya hai?
- Experimental evidence: Kya improvement statistically significant hai? Kya ablations convincing hain?
- Limitations: Kya kaam nahi karta? Unhone kya test nahi kiya?
Pass 3: 4-8 Hour Implementation (Reproduction Pass)
Goal: Core result ko scratch se reproduce karo.
Implementation checklist:
-
Environment Setup
- Paper ka framework note karo (TensorFlow/PyTorch/JAX)
- Dependencies, hardware list karo (GPU memory matter karta hai!)
- Official/unofficial repos reference ke liye dhundho (lekin abhi peek mat karo!)
-
Data Pipeline ⚠️ Yahaan sabse zyada bugs chhupi rehti hain
- Preprocessing steps (normalization, augmentation)
- Train/val/test splits (bilkul waise jaise paper describe karta hai)
- Batch size, shuffle, number of workers
-
Model Architecture
- Sabse chhote version se shuru karo (jaise ResNet-152 se pehle ResNet-18)
- Dimension mismatches pakadne ke liye har layer par shapes print karo
- Initialization scheme (Xavier, Kaiming, etc.)—papers often yeh omit kar deti hain!
-
Training Loop
- Learning rate schedule (step decay, cosine annealing?)
- Optimizer (Adam vs SGD—bahut bada farq hai!)
- Regularization (weight decay, dropout rates)
- Early stopping criteria
-
Verification Checkpoints
- Sanity check: Kya model 10 samples overfit kar sakta hai? (Agar nahi, toh loss/backprop mein bug hai)
- Baseline check: Kya yeh reported baseline performance match karta hai?
- Ablation check: Claimed innovation hatao—kya performance paper ke claim ke mutabiq girta hai?
Advanced Paper Reading Strategies
80/20 Focus Areas
Paper content ka 20% value ka 80% deta hai:
- Problem statement (Intro paragraph 1)
- Core mathematical formulation (Usually ek equation)
- Main results table (Numbers jo matter karte hain)
- Ablation study (Kya actually performance mein contribute karta hai)
Kya skim/skip karna hai:
- Related work (jab tak context ki zaroorat na ho)
- Lengthy proofs (sirf tabhi padho jab theorem core contribution ho)
- Excessive experimental details (jab tak reproduce na kar rahe ho)
Forecast-then-Verify Reading
Methods padhne se pehle: Pass 1 ke baad likho:
- "Agar main yeh problem solve karta, toh main try karta..."
- "Main challenge shayad yeh hai..."
- "Mera prediction hai ki solution mein yeh shaamil hoga..."
Phir methods padho: Apna forecast unke approach se compare karo.
- ✓ Match kiya? → Tum problem space ko achhi tarah samajhte ho
- ✗ Alag? → Seekho ki kyun unka approach behtar hai (ya nahi hai!)
Yeh researcher intuition build karta hai.
Paper Reading System Banana
Organizational structure:
papers/
├── to-read/ # Pass 1 triage
├── reading/ # Pass 2 in progress
├── implemented/ # Pass 3 completed with code
└── reference/ # Key papers for quick lookup
Annotation system:
- 🔴 Red: Samajh nahi aaya, dobara dekhna hai
- 🟡 Yellow: Core contribution
- 🟢 Green: Interesting extension idea
- 💡 Margin notes: "Kya yeh [meri problem] par apply ho sakta hai?"
Reading cadence:
- Daily: 1-2 Pass 1 reads (arxiv feed)
- Weekly: 2-3 Pass 2 reads (deep understanding)
- Monthly: 1 Pass 3 (full reproduction)
Irreproducible Papers se Deal Karna
Common blockers:
-
Missing hyperparameters
- Author ka GitHub code ke liye search karo
- Authors ko politely email karo: "Aapne [experiment] ke liye kaun sa learning rate use kiya?"
- Related papers se ranges try karo
-
Undisclosed dataset preprocessing
- Standard practices ke liye official dataset papers check karo
- Reported stats (mean/std) ko apni pipeline se compare karo
- Reported numbers mein off-by-one errors dhundho
-
Cherry-picked results
- Error bars, multiple seeds dhundho
- Agar "best of 10 runs" reported hai, toh suspicious raho
- Best ki jagah mean ± std reproduce karne ki koshish karo
-
Computational requirements
- Scale down: Chhota model variant use karo
- Paper ki techniques ko alag (chhote) dataset par use karo
- Absolute numbers ki jagah relative improvements reproduce karne par focus karo
Kab Chhodna hai vs. Lagey Rehna
Chhod do agar (2-3 solid attempts ke baad):
- Core idea poorly explained hai aur authors respond nahi karte
- Results bahut zyada achhe lagte hain aur koi aur replicate nahi kar pa raha
- Paper mein ablations nahi hain—tum contribution isolate nahi kar sakte
Lage raho agar:
- Core idea clear hai lekin implementation details missing hain (solvable!)
- Doosre researchers partial success report karte hain
- Failure tumhe problem domain ke baare mein kuch valuable sikhaati hai
Pivoting: Agar exact reproduction fail ho jaaye, try karo:
- Simpler/alag dataset par reproduce karo
- Core technique ko alag context mein implement karo
- "Attempted reproduction se lessons" blog post likho—yeh valuable hote hain!
Recall Explain Like I'm 12: ML Papers Padhna
Soch lo tumhe ek awesome spaceship ke liye LEGO instruction manual mila, lekin:
- Kuch pages missing hain
- Unhone special LEGO pieces use kiye jo tumhare paas nahi hain
- Unhone har ek step nahi dikhaya—unhone assume kiya ki tum basics jaante ho
Pass 1 = Dekhne ke liye flip karo ki yeh spaceship banane laayak cool hai ya nahi
Pass 2 = Dhyan se padhna, wings ke liye jo special technique unhone use ki wo samajhna
Pass 3 = Actually apne LEGO pieces se banao, missing steps figure out karo
Kabhi kabhi tum exact wahi spaceship nahi bana paate—lekin tum cool wing technique seekh jaate ho aur ise apne designs mein use karte ho. Yahi hai papers reproduce karna: Tum sabse smart builders se techniques seekh rahe ho, chahe unhe exactly copy na kar pao.
Kyun mushkil hai: Manual writers experts hain. Woh bhool jaate hain ki beginners cheezein nahi jaante. Woh kehte hain "stabilizer attach karo" lekin nahi batate kaun sa stabilizer ya kaise. Tumhe try karke figure out karna padta hai!
Connections
- Paper Writing and Publication ← Ulta process: reproducible papers banana
- Experiment Tracking and Versioning ← Reproduction attempts manage karne ke tools (MLflow, Weights & Biases)
- Hyperparameter Tuning ← Missing hyperparameters #1 reproduction blocker hai
- Statistical Significance Testing ← Evaluate karo ki reproduced results "match" karte hain ya nahi
- Model Debugging ← Techniques jab tumhara reproduction kaam na kare
- Transfer Learning ← ImageNet→YourTask papers ko reproduce karne ki understanding chahiye
- Attention Mechanisms ← Case study: highly-cited, heavily-reproduced architecture
#flashcards/ai-ml
Structured ML paper reading mein teen passes kya hain aur unka time commitment kya hai? :: Pass 1 (10 min): Relevance decide karne ke liye Survey | Pass 2 (1 ghanta): Samajhne ke liye Deep dive | Pass 3 (4-8 ghante): Code ke saath Full reproduction