4.8.23 · D5 · HinglishNumerical Methods
Question bank — Modified Euler (Heun's method)
4.8.23 · D5· Maths › Numerical Methods › Modified Euler (Heun's method)
Ek picture apne dimag mein rakho: ek step ke dono siron par do slopes khinchi hain, aur unki average direction mein ek akela walk liya gaya hai.

Sach ya jhooth — justify karo
Heun's method same ke liye plain Euler se hamesha zyada accurate hoti hai.
Aam taur par, hamesha nahi. Smooth problems ke liye yeh bahut behtar hai ( vs ), lekin bahut zyada stiff ya badly-scaled ODE par bahut bade ke saath, predictor itna aage nikal sakta hai ki corrected step Euler se bhi buri ho jaaye — accuracy order sirf us limit ko describe karta hai jab .
Heun's method har step mein function ko exactly do baar evaluate karti hai.
Sach hai basic Heun ke liye: ek baar ke liye aur ek baar ke liye. Iterated corrector variant har extra sweep ke liye ko dobara evaluate karta hai, isliye uska cost zyada hota hai.
Predictor value step ka final answer hai.
Jhooth hai. sirf ek scratch guess hai jiska ek hi maqsad hai — hume end-slope compute karne dena; ise pheink diya jaata hai aur corrected se replace kar diya jaata hai.
Heun's method ek Runge–Kutta method hai.
Sach hai. Yeh RK2 hai — apne do slopes par equal weights wala ek 2-stage Runge–Kutta scheme.
Agar sirf par depend karta hai ( par nahi), toh Heun's method ek plain integral ke liye trapezoidal rule mein reduce ho jaati hai.
Sach hai. Jab ho, predicted kabhi mein enter nahi karta, isliye — exactly Trapezoidal Rule par apply hota hai.
Step size ko double karne se Heun ka global error roughly double ho jaata hai.
Jhooth hai. Global error hai, isliye ko double karne se error roughly guna hota hai, nahi. (Double karne se plain Euler ka error roughly double hota hai.)
Corrector mein ek rounding convenience hai jiska koi gehri meaning nahi hai.
Jhooth hai. do slopes ka average hai: har slope step ka aadha contribute karta hai. Ise se replace karo aur tum double-length step lete ho — yeh ek genuine error hai, koi style choice nahi.
Heun ka local (per-step) error aur global error same order ke hain.
Jhooth hai. Local error per step hai; steps par accumulate hone se ek power drop hoti hai, global milta hai. Yeh ek-power drop one-step methods ke liye generic hai.
Error dhundho
Ek student corrector likhta hai . Kya galat hai?
End-slope predicted ki jagah purane par evaluate ki gayi hai. step ke across kaise move hua isko ignore karna second-order accuracy ko khatam kar deta hai — tum wahi "look-ahead" kho dete ho jo Heun ko define karta hai.
Ek student compute karta hai — same , moved . Theek karo.
End-slope end point par sample honi chahiye, isliye . ko advance karna lekin ko nahi, ko ek aisi jagah evaluate karta hai jo step par kabhi exist nahi karti.
Ek student step khatam hone se pehle corrected ko ke andar wapas use karta hai. Yeh circular kyun hai?
step ke start se fixed hota hai aur baaki sab se pehle jaana jaata hai. Isme baad ki value feed karna matlab ab tumhare paas start-slope nahi hai — method apna predictor kho deti hai aur Heun rehti nahi.
Koi likhta hai . Diagnose karo.
Unhone ek full Euler step aur aadha end-slope add kar diya — Euler aur Heun ka mix. Do slopes par sahi total weight tak sum hona chahiye: yeh hona chahiye.
Example 3 mein ek student corrector ko iterate karta hai lekin har sweep ke liye wahi pehla predictor ke liye use karta rehta hai. Kya galat hai?
Iterate karne ka matlab hai latest corrected se end-slope re-predict karna (jaise ), taaki har sweep mein update ho. ko original guess par freeze karna sirf pehla corrector repeat karta hai aur kuch naya nahi milta.
Why questions
Hum ko correct karne se pehle predict kyun karte hain?
Trapezoidal corrector ko chahiye, lekin wahi unknown hai jise hum solve kar rahe hain. Ek sasta Euler predictor is chicken-and-egg deadlock ko pehli guess se todta hai.
Do slopes ko average karne ki jagah sirf end-slope use kyun nahi karte?
Sirf use karna over-correct karta — true slope poore interval mein vary karti hai, aur entry aur exit slopes ka mean interval ke behaviour se akele kisi bhi endpoint se ek order zyada match karta hai.
Heun ko "predictor–corrector" method kyun kaha jaata hai, sirf "Euler twice" nahi?
Do stages alag roles play karti hain: predictor ek rough forward guess karta hai, corrector us guess ka use ek better-averaged step banane ke liye karta hai. Predictor-Corrector Methods dekho — yeh asymmetry defining feature hai.
Heun term tak true Taylor series se kyun match karta hai lekin par fail hota hai?
Start aur end slopes ko average karna aur ko exactly reproduce karta hai, lekin term ko (curvature-of-curvature) chahiye jise do slope samples capture nahi kar sakte. ko sahi karna hi tumhe RK4 ki taraf push karta hai. Taylor Series Methods dekho.
ko aadha karna Heun ki zyada madad kyun karta hai Euler se?
Heun ka error scale karta hai, Euler ka ; ko aadha karne se yeh aur se divide hote hain respectively — zyada power refinement ko zyada reward deti hai. Yahi Order of Accuracy and Step Size ka poora point hai.
Corrector ko iterate karna answer improve kyun kar sakta hai, phir bhi exact solution tak kabhi nahi pahunch sakta?
Iteration implicit trapezoidal equation ko zyada precisely solve karta hai, predictor error hatata hai — lekin trapezoidal rule mein discretisation error hai jo itni bhi iteration se erase nahi ho sakti.
Heun exact kyun hai jab true solution ek straight line ho ()?
Seedhi solution mein constant slope hoti hai, isliye aur unka average har jagah true slope ke equal hota hai. Trapezoid tab exact hota hai jab integrand constant ho, isliye koi error introduce nahi hoti.
Edge cases
Jab ho (flat start slope) toh Heun kya karta hai?
Predictor ruka rehta hai (), lekin nonzero ho sakta hai, isliye corrector phir bhi move karta hai. Yahi wajah hai ki Heun woh "curvature notice" karta hai jo plain Euler miss karta hai jab yeh flat start karta hai (Example 2 dekho).
Agar step size hai, toh formula kya deta hai?
aur — koi step nahi liya jaata. Predictor aur corrector dono identity mein collapse ho jaate hain; method consistent hai (zero step kuch nahi badalta).
Maan lo mein linear hai, jaise . Kya predictor phir bhi zaroori hai?
Practice mein haan, lekin note karo corrector ek explicit linear equation ban jaata hai jise tum ke liye seedha solve kar sakte ho. Heun ise predict karke sidestep karta hai — exactness ki jagah ek fixed, sasta recipe trade karta hai.
Agar predictor massively overshoot kare (fast-decaying ODE par huge ) toh corrector ka kya hota hai?
bilkul galat par sample hota hai, isliye averaged slope corrupt ho jaata hai aur Euler se bhi bura ho sakta hai — ek stability failure. Order-2 accuracy ek small- promise hai, large- guarantee nahi.
jaisi purely oscillatory problem ke liye ek step mein, Heun ka answer true decay se upar hai ya neeche?
Heun ka averaged slope large ke liye thoda under-decay karta hai kyunki trapezoid rule curved integrands ko over/undershoot karta hai; small ke liye discrepancy tiny hai ( per step) aur Heun true exponential ko closely track karta hai.
Agar do alag smooth ODEs ek step par same , aur share karein, toh kya woh same Heun step lete hain?
Haan — Heun ka step sirf aur do slope samples par depend karta hai, underlying formula par nahi. Recipe mein identical inputs se identical output milta hai, construction se.
Connections
- Euler's Method — predictor hai ek plain Euler step.
- Trapezoidal Rule — corrector disguise mein yahi rule hai (aur equals karta hai jab ).
- Runge-Kutta Methods — Heun hai RK2; RK4 gap fix karta hai.
- Order of Accuracy and Step Size — kyun halving ko reward karta hai.
- Predictor-Corrector Methods — Heun sabse simple member hai.
- Taylor Series Methods — woh tool jo prove karta hai Heun second order hai.