Parent note ko bina atke padhne se pehle, tumhe har letter apna banana hoga. Ye page har ek ko bilkul zero se build karta hai, us order mein jo har idea ko pehle wale pe lean karne deta hai.
Ek deewar se tukkron ki tarah bounce karte tiny gas molecules ki bheed imagine karo. Har bounce ek tiny shove hai. Ek square metre pe saare shoves ko add karo aur tumhe pressure milti hai.
Topic ko ye kyun chahiye? POORA subject do pressures ka comparison hai — nozzle se nikalne wali gas ki pressure versus uske aas-paas ki hawa ki pressure. Agar pressure ko tum "molecular pushing" ki tarah feel nahi karte, to "too high" aur "too low" phrases ka koi matlab nahi.
Parent note mein char pressure symbols hain. Ye rahe, har ek jahan rehta hai wahan pin kiya gaya.
pedesign ko alag kyun introduce karein? Kyunki "over-" aur "under-expanded" ka naam design point ke relative rakha gaya hai, current pb ke relative nahi. Jab parent kehta hai ek nozzle "sea level ke liye designed" altitude pe under-expanded ho jaata hai, to pe khud kabhi nahi badalti — ye hamesha pedesign ke barabar hoti hai. Jo badalti hai wo hai pb. To humein "ye hardware hamesha jo pressure produce karta hai" uska ek fixed naam chahiye jo moving target pb se alag ho; wo fixed naam hai pedesign, aur ek fully-supersonic nozzle ke liye pe≡pedesign.
Topic ko inki zarurat kyun: poora classification ek comparison hai — kya pe, pb se upar hai, neeche hai, ya barabar? Baaki sab pe calculate karne ki machinery hai.
Ek converging–diverging (de Laval) nozzle ek aisi tube hai jo pehle narrow hoti hai, phir wide. Sabse narrow slice ko throat kehte hain.
A∗ pe star kyun? Star ek convention hai jiska matlab hai "sonic point pe value" — wo jagah jahan flow exactly sound ki speed se move kar rahi hoti hai. Is nozzle mein throat wahi jagah hai (§6 mein dekhenge kyun). To A∗ aur "throat area" yahan ek hi cheez hain.
Topic ko areas kyun chahiye: parent ka punchline ye hai ki pe sirf area ratioAe/A∗ se fixed hoti hai. Geometry, bahar ki hawa nahi, exit pressure set karti hai. Wo sentence samajhna possible nahi agar pata na ho ye dono areas kya hain.
M kyun aur V kyun nahi: same speed pe do flows bilkul alag behave karti hain agar ek sound speed ke upar ho aur ek neeche. Sirf ratioM batata hai tum sonic line ke kis side pe ho — ye wahi ratio hai jis par physics actually dhyan deti hai.
Pictures ko formulas mein convert karne ke liye humein ek gas model chahiye.
Topic ko γ aur isentropic kyun chahiye: parent pe derive karta hai ye assume karke ki nozzle ke andar flow isentropic hai. Yahi assumption exactly humein pressure ko Mach number ka clean function likhne deti hai. Shocks (over-expanded case mein) wahi ek jagah hain jahan flow not isentropic hoti — isliye inhe special events ki tarah treat kiya jaata hai.
"Isentropic" shock pe kyun fail ho jaata hai?
Shock ek sudden, thin jump hai — ye smooth nahi hai, isliye entropy badhti hai aur p/ργ uske across constant nahi rehta.
Mass conservation (ρAV tube mein constant hai) ko smooth isentropic rules ke saath combine karo, aur kuch remarkable samne aata hai: kisi aisi gas ko speed up karne ke liye jo already supersonic hai, tube ko widen karna hoga, jabki subsonic gas ko speed up karne ke liye tube ko narrow karna hoga. Crossover — M=1 — sirf wahan ho sakta hai jahan area shrink karna band kare aur grow karna shuru kare: throat.
Isliye A∗ (sonic area) throat area ke barabar hoti hai, aur isliye hum kehte hain nozzle choked hai: ek baar jab M=1 throat pe baith jaata hai, mass flow max out ho jaati hai aur peg ho jaati hai.
Parent ka thrust equation F=m˙Ve+(pe−pb)Ae inhe sab chahiye: ek momentum term (m˙Ve) plus ek pressure term (pe−pb)Ae. Notice karo pressure term exactly hamara do-pressure comparison hai, ab exit area se multiplied — Rocket Nozzle Design & Thrust Optimization dekho.
Do words pehle hi sentence se appear hote hain, to inhe abhi pictures ke saath pin karo.
Dono kyun chahiye: ek fan sirf pressure gira sakta hai, ek shock sirf pressure badha sakta hai. Mismatch jis direction mein chale wo tool pick karta hai. Ye single choice — badhao ya ghataao — topic ka poora branching logic hai.