4.10.19 · D5 · HinglishAdvanced Topics (Elite Level)

Question bankKKT conditions for constrained optimization

1,854 words8 min read↑ Read in English

4.10.19 · D5 · Maths › Advanced Topics (Elite Level) › KKT conditions for constrained optimization

Shuru karne se pehle do reminders, taaki neeche har symbol already grounded ho:


Sahi hai ya galat — justify karo

TF1. Agar ek KKT point exist karta hai, to wo global minimum hona chahiye.
False — non-convex problems ke liye KKT sirf necessary hain, isliye ek KKT point maximum, saddle, ya local (global nahi) min ho sakta hai; sirf convexity unhe sufficient banata hai.
TF2. Equality multipliers non-negative hone chahiye.
False — sirf inequality multipliers hote hain; equality multipliers sign mein free hote hain, bilkul ordinary Lagrange Multipliers ki tarah.
TF3. Kisi bhi feasible point par, complementary slackness automatically hold karta hai.
False — ye ek condition hai jo KKT optimum par impose karta hai, har feasible point ke baare mein koi fact nahi; ek random feasible point mein ke saath nonzero ho sakta hai aur wo ise violate kar sakta hai.
TF4. Agar (baad ko touch nahi kiya), to .
True — slackness mein ke saath force hota hai; ek untouched baad koi push nahi karta.
TF5. Agar , to corresponding constraint active hona chahiye.
True — slackness force karta hai jab bhi ; ek baad tabhi push back karta hai jab tum usse lean kar rahe ho.
TF6. Ek convex problem ke liye, saari chaar KKT conditions satisfy karna global minimum guarantee karta hai.
True — convex aur affine ke saath, KKT global min ke liye necessary aur sufficient hain.
TF7. Har wo point jahan ( ka ek flat spot) ek KKT point hai.
False — ye tabhi KKT hai jab wo feasible bhi ho aur multipliers ko stationarity/slackness satisfy karne ke liye choose kiya ja sake; feasible region ke bahar ek flat spot solution hai hi nahi.
TF8. LICQ is liye zaroori hai ki KKT sufficient ho.
False — LICQ is liye zaroori hai ki KKT ek minimum par necessary ho; sufficiency convexity se aata hai, jo ek alag ingredient hai.
TF9. Agar dono fence par inactive hain, to problem locally unconstrained jaisi behave karti hai.
True — inactive constraints ke zero multipliers hote hain aur wo stationarity se bahar ho jaate hain, isliye locally tum sirf ke ek flat spot par ho.
TF10. Ek convex problem mein, KKT points unique hote hain.
False — convexity ek global optimum value guarantee karta hai lekin minimizer set poora flat region ho sakta hai (jaise ek segment par constant minimize karna), jisse bahut saare KKT points milte hain.

Error dhundo

SE1. "Maine likha ke saath aur mila, isliye problem ka koi solution nahi hai."
Sign galat hai: ke saath correct stationarity hai , yaani ; pehle form mein convert karne se flipped theek ho jaata hai.
SE2. "Optimum dhundne ke liye maine har constraint ko active set kiya aur resulting system solve kiya."
Ek truly-inactive constraint ko active force karna deta hai, jo dual feasibility violate karta hai — wo negative value ek signal hai ki tumhara active-set guess galat hai, answer nahi.
SE3. "Point feasible hai aur , isliye wo optimal hai — check karne ki zaroorat nahi."
Stationarity plus feasibility kaafi nahi hai; check kiye bina tumne maximum dhundha hoga ya ek galat active-set case jo baad ke khilaaf galat taraf lean kar raha hai.
SE4. "Mere paas hai, isliye maine ko ke saath seedha outward pointing use kiya."
Tumhe pehle ko mein rewrite karna hoga; conversion skip karna silently us sign ko flip kar deta hai jis par rule depend karta hai.
SE5. "Meri problem non-convex hai lekin mujhe ek KKT point mila, isliye maine use global minimum report kiya."
Non-convex problems ke liye KKT sirf necessary hai; tumhe saare KKT candidates (aur possibly boundary/infeasibility cases) compare karne honge kyunki kuch maxima ya saddles hote hain.
SE6. "LICQ mere optimum par fail ho gaya, isliye mera point actually minimum nahi ho sakta."
LICQ fail hone ka matlab sirf ye hai ki KKT multipliers exist nahi kar sakte ya unique nahi ho sakte — point phir bhi ek genuine minimum ho sakta hai; tum bas KKT se ise certify nahi kar sakte.
SE7. "Complementary slackness mujhe deta hai, isliye main hamesha set kar sakta hoon."
Sirf jab ; agar constraint active hai () to product kisi bhi ke liye zero hai, isliye tumhe ke liye solve karna hoga, ye assume nahi karna ki wo zero hai.

Kyun questions

WHY1. kyun hona chahiye lekin koi bhi sign ho sakta hai?
Ek fence motion ko sirf ek taraf block karta hai (), isliye uska push ek taraf point karna chahiye (non-negative multiplier); ek taar () dono taraf motion block karta hai, isliye uska multiplier dono direction mein pull kar sakta hai.
WHY2. Complementary slackness ek hi statement kyun hai jo "active vs inactive" ko unify karta hai?
Product force karta hai ki kam se kam ek factor vanish ho — ya (active) ya (inactive) — dono cases ko ek equation mein capture karta hai.
WHY3. KKT ko constraint qualification ki zaroorat kyun hai?
Iske bina, active constraint gradients degenerate ho sakte hain (jaise fences ek cusp mein milna), aur phir koi multipliers exist nahi karte jo ko unke combination ke roop mein express kar sake, chahe true minimum par bhi.
WHY4. Convexity KKT ko necessary se sufficient kyun banata hai?
Ek convex problem mein sahi sign conditions ke saath ek stationary feasible point ke paas kahi bhi (sirf locally nahi) koi feasible descent direction nahi hota, isliye wo global minimum hona chahiye — Convex Optimization dekho.
WHY5. Geometrically, active constraint gradients ke cone ke andar kyun hona chahiye?
Agar (downhill pull) us cone ke bahar nikla, to koi feasible direction abhi bhi reduce kar sakti; cone ke andar trap hona matlab har escape route ek constraint violate karta hai.
WHY6. Ek inactive constraint stationarity mein kuch contribute kyun nahi karta?
Uska multiplier slackness ke zariye zero force hota hai, isliye uska gradient term se drop ho jaata hai — ek fence jo tum touch nahi kar rahe wo koi force nahi lagata.
WHY7. KKT conditions Support Vector Machines ke liye itni important kyun hain?
SVM ek convex program hai, isliye KKT sufficient hain; complementary slackness exactly support vectors (active constraints with ) ko pick out karta hai jo margin define karte hain.
WHY8. Duality KKT se kyun relate karta hai?
KKT stationarity exactly hai, aur with slackness wo conditions hain jiske under primal aur dual optima coincide karte hain (strong duality).

Edge cases

EC1. Jab koi inequality constraints nahi hain, sirf equalities hain, to KKT conditions kya hain?
Wo ordinary Lagrange Multipliers mein collapse ho jaate hain: feasibility ke saath, aur kisi bhi multiplier par koi sign restriction nahi.
EC2. Agar bilkul koi constraints nahi hain to KKT ka kya hota hai?
Stationarity reduce ho jaati hai — plain unconstrained first-order condition, "flat ground" case.
EC3. Ek constraint active aur uska multiplier exactly zero hai (, ). Kya ye allowed hai?
Haan — ye "degenerate" ya weakly active case slackness satisfy karta hai; fence touch ho rahi hai lekin koi push nahi kar rahi, often ek sign ki optimum ek aisi boundary par baitha hai jo binding nahi hai.
EC4. Feasible region empty hai (constraints contradict karte hain). KKT kya kehta hai?
Kuch nahi — KKT ek feasible optimum presuppose karta hai; koi feasible point nahi hone se koi test karne ke liye nahi hai, isliye poora framework apply nahi hota.
EC5. Objective feasible set par unbounded below hai. Kya phir bhi ek KKT point exist kar sakta hai?
Koi finite minimizer exist nahi karta, isliye koi KKT point nahi; stationarity ko ek balance chahiye hoga jo hone par kabhi nahi hota.
EC6. Do fences ke par identical gradients hain (linearly dependent). Kya toot jaata hai?
LICQ fail ho jaata hai, isliye multipliers non-unique ya non-existent ho sakte hain — tum forces ko cleanly read off nahi kar sakte chahe point optimal bhi ho.
EC7. Kya ek KKT point ka local maximum ho sakta hai?
Haan, non-convex problems ke liye — stationarity min/max ke liye symmetric hai, isliye KKT maxima aur saddles bhi pakadta hai jab tak convexity unhe rule out na kare.
EC8. Iska kya matlab hai agar projected gradient descent ek aise point par ruk jaata hai jahan projected gradient zero hai?
Usne constrained problem ka ek KKT point reach kar liya hai — descent direction poori tarah constraint projection se cancel ho gayi hai, stationarity plus slackness ko mirror karta hai.

Recall Sabse gehre trap ka ek-line summary

Do conditions jinhe log confuse karte hain: sign ke baare mein hai (fences ek taraf push karte hain), slackness activity ke baare mein hai (fences sirf tab push karte hain jab touch ho) — ye alag rules hain, dono required hain.