(a) Choices hain x1,x2 → 2 decision variables.
(b) Har ≤ constraint ke liye ek slack (na ki x≥0 ke liye, kyunki woh variables ko
non-negative rakhke handle hota hai). Do constraints → 2 slacks s1,s2.
(c) Total = decisions + slacks =2+2=4.
Slacks:x1+s1=4,2x2+s2=12,3x1+2x2+s3=18. z-row hai z−3x1−5x2=0, yani
coefficients (−3,−5).
Enter: sabse zyada negative −5 hai x2 ke neeche → x2 enters (per unit x2 badhane se z sabse tezi se badhta hai).
Ratio test — sirf woh rows jahaan x2-column entry positive ho:
Row s1: x2-entry hai 0 → skip (ek 0 kabhi increase ko bound nahi karta).
Row s2: 12/2=6.
Row s3: 18/2=9.
Sabse chhota ratio 6 hai → s2 leaves. x2 ko 6 tak push karne se s2=0 ho jaata hai (constraint 2x2≤12
tight ho jaata hai) jabki baaki ≥0 rehte hain.
Naya corner:x1=0,x2=6, toh (0,6) aur z=3(0)+5(6)=30.
Pehle pivot ke baad, x2 basic hai (=6), aur z-row mein x1 ke neeche abhi bhi negative hai, toh hum
dobara pivot karte hain. Row-reduction ko completion tak le jaana (enter x1, ratio test
3x1+2x2≤18 row choose karta hai) humein 2x2=12 aur 3x1+2x2=18 ke intersection par le jaata hai:
2x2=12⇒x2=6,3x1+2(6)=18⇒3x1=6⇒x1=2.
Corner (2,6), aur z=3(2)+5(6)=6+30=36. z-row ab sab ≥0 hai → optimal.
Raaste mein teesra constraint check karo: x1=2≤4 ✓, dono sensibly use ho gaye. Neeche figure mein corner walk dekho.
z-row equation hai z=2x1+7x2−4s2 (negatives ko doosri taraf le jaao). Toh ∂z/∂x2=7, sabse bada positive rate. x2 enters — ise badhane se z per unit 7 badhta hai,
x1 ke 2 se zyada; s1,s2 columns (0 aur +4) ya toh kuch nahi karte ya zkam kar dete hain,
toh hum unhe kabhi nahi badhaaenge. "z-row mein sabse zyada negative" exactly "sabse bada positive rate of
gain" hai.
Haan — optimal hai, kyunki harz-row coefficient ≥0 hai. z=(const)−3x2−1s1−5(⋅) padhne par: kisi bhi currently-non-basic variable ko badhane se z sirf kam ho sakta hai (ek 0 ise unchanged
rakhta hai). Improvement ki koi direction nahi bachi, toh hum top corner par baithe hain. Yeh parent
note ka optimality test ek picture ki tarah hai: objective ramp ab kisi bhi feasible direction mein upar ki taraf nahi jhukti.
Negate kyun? Simplex loop maximize karne ke liye bana hai. z minimize karna same hai jaise
w=−z=x1+3x2 maximize karna, kyunki minz=−max(−z).
Slacks:x1+x2+s1=5,x1+2x2+s2=8. w-row coefficients hain (−1,−3).
Pivot 1 — enter x2 (most negative −3). Ratios: 5/1=5, 8/2=4 → s2 leaves.
Naya corner: line x1+2x2=8 par x1=0 ke saath → x2=4, giving (0,4), w=3(4)=12.
w-row abhi bhi x1 ke neeche negative dikhata hai, toh continue karo.
Pivot 2 — enter x1. Binding pair hai x1+x2=5 aur x1+2x2=8. Solve:
subtract: (x1+2x2)−(x1+x2)=8−5⇒x2=3,x1=5−3=2.
Corner (2,3): w=2+3(3)=2+9=11? Dono objectives carefully check karo:
w=x1+3x2=2+9=11. (0,4) se compare karo: w=12. Kyunki 12>11, corner (0,4) actually
w ke liye behtar hai — x1 column yahan w improve nahi karega, toh w-row pivot 1 ke baad already
sab ≥0 hai. Optimum: (0,4), w=12.
Isliye minz=−w=−12 at (0,4).
(Moral: hamesha evaluate karo — ratio/entering rules ek move propose karte hain, lekin optimality test hi
confirm karta hai ki aap pahunch gaye hain.)
Strong duality se, dual ka optimal (ek minimization) primal ke optimal ke barabar hota hai. Toh dual
optimum hai 36. Usefulness: simplex se primal finish karne ke baad, 36 value wala koi bhi feasible dual solution
compute karna prove karta hai ki aap true optimum par pahunche — "z-row sab non-negative ho gayi" se pare ek doosra, independent
certificate. Isliye tableau ke final z-row entries slack columns ke neeche exactly dual variable values hoti hain.
Tie ka matlab hai entering variable exact same value par do constraints hit karta hai — ek corner se m se zyada
constraints guzarti hain. Woh corner degenerate hai (over-determined). Practical danger:
ek pivot basis variables swap kar sakta hai jabki znahi badalta (ek "stall"), aur rare cases mein method
ek basis par cycle back kar sakta hai jo woh pehle visit kar chuka hai, kabhi terminate nahi karta. Fixes: Bland's rule
(smallest index wala variable choose karke ties break karo) termination guarantee karta hai. Geometrically vertex theek hai; bookkeeping ko bas ek anti-cycling tie-break chahiye.
Slack: x1−x2+s1=1. z-row hai (−1,−1); maano x2 enter karta hai. Sirf ek constraint row mein uska column entry hai −1 (negative). Ratio test sirf positive entries use karta hai — yahan koi nahi hai. Matlab: x2 badhne par, s1=1−x1+x2 bhi badhta hai, toh koi constraint kabhi x2 ko nahi rokti. Hum x2 (aur z) bina kisi limit ke badha sakte hain → LP unbounded hai, z→+∞.
Tableau mein signal: ek negative z-row entry jiske poore column mein koi positive entry nahi =
unbounded objective. (Figure dekho — feasible region upar hamesha ke liye khulti hai.)
≥ convert karo: x1+x2≥5⇒−(x1+x2)≤−5, jiska RHS −5<0 hai. Basic
starting solution x1=x2=0 slack =−5<0 deta hai → feasible nahi, toh origin ek valid
starting corner nahi hai; plain simplex ko b≥0 chahiye. Ek-line reason ki koi solution exist nahi karta: ek sum
dono≤2 aur ≥5 nahi ho sakta, toh feasible region empty hai (dono half-planes kabhi overlap nahi karte). Handle karne ke liye two-phase ya Big-M method chahiye jo pehle ek feasible corner dhoonde — jo yahan infeasibility report karta hai.
Entering variable woh hota hai jiska z-row coefficient most negative ho.
Leaving variable smallest positive ratio RHS ÷ column entry se choose hota hai.
Hum tab rukते hain jab har z-row coefficient ==≥0 ho.
Ratio-test column jisme no positive entries hon woh unbounded objective signal karta hai.
Ratio test mein tie ek degenerate== vertex signal karta hai aur cycling ka risk hota hai.