4.8.20 · D5 · HinglishNumerical Methods

Question bankIterative methods — Jacobi, Gauss-Seidel, convergence

2,140 words10 min read↑ Read in English

4.8.20 · D5 · Maths › Numerical Methods › Iterative methods — Jacobi, Gauss-Seidel, convergence

Shuru karne se pehle, har symbol ka ek-line refresher taaki kuch bhi rahasya na rahe:

Recall Woh objects jinpar neeche har sawaal tika hai
  • — woh linear system jo hum solve karna chahte hain.
  • Splitting jahan ko invert karna aasaan ho.
  • The decomposition: = ka diagonal; = strictly lower part (toh mein below-diagonal entries ke negatives hain); = strictly upper part. Is tarah . Jacobi , use karta hai; Gauss-Seidel , use karta hai.
  • Iteration , jahan iteration matrix hai aur fixed constant term hai (yeh ko loop mein laata hai).
  • Error is tarah behave karta hai: aur .
  • Spectral radius ka sabse bada absolute eigenvalue (dekho Spectral Radius).
  • SDD (strictly diagonally dominant): har row mein.
  • nnz = ki nonzero entries ki sankhya — Sparse Matrices ke liye yeh se bahut kam hoti hai.
Figure — Iterative methods — Jacobi, Gauss-Seidel, convergence
Figure — Iterative methods — Jacobi, Gauss-Seidel, convergence

True or false — justify

Convergence of from every start requires .
True. Kyunki , error tab sabke liye khatam hoga jab . diagonalize karne par milta hai jahan , aur har tab aur tabhi jab har , yaani (figure s01). Yeh ek non-negotiable law hai.
Agar strictly diagonally dominant hai, toh Jacobi aur Gauss-Seidel dono converge karte hain.
True. SDD ek sufficient condition hai jo dono methods ke liye guarantee karta hai (Gershgorin picture, figure s02, batata hai kyun), kisi bhi starting guess ke liye. Yeh ek gift hai, requirement nahi.
Agar diagonally dominant nahi hai, toh dono methods diverge karte hain.
False. SDD sufficient hai, necessary nahi. Ek non-SDD matrix ka phir bhi ho sakta hai; iska ek hi honest test hai — spectral radius khud.
Gauss-Seidel hamesha Jacobi se faster converge karta hai.
False. Yeh usually faster hota hai (fresher data ki wajah se), aur kaafi model problems mein hota hai, lekin aisi matrices bhi exist karti hain jahan Jacobi converge kare aur Gauss-Seidel diverge kare aur vice-versa. "Usually," kabhi "always" nahi.
Iteration matrix ka par depend karna.
False. sirf ki splitting se banta hai. Vector sirf constant term mein aata hai, jo affect karta hai ki tum kahan converge karte ho, naki karta hai ya nahi.
Bada (1 se kam ho tab bhi) matlab faster convergence.
False. Asymptotic error har step mein factor se sirkata hai, toh chota matlab faster. har sweep mein error ko dasguna crush karta hai; muskil se hilata hai.
Agar exactly hai, toh iteration phir bhi converge karta hai, bas slowly.
False. par dominant eigenvector ke direction mein error component na badhta hai na ghatta — yeh unit circle par baitha rehta hai (figure s01) aur origin tak kabhi nahi pahunchta. Tumhe strict chahiye.
Jacobi ka ek sweep aur Gauss-Seidel ka ek sweep roughly same cost ka hota hai.
True. Dono ke har nonzero ko ek baar touch karte hain, toh har sweep ka hai. GS ka faayda kam sweeps mein hai, saste sweeps mein nahi.
Convergence starting guess se independent guarantee hoti hai jab ho.
True. kisi bhi ke liye, kyunki . Achha guess sirf steps ki sankhya kam karta hai, result nahi badalta.
Agar Jacobi ke liye diverge karta hai, toh do rows swap karne se yeh converge ho sakta hai.
Principle mein True. Row permutation ye change karta hai ki diagonal par kaun se entries baithte hain, jo ek non-SDD matrix ko SDD bana sakta hai (parent Example 3). Yeh ki splitting badalta hai, isliye badalta hai, isliye badalta hai.

Spot the error

" ke diagonal par ek zero hai, toh main bas iterate karna shuru kar dunga aur umeed karunga ki kabhi matter nahi karega."
Error. Dono formulas se divide karte hain; zero diagonal entry pehle step par hi division by zero deta hai. Fix: pehle rows permute karo taaki diagonal par nonzeros aa jayein.
"Maine Gauss-Seidel code kiya poore purane vector ko rakh ke aur har term ke liye ussi se padhke."
Error. Lower-index terms ko purane vector se padhna Jacobi hai. GS ko ko in place overwrite karna chahiye taaki same sweep mein baad ke components fresh value dekh sakein.
"Jacobi ka iteration matrix hai."
Error. Woh Gauss-Seidel hai (yaad karo , ). Jacobi use karta hai, jisse milta hai. Yeh mix-up actually swap kar deta hai ki tum kaun sa method run kar rahe ho.
"Maine ka ek eigenvalue nikala, toh — converges."
Error. maximum absolute eigenvalue hai; ek chota eigenvalue kuch nahi batata. Koi dusra eigenvalue ho sakta hai (unit circle ke bahar). Tumhe sab ko bound karna hoga.
" SDD hai, toh main convergence par trust karne se pehle compute karunga."
Error (effort ka, logic ka nahi). SDD pehle se hi Gershgorin ke through convergence guarantee karta hai — eigenvalue computation waste of work hai. SDD shortcut ka poora point hi hai ki eigenvalues se bachna (dekho Eigenvalues and Eigenvectors).
" split karne ke liye, maine ko seedha ki lower-triangular entries ke barabar set kiya."
Error. Convention hai , toh strictly lower part hai; isliye mein below-diagonal entries ke negatives hain. Sign galat karne par ke terms ulat jaate hain.
"Kisi row mein ke saath diagonal dominance phir bhi SDD count hoti hai."
Error. Strict dominance ke liye har row mein strict inequality chahiye. Equality sirf "weakly" diagonally dominant hai (ek Gershgorin disk jo origin ko sirf touch karta hai) aur yeh khud convergence guarantee nahi karta.

Why questions

Sirf kyun decide karta hai ki hum converge karte hain ya nahi, ya kyun nahi?
Kyunki error recurrence har step mein error ko sirf se multiply karta hai; constant error equation se cancel ho jaata hai jab tum true-solution identity subtract karte ho.
(naki ya trace ) convergence kyun govern karta hai?
diagonalize karne par milta hai, aur ke liye har chahiye. Determinant (ek product) ya trace (ek sum) chota ho sakta hai tab bhi jab ek eigenvalue 1 se zyada ho, jo akela divergence cause karta hai.
Gauss-Seidel usually Jacobi ko kyun beat karta hai jabki har sweep same cost ka hai?
GS freshly-updated components ko turant inject karta hai, toh ek hi sweep mein vector mein information propagate ho jaati hai. Yeh typically ko se neeche le jaata hai, same accuracy ke liye kam sweeps chahiye.
Hum Gaussian Elimination use karne ki jagah iterate kyun karte hain?
Elimination cost karta hai aur sparsity ko destroy karta hai (fill-in). Bade Sparse Matrices ke liye har iterative sweep sirf ka hai, toh kai saste steps ek crushing direct solve se better hain.
Strict diagonal dominance "feel" kyun karta hai ki convergence force ho rahi hai?
Agar apni row ko dominate karta hai, toh har variable mainly apni hi equation se govern hota hai, toh use update karne se doosron par sirf weak perturbation hoti hai — woh coupling jo errors ko amplify kar sakti thi woh itni choti hai ki ko 1 tak pahunchne nahi deti. Geometrically, Gershgorin ke disks chote rehte hain aur unit circle se clear.
Poora framework Fixed-Point Iteration ka ek instance kyun hai?
ko ke roop mein rewrite karne par true solution ek fixed point ban jaata hai ; map ko iterate karna tab converge karta hai jab map contractive ho, jo linear maps ke liye matlab hai .
SOR — Successive Over-Relaxation Gauss-Seidel se faster kyun converge kar sakta hai?
SOR GS update ko ek over-relaxation factor ke saath blend karta hai jo har step ko uske direction mein aur aage push karta hai, aur ek well-chosen se ko Gauss-Seidel ki value se neeche le ja sakta hai, convergence accelerate karte hue.

Edge cases

Kya hota hai agar diagonalizable nahi hai (ek defective eigenvalue)?
Clean argument fail hota hai, lekin theorem phir bhi hold karta hai: Jordan form ke through, jahan polynomial-in- factors appear hote hain lekin jab ho toh unhe crush kar deta hai.
Kya hoga agar matrix ho, yaani ?
, , toh aur : yeh ek step mein par "converge" karta hai — provided ho, jo divide-by-diagonal rule ka trivial edge case hai.
Kya hoga agar exact solution ke barabar nikle?
Tab , toh sab ke liye: tum bilkul answer par baithe ho. Stopping test immediately trigger ho jaata hai.
Kya hoga agar ho lekin kuch intermediate iterates sirakte se pehle bade ho jayein?
Bilkul possible hai. eventual decay guarantee karta hai, lekin non-normal early sweeps mein transient growth cause kar sakta hai; norm briefly badh sakta hai phir asymptotic rate aane se pehle.
Jab 1 ke kareeb ho toh par based stopping rule kya risk leta hai?
Consecutive iterates har step mein barely move karte hain, toh difference chota lagta hai jabki true error abhi bhi bada hai — tum se door premature stop kar sakte ho. Residual check karna isse guard karta hai.
Kya hoga agar symmetric positive definite ho lekin SDD na ho?
Gauss-Seidel phir bhi converge karta hai (SPD apna sufficient condition hai), chahe SDD shortcut apply na ho. Yeh "SDD fail hone par bhi convergence" ka ek headline example hai.
Huge grid par Jacobi ki parallelism versus Gauss-Seidel ki kya hoti hai?
Jacobi sirf purana vector use karta hai, toh har independently aur parallel compute hota hai; Gauss-Seidel ke in-place updates inherently sequential hain, jo parallel speed ke badle kam sweeps leta hai — yeh Finite Difference Methods for PDEs mein ek real design tension hai.