Q7 — Automated Planning Theory
GraphPlan's fine print: when two orderings are twins, exactly which precondition/effect overlaps make actions mutex, and the monotonicity of NON-mutex.
The Question
Answer the given subquestions.
| # | Question | Official answer |
|---|---|---|
| 7.1 | Consider actions a and b and the two orderings (a then b) and (b then a). Which of the following conditions (each taken independently) will make both of the ... | A, B |
| 7.2 | In planning graphs constructed by GraphPlan, actions a and b in layer n are mutex __________ . | A, B |
| 7.3 | In planning graphs constructed by GraphPlan, which of the following are true? | A, B |
The Topic in 60 Seconds
| Concept | Test |
|---|---|
| Interchangeable orderings | neither action deletes a precondition or effect of the other, and their preconditions are jointly satisfiable |
| Action mutex (layer ) | inconsistent effects: some add of one is deleted by the other; OR interference: one deletes a precondition/effect of the other; OR competing needs: some , are proposition-mutex in layer |
| Non-mutex monotonicity | once two propositions co-exist in one layer, they co-exist in every later layer |
Deep-dive: browse the Concepts section for GraphPlan.
Solutions
7.1 — Both orderings feasible → A, B
and succeed identically exactly when the actions do not step on each other:
- No interference: deletes nothing that needs as precondition or brings as effect — and symmetrically for against .
- Jointly satisfiable preconditions: running second leaves enough of the state intact for the other's PRE list.
Any condition asserting "a must delete something of b" or demanding exclusive resources kills one of the two orders → wrong by construction.
7.2 — Action mutex definition → A, B
| Option | Reading | Verdict |
|---|---|---|
| A | , are mutex in layer | Correct — textbook competing needs |
| B | is in , in , in and in | Correct — each action needs what both destroy (inconsistent supports); they cannot co-exist |
| C | only if EVERY precondition of is deleted by | Far too strong — ONE overlapping deletion suffices ("only if" poisons it) |
| D | only if every add-effect of is deleted by | Same disease |
7.3 — Non-mutex monotonicity → A, B
GraphPlan's persistence semantics: if and genuinely hold together in some layer (non-mutex), the no-op edges carry both forward forever — co-existence never regresses:
- A ✓: non-mutex at layer 0 (the initial state) persists through all layers.
- B ✓: non-mutex at any layer persists to all future layers.
- C ✗: claims future mutex-ification — contradicts monotonicity; mutex sets can SHRINK going up, never the non-mutex relation.
The asymmetry to memorise: mutex-ness is proved fresh each layer (may disappear); non-mutex-ness, once established, is forever.
Tricks & Tips
Answers: 7.1 A, B · 7.2 A, B · 7.3 A, B