Worked examples — Backpropagation — chain rule, gradient computation
5.6.8 · D3· Coding › Machine Learning (Aerospace Applications) › Backpropagation — chain rule, gradient computation
Scenario matrix
Kuch bhi work karne se pehle, chalte hain har alag situation list karein jo backprop problem mein ho sakti hai. Har row ek "case class" hai; neeche har worked example us cell ke saath tagged hai jo wo cover karta hai.
| # | Case class | Kya khaas hai | Covered by |
|---|---|---|---|
| A | Linear output, positive slope | ReLU with , — the "clean" case | Ex 1 |
| B | Dead ReLU () | — unit zero error backward pass karta hai | Ex 2 |
| C | Sigmoid, mid-range | ek fraction hai — error shrink karta hai | Ex 3 |
| D | Saturated sigmoid | — vanishing-gradient failure | Ex 4 |
| E | Fan-in node (weight do paths ko feed karta hai) | paths par sum karna padta hai (multivariable rule) | Ex 5 |
| F | Zero / degenerate input ( ya ) | weight gradient ho jaata hai | Ex 6 |
| G | Sign bookkeeping ( vs ) | error signal ka sign badalta hai, aur saath mein har gradient ka bhi | Ex 7 |
| H | Real-world word problem (aerospace surrogate) | physics → net → gradient translate karo | Ex 8 |
| I | Exam twist (shared weight / weight tying) | ek weight do baar use hota hai ⇒ gradients add hote hain | Ex 9 |
Hum poore time yahi chhota network reuse karenge jab tak kuch aur na kaha jaaye:
Yahan input number hai, weights hain (multipliers), biases hain (offsets), activation function hai (per-unit nonlinear bend), network ki guess hai, true target hai, aur loss hai (kitna galat hain hum). Neeche ki picture wo map hai jis par hum backward chalte hain.

Ex 1 — Case A: linear/ReLU, positive slope (clean baseline)
Forecast: Padhne se pehle dono gradients ka sign guess karo. (Hint: target ko overshoot karega, toh hum expect karte hain positive gradients jo weights ko neeche push karein.)
- Forward, sab kuch cache karo. ; kyunki hai, ; ; ; . Yeh step kyun? Backward slopes () aur inputs () inhi cached numbers se padte hain — recompute karna time waste hai.
- Seed. . Kyun? .
- Layer 2. (output linear hai, slope ). Phir . Kyun? weight gradient = error out × signal in.
- Nonlinearity cross karo. . Kyun? error ke through backward flow karta hai (), phir local slope se scale hota hai.
- Layer 1. .
Verify: ko bump karo: , , toh ✓. Dono gradients positive jaise forecast kiya tha — gradient descent inhe subtract karega, weights ko better fit ki taraf le jaayega.
Ex 2 — Case B: Dead ReLU (error ek wall se takraata hai)
Forecast: Kya ko koi bhi gradient milega?
- Forward. . Kyunki hai, . Yeh kyun note karein? ReLU switch off ho gaya — uska output par stuck hai.
- Local slope. kyunki ke liye ReLU graph flat hai. Kyun matter karta hai: flat function ka derivative zero hota hai — ko nudge karna par kuch nahi karta.
- Backward. , isliye . Kyun? factor error ko annihilate kar deta hai — tak koi signal nahi pahunchta.
Verify: ko bump karo: moves to (abhi bhi hai), toh par rehta hai, par rehta hai, unchanged ✓.

Ex 3 — Case C: sigmoid mid-range (error ek fraction se shrink karta hai)
Forecast: par sigmoid apni steepest point par hai. Woh maximum slope kya hai?
- Forward. ; ; ; . Kyun? Slope evaluate karne ke liye hume chahiye.
- Local slope. . Yeh tool (product ) kyun? Sigmoid ki derivative ko uske apne output se likha ja sakta hai, isliye ek baar cache ho jaaye toh slope free mein milta hai — yeh ek badi wajah thi jab sigmoids popular the.
- Seed & backward. ; ; phir . Kyun? aata hua error , slope se quarter tak throttle ho jaata hai.
Verify: . ke around finite-difference karo: bump karo, change hota hai ✓. Note karo kabhi se zyada nahi hoti — har sigmoid layer error ko kam se kam shrink karti hai.
Ex 4 — Case D: saturated sigmoid (vanishing gradient)
Forecast: Bada matlab — kya slope bada hai ya tiny?
- Forward. . Kyun? Slope compute karne ke liye output chahiye.
- Slope. . Kyun matter karta hai: S-curve origin se door flat hai — unit saturated hai.
- Backward. Chahe koi bhi error aaye, , ke factor se crush ho jaata hai. Kyun? Aisi kuch layers stack karo aur tiny slopes ka product — gradients vanish ho jaate hain.
Verify: ✓. Ex 3 ke se compare karo: same function, sirf bade se kamzor gradient. Yehi wajah hai kyun ReLU ne deep nets mein sigmoids replace kiye — dekho Vanishing Gradients.
Ex 5 — Case E: fan-in node (paths par sum)
Forecast: ko do wires ( aur ) se influence karta hai. Kya hum ek choose karein ya add karein?
- Forward. ; ; ; ; .
- Seed & split. . Kyunki hai: , . Kyun? , .
- Fan-in par multivariable chain rule. tak aur ke zariye pahunchta hai, isliye hum do path contributions ko sum karte hain: Sum kyun, choose kyun nahi? Har path independent sensitivity carry karta hai; total sensitivity unka sum hai — yeh hai graph fan-in rule.
- Input tak. .
Verify: Note karo hai, toh hai, aur at ✓ — closed form summed backprop ko confirm karta hai.

Ex 6 — Case F: zero / degenerate input (gradient collapse)
Forecast: Agar input zero hai, toh kya phir bhi seekhega?
- Forward. ; (ReLU, ); ; ; .
- par backward error. ; .
- Weight vs bias gradient. Split kyun? ka gradient error × uska input hai, aur uska input hai — toh ko koi update nahi milta. Bias ka "input" constant hai, isliye woh abhi bhi seekhta hai.
Verify: bump karo: se independent hai, toh kabhi nahi badlega ✓. ko bump karo: badhta hai, badhta hai, toh ✓.
Ex 7 — Case G: sign bookkeeping (undershoot vs overshoot)
Forecast: Ex 1 mein guess too high thi; yahan too low hai. Kaunsa flip hoga?
- Forward. Ex 1 jaisa hi: , , lekin ab .
- Seed ka sign badalta hai. . Kyun? Error signal hai hi ; undershoot karna ise negative banata hai.
- Propagate. ; . Flip kyun? Gradient descent gradient subtract karta hai: negative gradient matlab "increase " — exactly sahi, kyunki too small hai.
Verify: , Ex 1 ke ka negation ✓. Finite difference: ko bump karo, , , slope ✓. Seed ka sign har downstream gradient ka sign set karta hai.
Ex 8 — Case H: aerospace word problem (ek lift surrogate)
Forecast: Kya model lift over- ya under-predict kar raha hai, aur upar jaayega ya neeche?
- Forward. ; ReLU ; . Kyun? Prediction evaluate karna padega pehle, tab hi error measure ho sakta hai.
- Seed. (hum lift underpredict kar rahe hain).
- ReLU cross karo. , toh .
- Weight gradient. . Kyun? mein jaata input hai.
- Update direction. Gradient descent: — negative gradient ko raise karta hai, lift curve ko steep karta hai taaki ki taraf chadhe. ✓ physically sensible.
Verify: ; . par finite difference: bump karo, , , slope ✓.
Ex 9 — Case I: exam twist (ek weight do baar use hona / weight tying)
Forecast: do baar appear karta hai — kya ek term hai ya do ka sum?
- Forward. ; ; .
- Seed. .
- Do uses ⇒ do paths. ki har occurrence ko ek distinct copy maano — (in ) aur (in ) — phir unke gradients add karo (multivariable chain rule):
- via : .
- via : ; phir . Sum kyun? Shared weight graph mein ek fan-in node hai — aap har jagah se contribute hua gradient sum karte hain.
- Update. .
Verify: Closed form: hai, toh hai; ✓. Ek occurrence ignore karne se milta — true gradient ka aadha — yeh classic exam trap hai.
Recall
Connections
- Backpropagation (parent) — woh machinery jo yeh examples exercise karti hain.
- Chain Rule — har "sum over paths" ke peeche ka engine.
- Gradient Descent — hamare compute kiye gradients consume karke weights update karta hai.
- Vanishing Gradients — Cases B aur D iske root causes hain.
- Activation Functions — ReLU vs sigmoid ne upar ke slope factors drive kiye.
- Computational Graphs — fan-in nodes (Ex 5, Ex 9) graph structure hain.
- Automatic Differentiation — exactly isi bookkeeping ko automate karta hai.
- Neural Network Surrogate Models (CFD) — Ex 8 ka aerospace context.