4.8.27 · D5 · HinglishNumerical Methods
Question bank — Systems of ODEs — RK4 for systems
4.8.27 · D5· Maths › Numerical Methods › Systems of ODEs — RK4 for systems
Shuru karne se pehle, ek reminder notation ki jo poori taraf use hoti hai, taaki kuch unexplained na rahe:
- sabhi unknowns ka stacked column hai ek moment in time par.
- stacked column of slopes return karta hai.
- chaar slope-vectors hain (har ek length ka) jo width ke ek step mein sample kiye jaate hain.
- step size hai (kitna mein jump karte hain har step mein).
True or false — justify
Har item: true/false decide karo, phir reason do. Reason hi answer hai.
RK4 for a system ek genuinely naya algorithm hai, scalar RK4 se bilkul alag.
False — ye identical recipe hai jisme har scalar symbol ki jagah uska vector version aata hai; weights over aur stage structure bilkul unchanged rehte hain.
Tum ek coupled system ki har equation ko apne independent scalar RK4 run se solve kar sakte ho.
False — kyunki sabhi components par depend karta hai, isliye ke baad kisi bhi stage ko doosre unknowns ki advanced state chahiye, jo ek independent run ne abhi compute nahi ki hoti.
Agar do equations uncoupled ho jaati hain (har sirf apne par depend karta hai), to alag-alag scalar RK4 chalana vector method ke bilkul same answer deta hai.
True — koi coupling nahi hone par ek component ki advanced state doosre ke slope mein nahi jaati, isliye stages decouple ho jaate hain aur independent scalar runs system method se match karte hain.
RK4 for systems mein weights over ho jaate hain kyunki do equations hain.
False — weights time-quadrature ki property hain (ek step par Simpson-like sampling), naa ki kitne unknowns hain; ye over hi rehte hain kisi bhi ke liye.
Har ek single number hota hai jo sabhi components ke liye reuse hota hai.
False — har ek length- vector hota hai; ka component us stage par ka estimated slope hota hai.
RK4 for a system ka global truncation error hai, scalar ke jaisa hi order.
True — order-4 dene wali Taylor-matching ne sirf , aur addition ki algebra use ki, jo vectors par har component par identically kaam karti hai, isliye order component-by-component preserve hota hai.
Agar tum ko half kar do, to global error roughly ke factor se girne ki expect karni chahiye.
True — global error hai aur , isliye step half karne par error roughly sixteen guna kam hoti hai (jab tak round-off dominate na kare).
Ek 2nd-order ODE ko RK4-for-systems handle nahi kar sakta; tumhe ek special second-order solver chahiye.
False — tum derivatives rename karte ho () aur use first-order system mein convert kar dete ho, jise RK4-for-systems directly solve karta hai.
mein pass kiya gaya intermediate state hai, time par evaluate kiya gaya.
True — predicted midpoint par slope probe karta hai, isliye time argument aur state argument dono use karke half step se aage jaate hain.
state mein full step use karta hai, half step nahi.
True — interval ke end par slope sample karta hai, isliye poore se aage jaata hai.
Spot the error
Har item ek plausible-sounding statement ya step dikhata hai. Batao kya galat hai aur kyun.
"Maine pehle ke saare compute kiye, phir ke liye repeat kiya."
Error hai stage synchronization kho dena: ka chahiye ki advanced state, jo exist nahi karti agar saath mein step nahi ki gayi; pehle poora vector compute karo, phir poora , aur aise hi aage.
" ke liye maine state use ki."
Galat slope feed ki — ko refined midpoint state use karni chahiye; wahan reuse karna ko mein collapse kar deta hai aur fourth-order accuracy destroy kar deta hai.
" reduce karne ke liye maine aur set kiya."
Labels readability ke liye ulte hain lekin asli trap consistency hai: chahe tum unhe jo bhi name do, tumhe (ya matching pair) chahiye — agar tum likhte ho jabki hai, to tumhare paas galat second equation ke saath paired hai aur system original ODE encode nahi karta.
"Mera final update tha ."
Middle do slopes ka wala weight missing hai; sahi combination hai , jo Simpson ke pattern ko mimic karta hai (do midpoint samples milke dete hain).
"Maine factor drop kar diya kyunki aise bhi chhota tha."
optional smallness nahi hai — ye hi step ki length scaling hai; iske bina tum time ke koi units nahi wala raw slope add kar rahe ho, jo ek wildly wrong (aur -independent) jump deta hai.
" mein maine time par advance kiya lekin state par hi rakhi."
Tumhe dono time aur state advance karni chahiye; purani state ko naye time ke saath use karna ko ek inconsistent slope banata hai aur midpoint prediction ko tod deta hai jis par method rely karti hai.
"Kyunki already ek achha slope deta hai, maine time bachane ke liye skip kar diye."
Sirf use karna bas Euler's method hai (dekho Euler's method for systems), jo globally sirf order-1 accurate hai; teen extra samples ka poora point order 4 tak pahunchna hai.
Why questions
Underlying reason se jawab do, sirf restatement nahi.
Kyun scalars ko vectors se replace karne par RK4 weights unchanged rehte hain?
Kyunki order-4 derivation ne sirf Taylor terms ko addition, se scalar multiplication, aur function evaluation use karke match kiya — ye sab har vector component par identically act karte hain, isliye kisi bhi weight ko re-tune karne ki zaroorat nahi padi.
RK4 midpoint par slope do baar kyun sample karta hai ( aur deta hua)?
Ye Simpson's rule ko mimic karta hai, jiska accuracy midpoint ko heavily weight karne se aata hai; do successive midpoint estimates ( improved use karke) method ko zyada Taylor error cancel karne dete hain jo ek single midpoint se nahi ho sakta tha.
Har component ko har stage par saath mein kyun advance karna chahiye?
Kyunki components coupled hain — doosre unknowns padhta hai — isliye kisi stage ka slope tabhi meaningful hai jab woh ek consistent snapshot dekhe jahan sabhi components ek hi intermediate time par move ho chuke hon. (Dekho Simpson's Rule us quadrature ke liye jo ye imitate karta hai.)
Ek high-order ODE ko first-order system mein reduce karna kyun worthwhile hai?
Ye ek single algorithm (RK4-for-systems) ko kisi bhi order ke ODEs solve karne deta hai, isliye tumhe kabhi alag-alag order ke liye separate integrator nahi chahiye; derivatives ko new unknowns ke roop mein name karna universal adapter hai (dekho Reducing higher-order ODEs to first-order systems).
Local error kyun hai lekin global error sirf kyun?
Ek fixed interval cross karne ke liye roughly steps accumulate hote hain, isliye per-step errors milke approximately ho jaate hain (detail mein Local vs Global Truncation Error mein hai).
Kuch systems par apni high order ke bawajood explicit RK4 badly kyun fail kar sakta hai?
Stiff systems par explicit RK4 ki stability region practically bahut chota force karti hai, isliye accuracy theek hoti hai lekin stable rehne ke liye enormous computation chahiye (dekho Stiff systems and stability).
Ek system aur reduced ke liye same numerical answer kyun aata hai?
Kyunki ye same equations hain — ka reduction exactly produce karta hai, isliye RK4 identical right-hand sides dekhta hai aur identical steps produce karta hai.
Edge cases
Boundary aur degenerate scenarios jo tumhe surprise nahi karne chahiye.
Kya hota hai agar system ho (ek single equation) RK4-for-systems se run karte waqt?
Ye exactly scalar RK4 for a single ODE mein reduce ho jaata hai — length one ka vector bas ek number hai, isliye dono methods koi special-casing ke bina coincide karte hain.
Agar par depend nahi karta (ek autonomous system), to kya hum phir bhi shifted times pass karte hain?
Time arguments formula mein phir bhi exist karte hain lekin unhe ignore karta hai, isliye effectively sirf state shifts matter karti hain; recipe unchanged aur correct hai.
Ek linear system ke liye, kya phir bhi chahiye, ya koi shortcut hai?
RK4 verbatim apply hota hai (har )); matrix exponential ke through ek closed-form bhi exist karta hai, lekin RK4 ko aisi koi special structure nahi chahiye aur ye identically kaam karta hai chahe constant ho ya naa ho.
Agar ek component ki initial value exactly hai — kya ye kisi stage ko break karta hai?
Nahi — ek zero entry ek perfectly valid state value hai; slopes aur averages usi tarah compute hote hain, isliye zeros bina kisi special handling ke arithmetic mein propagate ho jaate hain.
Agar ek component ek fixed point tak pahunch jaaye (wahan uska slope hai), kya RK4 use unchanged chodta hai?
Agar us component ke saare chaar vanish ho jaayein to woh jaisi hai waisi rehti hai; lekin agar coupling kisi midpoint slope ko nonzero banaata hai, to woh phir bhi drift kar sakti hai, isliye ek true equilibrium ke liye slope ko poore predicted step mein zero hona chahiye, sirf start mein nahi.
lene par accuracy aur cost dono par kya hota hai?
Accuracy ki tarah improve hoti hai lekin steps ki sankhya (aur -evaluations, chaar per step) ki tarah badhti hai, isliye ek practical trade-off hai — ko hamesha shrink karte rehne par eventually sirf round-off error accumulate hoti hai, precision nahi.
Agar do stages ko same state accidentally milti hai (jaise zero ho jaata hai), kya aur phir bhi valid hain?
Haan — zero ka matlab sirf ye hai ki midpoint state ke barabar hai, isliye wahan legitimately evaluate karta hai; kuch degenerate nahi hota, method is step mein sirf kam distinct states sample karta hai.
Connections
- Parent topic — RK4 for systems
- RK4 for a single ODE — scalar case jin traps ko ye generalise karte hain.
- Euler's method for systems — "sirf use karo" kya collapse karta hai.
- Reducing higher-order ODEs to first-order systems — edge cases ke peeche ka adapter.
- Local vs Global Truncation Error — reasoning.
- Stiff systems and stability — kyun order 4 akela kaafi nahi hai.
- Simpson's Rule — weights ka source.